help with recover volume 419p+ FW:3.5.0

Introduce yourself to us and other members here, or share your own product reviews, suggestions, and tips and tricks of using QNAP products.

help with recover volume 419p+ FW:3.5.0

Postby pallenda » Wed Oct 05, 2011 10:57 am

I had firmware 3.4.3 running for a while, and on 3rd of october I let the autoupdater update from 3.4.3 to 3.5.0.

I'm not 100% sure now of when what happend, its starting to become a blur aftr trying to fix this for 10 hours straight.

But at some point the display on the NAS just stalled at: Rebooting System Please wait...
I could access files and all.

If I try updating the firmware now it keeps freezing at 10%.
But it clearly isn't rebooting, even after stopping the 3 QPKG addons (Python, Optware, SABnzbdplus).
Still no restart.

The soft reset didn't work, did go beep, the front panel buttons didn't work. I tried ssh to the NAS via putty and did shutdown and a reboot. Nothing.
After some time the web UI didn't work either, and no connection via ssh/putty. So I manned up and cut the power after hearing that the hd's didn't seem to read or write (sooo scary).

Power back on, all looks ok, I readd 3.5.0 and loads old config.

In Shared Folders I see all the shares, and they look to have the correct size.
I can't access them via windows, or the web file manager.

Going to Raid Management I see a RAID5 and it says I can use recover option, but nothing happends.

I read this post: viewtopic.php?f=142&t=43581

Code: Select all
[~] # ls /share/
Download@              HDL_DATA/              HDX_DATA/
HDA_DATA/              HDM_DATA/              HDY_DATA/
HDB_DATA/              HDN_DATA/              HDZ_DATA/
HDC_DATA/              HDO_DATA/              MD0_DATA/
HDD_DATA/              HDP_DATA/              Multimedia@
HDE_DATA/              HDQ_DATA/              Network Recycle Bin 1@
HDF_DATA/              HDR_DATA/              Public@
HDG_DATA/              HDS_DATA/              Recordings@
HDH_DATA/              HDT_DATA/              Usb@
HDI_DATA/              HDU_DATA/              Web@
HDJ_DATA/              HDV_DATA/              external/
HDK_DATA/              HDW_DATA/
[~] #


Code: Select all
[~] # 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)
tmpfs on /.eaccelerator.tmp type tmpfs (rw,size=32M)


They also mentioned these 3 commands, that I didn't dare try yet as I know you can destroy alot with fidsk and I couldn't find online what the -ul option does.

# fdisk -ul
# cat /proc/mdstat
# df


So is there any hope for me getting my data back?
Should I try going back to 3.4.3 firmware?

Ofcause this happends as I was organizing data before doing a backup. :s
pallenda
New here
 
Posts: 6
Joined: Fri May 13, 2011 12:41 am
NAS Model: TS-219P+

Re: help with recover volume 419p+ FW:3.5.0

Postby pallenda » Wed Oct 05, 2011 10:46 pm

A bit more info:

Code: Select all
[~] # df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/ram                 32.9M     15.6M     17.3M  47% /
tmpfs                    32.0M    108.0k     31.9M   0% /tmp
/dev/sda4               310.0M    226.2M     83.8M  73% /mnt/ext
/dev/md9                509.5M    101.5M    407.9M  20% /mnt/HDA_ROOT
tmpfs                    32.0M         0     32.0M   0% /.eaccelerator.tmp

Code: Select all
[~] # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [linear] [raid0] [raid10]
md4 : active raid1 sdd2[2](S) sdc2[3](S) sdb2[1] sda2[0]
      530048 blocks [2/2] [UU]

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

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

unused devices: <none>

Code: Select all
[~] # cat /etc/config/mdadm.conf
ARRAY /dev/md0 devices=/dev/sda3,/dev/sdb3,/dev/sdc3,/dev/sdd3


[~] # mdadm -D /dev/md0
mdadm: md device /dev/md0 does not appear to be active.

[~] # e2fsck -n /dev/md0
e2fsck 1.41.4 (27-Jan-2009)
e2fsck: Invalid argument while trying to open /dev/md0

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

Code: Select all
[~] # cat /etc/config/raidtab
raiddev /dev/md0
        raid-level      5
        nr-raid-disks   4
        nr-spare-disks  0
        chunk-size      4
        persistent-superblock   1
        device  /dev/sda3
        raid-disk       0
        device  /dev/sdb3
        raid-disk       1
        device  /dev/sdc3
        raid-disk       2
        device  /dev/sdd3
        raid-disk       3

Code: Select all
[~] # cat /etc/storage.conf
[VOLUME 1]
device name = /dev/md0
raid level = 5
raid disks = 1,2,3,4
spare raid disks =
status = -2
record_time = Wed Oct  5 15:36:50 2011

filesystem = 103
[Global]
Available Disk = 4


