Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Seagete Business NAS 12TB crashed


  • Please log in to reply
No replies to this topic

#1 samtappin

samtappin

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:10:54 PM

Posted 27 July 2016 - 10:17 PM

i have Seagate 12 TB NAS, running RAID 5. one of my Hard disk suddnly stop working and RAID 5 crashed. some how i got the hard disk working but not able to mount my data volume as the disk have bad sectors. not sure if you had raid 5 setup or raid 0? i have tried lot of windows softwares but no luck.

 

UFS Explorer Professional Recovery does read my NAS version and everything but not able to recover data.

 

i guess windows/recovery software providers dont have Fuseext2 drivers. Paragon ExtFS for Windows doesnt support 3TB drives, so not able to mount with that either.

 

now i am trying Ubuntu and i get following results, can anyone tell me if i am doing anything wrong? i am trying to follow steps from the link below.

 

https://sidfishes.wordpress.com/2014/03/07/how-to-seagate-blackarmor-data-recovery-after-datavolume-failed-error/

 

 

any help will be greatly appreciated. i have posted my results below.

 

 

RAID 5 autodetected by ubuntu on startup >>>

 

deepak@Vostro-220:~$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md7 : active raid1 sdb9[2] sda9[1]
      999412 blocks super 1.2 [4/2] [U_U_]
     
md5 : active raid1 sdc7[3] sdb7[2] sda7[1]
      11252 blocks super 1.2 [4/3] [U_UU]
     
md6 : active raid1 sdc8[3] sdb8[2] sda8[1]
      290804 blocks super 1.2 [4/3] [U_UU]
     
md4 : active raid1 sdc6[3] sdb6[2] sda6[1]
      10228 blocks super 1.2 [4/3] [U_UU]
     
md2 : active raid1 sdc4[3] sdb4[2] sda4[1]
      10228 blocks super 1.2 [4/3] [U_UU]
     
md127 : active (auto-read-only) raid5 sdc10[4] sdb10[2] sda10[1]
      8778037248 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/3] [_UUU]
      bitmap: 0/22 pages [0KB], 65536KB chunk

md1 : active raid1 sdc3[3] sdb3[2] sda3[1]
      975860 blocks super 1.2 [4/3] [UU_U]
     
md3 : active raid1 sdc5[3] sdb5[2] sda5[1]
      976884 blocks super 1.2 [4/3] [U_UU]
     
md0 : active raid1 sdc2[3] sdb2[2] sda2[1]
      975860 blocks super 1.2 [4/3] [U_UU]
     
unused devices: <none>

-------------------------------------------------------

Raid 5 is detected, number of disks detected, size of Raid 5 detected

-------------------------------------------------------

deepak@Vostro-220:~$ sudo mdadm --examine /dev/sd[abc]10
[sudo] password for deepak:
/dev/sda10:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 1e0939de:25e70b9c:e3c0ac75:3211be62
           Name : BA-375726:8
  Creation Time : Mon Jan 11 20:47:01 2016
     Raid Level : raid5
   Raid Devices : 4

 Avail Dev Size : 5852025911 (2790.46 GiB 2996.24 GB)
     Array Size : 8778037248 (8371.39 GiB 8988.71 GB)
  Used Dev Size : 5852024832 (2790.46 GiB 2996.24 GB)
    Data Offset : 2048 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : 5ef294ef:b3642158:9c28a392:6b2cfd8f

Internal Bitmap : 8 sectors from superblock
    Update Time : Sat Jul 16 01:42:33 2016
       Checksum : 32cb6063 - correct
         Events : 7364

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 1
   Array State : .AAA ('A' == active, '.' == missing)
/dev/sdb10:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 1e0939de:25e70b9c:e3c0ac75:3211be62
           Name : BA-375726:8
  Creation Time : Mon Jan 11 20:47:01 2016
     Raid Level : raid5
   Raid Devices : 4

 Avail Dev Size : 5852025911 (2790.46 GiB 2996.24 GB)
     Array Size : 8778037248 (8371.39 GiB 8988.71 GB)
  Used Dev Size : 5852024832 (2790.46 GiB 2996.24 GB)
    Data Offset : 2048 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : c93bcca6:993d0199:c95be3af:5a72572a

Internal Bitmap : 8 sectors from superblock
    Update Time : Sat Jul 16 01:42:33 2016
       Checksum : e27cfbd0 - correct
         Events : 7364

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 2
   Array State : .AAA ('A' == active, '.' == missing)
