Problem with filesystem on RAID5 array (fsck -b?)
Morten A. Middelthon
morten at freenix.no
Tue Jun 27 12:50:22 UTC 2006
Hi list,
I'm running FreeBSD 6.1-RELEASE-p2 on a Dell PowerEdge 1850 with an attached
Dell PowerVault 220S disk cabinet. The cabinet has two RAID5 arrays each with
6 x 300GB SCSI disks. The RAID controller is a Dell PERC4/DC using the amr
driver. Two days ago a disk failed in one of the arrays. Rebuilding the array
after replacing the broken disk did not work as it should, so after discussing
our options with Dell support they recommended I should delete the array on
the controller BIOS, then create a new identical array without initializing
it. According to their theory the data should be intact. Unfortunately, that
doesn't seem to be the case. When FreeBSD boots I get an "UNEXPECTED
INCONSISTENCY" error message when the filesystem is mounted, and then I have
to run fsck manually. When running fsck I get this message:
------------------------------------------------------------------
kepler:~# fsck -y /dev/amrd1s1d
** /dev/amrd1s1d
CANNOT READ BLK: -1365437920
CONTINUE? yes
THE FOLLOWING DISK SECTORS COULD NOT BE READ: 2929529376, 2929529377,
2929529378, 2929529379,
LOOK FOR ALTERNATE SUPERBLOCKS? yes
32 is not a file system superblock
458302416 is not a file system superblock
916604800 is not a file system superblock
1374907184 is not a file system superblock
1833209568 is not a file system superblock
CANNOT SEEK BLK: -2003455344
CONTINUE? yes
CANNOT READ BLK: -2003455344
CONTINUE? yes
CANNOT SEEK BLK: -2003455344
CONTINUE? yes
THE FOLLOWING DISK SECTORS COULD NOT BE READ: -2003455344, -2003455343,
-2003455342, -2003455341, -2003455340, -2003455339, -2003455338, -2003455337,
-2003455336, -2003455335, -2003455334, -2003455333, -2003455332, -2003455331,
-2003455330, -2003455329,
CANNOT SEEK BLK: -1545152960
CONTINUE? yes
CANNOT READ BLK: -1545152960
CONTINUE? yes
CANNOT SEEK BLK: -1545152960
CONTINUE? yes
THE FOLLOWING DISK SECTORS COULD NOT BE READ: -1545152960, -1545152959,
-1545152958, -1545152957, -1545152956, -1545152955, -1545152954, -1545152953,
-1545152952, -1545152951, -1545152950, -1545152949, -1545152948, -1545152947,
-1545152946, -1545152945,
SEARCH FOR ALTERNATE SUPER-BLOCK FAILED. YOU MUST USE THE
-b OPTION TO FSCK TO SPECIFY THE LOCATION OF AN ALTERNATE
SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck(8).
------------------------------------------------------------------
However, the man page does not mention any '-b' option.
disklabel says:
------------------------------------------------------------------
disklabel /dev/amrd1s1d
# /dev/amrd1s1d:
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
c: 2929661532 63 unused 0 0 # "raw" part, don't
edit
d: 2929661532 63 4.2BSD 2048 16384 28528
partition c: partition extends past end of unit
disklabel: partition c doesn't start at 0!
disklabel: An incorrect partition c may cause problems for standard system
utilities
partition d: partition extends past end of unit
------------------------------------------------------------------
I'm guessing my data is lost, but I thought I'd check with you guys first before I
create a new filesystem on it.
--
Morten A. Middelthon
Do not meddle in the affairs of dragons, 'cuz,
like, you are crunchy and taste good with ketchup.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20060627/7806f956/attachment.pgp
More information about the freebsd-stable
mailing list