Code: Select all
[~] # mdadm --examine /dev/sda3
/dev/sda3:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : a7a64c66:a0a12b00:6da9b78e:5626f6f1
  Creation Time : Fri May  6 15:13:26 2011
     Raid Level : raid5
  Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB)
     Array Size : 5855836800 (5584.56 GiB 5996.38 GB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 0

    Update Time : Wed Oct  5 03:24:26 2011
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0
       Checksum : c5ec6f7f - correct
         Events : 0.20

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     0       8        3        0      active sync   /dev/sda3

   0     0       8        3        0      active sync   /dev/sda3
   1     1       8       19        1      active sync   /dev/sdb3
   2     2       8       35        2      active sync   /dev/sdc3
   3     3       8       51        3      active sync   /dev/sdd3

[~] # mdadm --examine /dev/sdb3
/dev/sdb3:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : a7a64c66:a0a12b00:6da9b78e:5626f6f1
  Creation Time : Fri May  6 15:13:26 2011
     Raid Level : raid5
  Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB)
     Array Size : 5855836800 (5584.56 GiB 5996.38 GB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 0

    Update Time : Wed Oct  5 03:24:26 2011
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0
       Checksum : c5ec6f91 - correct
         Events : 0.20

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     1       8       19        1      active sync   /dev/sdb3

   0     0       8        3        0      active sync   /dev/sda3
   1     1       8       19        1      active sync   /dev/sdb3
   2     2       8       35        2      active sync   /dev/sdc3
   3     3       8       51        3      active sync   /dev/sdd3
[~] # mdadm --examine /dev/sdc3
/dev/sdc3:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : a7a64c66:a0a12b00:6da9b78e:5626f6f1
  Creation Time : Fri May  6 15:13:26 2011
     Raid Level : raid5
  Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB)
     Array Size : 5855836800 (5584.56 GiB 5996.38 GB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 0

    Update Time : Wed Oct  5 03:24:26 2011
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0
       Checksum : c5ec6fa3 - correct
         Events : 0.20

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     2       8       35        2      active sync   /dev/sdc3

   0     0       8        3        0      active sync   /dev/sda3
   1     1       8       19        1      active sync   /dev/sdb3
   2     2       8       35        2      active sync   /dev/sdc3
   3     3       8       51        3      active sync   /dev/sdd3
[~] # mdadm --examine /dev/sdd3
/dev/sdd3:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : a7a64c66:a0a12b00:6da9b78e:5626f6f1
  Creation Time : Fri May  6 15:13:26 2011
     Raid Level : raid5
  Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB)
     Array Size : 5855836800 (5584.56 GiB 5996.38 GB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 0

    Update Time : Wed Oct  5 03:24:26 2011
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0
       Checksum : c5ec6fb5 - correct
         Events : 0.20

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     3       8       51        3      active sync   /dev/sdd3

   0     0       8        3        0      active sync   /dev/sda3
   1     1       8       19        1      active sync   /dev/sdb3
   2     2       8       35        2      active sync   /dev/sdc3
   3     3       8       51        3      active sync   /dev/sdd3

pallenda
New here
 
Posts: 6
Joined: Fri May 13, 2011 12:41 am
NAS Model: TS-219P+

Re: help with recover volume 419p+ FW:3.5.0

Postby pallenda » Thu Oct 06, 2011 2:56 pm

After some nice qualified help from Alan from QNAP he found out that updating to 3.5.1 would be enough to fix this. After installing 3.5.1 and a reboot the RAID array was active again. Now just waiting for check desk to make sure the array is clean, but it looked like my data was all there. :)

Thanks!
pallenda
New here
 
Posts: 6
Joined: Fri May 13, 2011 12:41 am
NAS Model: TS-219P+

Re: help with recover volume 419p+ FW:3.5.0

Postby kll » Sat Oct 08, 2011 9:39 am

I had the same issue on a live upgrade from 3.4.0 B 0212T to 3.5.0 and lost access to all files. The raid array seemed to become corrupt and unmounted. I was not able to rebuild it in any way. I tried to restore from a backup config, but that didn't help.

I decided to upgrade to 3.5.1 Build 1002T and upon reboot the raid array automatically began to reconstruct. 7 hours later, I have my files back. I guess I'll be sure to make a backup next time before any live updates.
kll
New here
 
Posts: 2
Joined: Tue Jan 18, 2011 5:46 pm
NAS Model: NMP-1000

Re: help with recover volume 419p+ FW:3.5.0

Postby P3R » Sat Oct 08, 2011 3:45 pm

@kll,

You always need that backup, not only when doing firmware upgrades.
No, RAID has never ever been a replacement for backups. Without backups you will eventually lose data!
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Unfortunately I felt I had to leave this forum, this is the reason why...
P3R
Ask me anything
 
Posts: 5616
Joined: Sat Dec 29, 2007 1:39 am
Location: Sweden
NAS Model: TS-459 Pro II

Re: help with recover volume 419p+ FW:3.5.0

Postby RyanBanks » Sun Oct 09, 2011 5:39 pm

You can recover RAID data from hard drive with RAID recovery software easily.
Here is a tutorial to guide you how to do:
http://www.google.com.hk/search?hl=zh-C ... 0l0l0ll0l0
Hope this helps!
I pressed F5, and I'm feeling refreshed...
RyanBanks
New here
 
Posts: 9
Joined: Thu May 12, 2011 9:47 am
NAS Model: TS-409/409 Pro


Return to Users' Corner

Who is online

Users browsing this forum: No registered users and 1 guest