|
FreeBSD Installation and Upgrading Installing and upgrading FreeBSD. |
|
Thread Tools | Display Modes |
|
|||
mountroot prompt after update
I have FreeBSD9-CURRENT_amd64 installed on ZFS only.
Just updated src and rebuilt world and kernel. Now I cannot make installworld because system failed to mount zroot after first reboot. /boot/loader.conf and /etc/fstab look unchanged, fstab has no mount point for zfs. AHCI mode in BIOS is unchanged. Everything looks the same as before the update. I tried to boot from /boot/kernel.old/ and even /boot/kernel.good/ with same drop to mountroot>. Of course I tried mountroot>zfs:zroot with all the kernels available and not luck at all. What could the reason? Is it possible to rescue the system? --------------------------------------------- FreeBSD 9-CURRENT_amd64, zfs v.4, zpool v.15. |
|
|||
It tries to mount zpool named zroot and exits with error 19.
There is only ZFS on the HDD. There is only swap line in /etc/fstab (plus proc and linproc lines). zroot in shown in /boot/loader.conf It shows a possibility like this: zfs:tank but panic occurs if enter zfs:zroot There is no zroot among valid devices (shown after ?). Panic also occurs if enter ada1p3, ada1p3a, /dev/ada1p3 ... Sometimes it gets frozen, sometimes reboot is possible. AHCI enabled long time ago and everything worked perfect for long time. The problem appeared right after src updating and rebuilding world and kernel. World is still old since I cannot mount the pool. |
|
||||
Hello,
the same problem was reported here by me- upgrade from 8.1 to 9.0, only new kernel was build and installed- nothing else touched. After upgrade I couldn't even boot ZFS from old 8.1 kernel. http://forums.freebsd.org/showthread.php?t=18179 Perhaps PR should be reported. Do you have much customized kernel config? D Pjoter. |
|
||||
Quote:
__________________
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. |
|
|||
I read that post and yes, it looks similar.
While customizing kernel config file (renamed /sys/amd64/conf/GENERIC) I only commented out "makeoptions DEBUG=-g" and all the "witness/malloc" options and removed all the drivers for hardware I don't have. I also limited a number of modules to build having in /etc/make.conf the line Code:
MODULES_OVERRIDE=acpi linux linprocfs sound/sound sound/driver/hda zfs opensolaris Having FreeBSD 8-STABLE on another HDD (ufs) I'm still trying to fix somehow my problem with ZFS. Indeed my lack of ZFS knowledge is bad helper On the other hand I did just nothing (except reading file UPDATING) before updating scr and rebuilding world and kernel. I used to have another problem with -CURRENT: after particular update I couldn't build any software at all only packages could be installed. I returned to previous snapshot and it worked fine. I tried several times with the same result. Some time passed and problem was gone: I guess developers eliminated it finally. I believe our current problem will disappear too after some time but it's really interesting what could be a reason? Looks like the update "renamed" partitions (changed IDs) that's why boot goes to mountroot and lack of knowledge of ZFS makes the situation fatal. |
|
||||
If you're not sure your kernel is fine, use a GENERIC kernel, or at the least build all the modules.
NOTES does not affect anything, it's another kernel config you can choose with KERNCONF= Quote:
CURRENT is intended mainly for developers, not the general public. For us mortals RELEASE or STABLE is recommended.
__________________
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. |
|
|||
True.
But I used to manage -current since 8 and I'm really happy with it. It's easy right now to just reinstall everything and be happy (?) but I'm trying to learn out of problem ... I have 9-current on ufs on another machine and I'm able to track it successfully (having issues too). This problem is about my poor knowledge of ZFS... but, look, nobody knows too! The worse thing now is that I cannot wait for newer src and try again: "access denied" |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Color Prompt in OpenBSD. | tetrodozombie | Guides | 18 | 13th April 2013 02:02 PM |
ZFS: how to mountroot or rescue? | zeiz | FreeBSD General | 1 | 20th December 2009 12:22 AM |
Nicer Prompt with ksh on 5.0 | nihonto | NetBSD Installation and Upgrading | 8 | 12th October 2009 08:49 PM |
Exec command in zsh prompt? | bsddaemon | General software and network | 2 | 18th October 2008 09:37 PM |
what to do at mountroot prompt? | Sunsawe | FreeBSD General | 13 | 5th June 2008 08:06 AM |