Raid 5 not accessible, no web admin interface

Printers, HDDs, USB/eSATA drives, 3rd-party programs
Post Reply
darkrichsmile
First post
Posts: 1
Joined: Thu May 15, 2014 1:04 pm

Raid 5 not accessible, no web admin interface

Post by darkrichsmile »

Hello, at first
I try to answer the most import information

If it's a technical question of any kind, please remember to include:

Your Operating System you are using to access your NAS.
Windows 7

NAS model
TS-412

Firmware revision
not the latest version but nearly, sry don't know exactly.
I can search via ssh if neccessary


Network Setup (ie Single Port or Port Trunking)
No, I have two used ports but each one has his own IP

If Disk related please also specify:
Drive Configuration: (ie SingleDrive, RAID0, JBOD, RAID1, RAID5, RAID6, RAID10)
Raid 5 on Bay 1+2+3
No Raid on Bay 4

Number of drives
For each drive please provide:
Drive Manufacturer (ie Seagate, WD, Hitachi, etc)
Drive Model

3x SEAGATE Barracuda 7200 3000GB 7200 U/min with 64MB
1x ?? but this HDD is still working as it should


So now exactly a description what has happened.
Had a power breakdown on 2014/05/10.
On 2014/05/11 I have moved some private Pics to the raid successfully.
On 2014/05/12 My shares were not accessible. I have seen, that Bay one was blinking red
I have restarted the Raid. No rebuild or something else. I have bought a new hdd (same model)
and inserted it to rebuild. Status LED is blinking green, HDD is green. It seems that when starting qnap.
the qnap is trying to rebuild. but after 3h the system is doing nothing any more. Only ssh is possible.
Web server seems to be down so the webadmin is not accessible

I have got a little help from a guy who has linux know how, here is what I've got from the ssh.
It seems to be a strange config. IMPORTANT these are the results with the new disk on BAY ONE!

