Re: bad primary superblock - bad magic number !!!

[Leo Davis <leo1783@xxxxxxxxx>]

Many Thanks.

 

I agree. I destroy and re-create raid and everything would show up GOOD, only for it to break again.

So was wondering whether those traces would point to anything.... my prime suspect is hard drives, but those xfs msgs confused me.

Apologies for posting before carrying put more tests.

 

Thanks,

leo

---

From: Eric Sandeen <sandeen@xxxxxxxxxxx>
To: stress_buster <leo1783@xxxxxxxxx>
Cc: xfs@xxxxxxxxxxx
Sent: Mon, May 10, 2010 4:42:13 PM
Subject: Re: bad primary superblock - bad magic number !!!

stress_buster wrote:
> my hp proliant DL185 server hangs/crashes and sometimes do not boot
> correctly...
>
> [root@localhost dev]# xfs_repair -n /dev/cciss/c0d0p1
> Phase 1 - find and verify superblock...
> bad primary superblock - bad magic number !!!
>
> attempting to find secondary superblock...
> .....................................................................................Sorry,
> could not find valid secondary superblock
> Exiting now.
>
> [root@localhost dev]# xfs_repair -n /dev/cciss/c0d2
> Phase 1 - find and verify superblock...
> superblock read failed, offset 0, size 524288, ag 0, rval -1
>
> fatal error -- Input/output error
>
>
> [root@localhost dev]# xfs_db /dev/cciss/c0d0p1
> xfs_db: /dev/cciss/c0d0p1 is not a valid XFS filesystem (unexpected SB magic
> number 0x00000000)
>
> The next time, server didnt even boot up alright
>
> i've managed to capture the msgs & traces dumped to console. See below
>
>
> end_request: I/O error, dev cciss/c0d2, sector 0
> end_request: I/O error, dev cciss/c0d2, sector 0
> end_request: I/O error, dev cciss/c0d2, sector 1
> Quote:
> ciss: cmd f6c00000 has CHECK CONDITION sense key = 0x4
> end_request: I/O error, dev cciss/c0d3, sector 0
> cciss: cmd f6c00000 has CHECK CONDITION sense key = 0x4
> end_request: I/O error, dev cciss/c0d3, sector 0

You seem to have serious storage problems that are not XFS related.

You'll need to get that resolved.

-Eric