Legacy Network Products

[Betty S]

Hello,

I have a Shared Storage 2 (1 TB, no RAID, just 'linear access') that has failed and is out of warranty. I have removed the drives and installed them into another PC (via SATA) and am using Knoppix (Live CD) to try and recovery the data.

Using "mdadm--examine --scan", returns:

"ARRAY /dev/md0 level=linear num-devices=2 UUID=f2644d4a:dfaebdc2:9f6fea4e:a2f41d92."

(If needed, I can also provide "sfdisk -l" or "mdadm -E /dev/sda6" output if that helps).

I am unsure of what I should do next, and was hoping to seek some guideance/answers.

Based on a number of web sources, I believe I need to create a "mdadm.conf" file, then use mdadm to assemble and start the array, and then mount this in order to gain access to the data (I am not sure on this, so could be very wrong)?

My intention is to simply mount this drive in Knoppix (Live CD), and then copy the contents from the 'RAID' to another network location. (I can confirm that I do have network access, as I have been able to access the web from Knoppix, in addition to using SSH (both as a client, and by setting up SSH server on Knoppix). My Linux skills are basic.

Thanks in advance for any assistance,

Betty

[EasyUser]

try this link:

http://www.linuxjournal.com/article/8874

[deesbek]

Hi Betty,

how do you know that your MSS has died? Orange light flashing, hard drive making noises? Cannot access the shares any more, or cannot access via web interface.

If you can still access it via the web interface I suggest you update the firmware to the OpenMSS as suggested in this post

http://forums.seagate.com/stx/board/message?board.id=mss&message.id=75&query.id=61358#M75 I know it means putting the mss back together but it is not that much hassle, reimaging the drive is though.

the instructions by trunksy are excellent and you may be able to recover the data without having to replace the drive.

[Betty S]

Hi deesbek,

The MSS failed after I was unable to obtain any network connection (the RJ45 port did not show up the link light, even though the cable and router port were OK) and the three status lights just stayed on during the boot up sequence.

I would have liked to have used the OpenMSS method, but unfortunately was not able to do so.

I have not had the opportunity to resume the 'data recovery process' yet, but when I do (hopefully later in the week), I'll post the outcome back to the board.

Regards,

Betty

[Betty S]

OK, well I tried the instructions from the Linux Journal link (as suggested by EasyUser), but didn't succeed.

I ended up with a mdadm.conf file containing (as per instructions added the DEVICE and devices=... lines):

DEVICE partitions
ARRAY /dev/md0 level=linear num-devices=2 UUID=f2644d4a:dfaebdc2:9f6fea4e:a2f41d92 devices=/dev/sda6,/dev/sdb6

 But when I went to assemble the array, mdadm returned an error:

mdadm --assemble --scan  --config=/etc/mdadm.conf
mdadm: error opening /dev/md0: No such device or address

To try and diagnose it, I used --query and --examine, as shown below.

Am I doing something wrong, or is the array more damaged/corrupted than I thought?

---

 

mdadm --query returned:

/dev/sda1: is not an md array
/dev/sda2: is not an md array
/dev/sda3: is not an md array
/dev/sda4: is not an md array
/dev/sda5: is not an md array
/dev/sda6: is not an md array
/dev/sda6: device 0 in 2 device undetected linear /dev/md0.  Use mdadm --examine for more detail.
/dev/sdb1: is not an md array
/dev/sdb2: is not an md array
/dev/sdb3: is not an md array
/dev/sdb4: is not an md array
/dev/sdb5: is not an md array
/dev/sdb6: is not an md array
/dev/sdb6: device 1 in 2 device undetected linear /dev/md0.  Use mdadm --examine for more detail.

So I tried mdadm --examine, resulting in:

/dev/sda6:
          Magic : a92b4efc
        Version : 00.90.01
           UUID : f2644d4a:dfaebdc2:9f6fea4e:a2f41d92
  Creation Time : Tue Jan  3 14:40:48 2006
     Raid Level : linear
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0

    Update Time : Tue Jan  3 14:40:48 2006
          State : active
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0
       Checksum : 6221253f - correct
         Events : 1

       Rounding : 64K

      Number   Major   Minor   RaidDevice State
this     0       8        6        0      active sync   /dev/sda6

   0     0       8        6        0      active sync   /dev/sda6
   1     1       8       22        1      active sync   /dev/sdb6
/dev/sdb6:
          Magic : a92b4efc
        Version : 00.90.01
           UUID : f2644d4a:dfaebdc2:9f6fea4e:a2f41d92
  Creation Time : Tue Jan  3 14:40:48 2006
     Raid Level : linear
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0

    Update Time : Tue Jan  3 14:40:48 2006
          State : active
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0
       Checksum : 62212551 - correct
         Events : 1

       Rounding : 64K

      Number   Major   Minor   RaidDevice State
this     1       8       22        1      active sync   /dev/sdb6

   0     0       8        6        0      active sync   /dev/sda6
   1     1       8       22        1      active sync   /dev/sdb6

[EasyUser]

Have you tried the following for you mdadm.conf file:

DEVICE /dev/sda6, /dev/sdb6
ARRAY /dev/md0 level=linear num-devices=2 devices=/dev/sda6,/dev/sdb6

[Ernst]

Hello Betty,

dont know if you have been successful in the meantime - I had similar problem - tried with knoppix too - no success - I couldn't mount the JBOD.

Then i started looking for data recovery tools - and ... found amazing tools.

I could revover about 99% of my data - I did the following:

I used DiskInternals Linux Recovery to create an image of the JBOD "raid" to a third disk  - I got a 929G sized image file.

Then I loaded this file into R-Linux from RTT Inc. and recovered with this free Utility almost all of my files (>400k)

regards

Ernst

[EasyUser]

Your approach works for single drive or raid 1, but not raid 0.

Message Edited by EasyUser on 08-10-2009 07:19 AM

[Ernst]

thats correct, for RAID0 or RAID1 you need different utilities, I just had same config like Betty ("linear access - no RAID") - therefore my post about how I got successful.

[Betty S · Accepted solution]

After much delay (apologies for such), I was able to mount the RAID unit by using a mdadm.conf file of:

DEVICE /dev/sd[ab][123456]
ARRAY /dev/md0 level=linear num-devices=2 UUID=f2644d4a:dfaebdc2:9f6fea4e:a2f41d92

Also, need to ensure the md module was loaded, by using modprobe md

Thanks to everyone, in particular EasyUser for their advice and assistance.

Betty