[Savannah-hackers-public] [gnu.org #447573] Savannah is down v2

[Ward Vandewege via RT]

> [beuc - Sat May 30 03:30:01 2009]:
> 
> Hi,
> 
> Savannah was unreachable again, with the same errors:
> 
> [50919.316366] EXT3-fs error (device md3): ext3_get_inode_loc: unable
> to read in
> ode block - inode=54200245, block=108396607
> [50919.317501] EXT3-fs error (device md3): ext3_get_inode_loc: unable
> to read in
> ode block - inode=60835372, block=121667635
> [50919.316366] EXT3-fs error (device md3): ext3_get_inode_loc: unable
> to read in
> ode block - inode=60835372, block=121667635
> [50919.316366] EXT3-fs error (device md3): ext3_get_inode_loc: unable
> to read in
> ode block - inode=45304252, block=90603599
> [50919.316366] EXT3-fs error (device md3): ext3_get_inode_loc: unable
> to read in
> ode block - inode=54200420, block=108396613
> [50919.316366] EXT3-fs error (device md3): ext3_get_inode_loc: unable
> to read in
> ode block - inode=54200245, block=108396607
> [50919.316366] EXT3-fs error (device md3): ext3_get_inode_loc: unable
> to read in
> ode block - inode=60835372, block=121667635
> [50919.316366] EXT3-fs error (device md3): ext3_get_inode_loc: unable
> to read in
> ode block - inode=60835372, block=121667635
> [50919.318106] EXT3-fs error (device md3): ext3_get_inode_loc: unable
> to read in
> ode block - inode=45304252, block=90603599
> [50919.318448] EXT3-fs error (device md3): ext3_get_inode_loc: unable
> to read in
> ode block - inode=54200420, block=108396613
> [50926.450881] EXT3-fs error (device md3): ext3_get_inode_loc: unable
> to read in
> ode block - inode=48185395, block=96370691
> [50926.450881] EXT3-fs error (device md3): ext3_get_inode_loc: unable
> to read in
> ode block - inode=48185395, block=96370691
> 
> 
> It doesn't reboot either:
> 
>    6144 MB Detected
> 
> ProLiant System BIOS - P29 (03/25/2003)
> Copyright 1982, 2003 Hewlett-Packard Development Group, L.P.
> 
> 
> Processor 1 initialized at 2.80 GHz/400 MHz(512 Kbyte L2)
> Processor 2 initialized at 2.80 GHz/400 MHz(512 Kbyte L2)
> 
>  207-Memory Configuration Warning - DIMM In DIMM Socket 1A.
> >  does not have Primary Width of 4 and only supports standard ECC.
>  207-Memory Configuration Warning - DIMM In DIMM Socket 2A.
> >  does not have Primary Width of 4 and only supports standard ECC.
>  207-Memory Configuration Warning - DIMM In DIMM Socket 3B.
> >  does not have Primary Width of 4 and only supports standard ECC.
>  207-Memory Configuration Warning - DIMM In DIMM Socket 4B.
> >  does not have Primary Width of 4 and only supports standard ECC.
>  207-Memory Configuration Warning - DIMM In DIMM Socket 5C.
> >  does not have Primary Width of 4 and only supports standard ECC.
>  207-Memory Configuration Warning - DIMM In DIMM Socket 6C.
> >  does not have Primary Width of 4 and only supports standard ECC.

I saw that yesterday and looked around; from what I can tell this memory
is not exactly the right type for the machine. But since we have not
changed it, my guess is that it's been like this from day one, which
means it can't be *that* horrible. It's complaining about all six memory
slots, each of which have a 1GB stick in them I believe.

The manual says:

Error Code                       

207-Memory Configuration
Warning - DIMM In DIMM Socket
X does not have Primary Width of
4 and only supports standard
ECC.

Audible Possible Problem       
Installed DIMMs have
a primary width of x8.   

Possible Action
Install DIMMs that have a
primary width of x4.

Looks like getting the right kind of ram would be   

> Advanced Memory Protection Mode: Advanced ECC Support
> Redundant ROM Detected - This system contains a valid backup system
> ROM.
> 
> 
> 602-Diskette Boot Record Error
> 
> 
> Maybe it tries to boot on the USB drive, 

Yes, this is a ridiculous bios bug. We need to disable diskette/usb
booting from the bios config screen, but you can't get there because
that only pops up after it gets beyond this point....

Thanks,
Ward.

-- 
Ward Vandewege <address@hidden>
Free Software Foundation - Senior System Administrator