QNAP TS-439 Pro II lost RAID-5-configuration / Filesystem

How to use TestDisk to recover lost partition
Message
Author
SHaran
Posts: 9
Joined: 15 May 2015, 05:17

Re: QNAP TS-439 Pro II lost RAID-5-configuration / Filesyste

#21 Post by SHaran » 16 May 2015, 16:33

Bernd,
You need to tell it the partitions like so... mdadm --examine /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3

For the sector copy I suggest ddrescue. But that is a big task and may not be necessary if you are careful.

If you can post the output from mdadm --examine ...

Stephen

Sponsored links

berndms
Posts: 16
Joined: 09 May 2015, 10:20
Location: Stuttgart, Germany

Re: QNAP TS-439 Pro II lost RAID-5-configuration / Filesyste

#22 Post by berndms » 16 May 2015, 17:05

Stephen,
thanks a lot for this crash course in Unix - it's been a while that I was actively coding - and never at this level!
I have copied the output of the examination here. Seems mdadm is able to find something!

As you suggested, I will now try to find a hex editor and see if I can search for the magic number and superblock.
I suppose in my case it is the magic number a92b4efc.

Any comments heartily appreciated ;-)

Thanks
Bernd

Code: Select all

[~] # mdadm --examine /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3
/dev/sda3:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : 8702c698:87af3610:f421567d:1ca69982
  Creation Time : Sat May  1 04:22:09 2010
     Raid Level : raid5
  Used Dev Size : 2928697600 (2793.02 GiB 2998.99 GB)
     Array Size : 8786092800 (8379.07 GiB 8996.96 GB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 0

    Update Time : Fri Apr 24 05:43:20 2015
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0
       Checksum : 18577669 - correct
         Events : 0.374819

         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
/dev/sdb3:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : 8702c698:87af3610:f421567d:1ca69982
  Creation Time : Sat May  1 04:22:09 2010
     Raid Level : raid5
  Used Dev Size : 2928697600 (2793.02 GiB 2998.99 GB)
     Array Size : 8786092800 (8379.07 GiB 8996.96 GB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 0

    Update Time : Fri Apr 24 05:43:20 2015
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0
       Checksum : 1857767b - correct
         Events : 0.374819

         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
/dev/sdc3:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : 8702c698:87af3610:f421567d:1ca69982
  Creation Time : Sat May  1 04:22:09 2010
     Raid Level : raid5
  Used Dev Size : 2928697600 (2793.02 GiB 2998.99 GB)
     Array Size : 8786092800 (8379.07 GiB 8996.96 GB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 0

    Update Time : Fri Apr 24 05:43:20 2015
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0
       Checksum : 1857768d - correct
         Events : 0.374819

         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
/dev/sdd3:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : 8702c698:87af3610:f421567d:1ca69982
  Creation Time : Sat May  1 04:22:09 2010
     Raid Level : raid5
  Used Dev Size : 2928697600 (2793.02 GiB 2998.99 GB)
     Array Size : 8786092800 (8379.07 GiB 8996.96 GB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 0

    Update Time : Fri Apr 24 05:43:20 2015
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0
       Checksum : 1857769f - correct
         Events : 0.374819

         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

SHaran
Posts: 9
Joined: 15 May 2015, 05:17

Re: QNAP TS-439 Pro II lost RAID-5-configuration / Filesyste

#23 Post by SHaran » 16 May 2015, 17:28

The --examine looks very good. The RAID5 should assemble fine. But first post the output from: cat /proc/mdstat

And also: uname -a

Also no need to hex search for the superblock now, the --examine displayed it's contents.

Stephen

berndms
Posts: 16
Joined: 09 May 2015, 10:20
Location: Stuttgart, Germany

Re: QNAP TS-439 Pro II lost RAID-5-configuration / Filesyste

#24 Post by berndms » 16 May 2015, 17:52

Stephen,
thanks for your fast reply!

Here are the results:

1. for /proc/mdstat

Code: Select all

~] # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] 
md13 : active raid1 sdb4[0] sdc4[3] sda4[2] sdd4[1]
		 458880 blocks [4/4] [UUUU]
		 bitmap: 0/57 pages [0KB], 4KB chunk

unused devices: <none>
2. for uname -a

Code: Select all

[~] # uname -a
Linux NASBF51A2 3.4.6 #1 SMP Sat Nov 1 04:43:04 CST 2014 x86_64 unknown
[~] # 
Also, there was Patrick from Canada in the QNAP forum who helped me to get some info using a script he wrote.
I am attaching the output of his script here s well:

Code: Select all

** QNAP NAS Report ************************************************
** System switched on with disks inserted from beginning **
*************************************************************************

NAS Model: TS-439 Pro II
Firmware: 4.1.1 Build 20141101
System Name: NASBF51A2
Workgroup: NAS
BusyBox v1.01 (2014.09.01-17:31+0000) multi-call binary

Usage: dirname FILENAME

Strips non-directory suffix from FILENAME

Base Directory: 
NAS IP address: 192.168.2.56

Default Gateway Device: eth0

inet addr:192.168.2.56 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3240 errors:0 dropped:0 overruns:0 frame:0
TX packets:3179 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:327614 (319.9 KiB) TX bytes:449989 (439.4 KiB)
Interrupt:18 Memory:feae0000-feb00000 


DNS Nameserver(s):192.168.2.1


HDD Information:

HDD1 - Model=Hitachi HDS723030ALA640 , FwRev=MKAOA5C0, SerialNo= MK0351YHGEKBAA

Model: Hitachi HDS723030ALA640 (scsi)
Disk /dev/sda: 3001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 20.5kB 543MB 543MB ext3 primary
2 543MB 1086MB 543MB linux-swap(v1) primary
3 1086MB 3000GB 2999GB primary
4 3000GB 3001GB 510MB ext3 primary


001 Raw_Read_Error_Rate 0 100 100 016 OK
002 Throughput_Performance 89 134 134 054 OK
003 Spin_Up_Time 610 (Average 615) 126 126 024 OK
004 Start_Stop_Count 2512 100 100 000 OK
005 Reallocated_Sector_Ct 0 100 100 005 OK
007 Seek_Error_Rate 0 100 100 067 OK
008 Seek_Time_Performance 27 133 133 020 OK
009 Power_On_Hours 28631 096 096 000 OK
010 Spin_Retry_Count 0 100 100 060 OK
012 Power_Cycle_Count 202 100 100 000 OK
192 Power-Off_Retract_Count 2644 098 098 000 OK
193 Load_Cycle_Count 2644 098 098 000 OK
194 Temperature_Celsius 26 230 230 000 OK
196 Reallocated_Event_Count 0 100 100 000 OK
197 Current_Pending_Sector 0 100 100 000 OK
198 Offline_Uncorrectable 0 100 100 000 OK
199 UDMA_CRC_Error_Count 0 200 200 000 OK

HDD2 - Model=Hitachi HDS723030ALA640 , FwRev=MKAOA5C0, SerialNo= MK0331YHGLD64A

Model: Hitachi HDS723030ALA640 (scsi)
Disk /dev/sdb: 3001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 20.5kB 543MB 543MB ext3 primary
2 543MB 1086MB 543MB linux-swap(v1) primary
3 1086MB 3000GB 2999GB primary
4 3000GB 3001GB 510MB ext3 primary


001 Raw_Read_Error_Rate 0 100 100 016 OK
002 Throughput_Performance 89 134 134 054 OK
003 Spin_Up_Time 616 (Average 573) 130 130 024 OK
004 Start_Stop_Count 2503 100 100 000 OK
005 Reallocated_Sector_Ct 0 100 100 005 OK
007 Seek_Error_Rate 0 100 100 067 OK
008 Seek_Time_Performance 26 135 135 020 OK
009 Power_On_Hours 28619 096 096 000 OK
010 Spin_Retry_Count 0 100 100 060 OK
012 Power_Cycle_Count 204 100 100 000 OK
192 Power-Off_Retract_Count 2636 098 098 000 OK
193 Load_Cycle_Count 2636 098 098 000 OK
194 Temperature_Celsius 25 240 240 000 OK
196 Reallocated_Event_Count 0 100 100 000 OK
197 Current_Pending_Sector 0 100 100 000 OK
198 Offline_Uncorrectable 0 100 100 000 OK
199 UDMA_CRC_Error_Count 0 200 200 000 OK

HDD3 - Model=Hitachi HDS723030ALA640 , FwRev=MKAOA5C0, SerialNo= MK0351YHGEKEGA

Model: Hitachi HDS723030ALA640 (scsi)
Disk /dev/sdc: 3001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 20.5kB 543MB 543MB ext3 primary
2 543MB 1086MB 543MB linux-swap(v1) primary
3 1086MB 3000GB 2999GB primary
4 3000GB 3001GB 510MB ext3 primary


001 Raw_Read_Error_Rate 0 100 100 016 OK
002 Throughput_Performance 90 133 133 054 OK
003 Spin_Up_Time 636 (Average 593) 126 126 024 OK
004 Start_Stop_Count 2533 100 100 000 OK
005 Reallocated_Sector_Ct 0 100 100 005 OK
007 Seek_Error_Rate 0 100 100 067 OK
008 Seek_Time_Performance 26 135 135 020 OK
009 Power_On_Hours 28619 096 096 000 OK
010 Spin_Retry_Count 0 100 100 060 OK
012 Power_Cycle_Count 203 100 100 000 OK
192 Power-Off_Retract_Count 2664 098 098 000 OK
193 Load_Cycle_Count 2664 098 098 000 OK
194 Temperature_Celsius 25 240 240 000 OK
196 Reallocated_Event_Count 0 100 100 000 OK
197 Current_Pending_Sector 0 100 100 000 OK
198 Offline_Uncorrectable 0 100 100 000 OK
199 UDMA_CRC_Error_Count 0 200 200 000 OK

HDD4 - Model=Hitachi HDS723030ALA640 , FwRev=MKAOA5C0, SerialNo= MK0331YHGLSBHA

Model: Hitachi HDS723030ALA640 (scsi)
Disk /dev/sdd: 3001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 20.5kB 543MB 543MB ext3 primary
2 543MB 1086MB 543MB linux-swap(v1) primary
3 1086MB 3000GB 2999GB primary
4 3000GB 3001GB 510MB ext3 primary


001 Raw_Read_Error_Rate 0 100 100 016 OK
002 Throughput_Performance 85 135 135 054 OK
003 Spin_Up_Time 615 (Average 567) 131 131 024 OK
004 Start_Stop_Count 2530 100 100 000 OK
005 Reallocated_Sector_Ct 0 100 100 005 OK
007 Seek_Error_Rate 0 100 100 067 OK
008 Seek_Time_Performance 26 135 135 020 OK
009 Power_On_Hours 28611 096 096 000 OK
010 Spin_Retry_Count 0 100 100 060 OK
012 Power_Cycle_Count 204 100 100 000 OK
192 Power-Off_Retract_Count 2661 098 098 000 OK
193 Load_Cycle_Count 2661 098 098 000 OK
194 Temperature_Celsius 25 240 240 000 OK
196 Reallocated_Event_Count 0 100 100 000 OK
197 Current_Pending_Sector 0 100 100 000 OK
198 Offline_Uncorrectable 0 100 100 000 OK
199 UDMA_CRC_Error_Count 0 200 200 000 OK

Volume Status


Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] 
md13 : active raid1 sdb4[0] sdc4[3] sda4[2] sdd4[1]
458880 blocks [4/4] [UUUU]
bitmap: 0/57 pages [0KB], 4KB chunk

unused devices: <none>

Disk Space:

Filesystem Size Used Available Use% Mounted on
/dev/ram0 139.5M 121.4M 18.0M 87% /
tmpfs 64.0M 92.0k 63.9M 0% /tmp
tmpfs 494.5M 0 494.5M 0% /dev/shm
/dev/sda4 371.0M 268.8M 102.1M 72% /mnt/ext
tmpfs 32.0M 0 32.0M 0% /.eaccelerator.tmp

Mount Status:

/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=64M)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/bus/usb type usbfs (rw)
/dev/sda4 on /mnt/ext type ext3 (rw)
tmpfs on /.eaccelerator.tmp type tmpfs (rw,size=32M)


Memory Information:

total used free shared buffers
Mem: 1012688 405424 607264 0 7052
Swap: 0 0 0
Total: 1012688 405424 607264

NASReport completed on 2015-05-08 11:11:36 (/tmp/nasreport)
So I suppose, mdstat only recognizes the 2nd partitions?

/Bernd

SHaran
Posts: 9
Joined: 15 May 2015, 05:17

Re: QNAP TS-439 Pro II lost RAID-5-configuration / Filesyste

#25 Post by SHaran » 16 May 2015, 19:10

Well mdstat is only showing a RAID1 made from partition 4, which is odd that the others are missing.

You should be able to assemble and see your data if you run...

mdadm -v --assemble /dev/md0 /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3

mount /dev/md0 /share/MD0_DATA

ls /share/MD0_DATA

And maybe a coincidence but the remote QNAP recovery I performed back in Feb. 2014 was also for a client named Bernd. Perhaps we have met again? :)

