On Sat, Apr 18, 2009 at 07:31:25AM +1000, Greg 'groggy' Lehey wrote: > On Friday, 17 April 2009 at 18:44:27 +0400, Alex Keda wrote: > > After boot, before mount, disk da0 lost, or some partition > > lost/uninitialised > > > > ... > > umass0:0:0:-1: Attached to scbus0 > > da0 at umass-sim0 bus 0 target 0 lun 0 > > da0: <Hitachi HTS541680J9SA00 > Fixed Direct Access SCSI-2 device > > da0: 40.000MB/s transfers > > da0: 76319MB (156301488 512 byte sectors: 255H 63S/T 9729C) > > Trying to mount root from ufs:/dev/da0s1a > > > > Manual root filesystem specification: > > <fstype>:<device> Mount <device> using filesystem <fstype> > > eg. ufs:da0s1a > > ? List valid disk boot devices > > <empty line> Abort manual input > > FWIW, I'm experiencing a similar problem with a USB stick. I get an > error 2 on the device entry (also /dev/da0s1a), followed by a panic > with an incomplete stack backtrace. I'm going to try remote debugging > to get more information; watch this space. There's a thread from a few days ago regarding this with a subject of "Booting from usb hard disk". There is a patch that allows me to boot, but there are still problems (I have to select usb:da0s1a at the manual root filesystem prompt still.) http://people.freebsd.org/~thompsa/root_wait.diff This was committed but then backed out as a less-than-perfect solution. Someone said that setting kern.cam.scsi_delay=10000 in loader.conf (or with option 6 at the boot prompt) helped them, but that was not the case for me. MarcusReceived on Fri Apr 17 2009 - 21:04:00 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:46 UTC