<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><DIV>Many Thanks.</DIV>
<DIV> </DIV>
<DIV>I agree. I destroy and re-create raid and everything would show up GOOD, only for it to break again.</DIV>
<DIV>So was wondering whether those traces would point to anything.... my prime suspect is hard drives, but those xfs msgs confused me. </DIV>
<DIV>Apologies for posting before carrying put more tests.</DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV>leo<BR></DIV>
<DIV style="FONT-FAMILY: times new roman, new york, times, serif; FONT-SIZE: 12pt"><BR>
<DIV style="FONT-FAMILY: arial, helvetica, sans-serif; FONT-SIZE: 13px"><FONT size=2 face=Tahoma>
<HR SIZE=1>
<B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Eric Sandeen <sandeen@sandeen.net><BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> stress_buster <leo1783@yahoo.com><BR><B><SPAN style="FONT-WEIGHT: bold">Cc:</SPAN></B> xfs@oss.sgi.com<BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> Mon, May 10, 2010 4:42:13 PM<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> Re: bad primary superblock - bad magic number !!!<BR></FONT><BR>stress_buster wrote:<BR>> my hp proliant DL185 server hangs/crashes and sometimes do not boot<BR>> correctly...<BR>> <BR>> [root@localhost dev]# xfs_repair -n /dev/cciss/c0d0p1<BR>> Phase 1 - find and verify superblock...<BR>> bad primary superblock - bad magic number !!!<BR>> <BR>> attempting to find secondary superblock...<BR>> .....................................................................................Sorry,<BR>> could not find valid secondary
superblock<BR>> Exiting now.<BR>> <BR>> [root@localhost dev]# xfs_repair -n /dev/cciss/c0d2<BR>> Phase 1 - find and verify superblock...<BR>> superblock read failed, offset 0, size 524288, ag 0, rval -1<BR>> <BR>> fatal error -- Input/output error<BR>> <BR>> <BR>> [root@localhost dev]# xfs_db /dev/cciss/c0d0p1<BR>> xfs_db: /dev/cciss/c0d0p1 is not a valid XFS filesystem (unexpected SB magic<BR>> number 0x00000000)<BR>> <BR>> The next time, server didnt even boot up alright<BR>> <BR>> i've managed to capture the msgs & traces dumped to console. See below<BR>> <BR>> <BR>> end_request: I/O error, dev cciss/c0d2, sector 0<BR>> end_request: I/O error, dev cciss/c0d2, sector 0<BR>> end_request: I/O error, dev cciss/c0d2, sector 1<BR>> Quote:<BR>> ciss: cmd f6c00000 has CHECK CONDITION sense key = 0x4<BR>> end_request: I/O error, dev cciss/c0d3, sector 0<BR>> cciss: cmd f6c00000 has
CHECK CONDITION sense key = 0x4<BR>> end_request: I/O error, dev cciss/c0d3, sector 0<BR><BR>You seem to have serious storage problems that are not XFS related.<BR><BR>You'll need to get that resolved.<BR><BR>-Eric<BR></DIV></DIV></div><br>
</body></html>