Stephen

berndms
Posts: 16
Joined: 09 May 2015, 10:20
Location: Stuttgart, Germany

Re: QNAP TS-439 Pro II lost RAID-5-configuration / Filesyste

#26 Post by berndms » 16 May 2015, 20:10

Hi Stephen,

I don't hope it is related to the name ;-) Good for me, but it was another Bernd that you've made happy!
For me, it is the first time it happened, and I will for sure setup a working backup routine immediately!!

However, this may be only a short step (hopefully) from now, but mounting md0 failed.
Before proceeding, I would like to show you the output of some commands I ran, including the ones you listed:

Code: Select all

[/] # mdadm -v --assemble /dev/md0 /dev/sda3 /dev/sdb3 /dev/sdc3 /dev/sdd3
mdadm: looking for devices for /dev/md0
mdadm: /dev/sda3 is identified as a member of /dev/md0, slot 0.
mdadm: /dev/sdb3 is identified as a member of /dev/md0, slot 1.
mdadm: /dev/sdc3 is identified as a member of /dev/md0, slot 2.
mdadm: /dev/sdd3 is identified as a member of /dev/md0, slot 3.
mdadm: added /dev/sdb3 to /dev/md0 as 1
mdadm: added /dev/sdc3 to /dev/md0 as 2
mdadm: added /dev/sdd3 to /dev/md0 as 3
mdadm: added /dev/sda3 to /dev/md0 as 0
mdadm: /dev/md0 has been started with 4 drives.

