Andy E

It's mostly dev stuff, almost all of it was backed up (some of it is backups of what I have on my laptop) except for about a weeks worth of work, but there were also some rips of my daughter's dance recital DVD that I didn't have backed up. Once again, thank you :-)

I'll be more careful in the future ;-)

yeah, I just didn't have another 3TB drive (nor could I afford one right now) to copy to

thanks again, I really appreciate the whole thing.

lol I will

it worked, thank you so much

GENIUS!

$ losetup -f
/dev/loop0

yay

0000030: 1419 a550 1a00 1f00 53ef 0100 0100 0000  ...P....S.......

got it with the +2048

$ cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md3 : active raid1 sdb5[0]
      2925531648 blocks super 1.2 [1/1] [U]

md1 : active raid1 sdb2[0]
      2097088 blocks [2/1] [U_]

md0 : active raid1 sdb1[0]
      2490176 blocks [2/1] [U_]

unused devices: <none>

nope

$ mdadm --assemble -v /dev/md5 /dev/sda1
mdadm: looking for devices for /dev/md5
mdadm: cannot open device /dev/sda1: Device or resource busy
mdadm: /dev/sda1 has no superblock - assembly aborted

it didn't like the --read-only option so I removed it, and got this:

maybe I didn't use mdadm --create on it. Although I really thought I did.

hmm, it's not mapped to an mdX

cool, you're a real life saver

It's Synology Hybrid Raid, their own custom implementation I think

$ dmsetup table
vg1000-lv: 0 5851054080 linear 9:3 1152

$ (parted /dev/sda p ; parted /dev/sdb p)
Model: ATA ST3000DM001-9YN1 (scsi)
Disk /dev/sda: 3001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name  Flags
 1      4840MB  3001GB  2996GB                     boot

Model: ATA ST3000DM001-9YN1 (scsi)
Disk /dev/sdb: 3001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system     Name  Flags
 1      131kB   2550MB  2550MB  ext4                  raid

ah I see

yeah, I believe so. would I lose that after a reboot though?

$ mdadm -E /dev/sdb5
/dev/sdb5:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 6fa3143c:344c9ebe:3d472d13:b7c7c298
           Name : DiskStation:2  (local to host DiskStation)
  Creation Time : Fri Nov 16 11:10:39 2012
     Raid Level : raid1
   Raid Devices : 1

 Avail Dev Size : 5851063680 (2790.00 GiB 2995.74 GB)
     Array Size : 5851063296 (2790.00 GiB 2995.74 GB)
  Used Dev Size : 5851063296 (2790.00 GiB 2995.74 GB)
    Data Offset : 2048 sectors
   Super Offset : 8 sectors

fdisk: device has more than 2^32 sectors, can't use all of them

Disk /dev/sdb: 2199.0 GB, 2199023255040 bytes
255 heads, 63 sectors/track, 267349 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sdb1               1      267350  2147483647+ ee EFI GPT

fdisk gives me

it looks like a custom Synology thing, they have their copyright on it

it says Please specify -z and -N

/dev/md3:
        Version : 1.2
  Creation Time : Fri Nov 16 11:10:39 2012
     Raid Level : raid1
     Array Size : 2925531648 (2790.00 GiB 2995.74 GB)
  Used Dev Size : 2925531648 (2790.00 GiB 2995.74 GB)
   Raid Devices : 1
  Total Devices : 1
    Persistence : Superblock is persistent

    Update Time : Fri Nov 30 18:12:10 2012
          State : clean
 Active Devices : 1
Working Devices : 1
 Failed Devices : 0
  Spare Devices : 0

           Name : DiskStation:2  (local to host DiskStation)

physical_volumes

there's not much to it other than that

            device = "/dev/md2" # Hint only
 24
 25             status = ["ALLOCATABLE"]
 26             dev_size = 5851063296   # 2.72461 Terabytes
 27             pe_start = 1152
 28             pe_count = 714240   # 2.72461 Terabytes

Well, I lol'ed because that is from before I bought the thing. Although thinking about it, the date probably wasn't set before the volume was created.

there's two from feb 13 2011 lol

$ ls /etc/lvm/archive/
vg1000_00000.vg  vg1000_00001.vg  vg1000_00002.vg  vg1000_00003.vg  vg1000_00004.vg  vg1000_00005.vg

yes

I think that may have done something to the partition table, not sure.

I used the Synology tool to remove the volume before I formatted the other disc, which I thought afterwards may have been a mistake

I guess that's bad... I'm sorry I'm pretty clueless about all this superblock stuff

mdadm: No super block found on /dev/sda1 (Expected magic a92b4efc, got 00000000)

$ cat /proc/partitions
major minor  #blocks  name

   8        0 2930266584 sda
   8        1 2925531652 sda1
   8       16 2930266584 sdb
   8       17    2490240 sdb1
   8       18    2097152 sdb2
   8       21 2925532864 sdb5
  31        0        512 mtdblock0
  31        1       2048 mtdblock1
  31        2       1280 mtdblock2
  31        3         64 mtdblock3
  31        4        128 mtdblock4
  31        5         64 mtdblock5
  31        6       4096 mtdblock6
   9        0    2490176 md0

there's only /dev/sda and /dev/sda1, although testdisk seems to have found more

$ mdadm -E /dev/sda1
/dev/sda1:
          Magic : a92b4efc
        Version : 1.2
    Feature Map : 0x0
     Array UUID : 01dd80d9:5b5dfe30:7cbc82a0:15cbc91d
           Name : DiskStation:2  (local to host DiskStation)
  Creation Time : Thu Nov 15 17:48:12 2012
     Raid Level : raid1
   Raid Devices : 1

 Avail Dev Size : 5851063680 (2790.00 GiB 2995.74 GB)
     Array Size : 5851063296 (2790.00 GiB 2995.74 GB)
  Used Dev Size : 5851063296 (2790.00 GiB 2995.74 GB)
    Data Offset : 2048 sectors
   Super Offset : 8 sectors

oh, yeah that's right

It was all done automatically using the Synology web interface.

I don't know, that was for the other drive, I think.

indicating the formatted drive only

just that

  PV /dev/md3   VG vg1000   lvm2 [2.72 TB / 0    free]
  Total: 1 [742.00 GB] / in use: 1 [742.00 GB] / in no VG: 0 [0   ]

3% :-)