Previously working drives now show up unformatted


Recommended Posts

I have recently had a motherboard die. Previous to it's demise, unRaid was functioning flawlessly. Since I have replaced it, my 2 data drives (sda and sdb) now both show as being unformatted. I could really use some help in getting the data accessible again on these two WD 2TB drives.

 

I read through the thread recently posted http://lime-technology.com/forum/index.php?topic=15385.0 regarding a similar issue, however the results of my testing as suggested by Joe was slightly different and, since I can't understand the results anyway, before I screw this up more I wanted to get people's input... (HELP JOE!!!!)

 

For the sake of honesty, I contacted Tom initially - thank you Tom for your time, and he reccommended that I use the reiserfsck --rebuild function. Which I did on /dev/sda and it now has a different message from the test results, but still isn't functional. I do have a valid parity.

 

Thanks,

Matt

syslog.txt

reiserfsck_results_sda1_sdb1.txt

reiserfsck_results_on_md1_md2.txt

fdisk_results.txt

Link to comment

Here are the results of

fdisk -lu /dev/sda

fdisk -lu /dev/sdb

 

Server login: root
Linux 3.1.0-unRAID.
root@Server:~# fdisk -lu /dev/sda

Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
1 heads, 63 sectors/track, 62016336 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xef18d6cd

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1              63  3907029167  1953514552+  83  Linux
Partition 1 does not end on cylinder boundary.
root@Server:~# fdisk -lu /dev/sdb

Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
1 heads, 63 sectors/track, 62016336 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xef18d6cf

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1              63  3907029167  1953514552+  83  Linux
Partition 1 does not end on cylinder boundary.
root@Server:~#

Link to comment

I have unzipped the program onto the flash drive, but can not seem to run it. I'm sure I'm missing smething small here... Do I need to do something special to run the script. Or from telnet should the following work?

root@server:~# unraid_partition_disk.sh  -A /dev/sda

 

Because it keeps returning

-bash: unraid partition disk.sh: command not found

 

 

Link to comment

I have unzipped the program onto the flash drive, but can not seem to run it. I'm sure I'm missing smething small here... Do I need to do something special to run the script. Or from telnet should the following work?

root@server:~# unraid_partition_disk.sh  -A /dev/sda

 

Because it keeps returning

-bash: unraid partition disk.sh: command not found

 

 

change directory to where the script was unzipped.

cd /boot

then type the command.

/boot is not in your search path, and you were in root's home directory.

Link to comment

OK, tried it. And now here's what I get

root@server:/boot# unraid_partition_disk.sh -A /dev/sdb

/dev/sdb: No medium found

 

sfdisk: cannot open /dev/sdb for reading

Sorry: Device /dev/sdb is busy.: 0

 

According to unRaid /dev/sdb *should* be Disk2 (md2)...

What am I doing wrong now?!?

Basically, it says /dev/sdb is busy.  (already in use by unRAID)

 

Stop the array, then try the command.

 

Joe L.

Link to comment

All right, progress. I now have md2 back, BUT, md1 is still showing as unformatted.

 

After running Joe's program, I get the following output for

 

root@Server:/boot# unraid_partition_disk.sh  -A /dev/sda
########################################################################
Model Family:     Western Digital Caviar Green (Adv. Format) family
Device Model:     WDC WD20EARS-00MVWB0
Serial Number:    WD-WCAZA5820109
Firmware Version: 51.0AB51
User Capacity:    2,000,398,934,016 bytes

Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
1 heads, 63 sectors/track, 62016336 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1              64  3907029167  1953514552   83  Linux
Partition 1 does not end on cylinder boundary.
########################################################################
============================================================================
==
== DISK /dev/sda IS partitioned for unRAID properly
== expected start = 64, actual start = 64
== expected size = 3907029104, actual size = 3907029104
==
============================================================================
root@Server:/boot#

 

Any ideas where I can go from here? My thought, is that since I DO have md2 back up and running, COULD I format md1, then rebuild it from the valid parity? Or is that a miserable idea?

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.