[/] # mount /dev/md0 /share/MD0_DATA
mount: mount point /share/MD0_DATA does not exist

[/] # cat proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] 
md0 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[1]
		 8786092800 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
		 
md13 : active raid1 sdb4[0] sdc4[3] sda4[2] sdd4[1]
		 458880 blocks [4/4] [UUUU]
		 bitmap: 0/57 pages [0KB], 4KB chunk

unused devices: <none>

[/] # 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=64M)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/bus/usb type usbfs (rw)
/dev/sda4 on /mnt/ext type ext3 (rw)
tmpfs on /.eaccelerator.tmp type tmpfs (rw,size=32M)
[/] # 

[/share] # ls -l
drwxrwxrwx    2 admin    administ      1024 Sep 19  2005 HDA_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDB_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDC_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDD_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDE_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDF_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDG_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDH_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDI_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDJ_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDK_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDL_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDM_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDN_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDO_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDP_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDQ_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDR_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDS_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDT_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDU_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDV_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDW_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDX_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDY_DATA/
drwxrwxrwx    2 admin    administ      1024 Dec  7  2005 HDZ_DATA/
drwxrwxr-x   28 admin    administ      1024 Feb 28  2006 external/
[/share] # 
Is it as simple as "mkdir /share/MDO_DATA" to get over that error message?
And hoping that I will get to see my data: are the logical volumes I had created on the RAID-space going to show up as directories?