[/share] # mount
/proc on /proc type proc (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
sysfs on /sys type sysfs (rw)
tmpfs on /tmp type tmpfs (rw,size=32M)
none on /proc/bus/usb type usbfs (rw)
/dev/sda4 on /mnt/ext type ext3 (rw)
/dev/md9 on /mnt/HDA_ROOT type ext3 (rw,data=ordered)
/dev/sdd3 on /share/HDD_DATA type ext4 (rw,usrjquota=aquota.user,jqfmt=vfsv0,user_xattr,data=ordered,delalloc,acl)
tmpfs on /.eaccelerator.tmp type tmpfs (rw,size=32M)


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

[/share] # mdadm -S /dev/md0
mdadm: stopped /dev/md0


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

we tried to connect the drives again to raid 5

[/share] # mdadm -CfR --assume-clean /dev/md0 -l 5 -n 3 /dev/sda3 /dev/sdb3 /dev/sdc3
mdadm: Cannot open /dev/sda3: No such device or address
mdadm: Defaulting to version 1.-1 metadata
mdadm: /dev/sdb3 appears to be part of a raid array:
level=raid5 devices=3 ctime=Sat Sep 15 11:10:43 2012
mdadm: /dev/sdc3 appears to contain an ext2fs file system
size=1382072768K mtime=Fri May 16 11:32:51 2031
mdadm: /dev/sdc3 appears to be part of a raid array:
level=raid5 devices=3 ctime=Sat Sep 15 11:10:43 2012
mdadm: create aborted


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

[/share] # blkid
/dev/sda1: UUID="5b25a7b4-f99d-0c93-e74e-720a45cf29f6" TYPE="mdraid"
/dev/sda2: UUID="f3e40104-bf6c-fb1f-2f41-8f8dbfa25f62" TYPE="mdraid"
/dev/sdc1: UUID="5b25a7b4-f99d-0c93-e74e-720a45cf29f6" TYPE="mdraid"
/dev/sdc2: UUID="f3e40104-bf6c-fb1f-2f41-8f8dbfa25f62" TYPE="mdraid"
/dev/sdc3: UUID="13dc1eff-043e-422d-9454-7fa05248f67d" EXT_JOURNAL="00000500-0000-0000-0000-00000020b0b7" TYPE="ext4"
/dev/sdc4: UUID="9ef0cbed-d308-242d-f9bd-4a2804581594" TYPE="mdraid"
/dev/sdb1: UUID="5b25a7b4-f99d-0c93-e74e-720a45cf29f6" TYPE="mdraid"
/dev/sdb2: UUID="f3e40104-bf6c-fb1f-2f41-8f8dbfa25f62" TYPE="mdraid"
/dev/sdb4: UUID="9ef0cbed-d308-242d-f9bd-4a2804581594" TYPE="mdraid"
/dev/sdd1: UUID="5b25a7b4-f99d-0c93-e74e-720a45cf29f6" TYPE="mdraid"
/dev/sdd2: UUID="f3e40104-bf6c-fb1f-2f41-8f8dbfa25f62" TYPE="mdraid"
/dev/sdd3: UUID="7c6869d4-89aa-46c7-86c7-95914bb320c1" TYPE="ext4"
/dev/sdd4: UUID="9ef0cbed-d308-242d-f9bd-4a2804581594" TYPE="mdraid"
/dev/md9: UUID="35ad4946-9005-4d36-a24e-beb8d4657060" TYPE="ext3"
/dev/sda4: UUID="1635fe4e-7721-4fac-9e5f-1d4d4bf3840c" TYPE="ext3"
/dev/md4: TYPE="swap" UUID="fabf94b0-4f9e-477a-b870-f75a06974851"


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

[/share] # fdisk -l /dev/sdc
You must set cylinders.
You can do this from the extra functions menu.

Disk /dev/sdc: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdc1 1 267350 2147483647+ ee EFI GPT
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(0, 0, 1) logical=(0, 0, 2)
Partition 1 has different physical/logical endings:
phys=(1023, 254, 63) logical=(267349, 89, 4)

----------------------
[/share] # fdisk -l /dev/sdb
You must set cylinders.
You can do this from the extra functions menu.

Disk /dev/sdb: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 1 267350 2147483647+ ee EFI GPT
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(0, 0, 1) logical=(0, 0, 2)
Partition 1 has different physical/logical endings:
phys=(1023, 254, 63) logical=(267349, 89, 4)


--------------------
[/share] # fdisk -l /dev/sda

Disk /dev/sda: 2000.4 GB, 2000421444608 bytes
255 heads, 63 sectors/track, 243204 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 66 530125 83 Linux


---------------------------------
[/share] # fdisk -l /dev/sdd

Disk /dev/sdd: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdd1 1 66 530125 83 Linux
/dev/sdd2 67 132 530142 83 Linux
/dev/sdd3 133 182338 1463569693 83 Linux
/dev/sdd4 182339 182400 498012 83 Linux

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

[/share] # tail -f /etc/mdadm.conf
ARRAY /dev/md0 devices=/dev/sda3,/dev/sdb3,/dev/sdc3


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

[/share] # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md4 : active raid1 sda2[2](S) sdd2[0] sdc2[3](S) sdb2[1]
530048 blocks [2/2] [UU]

md13 : active raid1 sdd4[1] sdc4[0] sdb4[2]
458880 blocks [4/3] [UUU_]
bitmap: 35/57 pages [140KB], 4KB chunk

md9 : active raid1 sda1[0] sdd1[3] sdb1[2] sdc1[1]
530048 blocks [4/4] [UUUU]
bitmap: 1/65 pages [4KB], 4KB chunk


I have no backups, because why do i have to with raid5? Now I know why :(

It would be very kind of you if you could help me. It seems that my partition is corrput and I have a bad superblock.
What else can I do?

Please be patient with answers, because tomorrow we are going on our honeymoon and I am back on 2014/06/10, but I am depressed right now.
I've paid much, just to know now, that my data is lost, maybe forever. And I know my misstake is that I've not done a double backup.

Best Regards

darkrichsmile
Post Reply

Return to “Hardware & Software Compatibility”