mountroot
I'm a little desperade. I installed a mirrored ZFS freebsd system in a VM the other day and all went well. Now I did the same procedure on a real systrem with two drives and I can't get the system to boot properly. Everytime it halts at the mountroot prompt. If I manually put zfs:zroot at the prompt the system boots to the login screen. I checked the /etc/rc.conf and the /boot/loader.conf for syntax errors but all seems well. What on earth can be the cause of this behaviour? What do I check? Help? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mountroot
On Wed, 29 Jun 2011 20:42+0200, Dick Hoogendijk wrote: I'm a little desperade. I installed a mirrored ZFS freebsd system in a VM the other day and all went well. Now I did the same procedure on a real systrem with two drives and I can't get the system to boot properly. Everytime it halts at the mountroot prompt. If I manually put zfs:zroot at the prompt the system boots to the login screen. I checked the /etc/rc.conf and the /boot/loader.conf for syntax errors but all seems well. What on earth can be the cause of this behaviour? What do I check? Help? Have you specified a bootfs? E.g.: zpool set bootfs=zroot zroot -- -- Trond Endrestøl | trond.endres...@fagskolen.gjovik.no ACM, NAS, NUUG, SAGE, USENIX |FreeBSD 8.2-STABLE Alpine 2.00___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mountroot
Op 29-6-2011 21:15, Trond Endrestøl schreef: On Wed, 29 Jun 2011 20:42+0200, Dick Hoogendijk wrote: I'm a little desperade. I installed a mirrored ZFS freebsd system in a VM the other day and all went well. Now I did the same procedure on a real systrem with two drives and I can't get the system to boot properly. Everytime it halts at the mountroot prompt. If I manually put zfs:zroot at the prompt the system boots to the login screen. I checked the /etc/rc.conf and the /boot/loader.conf for syntax errors but all seems well. What on earth can be the cause of this behaviour? What do I check? Help? Have you specified a bootfs? E.g.: zpool set bootfs=zroot zroot Yes, I did. And just did it again. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mountroot
On Wed, 29 Jun 2011 21:18+0200, Dick Hoogendijk wrote: Op 29-6-2011 21:15, Trond Endrestøl schreef: On Wed, 29 Jun 2011 20:42+0200, Dick Hoogendijk wrote: I'm a little desperade. I installed a mirrored ZFS freebsd system in a VM the other day and all went well. Now I did the same procedure on a real systrem with two drives and I can't get the system to boot properly. Everytime it halts at the mountroot prompt. If I manually put zfs:zroot at the prompt the system boots to the login screen. I checked the /etc/rc.conf and the /boot/loader.conf for syntax errors but all seems well. What on earth can be the cause of this behaviour? What do I check? Help? Have you specified a bootfs? E.g.: zpool set bootfs=zroot zroot Yes, I did. And just did it again. Please post your /boot/loader.conf. -- -- Trond Endrestøl | trond.endres...@fagskolen.gjovik.no ACM, NAS, NUUG, SAGE, USENIX |FreeBSD 8.2-STABLE Alpine 2.00___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mountroot
Op 29-6-2011 21:19, Trond Endrestøl schreef: On Wed, 29 Jun 2011 21:18+0200, Dick Hoogendijk wrote: Op 29-6-2011 21:15, Trond Endrestøl schreef: On Wed, 29 Jun 2011 20:42+0200, Dick Hoogendijk wrote: I'm a little desperade. I installed a mirrored ZFS freebsd system in a VM the other day and all went well. Now I did the same procedure on a real systrem with two drives and I can't get the system to boot properly. Everytime it halts at the mountroot prompt. If I manually put zfs:zroot at the prompt the system boots to the login screen. I checked the /etc/rc.conf and the /boot/loader.conf for syntax errors but all seems well. What on earth can be the cause of this behaviour? What do I check? Help? Have you specified a bootfs? E.g.: zpool set bootfs=zroot zroot Yes, I did. And just did it again. Please post your /boot/loader.conf. And did it again (zpool set bootfs=zroot zroot) ; rebooted and finally the system boots up. So, problem solved. Posts arfe being fetched. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mountroot
On Wed, 29 Jun 2011, Dick Hoogendijk wrote: Op 29-6-2011 21:19, Trond Endrestøl schreef: On Wed, 29 Jun 2011 21:18+0200, Dick Hoogendijk wrote: Op 29-6-2011 21:15, Trond Endrestøl schreef: On Wed, 29 Jun 2011 20:42+0200, Dick Hoogendijk wrote: I'm a little desperade. I installed a mirrored ZFS freebsd system in a VM the other day and all went well. Now I did the same procedure on a real systrem with two drives and I can't get the system to boot properly. Everytime it halts at the mountroot prompt. If I manually put zfs:zroot at the prompt the system boots to the login screen. I checked the /etc/rc.conf and the /boot/loader.conf for syntax errors but all seems well. What on earth can be the cause of this behaviour? What do I check? Help? Have you specified a bootfs? E.g.: zpool set bootfs=zroot zroot Yes, I did. And just did it again. Please post your /boot/loader.conf. And did it again (zpool set bootfs=zroot zroot) ; rebooted and finally the system boots up. So, problem solved. Posts arfe being fetched. Thanks. If it's a timeout problem, there's kern.cam.boot_delay=1.___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mountroot
2011/6/29 Warren Block wbl...@wonkity.com On Wed, 29 Jun 2011, Dick Hoogendijk wrote: Op 29-6-2011 21:19, Trond Endrestøl schreef: On Wed, 29 Jun 2011 21:18+0200, Dick Hoogendijk wrote: Op 29-6-2011 21:15, Trond Endrestøl schreef: On Wed, 29 Jun 2011 20:42+0200, Dick Hoogendijk wrote: I'm a little desperade. I installed a mirrored ZFS freebsd system in a VM the other day and all went well. Now I did the same procedure on a real systrem with two drives and I can't get the system to boot properly. Everytime it halts at the mountroot prompt. If I manually put zfs:zroot at the prompt the system boots to the login screen. I checked the /etc/rc.conf and the /boot/loader.conf for syntax errors but all seems well. What on earth can be the cause of this behaviour? What do I check? Help? Have you specified a bootfs? E.g.: zpool set bootfs=zroot zroot Yes, I did. And just did it again. Please post your /boot/loader.conf. And did it again (zpool set bootfs=zroot zroot) ; rebooted and finally the system boots up. So, problem solved. Posts arfe being fetched. Thanks. If it's a timeout problem, there's kern.cam.boot_delay=1. +1 for kern.cam.boot_delay=1. I had the same problem and that setting fixed it for me. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FBSD 8: custom kernel config ends boot at mountroot. Plz. help!
Hi, My system boots fine with the GENERIC kernel on FreeBSD 8.0 I made a custom kernel, but the boot process then ends with the mountroot error and prompt. Apparently something is wrong with my kernel config file. Can somebody check it below and tell me what is wrong with my kernel config file? Especially the GEOM_PART_* at the end might be the culprit, although this configuration used to work for 7.3. Thank you! Rob. # My kernel config file: cpuI686_CPU identMYKERNEL options SCHED_ULE# ULE scheduler options PREEMPTION# Enable kernel thread preemption options INET# InterNETworking options INET6# IPv6 communications protocols options SCTP# Stream Control Transmission Protocol options FFS# Berkeley Fast Filesystem options SOFTUPDATES# Enable FFS soft updates support options UFS_ACL# Support for access control lists options UFS_DIRHASH# Improve performance on big directories options COMPAT_FREEBSD7# Compatible with FreeBSD7 options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev devicepci deviceata deviceatadisk# ATA disk drives options ATA_STATIC_ID# Static device numbering devicescbus# SCSI bus (required for SCSI) deviceda# Direct Access (disks) devicepass# Passthrough device (direct SCSI access) deviceatkbdc# AT keyboard controller deviceatkbd# AT keyboard devicepsm# PS/2 mouse devicevga# VGA video card driver devicesplash# Splash screen and screen saver support devicesc devicepmtimer deviceloop# Network loopback deviceether# Ethernet support devicepty# BSD-style compatibility pseudo ttys devicemd# Memory disks devicebpf# Berkeley packet filter options SC_DISABLE_REBOOT options DEVICE_POLLING options HZ=1000 nodevice mem nodevice io nodevice uart_ns8250 nooptions GEOM_PART_BSD nooptions GEOM_PART_EBR nooptions GEOM_PART_EBR_COMPAT nooptions GEOM_PART_MBR ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FBSD 8: custom kernel config ends boot at mountroot. Plz. help!
Rob spamref...@yahoo.com wrote: My system boots fine with the GENERIC kernel on FreeBSD 8.0 I made a custom kernel, but the boot process then ends with the mountroot error and prompt. One thing to try is entering ? there, to produce a list of recognized filesystems. Comparing that list with what you expected might provide a clue. Another possibility would be to compare the dmesg from your kernel with the one from GENERIC. Apparently something is wrong with my kernel config file. Can somebody check it below and tell me what is wrong with my kernel config file? Especially the GEOM_PART_* at the end might be the culprit, although this configuration used to work for 7.3. Supposing the disk is partitioned with GPT (not with MBR/BSD, which you appear to be excluding) I see nothing blatantly obvious, but I am far from an expert in such matters. It might be worthwhile to check UPDATING to see if anything rings a bell, and/or compare your config file with the GENERIC one. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FBSD 8: custom kernel config ends boot at mountroot. Plz. help!
On Sun, Dec 19, 2010 at 05:11:58AM -0800, Rob wrote: Hi, My system boots fine with the GENERIC kernel on FreeBSD 8.0 I made a custom kernel, but the boot process then ends with the mountroot error and prompt. Apparently something is wrong with my kernel config file. Can somebody check it below and tell me what is wrong with my kernel config file? Especially the GEOM_PART_* at the end might be the culprit, although this configuration used to work for 7.3. Thank you! Rob. # My kernel config file: cpuI686_CPU identMYKERNEL options SCHED_ULE# ULE scheduler options PREEMPTION# Enable kernel thread preemption options INET# InterNETworking options INET6# IPv6 communications protocols options SCTP# Stream Control Transmission Protocol options FFS# Berkeley Fast Filesystem options SOFTUPDATES# Enable FFS soft updates support options UFS_ACL# Support for access control lists options UFS_DIRHASH# Improve performance on big directories options COMPAT_FREEBSD7# Compatible with FreeBSD7 options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev devicepci deviceata deviceatadisk# ATA disk drives options ATA_STATIC_ID# Static device numbering devicescbus# SCSI bus (required for SCSI) deviceda# Direct Access (disks) devicepass# Passthrough device (direct SCSI access) deviceatkbdc# AT keyboard controller deviceatkbd# AT keyboard devicepsm# PS/2 mouse devicevga# VGA video card driver devicesplash# Splash screen and screen saver support devicesc devicepmtimer deviceloop# Network loopback deviceether# Ethernet support devicepty# BSD-style compatibility pseudo ttys devicemd# Memory disks devicebpf# Berkeley packet filter options SC_DISABLE_REBOOT options DEVICE_POLLING options HZ=1000 nodevice mem nodevice io nodevice uart_ns8250 nooptions GEOM_PART_BSD nooptions GEOM_PART_EBR nooptions GEOM_PART_EBR_COMPAT nooptions GEOM_PART_MBR Rob, If you're going to use a custom kernel, copy GENERIC, edit it and save it as your kernel conf. Then when you run into trouble with your custom kernel you can post a diff(1) between it and GENERIC. Then it's easy to see what you've enabled/disabled, left-out etc. As it stands, it takes too much time for people to compare your custom kernel with GENERIC. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FBSD 8: custom kernel config ends boot at mountroot. Plz. help!
On Mon, 20 Dec 2010, Frank Shute wrote: If you're going to use a custom kernel, copy GENERIC, edit it and save it as your kernel conf. Then when you run into trouble with your custom kernel you can post a diff(1) between it and GENERIC. Then it's easy to see what you've enabled/disabled, left-out etc. Another option is to include GENERIC in the new config file and use nooptions and nodevice to exclude unwanted things. Then the config file is a diff. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mountroot prompt in the middle of updating - can't get past it
On Thu, 9 Dec 2010 11:38:29 -0800 Kurt Buff wrote: On Wed, Dec 8, 2010 at 22:50, Boris Samorodov b...@ipt.ru wrote: On Wed, 8 Dec 2010 11:49:41 -0800 Kurt Buff wrote: All, I have a Lenovo T61 with a 100g HD that I dual boot with FreeBSD 8.0-STABLE amd64 and Windows XP. How and to which version did you upgrade? FBSD is on ad0s2a, with ad0s2b as swap, and XP on ad0s1a. Yesterday I booted up FBSD, started xfce4, started a terminal session, su'ed to root and did the following - running a generic kernel: # cd /usr/src # make buildworld # make buildkernel # make installkernel Then I exited xfce4, did sudo shutdown -r now, and got a mountroot prompt that I now can't get past. I can get to the loader prompt, and lsdev shows the following: cd devices: disk devices: disk0: BIOS drive C: disk0s1: NTFS/HPFS disk0s2a: FFS disk02sb: swap Is it a typo? (seems should be disk0s2b: swap when I use '?' at the mountroot prompt I get: List of GEOM managed disk devices: acd0 Hm, ad0s2a should be listed here. Seems that the new kernel doesn't detect a disk adapter. Your kernel config and may be helpful. BTW, dmesg for both successful and unsuccessful boot may give us some tips too. Loader variables: vfs.root.mountfrom=ufs:/dev/ad0s2a vfs.root.mountfrom.options=rw I've tried entering the following at the mountroot prompt, with no success: ufs:/dev/ad0s2a That is the right one. ufs:/ad0s2a ufs:ad0s2a ffs:/dev/ad0s2a and several other variations that I've found while googling, but no success anywhere. Does anyone have thoughts on how to remedy this? Just for the last question: Try to load an old kernel. (Type boot /boot/kernel.old at loader prompt.) That worked... I think I'll try the update process again. Anything else you can recommend? -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mountroot prompt in the middle of updating - can't get past it
On Wed, Dec 8, 2010 at 22:50, Boris Samorodov b...@ipt.ru wrote: On Wed, 8 Dec 2010 11:49:41 -0800 Kurt Buff wrote: All, I have a Lenovo T61 with a 100g HD that I dual boot with FreeBSD 8.0-STABLE amd64 and Windows XP. FBSD is on ad0s2a, with ad0s2b as swap, and XP on ad0s1a. Yesterday I booted up FBSD, started xfce4, started a terminal session, su'ed to root and did the following - running a generic kernel: # cd /usr/src # make buildworld # make buildkernel # make installkernel Then I exited xfce4, did sudo shutdown -r now, and got a mountroot prompt that I now can't get past. I can get to the loader prompt, and lsdev shows the following: cd devices: disk devices: disk0: BIOS drive C: disk0s1: NTFS/HPFS disk0s2a: FFS disk02sb: swap when I use '?' at the mountroot prompt I get: List of GEOM managed disk devices: acd0 Loader variables: vfs.root.mountfrom=ufs:/dev/ad0s2a vfs.root.mountfrom.options=rw I've tried entering the following at the mountroot prompt, with no success: ufs:/dev/ad0s2a ufs:/ad0s2a ufs:ad0s2a ffs:/dev/ad0s2a and several other variations that I've found while googling, but no success anywhere. Does anyone have thoughts on how to remedy this? Just for the last question: Try to load an old kernel. (Type boot /boot/kernel.old at loader prompt.) That worked... I think I'll try the update process again. Anything else you can recommend? Thanks, Kurt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mountroot prompt in the middle of updating - can't get past it
On Thu, Dec 9, 2010 at 2:38 PM, Kurt Buff kurt.b...@gmail.com wrote: That worked... I think I'll try the update process again. Anything else you can recommend? Thanks, Did you read /usr/src/UPDATING ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mountroot prompt in the middle of updating - can't get past it
On Thu, Dec 9, 2010 at 12:50, Chris Brennan xa...@xaerolimit.net wrote: On Thu, Dec 9, 2010 at 2:38 PM, Kurt Buff kurt.b...@gmail.com wrote: That worked... I think I'll try the update process again. Anything else you can recommend? Thanks, Did you read /usr/src/UPDATING ? Why, yes I did. Didn't see anything in there that looked like it might cause this problem, though. Kurt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
mountroot prompt in the middle of updating - can't get past it
All, I have a Lenovo T61 with a 100g HD that I dual boot with FreeBSD 8.0-STABLE amd64 and Windows XP. FBSD is on ad0s2a, with ad0s2b as swap, and XP on ad0s1a. Yesterday I booted up FBSD, started xfce4, started a terminal session, su'ed to root and did the following - running a generic kernel: # cd /usr/src # make buildworld # make buildkernel # make installkernel Then I exited xfce4, did sudo shutdown -r now, and got a mountroot prompt that I now can't get past. I can get to the loader prompt, and lsdev shows the following: cd devices: disk devices: disk0: BIOS drive C: disk0s1: NTFS/HPFS disk0s2a: FFS disk02sb: swap when I use '?' at the mountroot prompt I get: List of GEOM managed disk devices: acd0 Loader variables: vfs.root.mountfrom=ufs:/dev/ad0s2a vfs.root.mountfrom.options=rw I've tried entering the following at the mountroot prompt, with no success: ufs:/dev/ad0s2a ufs:/ad0s2a ufs:ad0s2a ffs:/dev/ad0s2a and several other variations that I've found while googling, but no success anywhere. Does anyone have thoughts on how to remedy this? Thanks, Kurt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mountroot prompt in the middle of updating - can't get past it
On Wed, 8 Dec 2010 11:49:41 -0800 Kurt Buff wrote: All, I have a Lenovo T61 with a 100g HD that I dual boot with FreeBSD 8.0-STABLE amd64 and Windows XP. FBSD is on ad0s2a, with ad0s2b as swap, and XP on ad0s1a. Yesterday I booted up FBSD, started xfce4, started a terminal session, su'ed to root and did the following - running a generic kernel: # cd /usr/src # make buildworld # make buildkernel # make installkernel Then I exited xfce4, did sudo shutdown -r now, and got a mountroot prompt that I now can't get past. I can get to the loader prompt, and lsdev shows the following: cd devices: disk devices: disk0: BIOS drive C: disk0s1: NTFS/HPFS disk0s2a: FFS disk02sb: swap when I use '?' at the mountroot prompt I get: List of GEOM managed disk devices: acd0 Loader variables: vfs.root.mountfrom=ufs:/dev/ad0s2a vfs.root.mountfrom.options=rw I've tried entering the following at the mountroot prompt, with no success: ufs:/dev/ad0s2a ufs:/ad0s2a ufs:ad0s2a ffs:/dev/ad0s2a and several other variations that I've found while googling, but no success anywhere. Does anyone have thoughts on how to remedy this? Just for the last question: Try to load an old kernel. (Type boot /boot/kernel.old at loader prompt.) -- WBR, bsam ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
GPT/ZFS/USB mountroot prompt
I followed a gpt/zfs on USB stick guide for putting a base 8.1-RELEASE amd64 onto a 4GB sandisk USB memory stick. All went fairly well and the system will boot but fails to mount the root file system and dumps me a the mountroot prompt. Entering zfs:zrootusb at the prompt works and the system finishes booting. In /boot/loader.conf I've got: zfs_load=YES vfs.root.mountfrom=zfs:zrootusb zrootusb mountpoint is set to legacy and /etc/fstab exists but is empty, per the guide. Any ideas? Thanks, Carl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: GPT/ZFS/USB mountroot prompt
On Wed, Dec 1, 2010 at 12:07 AM, Carl Chave c...@chave.us wrote: I followed a gpt/zfs on USB stick guide for putting a base 8.1-RELEASE amd64 onto a 4GB sandisk USB memory stick. All went fairly well and the system will boot but fails to mount the root file system and dumps me a the mountroot prompt. Entering zfs:zrootusb at the prompt works and the system finishes booting. In /boot/loader.conf I've got: zfs_load=YES vfs.root.mountfrom=zfs:zrootusb zrootusb mountpoint is set to legacy and /etc/fstab exists but is empty, per the guide. Any ideas? Thanks, Carl adding kern.cam.boot_delay=1 to /boot/loader.conf seems to have fixed it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
mountroot error with memory based rootfs
Hi, I was trying to build root filesystem in to the kernel (i.e using /dev/md0) for Mips based target boards. In the process i built tool chain and kernel successfully. But when i boot the kernel on the target, it fails to mount the md0 and drops to mountroot prompt. mountroot ufs:/dev/md0 ROOT MOUNT ERROR If you have invalid mount options, reboot, and first try the following from the loader prompt: set vfs.root.mountfrom.options=rw and the remove invalid mount options from /etc/fstab. Loader variables: vfs.root.mountfrom= vfs.root.mountform.options= I could see that both the above variables are unset and not sure whether this is by default. As i am building a cross kernel, i can't add these options to /boot/loader.conf files which applies to current host machine. Please help me where the above settings need to be added i.e which directory and file for the settings to effect for my target kernel build. Thanks, Akash. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mountroot error with memory based rootfs
Hi, The root file system was built commenting out compact flash and enabling md0 as below in the config file for my target arch. #device cf #optionsROOTDEVNAME=\ufs:cf0s1\ # Use the following for RFS in mem-device options MD_ROOT options ROOTDEVNAME = \ufs:md0\ options MD_ROOT_SIZE = 7264 After the kernel was built and installed using 'make buildkernel KERNCONF=configfile and make installkernel commands. Please let me know if you need any more info. Thanks, Bhanu Prakash. From: Tim Judd taj...@gmail.com To: akash kumar akashb...@yahoo.co.in Sent: Fri, 18 June, 2010 7:50:14 AM Subject: Re: mountroot error with memory based rootfs On 6/17/10, akash kumar akashb...@yahoo.co.in wrote: Hi, I was trying to build root filesystem in to the kernel (i.e using /dev/md0) for Mips based target boards. In the process i built tool chain and kernel successfully. But when i boot the kernel on the target, it fails to mount the md0 and drops to mountroot prompt. mountroot ufs:/dev/md0 ROOT MOUNT ERROR If you have invalid mount options, reboot, and first try the following from the loader prompt: set vfs.root.mountfrom.options=rw and the remove invalid mount options from /etc/fstab. Loader variables: vfs.root.mountfrom= vfs.root.mountform.options= I could see that both the above variables are unset and not sure whether this is by default. As i am building a cross kernel, i can't add these options to /boot/loader.conf files which applies to current host machine. Please help me where the above settings need to be added i.e which directory and file for the settings to effect for my target kernel build. Thanks, Akash. Please give details on how the root filesystem image is built. What works is to format the rootfs image without a partition or bsdlabel. It is just unable to mount the image as specified. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Disk can't be found, boot stops at mountroot
On Tue, 11 May 2010 21:46:35 +0200 Leslie Jensen wrote: System 7.2-RELEASE I made the first reboot after freebsd-update -r 8.0-RELEASE freebsd-update install and I'm now stuck at the mountroot prompt that says trying to mount from ufs:/dev/ad0s1a ROOT MOUNT ERROR The command ? to list valid boot devices gives List of GEOM managed disk devices: cd0 ufsid/452b81499eec5ac8 ad0a acd0 ad0 fd0 Seems that your system is using a so-called dengerously dedicated disk (mind ad0a). I've tried ufs:/dev/da0s1a and ufs:/dev/ad0s1a Try ufs:/dev/ad0a With no luck Any suggestions on how to get booted? -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [#24493341] Disk can't be found, boot stops at mountroot
Hi, Please let us know if there is anything which we can assist you with, thanks. -- Best Regards Ramon Server engineer Hosting Services, Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Disk can't be found, boot stops at mountroot
System 7.2-RELEASE I made the first reboot after freebsd-update -r 8.0-RELEASE freebsd-update install and I'm now stuck at the mountroot prompt that says trying to mount from ufs:/dev/ad0s1a ROOT MOUNT ERROR The command ? to list valid boot devices gives List of GEOM managed disk devices: cd0 ufsid/452b81499eec5ac8 ad0a acd0 ad0 fd0 I've tried ufs:/dev/da0s1a and ufs:/dev/ad0s1a With no luck Any suggestions on how to get booted? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Disk can't be found, boot stops at mountroot
On Tue, May 11, 2010 at 2:46 PM, Leslie Jensen les...@eskk.nu wrote: System 7.2-RELEASE I made the first reboot after freebsd-update -r 8.0-RELEASE freebsd-update install and I'm now stuck at the mountroot prompt that says trying to mount from ufs:/dev/ad0s1a ROOT MOUNT ERROR The command ? to list valid boot devices gives List of GEOM managed disk devices: cd0 ufsid/452b81499eec5ac8 ad0a acd0 ad0 fd0 I've tried ufs:/dev/da0s1a and ufs:/dev/ad0s1a With no luck Any suggestions on how to get booted? If you boot off a 7.2 cd, can you see the proper partitions? What are they? -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Disk can't be found, boot stops at mountroot
On 2010-05-12 00:06, Adam Vande More wrote: On Tue, May 11, 2010 at 2:46 PM, Leslie Jensen les...@eskk.nu mailto:les...@eskk.nu wrote: System 7.2-RELEASE I made the first reboot after freebsd-update -r 8.0-RELEASE freebsd-update install and I'm now stuck at the mountroot prompt that says trying to mount from ufs:/dev/ad0s1a ROOT MOUNT ERROR The command ? to list valid boot devices gives List of GEOM managed disk devices: cd0 ufsid/452b81499eec5ac8 ad0a acd0 ad0 fd0 I've tried ufs:/dev/da0s1a and ufs:/dev/ad0s1a With no luck Any suggestions on how to get booted? If you boot off a 7.2 cd, can you see the proper partitions? What are they? -- Adam Vande More I used a 8.0 livefs CD and all I could find was ad0 and ad0a. Using sysinstall fdisk showed an empty disk! So I think I have some kind of hardware failure :-( /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Disk can't be found, boot stops at mountroot
On Tue, May 11, 2010 at 5:38 PM, Leslie Jensen les...@eskk.nu wrote: On 2010-05-12 00:06, Adam Vande More wrote: On Tue, May 11, 2010 at 2:46 PM, Leslie Jensen les...@eskk.nu mailto:les...@eskk.nu wrote: System 7.2-RELEASE I made the first reboot after freebsd-update -r 8.0-RELEASE freebsd-update install and I'm now stuck at the mountroot prompt that says trying to mount from ufs:/dev/ad0s1a ROOT MOUNT ERROR The command ? to list valid boot devices gives List of GEOM managed disk devices: cd0 ufsid/452b81499eec5ac8 ad0a acd0 ad0 fd0 I've tried ufs:/dev/da0s1a and ufs:/dev/ad0s1a With no luck Any suggestions on how to get booted? If you boot off a 7.2 cd, can you see the proper partitions? What are they? -- Adam Vande More I used a 8.0 livefs CD and all I could find was ad0 and ad0a. Using sysinstall fdisk showed an empty disk! **If you boot off a 7.2 cd** So I think I have some kind of hardware failure :-( /Leslie -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can't mountroot from ZFS pool
krad wrote: 2010/1/11 Steve Bertrand st...@ibctech.ca mailto:st...@ibctech.ca All, I've successfully upgraded the disks in my ZFS backup server, and can import/mount the pool properly. However, I designed this box originally so that it mounts / from zfs:storage after booting from a USB stick. After the upgrade of the disks, I'm stuck at a mountroot prompt when I attempt to boot the system with the original USB /boot key. Can someone inform me how to find the / filesystem at the mountroot prompt? If not, is there *any* way to boot the system normally from another medium, and then 'reload' the system with the ZFS / after its been mounted so that the system functions as designed (ie. cron works etc)? did you export the pool at all before rebooting it? Yes, I did. I just finally got it resolved :) It appears as though by importing the zpool onto another system obsoleted the cache file on the original USB /boot disk. I exported, then imported the pool on the secondary system, then copied the cache file into the /boot/zfs directory on my original boot medium. Things are now working again, and I have all of my new storage and original data in place! Thanks for all the help! Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can't mountroot from ZFS pool
2010/1/19 Steve Bertrand st...@ibctech.ca krad wrote: 2010/1/11 Steve Bertrand st...@ibctech.ca mailto:st...@ibctech.ca All, I've successfully upgraded the disks in my ZFS backup server, and can import/mount the pool properly. However, I designed this box originally so that it mounts / from zfs:storage after booting from a USB stick. After the upgrade of the disks, I'm stuck at a mountroot prompt when I attempt to boot the system with the original USB /boot key. Can someone inform me how to find the / filesystem at the mountroot prompt? If not, is there *any* way to boot the system normally from another medium, and then 'reload' the system with the ZFS / after its been mounted so that the system functions as designed (ie. cron works etc)? did you export the pool at all before rebooting it? Yes, I did. I just finally got it resolved :) It appears as though by importing the zpool onto another system obsoleted the cache file on the original USB /boot disk. I exported, then imported the pool on the secondary system, then copied the cache file into the /boot/zfs directory on my original boot medium. Things are now working again, and I have all of my new storage and original data in place! Thanks for all the help! Steve Its an easy mistake to make. People think exporting a pool is the same as unmounting but it isn't really, and its kind of difficult to explain why (unless ur an uber guru) One thing for sure is that the hostid of the system is stored in to the zpool somewhere as is the state of it. This also has to match the zpool.cache files details. The reason for this is probably largely to do with sun clustering, where a pool on a particular lun may be visible to many nodes in the cluster, but only one having it currently imported and the subsequent file systems mounted. Hmm, why does it always sound so clunky when I try to explain it 8/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can't mountroot from ZFS pool
2010/1/11 Steve Bertrand st...@ibctech.ca All, I've successfully upgraded the disks in my ZFS backup server, and can import/mount the pool properly. However, I designed this box originally so that it mounts / from zfs:storage after booting from a USB stick. After the upgrade of the disks, I'm stuck at a mountroot prompt when I attempt to boot the system with the original USB /boot key. Can someone inform me how to find the / filesystem at the mountroot prompt? If not, is there *any* way to boot the system normally from another medium, and then 'reload' the system with the ZFS / after its been mounted so that the system functions as designed (ie. cron works etc)? Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org did you export the pool at all before rebooting it? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Can't mountroot from ZFS pool
All, I've successfully upgraded the disks in my ZFS backup server, and can import/mount the pool properly. However, I designed this box originally so that it mounts / from zfs:storage after booting from a USB stick. After the upgrade of the disks, I'm stuck at a mountroot prompt when I attempt to boot the system with the original USB /boot key. Can someone inform me how to find the / filesystem at the mountroot prompt? If not, is there *any* way to boot the system normally from another medium, and then 'reload' the system with the ZFS / after its been mounted so that the system functions as designed (ie. cron works etc)? Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
mountroot prompt after hint.apic.0.disabled=1
Don't know if that loader.conf change affected this server, I disabled APIC in loader.conf after finding it may be responsible for a slow clock on this VMware guest FreeBSD install. I rebooted for the changes to take affect and it goes now to a mountroot prompt, can't seem to load the root partition. I type ? at the prompt and it does not list anything after 'List of GEOM managed disk devices'. Can anyone suggest how I can fix this problem? Thanks, Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
mountroot prompt after hint.apic.0.disabled=1
Don't know if that loader.conf change affected this server, I disabled APIC in loader.conf after finding it may be responsible for a slow clock on this VMware guest FreeBSD install. I rebooted for the changes to take affect and it goes now to a mountroot prompt, can't seem to load the root partition. I type ? at the prompt and it does not list anything after 'List of GEOM managed disk devices'. Can anyone suggest how I can fix this problem? Thanks, Robert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: mountroot
Franco Vitali [EMAIL PROTECTED] writes: I'm using some old Pentium PCs, to install and test FreeBSD 6.2 Te problem I have is when I move the HD containing the OS to another machine, I'm prompted to specify the root partition. I've checked the /etc/fstab file and everything is ok. I modified /boot/loader.conf with: rootdev=ad0s1a and /dev/ad0s1a (the same in /etc/fstab) But I keep prompted to mount the root manually when the OS boots: Mounroot ufs:ad0s1a What can I do? The only solution I can think is to reinstall the system in the new machine, but for other reasons I need to keep the installed OS. There aren't any SCSI disks in this machine, are there? That can complicate things a bit. Have you tried setting root_disk_unit? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mountroot
Franco Vitali [EMAIL PROTECTED] writes: I'm using some old Pentium PCs, to install and test FreeBSD 6.2 Te problem I have is when I move the HD containing the OS to another machine, I'm prompted to specify the root partition. I've checked the /etc/fstab file and everything is ok. I modified /boot/loader.conf with: rootdev=ad0s1a and /dev/ad0s1a (the same in /etc/fstab) But I keep prompted to mount the root manually when the OS boots: Mounroot ufs:ad0s1a Could this be a problem with the BIOS in the new machine? Many BIOS's will allow you to set the boot order for disks/CDs/floppies but will only remember a setting if that bit of hardware is actually present in the machine. If you ever booted the new machine with no disk in the same place as ad0s1a then maybe that disk is no longer available as a boot device when FreeBSD tries to boot. Check that the BIOS in the new machine has this disk (controller?) set somewhere in the boot order. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mountroot
I'm using some old Pentium PCs, to install and test FreeBSD 6.2 Te problem I have is when I move the HD containing the OS to another machine, I'm prompted to specify the root partition. I've checked the /etc/fstab file and everything is ok. I modified /boot/loader.conf with: rootdev=ad0s1a and /dev/ad0s1a (the same in /etc/fstab) But I keep prompted to mount the root manually when the OS boots: Mounroot ufs:ad0s1a What can I do? The only solution I can think is to reinstall the system in the new machine, but for other reasons I need to keep the installed OS. Thanks in advance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 hangs at mountroot during bootup
Hi, This has just occurred to one of our servers that installed and has been working fine for months. The only thing that changed between it booting and not booting was that we unplugged the keyboard and mouse prior to the last successful boot and now get the mountroot message (even though the keyboard and mouse are now plugged back in). Does 6.1 assume that it should become a serial console controlled server automatically if no KB/ mouse is attached and then alter some configuration setting? (I'm guessing). Regards, James -- [EMAIL PROTECTED] SDF-EU Public Access UNIX System - http://sdf-eu.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mountroot
Hello, I`m trying to boot my freebsd 5.5 system and i`m having some trouble. Every time the machine boots it runs into the mountroot prompt. It cannot find the rootvp file on the /dev/ad0s1a. Everytime i try to mount the /dev/ad0s1a it gives me the mountroot prompt again. also i tryed to type ufs:/dev/ad0s1a but nothing happens. i presume the ad0s1a is my harddisk, i find it strange it will not mount. The computer finds the hard drive at boot time so what`s the problem. Thanks in advance, Justin. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mountroot
On Sunday, 5 November 2006 at 21:10:25 -, justin wrote: Hello, I`m trying to boot my freebsd 5.5 system and i`m having some trouble. Every time the machine boots it runs into the mountroot prompt. It cannot find the rootvp file on the /dev/ad0s1a. Everytime i try to mount the /dev/ad0s1a it gives me the mountroot prompt again. also i tryed to type ufs:/dev/ad0s1a but nothing happens. i presume the ad0s1a is my harddisk, i find it strange it will not mount. The computer finds the hard drive at boot time so what`s the problem. The first problem is that you haven't given any details. What partition layout do you have? Have you ever been able to boot from this machine? What's in /etc/fstab? If this is a fresh install, I'd suggest moving to 6.1, or waiting a couple of days for 6.2. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgpeeq0w61sz9.pgp Description: PGP signature
Re: FreeBSD 6.1 hangs at mountroot during bootup
I have seen this in a few situations: 1.) the BIOS is set to not allow boot area writes 2.) The root partition is outside the first 1024 cylinders. This was on older hardware that didn't do good geometry translation on big drives. 3.) moved the root partition to another slice -Derek At 06:47 PM 9/20/2006, Mike Peirson wrote: Hi all, First off, I'm new to FreeBSD and this mailinglist so I hope I am in the right place. Anyways, right now I am having some problems with FreeBSD booting up. I have tried to install 3 times now and keep getting the same error. When I try to boot into FreeBSD, this eventually comes up: Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line abort manual input Mountroot This seems to be a prompt where I need to specify the location of the root partition, but the problem here is that it hangs or freezes and I cannot input any text. At first I thought it may be a result of FreeBSD not properly recognizing my HDD's geometry but I manually fixed that and it still is giving me this same issue. If anyone has had a similar problem or knows how to fix this I would greatly appreciate any help. I looked through the Handbook and googled this but I haven't found a solution yet. -- Michael Peirson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 hangs at mountroot during bootup
Odhiambo Washington wrote: * On 20/09/06 16:47 -0700, Mike Peirson wrote: | Hi all, | First off, I'm new to FreeBSD and this mailinglist so I hope I am in the | right place. Anyways, right now I am having some problems with FreeBSD | booting up. I have tried to install 3 times now and keep getting the | same error. When I try to boot into FreeBSD, this eventually comes up: | | Manual root filesystem specification: | fstype:device Mount device using filesystem | fstype |eg. ufs:da0s1a | ? List valid disk boot devices | empty line abort manual input | Mountroot | | This seems to be a prompt where I need to specify the location of the | root partition, but the problem here is that it hangs or freezes and I | cannot input any text. At first I thought it may be a result of FreeBSD | not properly recognizing my HDD's geometry but I manually fixed that and | it still is giving me this same issue. If anyone has had a similar | problem or knows how to fix this I would greatly appreciate any help. I | looked through the Handbook and googled this but I haven't found a | solution yet. Any further details about your hardware specs in general? -Wash http://www.netmeister.org/news/learn2quote.html DISCLAIMER: See http://www.wananchi.com/bms/terms.php -- +==+ |\ _,,,---,,_ | Odhiambo Washington[EMAIL PROTECTED] Zzz /,`.-'`'-. ;-;;,_ | Wananchi Online Ltd. www.wananchi.com |,4- ) )-,_. ,\ ( `'-'| Tel: +254 20 313985-9 +254 20 313922 '---''(_/--' `-'\_) | GSM: +254 722 743223 +254 733 744121 +==+ A man wrapped up in himself makes a very small package. Nothing out of the ordinary.. I've got a Abit VT7 socket 478 mother board with an Intel P4. Standard Western Digital 120GB HDD. I've got video and keyboard/mouse running through a KVM switch, so after reading what Greg posted.. I can see why I would be having issues with inputing any text at the mountroot prompt. -- Michael Peirson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 hangs at mountroot during bootup
Greg 'groggy' Lehey wrote: On Thursday, 21 September 2006 at 7:43:44 +0300, Odhiambo Washington wrote: * On 20/09/06 16:47 -0700, Mike Peirson wrote: Hi all, First off, I'm new to FreeBSD and this mailinglist so I hope I am in the right place. Anyways, right now I am having some problems with FreeBSD booting up. I have tried to install 3 times now and keep getting the same error. When I try to boot into FreeBSD, this eventually comes up: Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line abort manual input Mountroot This seems to be a prompt where I need to specify the location of the root partition, but the problem here is that it hangs or freezes and I cannot input any text. Any further details about your hardware specs in general? This is a keyboard problem. The background is that the boot process uses a different keyboard driver from the final kernel, and that it's much more finicky than the kernel version. It seems to have got worse in the last few years. I've found that a USB keyboard will do better, but YMMV. At first I thought it may be a result of FreeBSD not properly recognizing my HDD's geometry but I manually fixed that and it still is giving me this same issue. If anyone has had a similar problem or knows how to fix this I would greatly appreciate any help. I looked through the Handbook and googled this but I haven't found a solution yet. The background for the *message* (not the apparent freeze) is that your root file system can't be found. This happens typically when you change the device name. For example, my situation is that I'm doing development with a SATA disk drive and moving it from system to system. On my machine the root file system shows up as /dev/ad4s1a; on the other machine it's /dev/ad0s1a. It's probably worth putting in a PR about this problem. Greg -- See complete headers for address and phone numbers. About the keyboard.. I have it running through a KVM switch, would this also cause any problems? I booted into safemode and noticed that the problem with inputting text was nonexistant. I am not sure why it can't find my root filesystem. I haven't changed the device name or moved anything around at all. BTW, is there any way I can get into FreeBSD (maybe via the install disc?) to get a detailed printout of my FreeBSD slice? Posting that on here may be of some use. -- Michael Peirson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 hangs at mountroot during bootup
Some kvm's can be problematic, you may want to just plug a keyboard into the server for now. You can boot the CD and at a shell prompt run fdisk. You can give it the argument for the other drive to see that drive's partition table. -Derek At 03:30 AM 9/21/2006, Mike Peirson wrote: Greg 'groggy' Lehey wrote: On Thursday, 21 September 2006 at 7:43:44 +0300, Odhiambo Washington wrote: * On 20/09/06 16:47 -0700, Mike Peirson wrote: Hi all, First off, I'm new to FreeBSD and this mailinglist so I hope I am in the right place. Anyways, right now I am having some problems with FreeBSD booting up. I have tried to install 3 times now and keep getting the same error. When I try to boot into FreeBSD, this eventually comes up: Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line abort manual input Mountroot This seems to be a prompt where I need to specify the location of the root partition, but the problem here is that it hangs or freezes and I cannot input any text. Any further details about your hardware specs in general? This is a keyboard problem. The background is that the boot process uses a different keyboard driver from the final kernel, and that it's much more finicky than the kernel version. It seems to have got worse in the last few years. I've found that a USB keyboard will do better, but YMMV. At first I thought it may be a result of FreeBSD not properly recognizing my HDD's geometry but I manually fixed that and it still is giving me this same issue. If anyone has had a similar problem or knows how to fix this I would greatly appreciate any help. I looked through the Handbook and googled this but I haven't found a solution yet. The background for the *message* (not the apparent freeze) is that your root file system can't be found. This happens typically when you change the device name. For example, my situation is that I'm doing development with a SATA disk drive and moving it from system to system. On my machine the root file system shows up as /dev/ad4s1a; on the other machine it's /dev/ad0s1a. It's probably worth putting in a PR about this problem. Greg -- See complete headers for address and phone numbers. About the keyboard.. I have it running through a KVM switch, would this also cause any problems? I booted into safemode and noticed that the problem with inputting text was nonexistant. I am not sure why it can't find my root filesystem. I haven't changed the device name or moved anything around at all. BTW, is there any way I can get into FreeBSD (maybe via the install disc?) to get a detailed printout of my FreeBSD slice? Posting that on here may be of some use. -- Michael Peirson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 hangs at mountroot during bootup
Hi, On 9/21/06, Mike Peirson [EMAIL PROTECTED] wrote: Hi all, First off, I'm new to FreeBSD and this mailinglist so I hope I am in the right place. Anyways, right now I am having some problems with FreeBSD booting up. I have tried to install 3 times now and keep getting the same error. When I try to boot into FreeBSD, this eventually comes up: Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line abort manual input Mountroot This seems to be a prompt where I need to specify the location of the root partition, but the problem here is that it hangs or freezes and I cannot input any text. At first I thought it may be a result of FreeBSD not properly recognizing my HDD's geometry but I manually fixed that and it still is giving me this same issue. If anyone has had a similar problem or knows how to fix this I would greatly appreciate any help. I looked through the Handbook and googled this but I haven't found a solution yet. -- Michael Peirson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I guess you are using 6.1-RELEASE if so It's a bug in kbdmux, it was solved after in FreeBSD-STABLE. Booting in 'Safe mode' from the beastie menu, should workarround your hang problem. HTH Regards. -- There's this old saying: Give a man a fish, feed him for a day. Teach a man to fish, feed him for life. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 hangs at mountroot during bootup
On Wed, Sep 20, 2006 at 04:47:19PM -0700, Mike Peirson wrote: Hi all, First off, I'm new to FreeBSD and this mailinglist so I hope I am in the right place. Anyways, right now I am having some problems with FreeBSD booting up. I have tried to install 3 times now and keep getting the same error. When I try to boot into FreeBSD, this eventually comes up: Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line abort manual input Mountroot Hmmm. this looks like there is no boot sector available. I haven't seen messages before just exactly like this, but sort of. Maybe it would help if you described the sequence of things you did or tried, such as for the install. Which version did you install? Did you initiate the install (boot) from a CD? If not, what? Did you choose to use the FreeBSD MBR? Did you create a FreeBSD slice in sysinstall? Did you mark that slice as bootable? Did you create partitions within that FreeBSD slice? Did you choose which things to install? Did it appear to load things properly? After installation finished and you got the congradulations message, what did you do? jerry This seems to be a prompt where I need to specify the location of the root partition, but the problem here is that it hangs or freezes and I cannot input any text. At first I thought it may be a result of FreeBSD not properly recognizing my HDD's geometry but I manually fixed that and it still is giving me this same issue. If anyone has had a similar problem or knows how to fix this I would greatly appreciate any help. I looked through the Handbook and googled this but I haven't found a solution yet. -- Michael Peirson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 hangs at mountroot during bootup
Jerry McAllister wrote: On Wed, Sep 20, 2006 at 04:47:19PM -0700, Mike Peirson wrote: Hi all, First off, I'm new to FreeBSD and this mailinglist so I hope I am in the right place. Anyways, right now I am having some problems with FreeBSD booting up. I have tried to install 3 times now and keep getting the same error. When I try to boot into FreeBSD, this eventually comes up: Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line abort manual input Mountroot Hmmm. this looks like there is no boot sector available. I haven't seen messages before just exactly like this, but sort of. Maybe it would help if you described the sequence of things you did or tried, such as for the install. Which version did you install? Did you initiate the install (boot) from a CD? If not, what? Did you choose to use the FreeBSD MBR? Did you create a FreeBSD slice in sysinstall? Did you mark that slice as bootable? Did you create partitions within that FreeBSD slice? Did you choose which things to install? Did it appear to load things properly? After installation finished and you got the congradulations message, what did you do? jerry This seems to be a prompt where I need to specify the location of the root partition, but the problem here is that it hangs or freezes and I cannot input any text. At first I thought it may be a result of FreeBSD not properly recognizing my HDD's geometry but I manually fixed that and it still is giving me this same issue. If anyone has had a similar problem or knows how to fix this I would greatly appreciate any help. I looked through the Handbook and googled this but I haven't found a solution yet. -- Michael Peirson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Hi Jerry, I started the install from the standard 2 disc set and it is FreeBSD 6.1-release. I used the FreeBSD MBR. I created a FreeBSD slice using up all of the HDD in sysinstall. I did not mark the slice as bootable.. I tried to use that option but it told me that it didn't apply. I created several partitions inside the FreeBSD slice. /, swap, /var, /tmp, /usr, /home, /etc. I did a standard install and chose the Developer set of packages (I don't need X because I plan to run a server). I also went through and added extra programs off of the disc. Everything appeared to load properly. I rebooted after I finished with the install and it began to boot up fine but then I got that mountroot message. -- Michael Peirson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 hangs at mountroot during bootup
On Thu, Sep 21, 2006 at 09:01:58AM -0700, Mike Peirson wrote: Jerry McAllister wrote: On Wed, Sep 20, 2006 at 04:47:19PM -0700, Mike Peirson wrote: Hi all, First off, I'm new to FreeBSD and this mailinglist so I hope I am in the same error. When I try to boot into FreeBSD, this eventually comes up: Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line abort manual input Mountroot Hmmm. this looks like there is no boot sector available. I haven't seen messages before just exactly like this, but sort of. Did it appear to load things properly? After installation finished and you got the congradulations message, what did you do? jerry -- Michael Peirson Hi Jerry, I started the install from the standard 2 disc set and it is FreeBSD 6.1-release. I used the FreeBSD MBR. I created a FreeBSD slice using up all of the HDD in sysinstall. I did not mark the slice as bootable.. I tried to use that option but it told me that it didn't apply. I created several partitions inside the FreeBSD slice. /, swap, /var, /tmp, /usr, /home, /etc. I did a standard install and chose the Developer set of packages (I don't need X because I plan to run a server). I also went through and added extra programs off of the disc. Everything appeared to load properly. I rebooted after I finished with the install and it began to boot up fine but then I got that mountroot message. Most of that looks normal except for one thing. /etc should not really be in its own partition. It needs to stay in root. That is because the system needs to have it available during the boot up process. It mounts the assumed root (partition a) read-only in a temporary spot and reads necessary stuff from it. Then later, after fsck and such, it remounts it appropriately. Maybe, for some reason, it thinks it need information from something like /etc/fstab or another place and that is not available until after the remount. That is sort of grabbing at straws, but it is the only thing I can see at the moment. So, maybe try rethinking your slice division. jerry -- Michael Peirson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 hangs at mountroot during bootup
Mike Peirson wrote: Greg 'groggy' Lehey wrote: On Thursday, 21 September 2006 at 7:43:44 +0300, Odhiambo Washington wrote: * On 20/09/06 16:47 -0700, Mike Peirson wrote: Hi all, First off, I'm new to FreeBSD and this mailinglist so I hope I am in the right place. Anyways, right now I am having some problems with FreeBSD booting up. I have tried to install 3 times now and keep getting the same error. When I try to boot into FreeBSD, this eventually comes up: Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line abort manual input Mountroot This seems to be a prompt where I need to specify the location of the root partition, but the problem here is that it hangs or freezes and I cannot input any text. Any further details about your hardware specs in general? This is a keyboard problem. The background is that the boot process uses a different keyboard driver from the final kernel, and that it's much more finicky than the kernel version. It seems to have got worse in the last few years. I've found that a USB keyboard will do better, but YMMV. At first I thought it may be a result of FreeBSD not properly recognizing my HDD's geometry but I manually fixed that and it still is giving me this same issue. If anyone has had a similar problem or knows how to fix this I would greatly appreciate any help. I looked through the Handbook and googled this but I haven't found a solution yet. The background for the *message* (not the apparent freeze) is that your root file system can't be found. This happens typically when you change the device name. For example, my situation is that I'm doing development with a SATA disk drive and moving it from system to system. On my machine the root file system shows up as /dev/ad4s1a; on the other machine it's /dev/ad0s1a. It's probably worth putting in a PR about this problem. Greg -- See complete headers for address and phone numbers. About the keyboard.. I have it running through a KVM switch, would this also cause any problems? I booted into safemode and noticed that the problem with inputting text was nonexistant. I am not sure why it can't find my root filesystem. I haven't changed the device name or moved anything around at all. BTW, is there any way I can get into FreeBSD (maybe via the install disc?) to get a detailed printout of my FreeBSD slice? Posting that on here may be of some use. You get errors with KVM switches, yes. In my case one box that gives an error still works fine after the bios or whatever it is that complains has its say. Then continues the boot and doesnt complain again. Its an old HP Vector. Al Plant - Honolulu, Hawaii - Admin -- http://hawaiidakine.com -- http://hdk5.com -- -- http://internetohana.org -- http://freeBSDinfo.org -- + Supporting open source computing - FreeBSD 6.* + ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 hangs at mountroot during bootup
[rearranged, trimmed] On Thursday, 21 September 2006 at 2:32:59 -0500, Derek Ragona wrote: At 06:47 PM 9/20/2006, Mike Peirson wrote: Hi all, First off, I'm new to FreeBSD and this mailinglist so I hope I am in the right place. Anyways, right now I am having some problems with FreeBSD booting up. I have tried to install 3 times now and keep getting the same error. When I try to boot into FreeBSD, this eventually comes up: Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line abort manual input Mountroot This seems to be a prompt where I need to specify the location of the root partition, but the problem here is that it hangs or freezes and I cannot input any text. I have seen this in a few situations: 1.) the BIOS is set to not allow boot area writes 2.) The root partition is outside the first 1024 cylinders. This was on older hardware that didn't do good geometry translation on big drives. 3.) moved the root partition to another slice I don't think any of these can cause the keyboard to freeze. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgpKzd82HJaBQ.pgp Description: PGP signature
FreeBSD 6.1 hangs at mountroot during bootup
Hi all, First off, I'm new to FreeBSD and this mailinglist so I hope I am in the right place. Anyways, right now I am having some problems with FreeBSD booting up. I have tried to install 3 times now and keep getting the same error. When I try to boot into FreeBSD, this eventually comes up: Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line abort manual input Mountroot This seems to be a prompt where I need to specify the location of the root partition, but the problem here is that it hangs or freezes and I cannot input any text. At first I thought it may be a result of FreeBSD not properly recognizing my HDD's geometry but I manually fixed that and it still is giving me this same issue. If anyone has had a similar problem or knows how to fix this I would greatly appreciate any help. I looked through the Handbook and googled this but I haven't found a solution yet. -- Michael Peirson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 hangs at mountroot during bootup
* On 20/09/06 16:47 -0700, Mike Peirson wrote: | Hi all, | First off, I'm new to FreeBSD and this mailinglist so I hope I am in the | right place. Anyways, right now I am having some problems with FreeBSD | booting up. I have tried to install 3 times now and keep getting the | same error. When I try to boot into FreeBSD, this eventually comes up: | | Manual root filesystem specification: | fstype:device Mount device using filesystem | fstype |eg. ufs:da0s1a | ? List valid disk boot devices | empty line abort manual input | Mountroot | | This seems to be a prompt where I need to specify the location of the | root partition, but the problem here is that it hangs or freezes and I | cannot input any text. At first I thought it may be a result of FreeBSD | not properly recognizing my HDD's geometry but I manually fixed that and | it still is giving me this same issue. If anyone has had a similar | problem or knows how to fix this I would greatly appreciate any help. I | looked through the Handbook and googled this but I haven't found a | solution yet. Any further details about your hardware specs in general? -Wash http://www.netmeister.org/news/learn2quote.html DISCLAIMER: See http://www.wananchi.com/bms/terms.php -- +==+ |\ _,,,---,,_ | Odhiambo Washington[EMAIL PROTECTED] Zzz /,`.-'`'-. ;-;;,_ | Wananchi Online Ltd. www.wananchi.com |,4- ) )-,_. ,\ ( `'-'| Tel: +254 20 313985-9 +254 20 313922 '---''(_/--' `-'\_) | GSM: +254 722 743223 +254 733 744121 +==+ A man wrapped up in himself makes a very small package. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 hangs at mountroot during bootup
On Thursday, 21 September 2006 at 7:43:44 +0300, Odhiambo Washington wrote: * On 20/09/06 16:47 -0700, Mike Peirson wrote: Hi all, First off, I'm new to FreeBSD and this mailinglist so I hope I am in the right place. Anyways, right now I am having some problems with FreeBSD booting up. I have tried to install 3 times now and keep getting the same error. When I try to boot into FreeBSD, this eventually comes up: Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line abort manual input Mountroot This seems to be a prompt where I need to specify the location of the root partition, but the problem here is that it hangs or freezes and I cannot input any text. Any further details about your hardware specs in general? This is a keyboard problem. The background is that the boot process uses a different keyboard driver from the final kernel, and that it's much more finicky than the kernel version. It seems to have got worse in the last few years. I've found that a USB keyboard will do better, but YMMV. At first I thought it may be a result of FreeBSD not properly recognizing my HDD's geometry but I manually fixed that and it still is giving me this same issue. If anyone has had a similar problem or knows how to fix this I would greatly appreciate any help. I looked through the Handbook and googled this but I haven't found a solution yet. The background for the *message* (not the apparent freeze) is that your root file system can't be found. This happens typically when you change the device name. For example, my situation is that I'm doing development with a SATA disk drive and moving it from system to system. On my machine the root file system shows up as /dev/ad4s1a; on the other machine it's /dev/ad0s1a. It's probably worth putting in a PR about this problem. Greg -- See complete headers for address and phone numbers. pgpT7FSM4RDug.pgp Description: PGP signature
Re: Freebsdi386 4.11 release failed to mountroot after make buildworld make kerne
john pa [EMAIL PROTECTED] writes: Error after upgrade from fresh install 4.11-release to 4.-stable It fail to mountroot : ufs:/dev/ad4s2a Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rightsreserved. FreeBSD 4.11-STABLE #0: Tue Apr 26 22:14:24 SGT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL [snip] lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 ata1-slave: ATAPI identify retries exceeded ad10: DMA limited to UDMA33, non-ATA66 cable or device ad10: 76319MB WDC WD800JD-00HKA0 [155061/16/63] at ata5-master UDMA33 acd0: CD-RW AOPEN COM5232/AAH at ata1-master PIO4 Fail to Mount root from ufs:/dev/ad4s2a Hel Looks like it's trying to boot from ad4, but your disk was recognized as ad10. Break to the boot prompt before it tries to get the loader, and change the boot settings. Sorry, but I haven't messed with the boot process recently enough to give more detailed instructions. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Freebsdi386 4.11 release failed to mountroot after make buildworld make kerne
Error after upgrade from fresh install 4.11-release to 4.-stable It fail to mountroot : ufs:/dev/ad4s2a Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rightsreserved. FreeBSD 4.11-STABLE #0: Tue Apr 26 22:14:24 SGT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL Timecounter i8254 frequency 1193182 Hz CPU: Intel(R) Pentium(R) 4 CPU 3.20GHz (3198.47-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf34 Stepping = 4 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Hyperthreading: 2 logical CPUs real memory = 1072889856 (1047744K bytes) avail memory = 1038413824 (1014076K bytes) Preloaded elf kernel kernel at 0xc05bb000. Warning: Pentium 4 CPU: PSE disabled Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 12 entries at 0xc00f4df0 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 agp0: Intel 82875P host to AGP bridge mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: PCI to PCI bridge (vendor=8086 device=2579) at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: NVidia model 0322 graphics accelerator at 0.0 irq 10 pcib2: PCI to PCI bridge (vendor=8086 device=257b) at device 3.0 on pci0 pci2: PCI bus on pcib2 em0: Intel(R) PRO/1000 Network Connection, Version - 1.7.35 port 0xcf80-0xcf9f mem 0xfe9e-0xfe9f irq 5 at device 1.0 on pci2 em0: Speed:N/A Duplex:N/A uhci0: Intel 82801EB (ICH5) USB controller USB-A port 0xef00-0xef1f irq 10 at device 29.0 on pci0 usb0: Intel 82801EB (ICH5) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: vendor 0x1267 PS/2+USB Mouse, rev 1.10/0.01, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. uhci1: Intel 82801EB (ICH5) USB controller USB-B port 0xef20-0xef3f irq 5 at device 29.1 on pci0 usb1: Intel 82801EB (ICH5) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801EB (ICH5) USB controller USB-C port 0xef40-0xef5f irq 5 at device 29.2 on pci0 usb2: Intel 82801EB (ICH5) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: Intel 82801EB (ICH5) USB controller USB-D port 0xef80-0xef9f irq 10 at device 29.3 on pci0 usb3: Intel 82801EB (ICH5) USB controller USB-D on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered pci0: USB controller at 29.7 irq 11 pcib3: Intel 82801BA/BAM (ICH2) Hub to PCI bridge at device 30.0 on pci0 pci3: PCI bus on pcib3 fwohci0: VIA VT6306 port 0xdc00-0xdc7f mem 0xfeaff800-0xfeaf irq 11 at device 3.0 on pci3 fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channel is 4. fwohci0: EUI64 00:e0:18:00:00:77:6b:85 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: IEEE1394(FireWire) bus on fwohci0 fwe0: Ethernet over FireWire on firewire0 if_fwe0: Fake Ethernet address: 02:e0:18:77:6b:85 sbp0: SBP-2/SCSI over FireWire on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop = 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) atapci0: Promise SATA150 TX2 controller port 0xd880-0xd8ff,0xdfa0-0xdfaf,0xdf00-0xdf3f mem 0xfeac-0xfead,0xfeafe000-0xfeafefff irq 11 at device 4.0 on pci3 atapci0: channels 3 ata2: at 0xfeafe000 on atapci0 ata3: at 0xfeafe000 on atapci0 ata4: at 0xfeafe000 on atapci0 ata4: IDE port pci3: unknown card (vendor=0x163c, dev=0x3052) at 11.0 irq 11 xl0: 3Com 3c905B-TX Fast Etherlink XL port 0xd800-0xd87f mem 0xfeaff400-0xfeaff47f irq 11 at device 12.0 on pci3 xl0: Ethernet address: 00:50:04:18:2c:86 miibus0: MII bus on xl0 xlphy0: 3Com internal media interface on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: PCI to ISA bridge (vendor=8086 device=24d0) at device 31.0 on pci0 isa0: ISA bus on isab0 atapci1: Intel ICH5 ATA100 controller port 0xfc00-0xfc0f,0-0x3,0-0x7,0-0x3,0-0x7 irq 0 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata1: at 0x170 irq 15 on atapci1 atapci2: Intel ICH5 SATA150 controller port 0xef60-0xef6f,0xefa8-0xefab,0xefa0-0xefa7,0xefac-0xefaf,0xefe0-0xefe7 irq 5 at device 31.2 on pci0 ata5: at 0xefe0 on atapci2 ata6: at 0xefa0 on atapci2 pci0: unknown card (vendor=0x8086, dev=0x24d3) at 31.3 irq 5 pcm0: Intel ICH5 (82801EB) port 0xee80-0xeebf,0xe800-0xe8ff mem 0xfebff400-0xfebff4ff,0xfebff800-0xfebff9ff irq 5 at device 31.5 on pci0 pcm0: Analog Devices AD1985 AC97 Codec orm0: Option ROM
Re: Install 5.3 - Getting mountroot prompt
On February 11, 2005 09:42 pm, Scott wrote: I will really appreciate it of someone can help me out. I am installing 5.3 on a dual p3 server. I have two 160 gig Seagate IDE drives on the first IDE connector, and a CD rom on the 2nd IDE connector. I have reinstalled several times with different drive configurations and keep getting stuck at the same place. At boot, the normal countdown loader comes up and it begins to boot. The boot message gets to this drive section below and then stops at a mountroot prompt. Begin copy ... ad0: 152627MB ST3160023A/8.01 [310101/16/63] at ata0-master UDMA66 ad1: 152627MB ST3160023A/8.01 [310101/16/63] at ata0-master UDMA66 acd0: CDU5211/YYS2 at ata1-master PIO4 Your problem may be that you have two drives on the same connector that are both configured as the master. You need to switch the ad1 drive to be the slave. Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. usf:da0s1a ? List valid desk boot devices empty line Abort manual input mountroot End copy If I type: ufs:ad0s1a at that mountroot prompt, it will boot normally and as far as I can tell, all is working like I would expect. I suspected this may have something to do with my fstab but it looks normal to me: /dev/ad0s1b none swap sw 0 0 /dev/ad1s1b none swap sw 0 0 /dev/ad0s1a /ufs rw 1 1 /dev/ad1s1d /backup ufs rw 2 2 /dev/ad0s1d /tmp ufs rw 2 2 /dev/acd0 /cdromcd9660 ro,noauto 0 0 Please let me know if I can provide more information that will help you help me know what to do to get it to automatically go on to boot ad0s1a. Thanks much, Scott ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Ean Kingston E-Mail: ean AT hedron DOT org URL: http://www.hedron.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Install 5.3 - Getting mountroot prompt
On February 11, 2005 09:42 pm, Scott wrote: I will really appreciate it of someone can help me out. I am installing 5.3 on a dual p3 server. I have two 160 gig Seagate IDE drives on the first IDE connector, and a CD rom on the 2nd IDE connector. I have reinstalled several times with different drive configurations and keep getting stuck at the same place. At boot, the normal countdown loader comes up and it begins to boot. The boot message gets to this drive section below and then stops at a mountroot prompt. Begin copy ... ad0: 152627MB ST3160023A/8.01 [310101/16/63] at ata0-master UDMA66 ad1: 152627MB ST3160023A/8.01 [310101/16/63] at ata0-master UDMA66 acd0: CDU5211/YYS2 at ata1-master PIO4 Your problem may be that you have two drives on the same connector that are both configured as the master. You need to switch the ad1 drive to be the slave. Thanks Ean, That was an error in my posting. The second drive actually does show on the output as slave. I retyped that into my message from the screen and copied and pasted that line and didn't change the master to slave. It actually does show master and slave correctly. The master/slave settings are actually correct. Sorry for the confusion. I'm going to try to install 5.2.1 again and see if I still have the same issue. Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. usf:da0s1a ? List valid desk boot devices empty line Abort manual input mountroot End copy If I type: ufs:ad0s1a at that mountroot prompt, it will boot normally and as far as I can tell, all is working like I would expect. I suspected this may have something to do with my fstab but it looks normal to me: /dev/ad0s1b none swap sw 0 0 /dev/ad1s1b none swap sw 0 0 /dev/ad0s1a /ufs rw 1 1 /dev/ad1s1d /backup ufs rw 2 2 /dev/ad0s1d /tmp ufs rw 2 2 /dev/acd0 /cdromcd9660 ro,noauto 0 0 Please let me know if I can provide more information that will help you help me know what to do to get it to automatically go on to boot ad0s1a. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Solved: Re: Install 5.3 - Getting mountroot prompt
At boot, the normal countdown loader comes up and it begins to boot. The boot message gets to this drive section below and then stops at a mountroot prompt. I believe I have solved my problem. When I was creating partitions, I first created the swap, then /tmp to the size I wanted, and all remaining space went to / . I began to think and wonder if the order in which the partitions were created makes a difference so I tried again. I then created the swap, next / and finally /tmp. That seems to have made a difference. It is booting normally now unless I chose option 2 to boot without ACPI. If I boot without ACPI, it times out when finding the drives. Any ideas what would cause that? I'd prefer to not run ACPI on the server. Thanks, Scott ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Install 5.3 - Getting mountroot prompt
On February 12, 2005 12:18 pm, you wrote: On February 11, 2005 09:42 pm, Scott wrote: I will really appreciate it of someone can help me out. I am installing 5.3 on a dual p3 server. I have two 160 gig Seagate IDE drives on the first IDE connector, and a CD rom on the 2nd IDE connector. I have reinstalled several times with different drive configurations and keep getting stuck at the same place. At boot, the normal countdown loader comes up and it begins to boot. The boot message gets to this drive section below and then stops at a mountroot prompt. Begin copy ... ad0: 152627MB ST3160023A/8.01 [310101/16/63] at ata0-master UDMA66 ad1: 152627MB ST3160023A/8.01 [310101/16/63] at ata0-master UDMA66 acd0: CDU5211/YYS2 at ata1-master PIO4 Your problem may be that you have two drives on the same connector that are both configured as the master. You need to switch the ad1 drive to be the slave. Thanks Ean, That was an error in my posting. The second drive actually does show on the output as slave. I retyped that into my message from the screen and copied and pasted that line and didn't change the master to slave. It actually does show master and slave correctly. Okay. No problem. I didn't see anything else wrong with what you posted. For what it's worth, I've got an almost identical setup except my drives are 120GB ATA-100. The master/slave settings are actually correct. Sorry for the confusion. I'm going to try to install 5.2.1 again and see if I still have the same issue. Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. usf:da0s1a ? List valid desk boot devices empty line Abort manual input mountroot End copy If I type: ufs:ad0s1a at that mountroot prompt, it will boot normally and as far as I can tell, all is working like I would expect. I suspected this may have something to do with my fstab but it looks normal to me: /dev/ad0s1b none swap sw 0 0 /dev/ad1s1b none swap sw 0 0 /dev/ad0s1a /ufs rw 1 1 /dev/ad1s1d /backup ufs rw 2 2 /dev/ad0s1d /tmp ufs rw 2 2 /dev/acd0 /cdromcd9660 ro,noauto 0 0 Please let me know if I can provide more information that will help you help me know what to do to get it to automatically go on to boot ad0s1a. -- Ean Kingston E-Mail: ean AT hedron DOT org URL: http://www.hedron.org/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Install 5.3 - Getting mountroot prompt
I will really appreciate it of someone can help me out. I am installing 5.3 on a dual p3 server. I have two 160 gig Seagate IDE drives on the first IDE connector, and a CD rom on the 2nd IDE connector. I have reinstalled several times with different drive configurations and keep getting stuck at the same place. At boot, the normal countdown loader comes up and it begins to boot. The boot message gets to this drive section below and then stops at a mountroot prompt. Begin copy ... ad0: 152627MB ST3160023A/8.01 [310101/16/63] at ata0-master UDMA66 ad1: 152627MB ST3160023A/8.01 [310101/16/63] at ata0-master UDMA66 acd0: CDU5211/YYS2 at ata1-master PIO4 Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. usf:da0s1a ? List valid desk boot devices empty line Abort manual input mountroot End copy If I type: ufs:ad0s1a at that mountroot prompt, it will boot normally and as far as I can tell, all is working like I would expect. I suspected this may have something to do with my fstab but it looks normal to me: /dev/ad0s1b none swap sw 0 0 /dev/ad1s1b none swap sw 0 0 /dev/ad0s1a /ufs rw 1 1 /dev/ad1s1d /backup ufs rw 2 2 /dev/ad0s1d /tmp ufs rw 2 2 /dev/acd0 /cdromcd9660 ro,noauto 0 0 Please let me know if I can provide more information that will help you help me know what to do to get it to automatically go on to boot ad0s1a. Thanks much, Scott ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Install 5.3 - Getting mountroot prompt
I will really appreciate it of someone can help me out. I am installing 5.3 on a dual p3 server. I have two 160 gig Seagate IDE drives on the first IDE connector, and a CD rom on the 2nd IDE connector. I have reinstalled several times with different drive configurations and keep getting stuck at the same place. At boot, the normal countdown loader comes up and it begins to boot. The boot message gets to this drive section below and then stops at a mountroot prompt. Begin copy ... ad0: 152627MB ST3160023A/8.01 [310101/16/63] at ata0-master UDMA66 ad1: 152627MB ST3160023A/8.01 [310101/16/63] at ata0-master UDMA66 acd0: CDU5211/YYS2 at ata1-master PIO4 Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. usf:da0s1a ? List valid desk boot devices empty line Abort manual input mountroot End copy If I type: ufs:ad0s1a at that mountroot prompt, it will boot normally and as far as I can tell, all is working like I would expect. I suspected this may have something to do with my fstab but it looks normal to me: /dev/ad0s1b none swap sw 0 0 /dev/ad1s1b none swap sw 0 0 /dev/ad0s1a /ufs rw 1 1 /dev/ad1s1d /backup ufs rw 2 2 /dev/ad0s1d /tmp ufs rw 2 2 /dev/acd0 /cdromcd9660 ro,noauto 0 0 Please let me know if I can provide more information that will help you help me know what to do to get it to automatically go on to boot ad0s1a. One more thing I just found out, if it helps. If I just let it boot, I get to the mountroot prompt as above and can boot the system after entering the location of the root partition. If I chose option 2 and boot with ACPI off, the drives are not found and I get: FAILURE - ATA_IDENTIFY timed out errors on both the master and slave drives. At that point, I get the mountroot prompt again, but of course can not mount the root partition. So now I'm wondering why if I boot with ACPI on, the drives are found, but root doesn't boot. With ACPI off, the drives are not even found. I hope that helps someone tell me where to look. 5.2.1 was booting off this same drive normally before I replaced it with 5.3. Thanks, Scott ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mountroot
Hi all, My disk file system was crash sice while booting Mounting root from ufs:/dev/ad0s1a Root mount failed:6 Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:/dev/da0s1a ? List valid disk boot devices empty line Abort manual input mountroot How I can mount? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
installed ATA RAID, now cannot boot - get mountroot prompt
Hiya all I'm searching the web for answers on this too, but so far nothing useful. hard to know what question to ask the search engines! anyhow, the situation: I installed 5.2.1-R some time back as a start to making a new server. I used a 40 and an 80 Gb IDE drive plugged into the motherboard Now I've got an Adaptec 2400a IDE RAID card and have installed it. I created to raid 1 packs (2x40 and 2x80) and behold it starts to boot, finds all the drives etc, no problems, but then it cannot find root as root WAS on /dev/ad0s1a and is now on /dev/da0s1a I get a mountroot prompt and I type ufs:/dev/da0s1a and it starts to boot but obviously gets a lot of errors because /etc/fstab contains the old drives names. I eventually get a shell but cannot now edit fstab because only root has mounted and all the editors are 'somewhere unmounted' now I'm lost. how to do edit fstab to get it to mount the partitions? doubly lost because I know I can mount them manually but don't know the parameters for 'mount' and , yes, 'man' won't work either. yes, I'm still new at this BSD thing please help anyway. -- DA Fo rsythNetwork Supervisor Principal Technical Officer -- Institute for Water Research http://www.ru.ac.za/institutes/iwr/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: installed ATA RAID, now cannot boot - get mountroot prompt
You could try using the ed editor which should be located on the root partition for just this reason. Or, manually mount the usr partition when you get to the shell prompt so you have access to other editors such as vi. Hopefully you know what partition the usr file system is on (ie da0s1e) and can then use: mount /dev/da0s1e /usr On Wednesday 25 August 2004 12:53 pm, DA Forsyth wrote: Hiya all I'm searching the web for answers on this too, but so far nothing useful. hard to know what question to ask the search engines! anyhow, the situation: I installed 5.2.1-R some time back as a start to making a new server. I used a 40 and an 80 Gb IDE drive plugged into the motherboard Now I've got an Adaptec 2400a IDE RAID card and have installed it. I created to raid 1 packs (2x40 and 2x80) and behold it starts to boot, finds all the drives etc, no problems, but then it cannot find root as root WAS on /dev/ad0s1a and is now on /dev/da0s1a I get a mountroot prompt and I type ufs:/dev/da0s1a and it starts to boot but obviously gets a lot of errors because /etc/fstab contains the old drives names. I eventually get a shell but cannot now edit fstab because only root has mounted and all the editors are 'somewhere unmounted' now I'm lost. how to do edit fstab to get it to mount the partitions? doubly lost because I know I can mount them manually but don't know the parameters for 'mount' and , yes, 'man' won't work either. yes, I'm still new at this BSD thing please help anyway. -- DA Fo rsythNetwork Supervisor Principal Technical Officer -- Institute for Water Research http://www.ru.ac.za/institutes/iwr/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: installed ATA RAID, now cannot boot - get mountroot prompt
Try this. Get to the shell prompt and run: ed /etc/fstab 1,$s/ad0/da0/ w q Then reboot the system. On Wednesday 25 August 2004 12:53 pm, DA Forsyth wrote: Hiya all I'm searching the web for answers on this too, but so far nothing useful. hard to know what question to ask the search engines! anyhow, the situation: I installed 5.2.1-R some time back as a start to making a new server. I used a 40 and an 80 Gb IDE drive plugged into the motherboard Now I've got an Adaptec 2400a IDE RAID card and have installed it. I created to raid 1 packs (2x40 and 2x80) and behold it starts to boot, finds all the drives etc, no problems, but then it cannot find root as root WAS on /dev/ad0s1a and is now on /dev/da0s1a I get a mountroot prompt and I type ufs:/dev/da0s1a and it starts to boot but obviously gets a lot of errors because /etc/fstab contains the old drives names. I eventually get a shell but cannot now edit fstab because only root has mounted and all the editors are 'somewhere unmounted' now I'm lost. how to do edit fstab to get it to mount the partitions? doubly lost because I know I can mount them manually but don't know the parameters for 'mount' and , yes, 'man' won't work either. yes, I'm still new at this BSD thing please help anyway. -- DA Fo rsythNetwork Supervisor Principal Technical Officer -- Institute for Water Research http://www.ru.ac.za/institutes/iwr/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: installed ATA RAID, now cannot boot - get mountroot prompt
DA Forsyth [EMAIL PROTECTED] writes: I'm searching the web for answers on this too, but so far nothing useful. hard to know what question to ask the search engines! I made a mistake in rc.conf, or another startup file, and now I cannot edit it because the filesystem is read-only. What should I do? http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#RCCONF-READONLY ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: installed ATA RAID, now cannot boot - get mountroot prompt
I'm by no means an expert, and thus the reason for my crude and unscientific solution that I'm proposing Seeing as you now know what it'll turn into upon adding this RAID card to your system, why don't you try the crude method of undoing everything, booting successfully, and then editing /etc/fstab accordingly just prior to shutting it back down to allow for a successful boot once you put the new hardware back in? The link to the FAQ mentioned below won't work for this scenario IMO because his /etc/fstab is currently inaccurate. Merely typing mount / would still generate an error. You could however type mount /dev/da0s1e / perhaps to get what you want though. -Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of Lowell Gilbert Sent: Wednesday, August 25, 2004 12:15 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: installed ATA RAID, now cannot boot - get mountroot prompt DA Forsyth [EMAIL PROTECTED] writes: I'm searching the web for answers on this too, but so far nothing useful. hard to know what question to ask the search engines! I made a mistake in rc.conf, or another startup file, and now I cannot edit it because the filesystem is read-only. What should I do? http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#RCCONF- READONLY ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
installation of FreeBSD 4.10 on Dell PowerEdge 650 fails after reboot with mountroot
Just tried installing FreeBSD 4.10 on a Dell PowerEdge 650. No problems with the install, tried creating a partition with dangerously dedicated and also, just using the entire disk with standard bootmanager. Each time, after the initial reboot I get an error: Mounting root from ufs:ad0s1a Root mount failed: 6 Mounting root from ufs:ad0a Root mount failed: 6 Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:/dev/da0s1a ? List valid disk boot devices empty line Abort manual input mountroot I tried: mountroot ufs:/dev/ad4s1a but that fails too. The disk is a Seagate 120GB and it's actually ad4, not ad0. If I interrupt the boot process at: FreeBSD/i386 BOOT Default: 0:ad(0,a)/kernel boot: and enter: FreeBSD/i386 BOOT Default: 0:ad(0,a)/kernel boot: 0:ad(4,a)/kernel the machine will boot properly. I've tried two things I found while checking on this: 1. Adding to loader.conf: rootdev=disk4s1a root_disk_unit=0 2. Rebuilding the kernel and adding: optionsROOTDEVNAME=\ufs:ad4s1a\ Neither of which worked.Is there something I'm missing while doing the installation? If I look in /dev the devices are there ad4, ad4s1, ad4s1a, ad4s1b, etc. About at wit's end ... any help would be great. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: installation of FreeBSD 4.10 on Dell PowerEdge 650 fails after reboot with mountroot
I don't own a dell power edge but I seem to remember another thread with this same problem and I think the problem seemed to be how the dell found the cdrom and harddrives, I think if you look at how the ide/ata cables are run, this may be the problem, but my memory is flakky hope this points you to the right fix. On Fri, Aug 06, 2004 at 07:21:15PM -0500, Spumonti wrote: Just tried installing FreeBSD 4.10 on a Dell PowerEdge 650. No problems with the install, tried creating a partition with dangerously dedicated and also, just using the entire disk with standard bootmanager. Each time, after the initial reboot I get an error: Mounting root from ufs:ad0s1a Root mount failed: 6 Mounting root from ufs:ad0a Root mount failed: 6 Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:/dev/da0s1a ? List valid disk boot devices empty line Abort manual input mountroot I tried: mountroot ufs:/dev/ad4s1a but that fails too. The disk is a Seagate 120GB and it's actually ad4, not ad0. If I interrupt the boot process at: FreeBSD/i386 BOOT Default: 0:ad(0,a)/kernel boot: and enter: FreeBSD/i386 BOOT Default: 0:ad(0,a)/kernel boot: 0:ad(4,a)/kernel the machine will boot properly. I've tried two things I found while checking on this: 1. Adding to loader.conf: rootdev=disk4s1a root_disk_unit=0 2. Rebuilding the kernel and adding: optionsROOTDEVNAME=\ufs:ad4s1a\ Neither of which worked.Is there something I'm missing while doing the installation? If I look in /dev the devices are there ad4, ad4s1, ad4s1a, ad4s1b, etc. About at wit's end ... any help would be great. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- -- ** The information contained in this communication is confidential, private, proprietary, or otherwise privileged and is intended only for the use of the addressee. Unauthorized use, disclosure, distribution or copying is strictly prohibited and may be unlawful. If you have received this communication in error, please notify the sender immediately. ** == ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: installation of FreeBSD 4.10 on Dell PowerEdge 650 fails after reboot with mountroot
Spumonti wrote: snip The disk is a Seagate 120GB and it's actually ad4, not ad0. If I interrupt the boot process at: FreeBSD/i386 BOOT Default: 0:ad(0,a)/kernel boot: and enter: FreeBSD/i386 BOOT Default: 0:ad(0,a)/kernel boot: 0:ad(4,a)/kernel the machine will boot properly. I've tried two things I found while checking on this: 1. Adding to loader.conf: rootdev=disk4s1a root_disk_unit=0 2. Rebuilding the kernel and adding: optionsROOTDEVNAME=\ufs:ad4s1a\ Neither of which worked.Is there something I'm missing while doing the installation? If I look in /dev the devices are there ad4, ad4s1, ad4s1a, ad4s1b, etc. About at wit's end ... any help would be great. Is this the only disk in the box? Why is it ad4 instead of ad0? That's at issue, but maybe it's not as bad as pulling out your hair... It might be possible to fix it without changing disk numbers by adding the following to /boot/loader.conf: set root_disk_unit=4 boot /kernel See loader(8) for details. That said, I'm no expert on loader(8) et al. But that's what the docs say, anyway. HTH, Kevin Kinsey DaleCo, S.P. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: #2 - Swapped disks and now stuck in the mountroot prompt
hello, i'm eechia. i've come across your mountroot problem on the web. i'm facing the similiar problem too. can you give me some guideline regarding it? thanks you -eechia- Date: 12 jan 2004 According to me, you have choice: 1) start the kernel with -a option (e.g. boot -a ): with this flag the device ufs:/dev/ad2s1a (warning: type in your appropriate device) is accepted by mountroot and the boot proceed. Than I can change the fstab accordingly to make the change permanent. 2) boot with a rescue cdrom, get a shell prompt and change the /etc/fstab accordingly (yes this file is red before booting the kernel, to instruct the kernel itself to the right root device); But I've an unanswered question from freebsd-questions people: - Why without the boot -a flag, why the kernel ask me a device and even it is the correct one vfs_conf.c:vfs_mountroot_ask() give me the error code 6? Bye Roberto ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Mountroot prompt with 4.9 Generic kernel
Hi, I've got a running 4.6 system that I want to upgrade to 4.9. I've updated source with RELENG=4_9 in my supfile, and have build a new kernel using the GENERIC config file. The box is a Compaq Proliant 1600 with two embedded wide-ultra SCSI controllers, detected by 4.6 as sym0 and sym1. There is only one disk, it's on the first controller, so when booting 4.6, I get this: snip (sym0 and sym1 detected) snip Waiting 5 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s2a da0 at sym0 bus 0 target 0 lun 0 da0: COMPAQ WDE4360S 1.52 Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C) snip Trying to boot with the GENERIC kernel results in the following: snip (sym0 and sym1 detected same as with 4.6) snip Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s2a no such device 'da' setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 snip mountroot At the mountroot prompt, I hit ? and get: Possibly valid devices for 'ufs' root: console, ctty, mem, pts, ptc, log, fd, sc, FD, bpf, sio, tun, pci, md, xpt, kbd, acd, asr, ata, iir, MFS I've search this list's archives, and have gotten some hints/ideas, but none that get me a shiny new FreeBSD 4.9 system. Any help? --Kristian Kristian Strickland, BSc Math CompSci (StFX '94) IBM (e)server Certified Specialist: - pSeries AIX System Administration - pSeries AIX System Support System Support Specialist (AIX, OpenVMS FreeBSD) for Co-op Atlantic in Moncton, NB, Canada My Books: AIX admin: http://www.redbooks.ibm.com/abstracts/sg246191.html AIX support: http://www.redbooks.ibm.com/abstracts/sg246199.html Please R.U.N.S.A.F.E. http://www.jmu.edu/computing/runsafe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
#2 - Swapped disks and now stuck in the mountroot prompt
Date: 12 jan 2004 I've installed FreeBSD 4.9 on a ide0:0 (primary IDE, master hd) then ported the hard disk on a second PC and installed as ide1:0 (secondary IDE, master hd) without update the /etc/fstab file. When booting the kernel start probing devices, I see the disk as ad2 then the kernel halts when trying to mount the root file system with the following message: mount root from ufs:/dev/ad0s1a root mount failed: 6 At the prompt I've tried with ufs:/dev/ad2s1a, now the right device, but it does not work. The solution is to instruct the kernel with the right device: but ad2s1a seems to be wrong... After several attempts I discover that the kernel must be started with the option -a: with this flag the device ufs:/dev/ad2s1a is accepted by mountroot and the boot proceed. Than I can change the fstab accordingly to make the change permanent. My question are: 1) I've made any mistake ? 2) Without the boot -a flag, why the kernel ask me a device and even it is the correct one vfs_conf.c:vfs_mountroot_ask() give me the error code 6? Thanks Roberto ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Swapped disks and now stuck in the mountroot prompt
I run into the same problem: I've installed FreeBSD 4.9 on a ide0:0 (primary IDE, master hd) then ported the hard disk on a second PC and installed as ide1:0 (secondary IDE, master hd). When booting the kernel start probing devices but halts when it try to mount the root file system with the following message: mount root from ufs:/dev/ad0s1a root mount failed: 6 At the prompt I've tried with ufs:/dev/ad2s1a but it does not work. The problem is that the kernel (in some way that I do not know) is instructed to load /dev/ad0s1a as root file system (yes at this stage the config file /etc/fstab is not involved yet, becouse it is no available until the root file system will be mounted). The solution is to instruct the kernel with the right device: ad2s1a seems to be wrong... I'm working on it... Bye Roberto ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Swapped disks and now stuck in the mountroot prompt
Hi, I've installed FreeBSD 4.9 via FTP on my T22-laptop while having the hard disk as my first disk on it and then I had to put that disk into the ultrabay and thus have made it the second disk. I know, that all I have to do is probably to edit the /etc/fstab but I can't get there - I'm stuck at the mountroot prompt. I've tried all the possible combinations including the one which I'd expected to be correct: ufs:/dev/ad2s1a but they all fail with Root mount failed: 22. The ? at the mountroot prompt does show ad device. And the lines in the grub/conf on the 1st hard drive which I use to load that 2nd hard drive look like: title FreeBSD root (hd1,0,a) kernel /boot/loader title OpenBSD root (hd1,1,a) chainloader +1 (The OpenBSD has worked already - I had booted /bsd.rd, mounted the / and edited the /etc/fstab). I couldn't find the answer in the Handbook or on Google yet... Any help? Thank you Alex ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cannot boot, at mountroot prompt
Bob Collins [EMAIL PROTECTED] writes: I have a system running 5.0-RELEASE on an AMD 667Mhz processor with 256MB ram, Soyo mobo. Install was no trouble, and setup of X, KDE, MySQL, Apache went fine. I ran a setup of both xmms and mplayer as well. Then I went for an install of Webmin. Once webmin was complete, I was running in KDE, I closed the term window and the machine rebooted immediately, no shutdown, nothing. Question, does this sound like a bad drive, RAM, or perhaps my bad luck. Second question, how can I address the mountroot prompt? Per the instructions at the prompt, I put in ufs:/dev/ad0s1a and hit the return key. The system then reboots. To start with, you should definitely update your system to something more recent. 5.0 was, after all, a very early technology preview release from a branch that, after nearly a year, still isn't ready to produce a production release. Unless you have some (at least minimal) skills at tracking down these kinds of problems, you should probably move to the latest release, 4.9. That said, there will probably be some hints in a kernel dump. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
cannot boot, at mountroot prompt
I have a system running 5.0-RELEASE on an AMD 667Mhz processor with 256MB ram, Soyo mobo. Install was no trouble, and setup of X, KDE, MySQL, Apache went fine. I ran a setup of both xmms and mplayer as well. Then I went for an install of Webmin. Once webmin was complete, I was running in KDE, I closed the term window and the machine rebooted immediately, no shutdown, nothing. Question, does this sound like a bad drive, RAM, or perhaps my bad luck. Second question, how can I address the mountroot prompt? Per the instructions at the prompt, I put in ufs:/dev/ad0s1a and hit the return key. The system then reboots. Thanks Bob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (Fwd) mountroot
hi, exactly this is my problem.. i've read the 7.3 section of the handbook and searched also other forums and sites for this .. it seems i'm not the only one with this problem but i did not find somewhere an answer.. my lilo.conf looks like this: other=/dev/sdb1 table=/dev/sdb loader=/boot/chain.b label=FreeBSD what is going wrong?! mfg Alexandru On 20 Jun 2003 at 22:03, Viktor Lazlo wrote: Have you followed the applicable instructions from section 7.3.1 of the handbook? It give a sample format and instructions specifically for when linux and FreeBSD are on separate hard drives. Cheers, Viktor On Sat, 21 Jun 2003, Alexandru Savescu wrote: Hello BSD-lovers, i'm stuck on a tricky situation: i got FreeBSD 4.8-STABLE running smoothly on a SCSI disk, but i had to move the HDD on a multi-OS system, so i am heading this problem: there are 3 disks - ad0: IDE WDC-drive with a MSwinOS - da0: SCSI IBM-drive with Debian Linux - da1: SCSI IBM FreeBSD disk ad0 is the primary disk with lilo in the MBR lilo.conf uses boot=/dev/hda ... /dev/sda1 to boot the debianOS /dev/sdb1 to boot FreeBSD well, this is working fine for winOS and linux but FreeBSD returns this error lines: Root mount failed: 22 Mounting root from ufs:/dev/da2s1a Root mount failed: 22 Mounting root from ufs:/dev/da2a Root mount failed: 22 Manual root filesystem specification: mountroot i've tried all kind of combos like ufs:/dev/da1s1a but nothing worked out. what i still can't understand is why it's trying to mount /dev/da2 instead of /dev/da1 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [rofug] Re: (Fwd) mountroot
Hi, Please use english. Try inserting the following in /boot/loader.conf: root_disk_unit=1 From loader(8): root_disk_unit If the code which detects the disk unit number for the root disk is confused, eg. by a mix of SCSI and IDE disks, or IDE disks with gaps in the sequence (eg. no primary slave), the unit number can be forced by setting this variable. Alternatively you can try creating a file boot.config in the root filesystem containting: 2:da(1,a)/kernel See boot(8). Ady (@freebsd.ady.ro) On Sat, 21 Jun 2003, Camelia Nastase wrote: 1. pe mine personal ma enerveaza cross-posting'ul. 2. ai incercat cu boot -c, unload, boot-conf ? sau un ls dupa unload, sau lsdev sa vezi ce posibilitati ai? Hello BSD-lovers, i'm stuck on a tricky situation: i got FreeBSD 4.8-STABLE running smoothly on a SCSI disk, but i had to move the HDD on a multi-OS system, so i am heading this problem: there are 3 disks - ad0: IDE WDC-drive with a MSwinOS - da0: SCSI IBM-drive with Debian Linux - da1: SCSI IBM FreeBSD disk ad0 is the primary disk with lilo in the MBR lilo.conf uses boot=/dev/hda ... /dev/sda1 to boot the debianOS /dev/sdb1 to boot FreeBSD well, this is working fine for winOS and linux but FreeBSD returns this error lines: Root mount failed: 22 Mounting root from ufs:/dev/da2s1a Root mount failed: 22 Mounting root from ufs:/dev/da2a Root mount failed: 22 Manual root filesystem specification: mountroot i've tried all kind of combos like ufs:/dev/da1s1a but nothing worked out. what i still can't understand is why it's trying to mount /dev/da2 instead of /dev/da1 __ Send 'unsubscribe rofug' to [EMAIL PROTECTED] to unsubscribe -- Camelia Nastase Network Administrator Motto: All you have to do Departamentul Internet is want it bad enough ASTRAL TELECOM SA, Sucursala Cluj __ Send 'unsubscribe rofug' to [EMAIL PROTECTED] to unsubscribe ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mountroot
Hello BSD-lovers, i'm stuck on a tricky situation: i got FreeBSD 4.8-STABLE running smoothly on a SCSI disk, but i had to move the HDD on a multi-OS system, so i am heading this problem: there are 3 disks - ad0: IDE WDC-drive with a MSwinOS - da0: SCSI IBM-drive with Debian Linux - da1: SCSI IBM FreeBSD disk ad0 is the primary disk with lilo in the MBR lilo.conf uses boot=/dev/hda ... /dev/sda1 to boot the debianOS /dev/sdb1 to boot FreeBSD well, this is working fine for winOS and linux but FreeBSD returns this error lines: Root mount failed: 22 Mounting root from ufs:/dev/da2s1a Root mount failed: 22 Mounting root from ufs:/dev/da2a Root mount failed: 22 Manual root filesystem specification: mountroot i've tried all kind of combos like ufs:/dev/da1s1a but nothing worked out. what i still can't understand is why it's trying to mount /dev/da2 instead of /dev/da1 i would appreciate any advice! thank you in advance Alexandru Savescu ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mountroot Please Help / URGENT..
Date: 12-22-02 Operating System / Configuration: FreeBSD 4.6 with RAID 1 ( Mirrored ) Situation: I have 2 active drives running in the same machine at all times. In addition, I have 1 extra drive that sits on the shelf with a copy of the previous backup that I swap out with one of the other active drives every week. When I swap out the drive from the shelf with one of the drives in the machine upon booting it says array failure so I press Ctrl + F and re-create the array. After successful replication has taken place I reboot the machine and everything runs flawlessly as it should... However, here is the problem: The remaining drive that I leave on the shelf for additional backup will NOT boot up as a single drive to get data off that I need very badly... Upon booting it brings me to this prompt: === Manual root filesystem specification: fstype:device Mount device using filesystem fstype Example: ufs:/dev/da0s1a ? List valid disk boot devices empty line Abort manual input Mountroot === I then type: mountroot ufs:/dev/ar0s1a and receive this message: Mounting root from ufs:/dev/ar0s1a No such device 'ar' Getrootbyname failed mfs_mountroot: can't find rootvp root mount failed: 6 - I then type: mountroot ufs:/dev/ad0s1a and it lets me log in with read-only access and browsing is limited to the /root /dev /etc directory. I then 'cat' the FSTAB directory to see this configuration: /dev/ar0s1b none swap sw 0 0 /dev/ar0s1a / ufs rw 1 1 /dev/ar0s1e /usr ufs rw 2 2 /dev/acodoc /cdrom cd9660 ro,noauto 0 0 proc /proc procfs rw 0 0 - Would anyone able to help me out with this situation ? The data on the backup drive is VERY IMPORTANT and I can't get to it... I can be reached via email and I will reply immediately!! Please have the subject line pertaining to FreeBSD / Backup Drives or something comparable to that so I do not accidentally delete it thinking it is spam... [EMAIL PROTECTED] Thanks, Ethan _ MSN 8 with e-mail virus protection service: 3 months FREE*. http://join.msn.com/?page=features/virusxAPID=42PS=47575PI=7324DI=7474SU= http://www.hotmail.msn.com/cgi-bin/getmsgHL=1216hotmailtaglines_eliminateviruses_3mf To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: mountroot Please Help / URGENT..
I then type: mountroot ufs:/dev/ad0s1a and it lets me log in with read-only access and browsing is limited to the /root /dev /etc directory. once there, just type % mount / % mount /usr that will at least get you access to your data. -randall -- :// randall s. ehren :// voice 805.893.5632 :// systems administrator:// isber|survey|avss.ucsb.edu :// institute for social, behavioral, and economic research To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: mountroot Please Help / URGENT..
# [EMAIL PROTECTED] / 2002-12-23 01:23:53 +: Date: 12-22-02 Operating System / Configuration: FreeBSD 4.6 with RAID 1 ( Mirrored ) I have 2 active drives running in the same machine at all times. In addition, I have 1 extra drive that sits on the shelf with a copy of the previous backup that I swap out with one of the other active drives every week. When I swap out the drive from the shelf with one of the drives in the machine upon booting it says array failure so I press Ctrl + F and re-create the array. After successful replication has taken place I reboot the machine and everything runs flawlessly as it should... However, here is the problem: The remaining drive that I leave on the shelf for additional backup will NOT boot up as a single drive to get data off that I need very badly... Upon booting it brings me to this prompt: Manual root filesystem specification: fstype:device Mount device using filesystem fstype Example: ufs:/dev/da0s1a ? List valid disk boot devices empty line Abort manual input Mountroot I then type: mountroot ufs:/dev/ar0s1a and receive this message: Mounting root from ufs:/dev/ar0s1a No such device 'ar' Getrootbyname failed mfs_mountroot: can't find rootvp root mount failed: 6 right. when you plug the drive into a regular IDE controller it's not /dev/ar* anymore. I then type: mountroot ufs:/dev/ad0s1a and it lets me log in with read-only access right. the drive is ad0* now, and it's mounted read-only because the system assumes a problem, and stays on the safe side. and browsing is limited to the /root /dev /etc directory. right. see below. I then 'cat' the FSTAB directory to see this configuration: you mean /etc/fstab, right? it's fstab, not FSTAB (the case matters; I've seen someone rename the file to Fstab and then wonder what broke), and it's a file, not a directory. /dev/ar0s1b none swap sw 0 0 /dev/ar0s1a / ufs rw 1 1 /dev/ar0s1e /usr ufs rw 2 2 the system can't mount /usr because it is listed being in ar0s1e, but that device is not present now. /dev/acodoc /cdrom cd9660 ro,noauto 0 0 proc /proc procfs rw 0 0 Would anyone able to help me out with this situation ? The data on the backup drive is VERY IMPORTANT and I can't get to it... have you read the Handbook? http://www.freebsd.org/doc/handbook/mount-unmount.html also, you *do* know mount(8), why don't you use your knowledge? # mount -u /dev/ad0s1a / # mount /dev/ad0s1e /usr # sed -E 's/ar0/ad0/' /etc/fstab /tmp/fstab # cat /tmp/fstab (check that it's ok) # mv /tmp/fstab /etc (/etc/fstab should be root:wheel 644, chown/chmod it if it's not) # swapon -a and you're set. since you will most probably be in singleuser at this point, you'll want to finish the booting procedure: # exit -- If you cc me or remove the list(s) completely I'll most likely ignore your message.see http://www.eyrie.org./~eagle/faqs/questions.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: mountroot Please Help / URGENT..
- Original Message - From: Ethan Akins [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, December 23, 2002 2:23 AM Subject: mountroot Please Help / URGENT.. Operating System / Configuration: FreeBSD 4.6 with RAID 1 ( Mirrored ) Situation: I have 2 active drives running in the same machine at all times. In addition, I have 1 extra drive that sits on the shelf with a copy of the previous backup that I swap out with one of the other active drives every week. When I swap out the drive from the shelf with one of the drives in the machine upon booting it says array failure so I press Ctrl + F and re-create the array. Lemme guess, you're using a FastTrack RAID controller? I use the exact same method of backing up as you do (on my ASUS A7V333), down to the same rotation scheme even. :) The remaining drive that I leave on the shelf for additional backup will NOT boot up as a single drive to get data off that I need very badly... How odd. On my ASUS A7V333 board I can yank out either of the two disks, and even though the BIOS complains a bit about my array being in a critical state, it will still boot, of course. I say of course, for that is the whole point of having a RAID 1, right? That if one of the drives fails, you can continue with the other. Naturally, FreeBSD 4.7R still notices the drive missing from the array, but unless you checked the logs, you would not know it. Would anyone able to help me out with this situation ? Have you tried physically removing (disconnecting) the first drive? That may help. It could be a FreeBSD issue (though I doubt it; it is hard to imagine the difference between 4.6 and 4.7 would be this major). I have heard people say here that FreeBSD could not possibly mount the single drive partitions as they are part of an array. Well, I cannot speak for others, but there have been several occassions where I had to do exactly what you want: boot from the backup disk to retrieve data; and, like I said, unless I checked the logs, FreeBSD ran just as it always does: smoothly. :) - Mark To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
