[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: -current dmesg changes: aprintification adding spaces; findrooterror
On Mon, Apr 07, 2008 at 08:44:43AM +0100, Iain Hibbert wrote:
> are there any other disk devices present? I get something like that if I
> have a CF card inserted at boot, and the block number printed is the
> offset of my root device wd0a.
a: 558763632 102398310 4.2BSD 2048 16384 0 # (Cyl. 101585*-
and the error message is
findroot: unable to read block 102398311
and I do have a
sd0 at scsibus0 target 0 lun 0: <Meizu, MiniPlayer, 1.00> disk removable
sd0: 7820 MB, 7840 cyl, 16 head, 32 sec, 512 bytes/sect x 16015360 sectors
connected during boot, so you get full points here.
> I have supposed that it is looking for the root block on each drive but is
> unable to read that block on the CF card because it doesn't exist.
I have some more drives connected, wd1-wd4, but those are all big
enough that the block really exists.
Main Index |
Thread Index |