/dev/sdc10:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x1
     Array UUID : 1e0939de:25e70b9c:e3c0ac75:3211be62
           Name : BA-375726:8
  Creation Time : Mon Jan 11 20:47:01 2016
     Raid Level : raid5
   Raid Devices : 4

 Avail Dev Size : 5852025911 (2790.46 GiB 2996.24 GB)
     Array Size : 8778037248 (8371.39 GiB 8988.71 GB)
  Used Dev Size : 5852024832 (2790.46 GiB 2996.24 GB)
    Data Offset : 2048 sectors
   Super Offset : 8 sectors
          State : clean
    Device UUID : cdbc1452:fec51fe5:127a044d:99a5db5a

Internal Bitmap : 8 sectors from superblock
    Update Time : Sat Jul 16 01:42:33 2016
       Checksum : a78956c3 - correct
         Events : 7364

         Layout : left-symmetric
     Chunk Size : 512K

   Device Role : Active device 3
   Array State : .AAA ('A' == active, '.' == missing)

deepak@Vostro-220:~$ sudo mdadm --assemble --force -v /dev/md127 --uuid=1e0939de:25e70b9c:e3c0ac75:3211be62
mdadm: looking for devices for /dev/md127
mdadm: no recogniseable superblock on /dev/sdd6
mdadm: no recogniseable superblock on /dev/sdd5
mdadm: Cannot assemble mbr metadata on /dev/sdd3
mdadm: Cannot assemble mbr metadata on /dev/sdd2
mdadm: Cannot assemble mbr metadata on /dev/sdd1
mdadm: Cannot assemble mbr metadata on /dev/sdd
mdadm: /dev/sdc10 is busy - skipping
mdadm: /dev/sdc9 has wrong uuid.
mdadm: /dev/sdc8 has wrong uuid.
mdadm: /dev/sdc7 has wrong uuid.
mdadm: /dev/sdc6 has wrong uuid.
mdadm: /dev/sdc5 has wrong uuid.
mdadm: /dev/sdc4 has wrong uuid.
mdadm: /dev/sdc3 has wrong uuid.
mdadm: /dev/sdc2 has wrong uuid.
mdadm: no recogniseable superblock on /dev/sdc1
mdadm: Cannot assemble mbr metadata on /dev/sdc
mdadm: /dev/sdb10 is busy - skipping
mdadm: /dev/sdb9 has wrong uuid.
mdadm: /dev/sdb8 has wrong uuid.
mdadm: /dev/sdb7 has wrong uuid.
mdadm: /dev/sdb6 has wrong uuid.
mdadm: /dev/sdb5 has wrong uuid.
mdadm: /dev/sdb4 has wrong uuid.
mdadm: /dev/sdb3 has wrong uuid.
mdadm: /dev/sdb2 has wrong uuid.
mdadm: no recogniseable superblock on /dev/sdb1
mdadm: Cannot assemble mbr metadata on /dev/sdb
mdadm: no recogniseable superblock on /dev/md/7
mdadm: no recogniseable superblock on /dev/md/5
mdadm: no recogniseable superblock on /dev/md/6
mdadm: no recogniseable superblock on /dev/md/4
mdadm: no recogniseable superblock on /dev/md/2
mdadm: no recogniseable superblock on /dev/md/BA-375726:8
mdadm: no recogniseable superblock on /dev/md/1
mdadm: no recogniseable superblock on /dev/md/3
mdadm: no recogniseable superblock on /dev/md/0
mdadm: /dev/sda10 is busy - skipping
mdadm: /dev/sda9 has wrong uuid.
mdadm: /dev/sda8 has wrong uuid.
mdadm: /dev/sda7 has wrong uuid.
mdadm: /dev/sda6 has wrong uuid.
mdadm: /dev/sda5 has wrong uuid.
mdadm: /dev/sda4 has wrong uuid.
mdadm: /dev/sda3 has wrong uuid.
mdadm: /dev/sda2 has wrong uuid.
mdadm: no recogniseable superblock on /dev/sda1
mdadm: Cannot assemble mbr metadata on /dev/sda
mdadm: no recogniseable superblock on /dev/ram15
mdadm: no recogniseable superblock on /dev/ram14
mdadm: no recogniseable superblock on /dev/ram13
mdadm: no recogniseable superblock on /dev/ram12
mdadm: no recogniseable superblock on /dev/ram11
mdadm: no recogniseable superblock on /dev/ram10
mdadm: no recogniseable superblock on /dev/ram9
mdadm: no recogniseable superblock on /dev/ram8
mdadm: no recogniseable superblock on /dev/ram7
mdadm: no recogniseable superblock on /dev/ram6
mdadm: no recogniseable superblock on /dev/ram5
mdadm: no recogniseable superblock on /dev/ram4
mdadm: no recogniseable superblock on /dev/ram3
mdadm: no recogniseable superblock on /dev/ram2
mdadm: no recogniseable superblock on /dev/ram1
mdadm: no recogniseable superblock on /dev/ram0

