Failed disk Now Raid Missing

leester01 · 19. Mai 2016

Hi Guys,

I lost my Raid a few weeks ago, turns out It was corrupt ryecoaaron helped me get this resolved and I managed to recover most of my data using photorec

So I purchased some new drives set-up Raid 5 over 4 2TB Barracuda Green disks. All great, got all my data back.

I then had a notification telling me I had a drive failure. lucky I purchased a spare disk. So I shutdown. Installed disk and started my system back up. now my RAID is missing completely.

Please advise I really don't want to rebuild and trash this disks again.

Regards

Output from fdisk

Code

root@snowdon:~# fdisk -l


Disk /dev/sda: 128.0 GB, 128035676160 bytes


255 heads, 63 sectors/track, 15566 cylinders, total 250069680 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: 0x00026f46


   Device Boot      Start         End      Blocks   Id  System


/dev/sda1   *        2048   239855615   119926784   83  Linux


/dev/sda2       239857662   250068991     5105665    5  Extended


/dev/sda5       239857664   250068991     5105664   82  Linux swap / Solaris


Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes


255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors


Units = sectors of 1 * 512 = 512 bytes


Sector size (logical/physical): 512 bytes / 4096 bytes


I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk identifier: 0xd7085746


Disk /dev/sdb doesn't contain a valid partition table


Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes


255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors


Units = sectors of 1 * 512 = 512 bytes


Sector size (logical/physical): 512 bytes / 4096 bytes


I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk identifier: 0x6c3a832a


Disk /dev/sdc doesn't contain a valid partition table


Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes


255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors


Units = sectors of 1 * 512 = 512 bytes


Sector size (logical/physical): 512 bytes / 4096 bytes


I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk identifier: 0x30dfb705


Disk /dev/sdd doesn't contain a valid partition table

Alles anzeigen

leester01 · 19. Mai 2016

Some Additional Information

Code

root@snowdon:/dev# mount -a
root@snowdon:/dev# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=462780,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=378540k,mode=755)
/dev/disk/by-uuid/7af13745-c1c8-443f-961a-7205b9b79af7 on / type ext4 (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1778200k)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatie)

Alles anzeigen

Code

root@snowdon:/dev# cat /etc/fstab | grep md
root@snowdon:/dev# 


root@snowdon:/dev# blkid 
/dev/sdd: UUID="a0dfcd71-f8eb-0f8c-5bf1-ec65b7e4b2d1" UUID_SUB="182c449c-6f98-9cc7-7eef-5b37516df699" LABEL="snowdon:0" TYPE="linux_raid_member" 
/dev/sdc: UUID="a0dfcd71-f8eb-0f8c-5bf1-ec65b7e4b2d1" UUID_SUB="2cce1266-cb93-3d17-f8eb-34dcdbe6fc9e" LABEL="snowdon:0" TYPE="linux_raid_member" 
/dev/sdb: UUID="a0dfcd71-f8eb-0f8c-5bf1-ec65b7e4b2d1" UUID_SUB="8cbb75af-0fe4-0f3b-8258-5f3d618aa3d3" LABEL="snowdon:0" TYPE="linux_raid_member" 
/dev/sda1: UUID="7af13745-c1c8-443f-961a-7205b9b79af7" TYPE="ext4" 
/dev/sda5: UUID="fe61d8b1-b199-4aac-8557-24e66cfddeff" TYPE="swap"

Code

root@snowdon:/dev# mdadm --stop /dev/md0
mdadm: stopped /dev/md0
root@snowdon:/dev# blkid
/dev/sdd: UUID="a0dfcd71-f8eb-0f8c-5bf1-ec65b7e4b2d1" UUID_SUB="182c449c-6f98-9cc7-7eef-5b37516df699" LABEL="snowdon:0" TYPE="linux_raid_member" 
/dev/sdc: UUID="a0dfcd71-f8eb-0f8c-5bf1-ec65b7e4b2d1" UUID_SUB="2cce1266-cb93-3d17-f8eb-34dcdbe6fc9e" LABEL="snowdon:0" TYPE="linux_raid_member" 
/dev/sdb: UUID="a0dfcd71-f8eb-0f8c-5bf1-ec65b7e4b2d1" UUID_SUB="8cbb75af-0fe4-0f3b-8258-5f3d618aa3d3" LABEL="snowdon:0" TYPE="linux_raid_member" 
/dev/sda1: UUID="7af13745-c1c8-443f-961a-7205b9b79af7" TYPE="ext4" 
/dev/sda5: UUID="fe61d8b1-b199-4aac-8557-24e66cfddeff" TYPE="swap"

Code

root@snowdon:/dev# mdadm --assemble --force --verbose /dev/md127 /dev/sd[bcd]
mdadm: looking for devices for /dev/md127
mdadm: /dev/sdb is identified as a member of /dev/md127, slot 1.
mdadm: /dev/sdc is identified as a member of /dev/md127, slot 2.
mdadm: /dev/sdd is identified as a member of /dev/md127, slot 3.
mdadm: Marking array /dev/md127 as 'clean'
mdadm: no uptodate device for slot 0 of /dev/md127
mdadm: added /dev/sdc to /dev/md127 as 2
mdadm: added /dev/sdd to /dev/md127 as 3
mdadm: added /dev/sdb to /dev/md127 as 1
mdadm: /dev/md127 has been started with 3 drives (out of 4).
root@snowdon:/dev# blkid
/dev/sdd: UUID="a0dfcd71-f8eb-0f8c-5bf1-ec65b7e4b2d1" UUID_SUB="182c449c-6f98-9cc7-7eef-5b37516df699" LABEL="snowdon:0" TYPE="linux_raid_member" 
/dev/sdc: UUID="a0dfcd71-f8eb-0f8c-5bf1-ec65b7e4b2d1" UUID_SUB="2cce1266-cb93-3d17-f8eb-34dcdbe6fc9e" LABEL="snowdon:0" TYPE="linux_raid_member" 
/dev/sdb: UUID="a0dfcd71-f8eb-0f8c-5bf1-ec65b7e4b2d1" UUID_SUB="8cbb75af-0fe4-0f3b-8258-5f3d618aa3d3" LABEL="snowdon:0" TYPE="linux_raid_member" 
/dev/sda1: UUID="7af13745-c1c8-443f-961a-7205b9b79af7" TYPE="ext4" 
/dev/sda5: UUID="fe61d8b1-b199-4aac-8557-24e66cfddeff" TYPE="swap" 
/dev/md127: LABEL="Nixdy" UUID="9250a5d0-517e-409a-8afd-9071d590f6ec" TYPE="ext4" 
root@snowdon:/dev#

Alles anzeigen

leester01 · 19. Mai 2016

I've kinda fixed it following ryecoaaron's instructions from last time.

ryecoaaron · 19. Mai 2016

Does the array show up in the raid tab in the web interface?

Failed disk Now Raid Missing

Jetzt mitmachen!

Tags