TheMantis Posted May 23, 2016 Share Posted May 23, 2016 I have a disk that has been ejected from the array and is now showing as an unassigned, unformatted disk. After starting the array in maintenance mode I've run an Fsck check with the following outcome: Will read-only check consistency of the filesystem on /dev/sdq1 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Mon May 23 12:15:51 2016 ########### Replaying journal: Done. Reiserfs journal '/dev/sdq1' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 740460 Internal nodes 4405 Directories 169 Other files 3080 Data block pointers 748915833 (514457 of them are zero) Safe links 0 Following that I ran fdisk -lu /dev/sdq and got the following output: WARNING: GPT (GUID Partition Table) detected on '/dev/sdq'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sdq: 4000.8 GB, 4000787030016 bytes 256 heads, 63 sectors/track, 484501 cylinders, total 7814037168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdq1 1 4294967295 2147483647+ ee GPT Partition 1 does not start on physical sector boundary. From my extremely limited knowledge it looks like the data on this disk is good but something has happened to the formatting causing unRAID to think the disk is unformatted. Any help is appreciated. Diagnostic file is attached tower-diagnostics-20160523-1609.zip Quote Link to comment
Squid Posted May 23, 2016 Share Posted May 23, 2016 I'm going to leave the actual answer to somebody smarter than myself, but I will point out one thing: When running file system checks, always refer to the device as /dev/mdX (X = drive #) as this keeps the parity information valid at all times whereas referring to them as /dev/sdX will invalidate the parity information Quote Link to comment
JorgeB Posted May 23, 2016 Share Posted May 23, 2016 The emulated disk11 is the one showing unmountable, you checked fs for actual disk11, which is was dropped from the array with good reason: Device Model: WDC WD40EFRX-68WT0N0 Serial Number: WD-WCC4E1719266 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 2 -check fs for /dev/md11 -hopefully it will mount -rebuild disk11 to a new spare -if needed mount old disk11 outside the array and compare data to the rebuilt one Quote Link to comment
trurl Posted May 23, 2016 Share Posted May 23, 2016 The emulated disk11 is the one showing unmountable, you checked fs for actual disk11, which is was dropped from the array with good reason: Device Model: WDC WD40EFRX-68WT0N0 Serial Number: WD-WCC4E1719266 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 2 -check fs for /dev/md11 -hopefully it will mount -rebuild disk11 to a new spare -if needed mount old disk11 outside the array and compare data to the rebuilt one Be sure to do this in the order johnnie gave. If you just jump ahead to rebuilding the disk you will rebuild an unmountable disk. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.