panic mount root failed
Env: Yesterday I went to a friends house for installing a box from the freebsd 3.0-release cdrom (I have also the src and obj very current on another cd to do a quick make installword :-). He has : 1 hd master (A) + 1 cdrom slave on primary ch. 1 hd master (B) + 1 zip atapi slave on secundary ch. on (A) there is a primary win98 partition. on (B) there is a fat partition on wd2s1 and a freebsd installation on wd2s2a. The installation procedure was fine, but at the next reboot it can't mount the root fs because it tries to mount / on wd1s2a even if in /etc/fstab there is wd2s2a ! I think it is a problem related to the fact that the cdrom make confusion on the routine that have to find the hd slice number... everything was fine after adding a boot config with 1:wd(2,a)kernel Is it a known problem or I miss something ? Best Regards, Gianmarco Giovannelli , Unix expert since yesterday http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic mount root failed
:Env: : :Yesterday I went to a friends house for installing a box from the freebsd :3.0-release cdrom (I have also the src and obj very current on another cd :to do a quick make installword :-). : :He has : :1 hd master (A) + 1 cdrom slave on primary ch. :1 hd master (B) + 1 zip atapi slave on secundary ch. : :on (A) there is a primary win98 partition. on (B) there is a fat partition :on wd2s1 and a freebsd installation on wd2s2a. : :The installation procedure was fine, but at the next reboot it can't mount :the root fs because it tries to mount / on wd1s2a even if in /etc/fstab :there is wd2s2a ! I think it is a problem related to the fact that the :cdrom make confusion on the routine that have to find the hd slice number... : :everything was fine after adding a boot config with 1:wd(2,a)kernel : :Is it a known problem or I miss something ? : :Best Regards, :Gianmarco Giovannelli , Unix expert since yesterday :http://www.giovannelli.it/~gmarco :http://www2.masternet.it Look at the disklabel for wd2s2. If the 'disk:' field in the label says wd1 that may be your problem. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic mount root failed
At 17.49 17/02/99 -0800, you wrote: :everything was fine after adding a boot config with 1:wd(2,a)kernel Look at the disklabel for wd2s2. If the 'disk:' field in the label says wd1 that may be your problem. I think is our installer that have some problems :-) Btw I'll check it, but also is to investigate if it's true why installer put it there :-) Thanks for your kind reply Best Regards, Gianmarco Giovannelli , Unix expert since yesterday http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic mount root failed
:Env: : :Yesterday I went to a friends house for installing a box from the freebsd :3.0-release cdrom (I have also the src and obj very current on another cd :to do a quick make installword :-). : :He has : :1 hd master (A) + 1 cdrom slave on primary ch. :1 hd master (B) + 1 zip atapi slave on secundary ch. : :on (A) there is a primary win98 partition. on (B) there is a fat partition :on wd2s1 and a freebsd installation on wd2s2a. : :The installation procedure was fine, but at the next reboot it can't mount :the root fs because it tries to mount / on wd1s2a even if in /etc/fstab :there is wd2s2a ! I think it is a problem related to the fact that the :cdrom make confusion on the routine that have to find the hd slice number... : :everything was fine after adding a boot config with 1:wd(2,a)kernel : :Is it a known problem or I miss something ? : Look at the disklabel for wd2s2. If the 'disk:' field in the label says wd1 that may be your problem. It's amazing how many folk remedies people come up with for this one, regardless of the number of times it's solved correctly. So, for everyone bothering to read this, here it is again: You have two IDE disks, wd0 and wd2. You have two BIOS disk devices, 0x80 and 0x81. FreeBSD can't tell that the disk you're booting from (0x81) is actually wd2 without some help. For 3.0 and earlier systems, you would use 1:wd(2,a)kernel at the boot: prompt. For 3.1 and later systems, use: set root_disk_unit=2 at the loader prompt. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
