Re: USB disk boot issues
On Mon, Apr 5, 2010 at 4:24 PM, Boris Samorodov b...@ipt.ru wrote: On Thu, 1 Apr 2010 07:38:53 -0500 Peter Steele wrote: We clone systems from specially prepared USB flash sticks and this all works well, except that occasionally the flash stick fails to boot. It fails at the mount root step, saying that it cannot mount the specified root partition. We use a labeled partition on the disk to make it device independent, so we have something like /dev/label/usbroot / ufs rw 1 1 in our fstab. When it fails it doesn't recognize this device, and even ? doesn't list it as one of the available devices. If we reboot, it's likely the problem won't occur again. It seems to be some kind of timing issue. Is this a known problem? You can try to solve the problem by: - # echo kern.cam.boot_delay=1 /boot/loader.conf - above did not work for me, however this did: kern.cam.scsi_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: USB disk boot issues
On Thu, 1 Apr 2010 07:38:53 -0500 Peter Steele wrote: We clone systems from specially prepared USB flash sticks and this all works well, except that occasionally the flash stick fails to boot. It fails at the mount root step, saying that it cannot mount the specified root partition. We use a labeled partition on the disk to make it device independent, so we have something like /dev/label/usbroot /ufsrw 1 1 in our fstab. When it fails it doesn't recognize this device, and even ? doesn't list it as one of the available devices. If we reboot, it's likely the problem won't occur again. It seems to be some kind of timing issue. Is this a known problem? You can try to solve the problem by: - # echo kern.cam.boot_delay=1 /boot/loader.conf - -- 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: USB disk boot issues
You can try to solve the problem by: - # echo kern.cam.boot_delay=1 /boot/loader.conf - We've put a pretty sizeable delay already directly in the kernel. There is now a noticeable pause before the mount root step is about to be performed. We don't see the problem often now, but even with this delay it still occasionally happens. The problem is that when a system is rebooted programmatically there isn't anyone around to go to the console and reboot manually. It would be nice to be able to reboot a system and have confidence it will actually reboot... ___ 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: USB disk boot issues
On 4/1/10, Peter Steele pste...@maxiscale.com wrote: We clone systems from specially prepared USB flash sticks and this all works well, except that occasionally the flash stick fails to boot. It fails at the mount root step, saying that it cannot mount the specified root partition. We use a labeled partition on the disk to make it device independent, so we have something like /dev/label/usbroot /ufsrw 1 1 in our fstab. When it fails it doesn't recognize this device, and even ? doesn't list it as one of the available devices. If we reboot, it's likely the problem won't occur again. It seems to be some kind of timing issue. Is this a known problem? Yes, it is. ___ 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
USB disk boot issues
We clone systems from specially prepared USB flash sticks and this all works well, except that occasionally the flash stick fails to boot. It fails at the mount root step, saying that it cannot mount the specified root partition. We use a labeled partition on the disk to make it device independent, so we have something like /dev/label/usbroot /ufsrw 1 1 in our fstab. When it fails it doesn't recognize this device, and even ? doesn't list it as one of the available devices. If we reboot, it's likely the problem won't occur again. It seems to be some kind of timing issue. Is this a known problem? ___ 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