Thanks again,
Bernd the Second ;-)

SHaran
Posts: 9
Joined: 15 May 2015, 05:17

Re: QNAP TS-439 Pro II lost RAID-5-configuration / Filesyste

#27 Post by SHaran » 16 May 2015, 20:20

Yes run: mkdir /share/MD0_DATA

Then try the mount again.

To see logical volumes run: lvdisplay

berndms
Posts: 16
Joined: 09 May 2015, 10:20
Location: Stuttgart, Germany

Re: QNAP TS-439 Pro II lost RAID-5-configuration / Filesyste

#28 Post by berndms » 16 May 2015, 20:29

Stephen,
thanks - now mounting failed with

Code: Select all

[/] # mount /dev/md0 /share/MD0_DATA
mount: wrong fs type, bad option, bad superblock on /dev/md0,
       missing codepage or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

[/] # 
dmesg gave me

Code: Select all

[/] # dmesg | tail                  
[11017.363336] md/raid:md0: raid level 5 active with 4 out of 4 devices, algorithm 2
[11017.364208] RAID conf printout:
[11017.364213]  --- level:5 rd:4 wd:4
[11017.364220]  disk 0, o:1, dev:sda3
[11017.364225]  disk 1, o:1, dev:sdb3
[11017.364231]  disk 2, o:1, dev:sdc3
[11017.364236]  disk 3, o:1, dev:sdd3
[11017.364316] md0: detected capacity change from 0 to 8996959027200
[11041.230794]  md0: unknown partition table
[12734.603120] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (240)
[/] # 
In one of my earlier posts I saw testdisk coming up with an indication that the RAID was using ext4 as filesystem.