deepak@Vostro-220:~$ sudo modprobe dm-mod

deepak@Vostro-220:~$ sudo vgchange -ay
  0 logical volume(s) in volume group "vg8" now active

deepak@Vostro-220:~$ sudo mdadm -S /dev/md127
mdadm: stopped /dev/md127

deepak@Vostro-220:~$ sudo mdadm --assemble --force -v /dev/md127 --uuid=1e0939de:25e70b9c:e3c0ac75:3211be62
mdadm: looking for devices for /dev/md127
mdadm: no recogniseable superblock on /dev/sdd6
mdadm: no recogniseable superblock on /dev/sdd5
mdadm: Cannot assemble mbr metadata on /dev/sdd3
mdadm: Cannot assemble mbr metadata on /dev/sdd2
mdadm: Cannot assemble mbr metadata on /dev/sdd1
mdadm: Cannot assemble mbr metadata on /dev/sdd
mdadm: /dev/sdc9 has wrong uuid.
mdadm: /dev/sdc8 has wrong uuid.
mdadm: /dev/sdc7 has wrong uuid.
mdadm: /dev/sdc6 has wrong uuid.
mdadm: /dev/sdc5 has wrong uuid.
mdadm: /dev/sdc4 has wrong uuid.
mdadm: /dev/sdc3 has wrong uuid.
mdadm: /dev/sdc2 has wrong uuid.
mdadm: no RAID superblock on /dev/sdc1
mdadm: no RAID superblock on /dev/sdc
mdadm: /dev/sdb9 has wrong uuid.
mdadm: /dev/sdb8 has wrong uuid.
mdadm: /dev/sdb7 has wrong uuid.
mdadm: /dev/sdb6 has wrong uuid.
mdadm: /dev/sdb5 has wrong uuid.
mdadm: /dev/sdb4 has wrong uuid.
mdadm: /dev/sdb3 has wrong uuid.
mdadm: /dev/sdb2 has wrong uuid.
mdadm: no RAID superblock on /dev/sdb1
mdadm: no RAID superblock on /dev/sdb
mdadm: no RAID superblock on /dev/md/7
mdadm: no RAID superblock on /dev/md/5
mdadm: no RAID superblock on /dev/md/6
mdadm: no RAID superblock on /dev/md/4
mdadm: no RAID superblock on /dev/md/2
mdadm: no RAID superblock on /dev/md/1
mdadm: no RAID superblock on /dev/md/3
mdadm: no RAID superblock on /dev/md/0
mdadm: /dev/sda9 has wrong uuid.
mdadm: /dev/sda8 has wrong uuid.
mdadm: /dev/sda7 has wrong uuid.
mdadm: /dev/sda6 has wrong uuid.
mdadm: /dev/sda5 has wrong uuid.
mdadm: /dev/sda4 has wrong uuid.
mdadm: /dev/sda3 has wrong uuid.
mdadm: /dev/sda2 has wrong uuid.
mdadm: no RAID superblock on /dev/sda1
mdadm: no RAID superblock on /dev/sda
mdadm: no RAID superblock on /dev/ram15
mdadm: no RAID superblock on /dev/ram14
mdadm: no RAID superblock on /dev/ram13
mdadm: no RAID superblock on /dev/ram12
mdadm: no RAID superblock on /dev/ram11
mdadm: no RAID superblock on /dev/ram10
mdadm: no RAID superblock on /dev/ram9
mdadm: no RAID superblock on /dev/ram8
mdadm: no RAID superblock on /dev/ram7
mdadm: no RAID superblock on /dev/ram6
mdadm: no RAID superblock on /dev/ram5
mdadm: no RAID superblock on /dev/ram4
mdadm: no RAID superblock on /dev/ram3
mdadm: no RAID superblock on /dev/ram2
mdadm: no RAID superblock on /dev/ram1
mdadm: no RAID superblock on /dev/ram0
mdadm: /dev/sdc10 is identified as a member of /dev/md127, slot 3.
mdadm: /dev/sdb10 is identified as a member of /dev/md127, slot 2.
mdadm: /dev/sda10 is identified as a member of /dev/md127, slot 1.
mdadm: no uptodate device for slot 0 of /dev/md127
mdadm: added /dev/sdb10 to /dev/md127 as 2
mdadm: added /dev/sdc10 to /dev/md127 as 3
mdadm: added /dev/sda10 to /dev/md127 as 1
mdadm: /dev/md127 has been started with 3 drives (out of 4).

deepak@Vostro-220:~$ sudo modprobe dm-mod

deepak@Vostro-220:~$ sudo vgchange -ay
  0 logical volume(s) in volume group "vg8" now active

deepak@Vostro-220:~$ sudo lvscan

 



BC AdBot (Login to Remove)

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users