[SOLVED] Yikes, three drives unformatted?


Recommended Posts

I recently had a drive failure, and rebuilt my 750GB drive onto a new WD20EARS. After that completed, that new drive is showing as unformatted, as well as two others. Can anyone help?

 

I am using 4.7-beta. From what I understand, the only difference between 4.7-beta and 4.7 was the name, but I'll obviously upgrade if someone thinks that could fix it.

 

I've been trying to figure out what the problem is by reading on the forums, but I'm still unsure. Here is the output of some stuff I've tried running to get information:

 

root@Tower:~# fdisk -lu /dev/sdh; fdisk -lu /dev/sde; fdisk -lu /dev/sdl

Disk /dev/sdh: 2000.3 GB, 2000398934016 bytes
1 heads, 63 sectors/track, 62016336 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000

  Device Boot      Start         End      Blocks   Id  System
/dev/sdh1              64  3907029167  1953514552   83  Linux
Partition 1 does not end on cylinder boundary.

Disk /dev/sde: 1500.3 GB, 1500301910016 bytes
1 heads, 63 sectors/track, 46512336 cylinders, total 2930277168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000

  Device Boot      Start         End      Blocks   Id  System
/dev/sde1              64  2930277167  1465138552   83  Linux
Partition 1 does not end on cylinder boundary.

Disk /dev/sdl: 2000.3 GB, 2000398934016 bytes
1 heads, 63 sectors/track, 62016336 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x00000000

  Device Boot      Start         End      Blocks   Id  System
/dev/sdl1              64  3907029167  1953514552   83  Linux
Partition 1 does not end on cylinder boundary.

 

I tried running reiserfsck here. The same "no file or directory" response came back for md9 and md10.

 

root@Tower:~# reiserfsck --check /dev/md1
Will read-only check consistency of the filesystem on /dev/md1
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
Failed to open the device '/dev/md1': No such file or directory

 

root@Tower:~# reiserfsck --check /dev/sdh1
Will read-only check consistency of the filesystem on /dev/sdh1
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 Sat Nov 12 18:02:39 2011
###########
Replaying journal: Done.
Reiserfs journal '/dev/sdh1' in blocks [18..8211]: 0 transactions replayed
reiserfs_open_ondisk_bitmap: wrong either bitmaps number,
count of blocks or blocksize, run with --rebuild-sb to fix it
reiserfsck: Could not open bitmap

 

root@Tower:~# reiserfsck --check /dev/sde1
Will read-only check consistency of the filesystem on /dev/sde1
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes

reiserfs_open: the reiserfs superblock cannot be found on /dev/sde1.
Failed to open the filesystem.

If the partition table has not been changed, and the partition is
valid  and  it really  contains  a reiserfs  partition,  then the
superblock  is corrupted and you need to run this utility with
--rebuild-sb.

 

root@Tower:~# reiserfsck --check /dev/sdl1

Will read-only check consistency of the filesystem on /dev/sdl1
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes

reiserfs_open: the reiserfs superblock cannot be found on /dev/sdl1.
Failed to open the filesystem.

If the partition table has not been changed, and the partition is
valid  and  it really  contains  a reiserfs  partition,  then the
superblock  is corrupted and you need to run this utility with
--rebuild-sb.

 

root@Tower:~# dd if=/dev/sdh count=195 | od -c -A d |  sed  30q
0000000  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0000448  \0  \0 203  \0  \0  \0   @  \0  \0  \0   p 210 340 350  \0  \0
0000464  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0000496  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0   U 252
0000512  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0097792   P 036 311  \b   $ 331  \0  \0   * 337 317 005  \0  \0  \0  \0
0097808  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0 375   V   9   m
0097824  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0097856  \0  \0  \0  \0  \0  \0 222 021  \0  \0  \0  \0 311 001  \0  \0
0097872  \0  \0  \0  \0 226 236   - 225 367   =  \f 262   '   4   [   @
0097888 022 203   4 256  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
0097904  \0  \0  \0  \0 001  \0  \0  \0 030   = 001  \0  \0  \0  \0  \0
0097920  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0098000 275   I  \0  \0 322   w  \0  \0   N   I  \0  \0 322   w  \0  \0
0098016   N   I  \0  \0 376   w  \0  \0   N   I  \0  \0 376   w  \0  \0
*
0098048   N   I  \0  \0 364   v  \0  \0   %   v  \0  \0 353   x  \0  \0
0098064 307   x  \0  \0 353   x  \0  \0 307   x  \0  \0 353   x  \0  \0
*
0098112 307   x  \0  \0 353   x  \0  \0 307   x  \0  \0   + 205  \0  \0
0098128 366 205  \0  \0   + 205  \0  \0 366 205  \0  \0   + 205  \0  \0
*
0098160 366 205  \0  \0   + 205  \0  \0 366 205  \0  \0   * 205  \0  \0
0098176 366 205  \0  \0   n   "  \0  \0 200   "  \0  \0   n   "  \0  \0
0098192 200   "  \0  \0   n   "  \0  \0 200   "  \0  \0   n   "  \0  \0
195+0 records in
195+0 records out
99840 bytes (100 kB) copied, 0.446865 s, 223 kB/s

 