Code: Select all

block_group_nr 3

recover_EXT2: "e2fsck -b 98304 -B 4096 device" may be needed
recover_EXT2: s_block_group_nr=3/67032, s_mnt_count=22/4294967295, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 2196523200
recover_EXT2: part_size 17572185600
     MS Data                  1596294 17573781893 17572185600
     ext4 blocksize=4096 Large_file Sparse_SB Backup_SB, 8996 GB / 8379 GiB
This partition ends after the disk limits. (start=1596294, size=17572185600, end=17573781893, disk end=5860533168)

block_group_nr 3
To be honest, I am not sure if I chose ext4 on inital setup. But I think so...

Can I dare to "mount -t ext4" without destroying anything?

Or do you think it is a problem with the superblock?

BTW: testdisk now sees the RAID /dev/mdo and autodetects NO partitiontable. I have stopped here...

Thanks
Bernd

SHaran
Posts: 9
Joined: 15 May 2015, 05:17

Re: QNAP TS-439 Pro II lost RAID-5-configuration / Filesyste

#29 Post by SHaran » 17 May 2015, 05:20

Hmmm. Per dmesg it sees an ext3 but it looks damaged. No -t ext4 won't help or hurt.

You're right it looks like a superblock problem, the ext3 superblock that is.

I sent you a PM.

berndms
Posts: 16
Joined: 09 May 2015, 10:20
Location: Stuttgart, Germany

Re: QNAP TS-439 Pro II lost RAID-5-configuration / Filesyste

#30 Post by berndms » 17 May 2015, 09:04

Stephen,

mounting with the -t ext4 option did the trick! Why ever...
Everything is visible and accessible!

I still don't know what has happened, but I am currently copying / backing up everything and will setup a completely new system on newest firmware afterwards.

Really appreciating your consistent help, especially as I suppose you are in the business, but still helping people like me at this level! Thank you so much!

Bernd

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest