bad primary superblock - bad magic number !!!
Eric Sandeen
sandeen at sandeen.net
Mon May 10 10:42:13 CDT 2010
stress_buster wrote:
> my hp proliant DL185 server hangs/crashes and sometimes do not boot
> correctly...
>
> [root at 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 at 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 at 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
More information about the xfs
mailing list