Hello Greg,

On Tue, Aug 06, 2002 at 02:28:18PM -0600, Greg Oster wrote:
>
> On openbsd-misc you said:
> > the system starts booting but drops into ddb after these messages:
> > Kernelized RAIDframe activated
> > RAID autoconfigure
> > Configuring raid0:
> > [snip]
> > raid0 (root) <-- ok !
> > [snip]
> > Configuring raid1:
> > [snip]
> > raid1 (root) <-- ???
> > dkcsum: wd0 matched BIOS disk 80
> > dkcsum: wd1 matched BIOS disk 81
> > dkcsum: wd2 matched BIOS disk 82 <-- meanwhile I reconnected wd2
> > rootdev = 0x1300 rrootdev = 0x3600 rawdev = 0x36202
> > panic: root filesystem has size 0
> > Stopped at: _Debugger+0x4: movl %ebp,%esp
> > ddb>
>
> Can you ship me the bits you cut out from the "[snip]" parts above?
> Of all the good debugging stuff you had in your message, the bits most
> useful to me were the ones you cut :)

sorry I don't have them anymore. the thing is during one of the numerous email
exchanges I had with tdeval, he hinted that it may be a pb with the secondary
IDE bus. I moved wd1 to the primary channel (with wd0) and this time I paid
attention to some "uncorrectable blah fsbn 32 of 32-33 blah" errors that I
thought were insignificant since wd2 is a UDMA4 & wd1 UDMA5 and they connected
to the same channel with a UDMA5 cable. I decided to check wd1 with a disk
verification utility and this was the solution to my pbs: bad sectors.
repairing the bad sectors solved the panic pb. the box now runs fine with the
disks on separate channels.

cheers.

-- 
Saad Kadhi 
[pgp keyid: 35592A6D http://pgp.mit.edu]
[pgp fingerprint: BF7D D73E 1FCF 4B4F AF63  65EB 34F1 DBBF 3559 2A6D]
# booth slave for hire

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]