Date: Tue, 27 Jun 2006 14:49:37 +0200 From: "Morten A. Middelthon" <morten@freenix.no> To: stable@freebsd.org Subject: Problem with filesystem on RAID5 array (fsck -b?) Message-ID: <20060627124937.GA72178@freenix.no>
next in thread | raw e-mail | index | archive | help
--PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 wi= th 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 arr= ay after replacing the broken disk did not work as it should, so after discuss= ing 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, -200345533= 7, -2003455336, -2003455335, -2003455334, -2003455333, -2003455332, -200345533= 1, -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, -154515295= 3, -1545152952, -1545152951, -1545152950, -1545152949, -1545152948, -154515294= 7, -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.=20 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=20 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 b= efore I create a new filesystem on it. --=20 Morten A. Middelthon Do not meddle in the affairs of dragons, 'cuz, like, you are crunchy and taste good with ketchup. --PEIAKu/WMn1b1Hv9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEoSlhvsz2LoKf32oRAljAAJ0c+B81mqcfIalrfnu6TAXgttbnAwCdF8BK vwLb/Bo261NEtHgGZxmXx9c= =mNnt -----END PGP SIGNATURE----- --PEIAKu/WMn1b1Hv9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060627124937.GA72178>