root@Tower:~# dd if=/dev/sde count=195 | od -c -A d |  sed  30q
195+0 records in
195+0 records out
99840 bytes (100 kB) copied, 0.00347958 s, 28.7 MB/s
0000000  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0000448  \0  \0 203  \0  \0  \0   @  \0  \0  \0 360   z 250 256  \0  \0
0000464  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0000496  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0   U 252
0000512  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0097792   ^ 017 325 025 301   l 305 001 241 006   K 025 022  \0  \0  \0
0097808  \0  \0  \0  \0  \0      \0  \0  \0 004  \0  \0   n 221       #
0097824 204 003  \0  \0 036  \0  \0  \0  \0  \0  \0  \0  \0 020 314 003
0097840 002  \0 001  \0   R   e   I   s   E   r   2   F   s  \0  \0  \0
0097856 003  \0  \0  \0 005  \0 253   + 002  \0  \0  \0 026 001  \0  \0
0097872 001  \0  \0  \0   . 265 235   T 321 033   G   g 225   M 226   o
0097888 324   0   u 202  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
0097904  \0  \0  \0  \0   ]  \0 036  \0  \r 333   @   M  \0   N 355  \0
0097920  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0097984  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0 001  \0  \0  \0
0098000 365 252  \0  \0   [ 251  \0  \0 224 251  \0  \0   [ 251  \0  \0
0098016 224 251  \0  \0   [ 251  \0  \0 224 251  \0  \0   [ 251  \0  \0
*
0098048 224 251  \0  \0   [ 251  \0  \0 224 251  \0  \0   D 247  \0  \0
0098064   v 247  \0  \0   D 247  \0  \0   v 247  \0  \0   D 247  \0  \0
*
0098176   v 247  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
0098192  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0099840

 

root@Tower:~# dd if=/dev/sdl count=195 | od -c -A d |  sed  30q
195+0 records in
195+0 records out
99840 bytes (100 kB) copied, 0.00199799 s, 50.0 MB/s
0000000  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0000448  \0  \0 203  \0  \0  \0   @  \0  \0  \0   p 210 340 350  \0  \0
0000464  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0000496  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0   U 252
0000512  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0097792 016 021 034 035 345 265 305 001 213 331 204 020 022  \0  \0  \0
0097808  \0  \0  \0  \0  \0      \0  \0  \0 004  \0  \0 223 307 031   N
0097824 204 003  \0  \0 036  \0  \0  \0  \0  \0  \0  \0  \0 020 314 003
0097840 002  \0 001  \0   R   e   I   s   E   r   2   F   s  \0  \0  \0
0097856 003  \0  \0  \0 005  \0   9   : 002  \0  \0  \0 337  \0  \0  \0
0097872 001  \0  \0  \0 270   + 260 301   &   &   K 325 262   y 315   /
0097888 306 263   A   ,  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
0097904  \0  \0  \0  \0   \  \0 036  \0 025 346   A   M  \0   N 355  \0
0097920  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
*
0097984  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0 001  \0  \0  \0
0098000   H 343  \0  \0 211 336  \0  \0 332 340  \0  \0 211 336  \0  \0
0098016 332 340  \0  \0 245 336  \0  \0 332 340  \0  \0 245 336  \0  \0
*
0098048 332 340  \0  \0 257 337  \0  \0 261 337  \0  \0 257 337  \0  \0
0098064 261 337  \0  \0 257 337  \0  \0 261 337  \0  \0 257 337  \0  \0
*
0098112 261 337  \0  \0 257 337  \0  \0 261 337  \0  \0   o   "  \0  \0
0098128 200   "  \0  \0   o   "  \0  \0 200   "  \0  \0   o   "  \0  \0
*
0098160 200   "  \0  \0   o   "  \0  \0 200   "  \0  \0   n   "  \0  \0
0098176 200   "  \0  \0   n   "  \0  \0 200   "  \0  \0   n   "  \0  \0

 

If there's any other commands I can run to give more information, please let me know. Any help in diagnosing and solving this is much appreciated.

 

Thanks,

Scott

syslog-2011-11-12.txt

Link to comment

/dev/sdh does not seem to have a reiserfs.  The other two do, but starting on sector 63, not sector 64.

 

Your MBR on those disks needs to be fixed to point to the correct partition start.  DO NOT REBUILD THE SUPERBLOCK...  the superblock is probably just fine, the MBR is pointing to a start sector of 64, not 63.

 

If the file-system actually starts on sector 63 you would see:

0097840 220  \0 002  \0  R  e  I  s  E  r  2  F  s  \0  \0  \0

 

You can use the utility I posted in the other thread to fix the MBR on two of the disks that seem to have a reiserfs.

unraid_partition_disk.sh -p /dev/sdl

unraid_partition_disk.sh -p /dev/sde

 

Once fixed so they point to sector 63 as their start, they should show properly when you reboot the server.

(A stop array followed by a start array might be all that is needed, try that before a full reboot)

 

DO NOT PRESS THE FORMAT BUTTON.  (you probably knew that, but figured I'd say it anyway)

 

You can probably run the same command to fix the third disk too.  Its "data" seems to start at the same ponit at address 0097792, just like the other two, so it probably also needs to be corrected.   

unraid_partition_disk.sh -p /dev/sdh

It is unlikely this disk will show properly, but at least it will have a chance.

 

Is there something special about this third disk you did not mention?  Was it specifically partitioned on sector 64?

 

the unraid_partition_disk.sh script is described in this post:

http://lime-technology.com/forum/index.php?topic=15385.msg144822#msg144822

 

In your case, since you want a sector 63 start, (on at least the first two disks) you do NOT want to use the "-A" option as in the other post.

 

Please report this to lime-tech as a BUG.  It exists in 4.7 as well and could result in a loss of data if you did not take the time too seek help.  Apparently, in some conditions, unRAID is re-writing the MBRs on existing disks, and doing it incorrectly, pointing to the wrong starting sector.

 

Joe L.

Link to comment

Thanks for the response, Joe.

 

That utility fixed disks 9 and 10 just as you said. However, it didn't do the job for disk 1.

 

I'm not sure if disk 1 was specifically partitioned on sector 64. I'm pretty sure that I ran the preclear script with the -A option. Did I just do it wrong, or is that actually a bug?

 

Anyhow, do you have a recommendation of how I should proceed with disk 1?

syslog-2011-11-122.txt

Link to comment

Thanks for the response, Joe.

 

That utility fixed disks 9 and 10 just as you said. However, it didn't do the job for disk 1.

 

I'm not sure if disk 1 was specifically partitioned on sector 64. I'm pretty sure that I ran the preclear script with the -A option. Did I just do it wrong, or is that actually a bug?

 

Anyhow, do you have a recommendation of how I should proceed with disk 1?

well...

 

disk1 did not show signs of having a reiserfs file system on it.

 

If you specifically used the -A option on it, then you would want the MBR to point to sector 64, not 63.

 

Again you can fix the MBR to point to sector 64, but this time by using the "-A" option to the unraid_partition_disk.sh command

unraid_partition_disk.sh -A -p /dev/sdh

 

Once you have the correct partition start, you can run

reiserfsck --check /dev/sdh1

 

It almost sounds as if you need to un-assign disk1, start the array with it un-assigned, then re-assign it, and re-construct it once more.

It sounds as if the first time you re-constructed it, the other disks were not pointing to the correct partition start, so you re-constructed garbage instead of actual files.

 

Now that the other disks are pointing to their correct partition starts, the re-construction might work better.

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.