TS-859 Pro+ - RAID5 cannot be mounted after restart...

Printers, HDDs, USB/eSATA drives, 3rd-party programs
Post Reply
Dreamweaver
New here
Posts: 5
Joined: Sun Sep 04, 2011 4:42 am

TS-859 Pro+ - RAID5 cannot be mounted after restart...

Post by Dreamweaver » Fri Sep 16, 2011 9:24 am

Hi,

first of all my System:

- TS-859 Pro+ with FW 3.50 build 0815 - I own the system for 1,5 Weeks now and the first thing I did - flashing the new Firmware before I installed the HDDs.
- 8x Hitachi HDS723030ALA640 MKAO in RAID5 EXT4 without Encryption

What I did:
I put in the 8 HDDs, then I installed RAID5 for the 8 Drives, I formatted them with EXT4. After the format procedure everything was fine, the sync took about 24hrs after that I created users, groups, file shares etc... and copied in a lot of data. The whole thing took about 1 Week. In this time I didn't restart the NAS.

Now I decided to put the NAS to another place at home. I shutwown the NAS via Power Management. On their new place I started the NAS normally, it powered up and everything seems to be good... but it fails to mount the Raid.


Here are some Pictures and dumps... please help me!!!


Boot-Log (dmesg):

Code: Select all

login as: admin
admin@192.168.2.125's password:
[~] # dmesg
0.250928] md: bind<sdf4>
[   50.251266] md: bind<sdg4>
[   50.251588] md: bind<sdh4>
[   50.251830] md: bind<sda4>
[   50.253467] raid1: raid set md13 active with 8 out of 8 mirrors
[   50.257192] md13: bitmap initialized from disk: read 4/4 pages, set 0 bits
[   50.257306] created bitmap (57 pages) for device md13
[   50.286964] md13: detected capacity change from 0 to 469893120
[   50.291071]  md13: unknown partition table
[   51.697288] kjournald starting.  Commit interval 5 seconds
[   51.749954] EXT3-fs (md9): using internal journal
[   51.750126] EXT3-fs (md9): mounted filesystem with writeback data mode
[   70.325304] kjournald starting.  Commit interval 5 seconds
[   70.387568] EXT3-fs (md9): using internal journal
[   70.387741] EXT3-fs (md9): mounted filesystem with writeback data mode
[   89.050514] kjournald starting.  Commit interval 5 seconds
[   89.121988] EXT3-fs (md13): using internal journal
[   89.122171] EXT3-fs (md13): mounted filesystem with writeback data mode
[   92.673151] usbcore: registered new interface driver hiddev
[   92.677539] usbcore: registered new interface driver usbhid
[   92.677658] usbhid: USB HID core driver
[   92.681177] Register ICH/PCH RTC driver.
[   92.686647] iTCO_vendor_support: vendor-support=0
[   92.691776] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.05
[   92.694895] iTCO_wdt: Found a ICH9R TCO device (Version=2, TCOBASE=0x0860)
[   92.696345] iTCO_wdt: initialized. heartbeat=120 sec (nowayout=0)
[   92.703543] usbcore: registered new interface driver usblp
[   92.710645] ufsd: module license 'Commercial product' taints kernel.
[   92.710783] Disabling lock debugging due to kernel taint
[   92.736853] ufsd: driver 8.3 (Aug 15 2011 01:44:00) with acl LBD=OFF with ioctl loaded at ffffffffa00b5000
[   92.736858] NTFS read/write support included
[   92.736860] Hfs+/HfsX read/write support included
[   92.760673] fnotify: Load file notify kernel module.
[   92.761093] fnotify:   Global_Private_Data_List_Init()
[   92.761252] fnotify:   Launch the fnotify thread: 1856
[   92.761260] fnotify:   The fnotify thread starts...
[   93.821906] usbcore: registered new interface driver snd-usb-audio
[   93.831461] usbcore: registered new interface driver snd-usb-caiaq
[   93.863959] pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   93.864083] pci 0000:00:02.0: setting latency timer to 64
[   93.877759]   alloc irq_desc for 35 on node -1
[   93.877767]   alloc kstat_irqs on node -1
[   93.877780] pci 0000:00:02.0: irq 35 for MSI/MSI-X
[   93.878120] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[   93.896641] Linux video capture interface: v2.00
[   93.917326] usbcore: registered new interface driver uvcvideo
[   93.917455] USB Video Class driver (v0.1.0)
[   94.062091] 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
[   94.062217] All bugs added by David S. Miller <davem@redhat.com>
[   94.525545] kjournald starting.  Commit interval 5 seconds
[   94.533293] EXT3-fs (md9): using internal journal
[   94.533482] EXT3-fs (md9): mounted filesystem with writeback data mode
[   97.274495] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[   97.424108] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[   97.814823] active port 0 :139
[   97.814938] active port 1 :445
[   97.815058] active port 2 :20
[  100.011547] md: bind<sda2>
[  100.013903] raid1: raid set md8 active with 1 out of 1 mirrors
[  100.014061] md8: detected capacity change from 0 to 542769152
[  101.018927]  md8: unknown partition table
[  103.189791] Adding 530040k swap on /dev/md8.  Priority:-1 extents:1 across:530040k
[  107.151815] md: bind<sdb2>
[  107.169447] RAID1 conf printout:
[  107.169559]  --- wd:1 rd:2
[  107.169671]  disk 0, wo:0, o:1, dev:sda2
[  107.169790]  disk 1, wo:1, o:1, dev:sdb2
[  107.170002] md: recovery of RAID array md8
[  107.170145] md: minimum _guaranteed_  speed: 5000 KB/sec/disk.
[  107.170269] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
[  107.170452] md: using 128k window, over a total of 530048 blocks.
[  109.328485] md: bind<sdc2>
[  111.507911] md: bind<sdd2>
[  113.749034] md: bind<sde2>
[  114.907424] md: md0 stopped.
[  114.924856] md: md0 stopped.
[  115.358772] md: bind<sdb3>
[  115.359010] md: bind<sdc3>
[  115.359241] md: bind<sdd3>
[  115.359527] md: bind<sde3>
[  115.359819] md: bind<sdf3>
[  115.360131] md: bind<sdg3>
[  115.360444] md: bind<sdh3>
[  115.360677] md: bind<sda3>
[  115.362131] raid5: device sda3 operational as raid disk 0
[  115.362236] raid5: device sdh3 operational as raid disk 7
[  115.362341] raid5: device sdg3 operational as raid disk 6
[  115.362449] raid5: device sdf3 operational as raid disk 5
[  115.362548] raid5: device sde3 operational as raid disk 4
[  115.362646] raid5: device sdd3 operational as raid disk 3
[  115.362745] raid5: device sdc3 operational as raid disk 2
[  115.362843] raid5: device sdb3 operational as raid disk 1
[  115.379303] raid5: allocated 135840kB for md0
[  115.379532] 0: w=1 pa=0 pr=8 m=1 a=2 r=8 op1=0 op2=0
[  115.379638] 7: w=2 pa=0 pr=8 m=1 a=2 r=8 op1=0 op2=0
[  115.379735] 6: w=3 pa=0 pr=8 m=1 a=2 r=8 op1=0 op2=0
[  115.379833] 5: w=4 pa=0 pr=8 m=1 a=2 r=8 op1=0 op2=0
[  115.379931] 4: w=5 pa=0 pr=8 m=1 a=2 r=8 op1=0 op2=0
[  115.380034] 3: w=6 pa=0 pr=8 m=1 a=2 r=8 op1=0 op2=0
[  115.380148] 2: w=7 pa=0 pr=8 m=1 a=2 r=8 op1=0 op2=0
[  115.380247] 1: w=8 pa=0 pr=8 m=1 a=2 r=8 op1=0 op2=0
[  115.380348] raid5: raid level 5 set md0 active with 8 out of 8 devices, algorithm 2
[  115.380505] RAID5 conf printout:
[  115.380596]  --- rd:8 wd:8
[  115.380686]  disk 0, o:1, dev:sda3
[  115.380778]  disk 1, o:1, dev:sdb3
[  115.380870]  disk 2, o:1, dev:sdc3
[  115.380961]  disk 3, o:1, dev:sdd3
[  115.381066]  disk 4, o:1, dev:sde3
[  115.381172]  disk 5, o:1, dev:sdf3
[  115.381266]  disk 6, o:1, dev:sdg3
[  115.381357]  disk 7, o:1, dev:sdh3
[  115.381543] md0: detected capacity change from 0 to 20992903938048
[  115.923716] md: bind<sdf2>
[  116.595614]  md0: unknown partition table
[  117.114595] EXT4-fs (md0): ext4_check_descriptors: Checksum for group 35712 failed (59361!=53007)
[  117.114826] EXT4-fs (md0): group descriptors corrupted!
[  118.073836] md: bind<sdg2>
[  119.694531] bonding: Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
[  119.694714] bonding: MII link monitoring set to 100 ms
[  119.780222] bonding: bond0: enslaving eth0 as an active interface with a down link.
[  119.864212] bonding: bond0: enslaving eth1 as an active interface with a down link.
[  120.319806] md: bind<sdh2>
[  122.711106] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[  122.797039] bonding: bond0: link status definitely up for interface eth0.
[  123.003181] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[  123.098313] bonding: bond0: link status definitely up for interface eth1.
[  127.164511] md: md8: recovery done.
[  127.302065] RAID1 conf printout:
[  127.302202]  --- wd:2 rd:2
[  127.302309]  disk 0, wo:0, o:1, dev:sda2
[  127.302420]  disk 1, wo:0, o:1, dev:sdb2
[  142.134431] active port 0 :139
[  142.134526] active port 1 :445
[  142.134615] active port 2 :20
[  142.219504] warning: `proftpd' uses 32-bit capabilities (legacy support in use)
[  168.247387] rule type=2, num=0
[  168.254237]  Set Adpater:port=0:0 standby to 241 (1800 secs).
[  168.261358]  Set Adpater:port=0:1 standby to 241 (1800 secs).
[  168.268186]  Set Adpater:port=0:2 standby to 241 (1800 secs).
[  168.273053]  Set Adpater:port=0:3 standby to 241 (1800 secs).
[  170.086153] Loading iSCSI transport class v2.0-871.
[  170.159872] iscsi: registered transport (tcp)
[~] #

-------> [ 116.595614] md0: unknown partition table
[ 117.114595] EXT4-fs (md0): ext4_check_descriptors: Checksum for group 35712 failed (59361!=53007)
[ 117.114826] EXT4-fs (md0): group descriptors corrupted!



RAID5-Config...

Code: Select all

[~] # mdadm --detail /dev/md0
/dev/md0:
        Version : 01.00.03
  Creation Time : Thu Sep  8 21:17:11 2011
     Raid Level : raid5
     Array Size : 20500882752 (19551.17 GiB 20992.90 GB)
  Used Dev Size : 2928697536 (2793.02 GiB 2998.99 GB)
   Raid Devices : 8
  Total Devices : 8
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Thu Sep 15 19:15:27 2011
          State : clean
 Active Devices : 8
Working Devices : 8
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 64K

           Name : 0
           UUID : 5457aee4:2e49b3ac:79a297f3:914a2283
         Events : 645857

    Number   Major   Minor   RaidDevice State
       0       8        3        0      active sync   /dev/sda3
       1       8       19        1      active sync   /dev/sdb3
       2       8       35        2      active sync   /dev/sdc3
       3       8       51        3      active sync   /dev/sdd3
       4       8       67        4      active sync   /dev/sde3
       5       8       83        5      active sync   /dev/sdf3
       6       8       99        6      active sync   /dev/sdg3
       7       8      115        7      active sync   /dev/sdh3


mdstat:

Code: Select all

login as: admin
admin@192.168.2.125's password:
[~] # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath]
md0 : active raid5 sda3[0] sdh3[7] sdg3[6] sdf3[5] sde3[4] sdd3[3] sdc3[2] sdb3[1]
      20500882752 blocks super 1.0 level 5, 64k chunk, algorithm 2 [8/8] [UUUUUUUU]

md8 : active raid1 sdh2[2](S) sdg2[3](S) sdf2[4](S) sde2[5](S) sdd2[6](S) sdc2[7](S) sdb2[1] sda2[0]
      530048 blocks [2/2] [UU]

md13 : active raid1 sda4[0] sdh4[7] sdg4[6] sdf4[5] sde4[4] sdd4[3] sdc4[2] sdb4[1]
      458880 blocks [8/8] [UUUUUUUU]
      bitmap: 0/57 pages [0KB], 4KB chunk

md9 : active raid1 sda1[0] sdh1[7] sdg1[6] sde1[5] sdf1[4] sdd1[3] sdc1[2] sdb1[1]
      530048 blocks [8/8] [UUUUUUUU]
      bitmap: 0/65 pages [0KB], 4KB chunk

unused devices: <none>



8x HDD:

Code: Select all

[~] # mdadm --examine /dev/sda3
/dev/sda3:
          Magic : a92b4efc
        Version : 1.0
    Feature Map : 0x0
     Array UUID : 5457aee4:2e49b3ac:79a297f3:914a2283
           Name : 0
  Creation Time : Thu Sep  8 21:17:11 2011
     Raid Level : raid5
   Raid Devices : 8

  Used Dev Size : 5857395112 (2793.02 GiB 2998.99 GB)
     Array Size : 41001765504 (19551.17 GiB 20992.90 GB)
      Used Size : 5857395072 (2793.02 GiB 2998.99 GB)
   Super Offset : 5857395368 sectors
          State : clean
    Device UUID : 9d149b64:ba714ff4:fe62813e:0ac636b1

    Update Time : Fri Sep 16 02:29:40 2011
       Checksum : ae41a29d - correct
         Events : 663909

         Layout : left-symmetric
     Chunk Size : 64K

    Array Slot : 0 (0, 1, 2, 3, 4, 5, 6, 7)
   Array State : Uuuuuuuu


Code: Select all

[~] # mdadm --examine /dev/sdb3
/dev/sdb3:
          Magic : a92b4efc
        Version : 1.0
    Feature Map : 0x0
     Array UUID : 5457aee4:2e49b3ac:79a297f3:914a2283
           Name : 0
  Creation Time : Thu Sep  8 21:17:11 2011
     Raid Level : raid5
   Raid Devices : 8

  Used Dev Size : 5857395112 (2793.02 GiB 2998.99 GB)
     Array Size : 41001765504 (19551.17 GiB 20992.90 GB)
      Used Size : 5857395072 (2793.02 GiB 2998.99 GB)
   Super Offset : 5857395368 sectors
          State : clean
    Device UUID : 191f28b1:f766bc57:d41f4f0a:ea695805

    Update Time : Fri Sep 16 02:30:37 2011
       Checksum : 7e2b0375 - correct
         Events : 663957

         Layout : left-symmetric
     Chunk Size : 64K

    Array Slot : 1 (0, 1, 2, 3, 4, 5, 6, 7)
   Array State : uUuuuuuu
[~] #

Code: Select all

[~] # mdadm --examine /dev/sdc3
/dev/sdc3:
          Magic : a92b4efc
        Version : 1.0
    Feature Map : 0x0
     Array UUID : 5457aee4:2e49b3ac:79a297f3:914a2283
           Name : 0
  Creation Time : Thu Sep  8 21:17:11 2011
     Raid Level : raid5
   Raid Devices : 8

  Used Dev Size : 5857395112 (2793.02 GiB 2998.99 GB)
     Array Size : 41001765504 (19551.17 GiB 20992.90 GB)
      Used Size : 5857395072 (2793.02 GiB 2998.99 GB)
   Super Offset : 5857395368 sectors
          State : clean
    Device UUID : 540199dd:389296ed:f0d43641:145d69b9

    Update Time : Fri Sep 16 02:31:04 2011
       Checksum : 2b6eb96d - correct
         Events : 663981

         Layout : left-symmetric
     Chunk Size : 64K

    Array Slot : 2 (0, 1, 2, 3, 4, 5, 6, 7)
   Array State : uuUuuuuu
[~] #

Code: Select all

[~] # mdadm --examine /dev/sdd3
/dev/sdd3:
          Magic : a92b4efc
        Version : 1.0
    Feature Map : 0x0
     Array UUID : 5457aee4:2e49b3ac:79a297f3:914a2283
           Name : 0
  Creation Time : Thu Sep  8 21:17:11 2011
     Raid Level : raid5
   Raid Devices : 8

  Used Dev Size : 5857395112 (2793.02 GiB 2998.99 GB)
     Array Size : 41001765504 (19551.17 GiB 20992.90 GB)
      Used Size : 5857395072 (2793.02 GiB 2998.99 GB)
   Super Offset : 5857395368 sectors
          State : clean
    Device UUID : 9f3cab97:2229c40f:e4b3873a:9c52a4bb

    Update Time : Fri Sep 16 02:31:22 2011
       Checksum : 33a6040 - correct
         Events : 663997

         Layout : left-symmetric
     Chunk Size : 64K

    Array Slot : 3 (0, 1, 2, 3, 4, 5, 6, 7)
   Array State : uuuUuuuu
[~] #


Code: Select all

[~] # mdadm --examine /dev/sde3
/dev/sde3:
          Magic : a92b4efc
        Version : 1.0
    Feature Map : 0x0
     Array UUID : 5457aee4:2e49b3ac:79a297f3:914a2283
           Name : 0
  Creation Time : Thu Sep  8 21:17:11 2011
     Raid Level : raid5
   Raid Devices : 8

  Used Dev Size : 5857395112 (2793.02 GiB 2998.99 GB)
     Array Size : 41001765504 (19551.17 GiB 20992.90 GB)
      Used Size : 5857395072 (2793.02 GiB 2998.99 GB)
   Super Offset : 5857395368 sectors
          State : clean
    Device UUID : 41d2f62a:44b2c5f0:c912446d:cdb6ef4e

    Update Time : Fri Sep 16 02:31:41 2011
       Checksum : 3d8f423e - correct
         Events : 664013

         Layout : left-symmetric
     Chunk Size : 64K

    Array Slot : 4 (0, 1, 2, 3, 4, 5, 6, 7)
   Array State : uuuuUuuu
[~] #

Code: Select all

[~] # mdadm --examine /dev/sdf3
/dev/sdf3:
          Magic : a92b4efc
        Version : 1.0
    Feature Map : 0x0
     Array UUID : 5457aee4:2e49b3ac:79a297f3:914a2283
           Name : 0
  Creation Time : Thu Sep  8 21:17:11 2011
     Raid Level : raid5
   Raid Devices : 8

  Used Dev Size : 5857395112 (2793.02 GiB 2998.99 GB)
     Array Size : 41001765504 (19551.17 GiB 20992.90 GB)
      Used Size : 5857395072 (2793.02 GiB 2998.99 GB)
   Super Offset : 5857395368 sectors
          State : clean
    Device UUID : f18f1e80:7ebf18a7:717a0aed:a085d415

    Update Time : Fri Sep 16 02:31:59 2011
       Checksum : 8fb543c6 - correct
         Events : 664029

         Layout : left-symmetric
     Chunk Size : 64K

    Array Slot : 5 (0, 1, 2, 3, 4, 5, 6, 7)
   Array State : uuuuuUuu

Code: Select all

[~] # mdadm --examine /dev/sdg3
/dev/sdg3:
          Magic : a92b4efc
        Version : 1.0
    Feature Map : 0x0
     Array UUID : 5457aee4:2e49b3ac:79a297f3:914a2283
           Name : 0
  Creation Time : Thu Sep  8 21:17:11 2011
     Raid Level : raid5
   Raid Devices : 8

  Used Dev Size : 5857395112 (2793.02 GiB 2998.99 GB)
     Array Size : 41001765504 (19551.17 GiB 20992.90 GB)
      Used Size : 5857395072 (2793.02 GiB 2998.99 GB)
   Super Offset : 5857395368 sectors
          State : clean
    Device UUID : ff5dc905:2fea9a94:5f042187:2ce10bef

    Update Time : Fri Sep 16 02:32:17 2011
       Checksum : 76302222 - correct
         Events : 664045

         Layout : left-symmetric
     Chunk Size : 64K

    Array Slot : 6 (0, 1, 2, 3, 4, 5, 6, 7)
   Array State : uuuuuuUu

Code: Select all

[~] # mdadm --examine /dev/sdh3
/dev/sdh3:
          Magic : a92b4efc
        Version : 1.0
    Feature Map : 0x0
     Array UUID : 5457aee4:2e49b3ac:79a297f3:914a2283
           Name : 0
  Creation Time : Thu Sep  8 21:17:11 2011
     Raid Level : raid5
   Raid Devices : 8

  Used Dev Size : 5857395112 (2793.02 GiB 2998.99 GB)
     Array Size : 41001765504 (19551.17 GiB 20992.90 GB)
      Used Size : 5857395072 (2793.02 GiB 2998.99 GB)
   Super Offset : 5857395368 sectors
          State : clean
    Device UUID : 57bbd9a9:c3a568cd:57ee7af5:1d4ea8b9

    Update Time : Fri Sep 16 02:32:26 2011
       Checksum : 8c04920a - correct
         Events : 664053

         Layout : left-symmetric
     Chunk Size : 64K

    Array Slot : 7 (0, 1, 2, 3, 4, 5, 6, 7)
   Array State : uuuuuuuU



Bad Block Scan is still working... the scan for the first four HDDs is ready...
You do not have the required permissions to view the files attached to this post.

Dreamweaver
New here
Posts: 5
Joined: Sun Sep 04, 2011 4:42 am

Re: TS-859 Pro+ - RAID5 cannot be mounted after restart...

Post by Dreamweaver » Fri Sep 16, 2011 7:16 pm

BadBlock Scan finished:

Nothing changed.

Code: Select all

[~] # dmesg | tail
[  141.222570] warning: `proftpd' uses 32-bit capabilities (legacy support in use)
[  168.327972] rule type=2, num=0
[  168.329766]  Set Adpater:port=0:0 standby to 241 (1800 secs).
[  168.335467]  Set Adpater:port=0:1 standby to 241 (1800 secs).
[  168.341088]  Set Adpater:port=0:2 standby to 241 (1800 secs).
[  168.346714]  Set Adpater:port=0:3 standby to 241 (1800 secs).
[  170.188876] Loading iSCSI transport class v2.0-871.
[  170.262167] iscsi: registered transport (tcp)
[  355.214129] EXT4-fs (md0): ext4_check_descriptors: Checksum for group 35712 failed (59361!=53007)
[  355.214363] EXT4-fs (md0): group descriptors corrupted!
[~] #



Code: Select all

[~] # dmesg
9.835274] md: bind<sdf4>
[   49.835608] md: bind<sdg4>
[   49.835939] md: bind<sdh4>
[   49.836183] md: bind<sda4>
[   49.837803] raid1: raid set md13 active with 8 out of 8 mirrors
[   49.841538] md13: bitmap initialized from disk: read 4/4 pages, set 0 bits
[   49.841645] created bitmap (57 pages) for device md13
[   49.862986] md13: detected capacity change from 0 to 469893120
[   49.867144]  md13: unknown partition table
[   51.263368] kjournald starting.  Commit interval 5 seconds
[   51.317483] EXT3-fs (md9): using internal journal
[   51.317655] EXT3-fs (md9): mounted filesystem with writeback data mode
[   69.808375] kjournald starting.  Commit interval 5 seconds
[   69.849005] EXT3-fs (md9): using internal journal
[   69.849180] EXT3-fs (md9): mounted filesystem with writeback data mode
[   88.599425] kjournald starting.  Commit interval 5 seconds
[   88.670779] EXT3-fs (md13): using internal journal
[   88.670952] EXT3-fs (md13): mounted filesystem with writeback data mode
[   92.221779] usbcore: registered new interface driver hiddev
[   92.222261] usbcore: registered new interface driver usbhid
[   92.222429] usbhid: USB HID core driver
[   92.229181] Register ICH/PCH RTC driver.
[   92.234335] iTCO_vendor_support: vendor-support=0
[   92.240616] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.05
[   92.241433] iTCO_wdt: Found a ICH9R TCO device (Version=2, TCOBASE=0x0860)
[   92.241997] iTCO_wdt: initialized. heartbeat=120 sec (nowayout=0)
[   92.252037] usbcore: registered new interface driver usblp
[   92.259020] ufsd: module license 'Commercial product' taints kernel.
[   92.259143] Disabling lock debugging due to kernel taint
[   92.283472] ufsd: driver 8.3 (Aug 15 2011 01:44:00) with acl LBD=OFF with ioctl loaded at ffffffffa00b5000
[   92.283477] NTFS read/write support included
[   92.283479] Hfs+/HfsX read/write support included
[   92.308919] fnotify: Load file notify kernel module.
[   92.309417] fnotify:   Global_Private_Data_List_Init()
[   92.309571] fnotify:   Launch the fnotify thread: 1851
[   92.309776] fnotify:   The fnotify thread starts...
[   93.374454] usbcore: registered new interface driver snd-usb-audio
[   93.383122] usbcore: registered new interface driver snd-usb-caiaq
[   93.415765] pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   93.415884] pci 0000:00:02.0: setting latency timer to 64
[   93.429553]   alloc irq_desc for 35 on node -1
[   93.429560]   alloc kstat_irqs on node -1
[   93.429573] pci 0000:00:02.0: irq 35 for MSI/MSI-X
[   93.429917] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[   93.448363] Linux video capture interface: v2.00
[   93.467367] usbcore: registered new interface driver uvcvideo
[   93.467502] USB Video Class driver (v0.1.0)
[   93.612901] 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
[   93.613034] All bugs added by David S. Miller <davem@redhat.com>
[   94.111684] kjournald starting.  Commit interval 5 seconds
[   94.119197] EXT3-fs (md9): using internal journal
[   94.119372] EXT3-fs (md9): mounted filesystem with writeback data mode
[   95.821499] active port 0 :139
[   95.821593] active port 1 :445
[   95.821683] active port 2 :20
[   96.504198] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[   96.813179] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[   99.813388] md: bind<sda2>
[   99.815034] raid1: raid set md8 active with 1 out of 1 mirrors
[   99.815204] md8: detected capacity change from 0 to 542769152
[  100.820984]  md8: unknown partition table
[  102.897751] Adding 530040k swap on /dev/md8.  Priority:-1 extents:1 across:530040k
[  106.886236] md: bind<sdb2>
[  106.902452] RAID1 conf printout:
[  106.902569]  --- wd:1 rd:2
[  106.902675]  disk 0, wo:0, o:1, dev:sda2
[  106.902789]  disk 1, wo:1, o:1, dev:sdb2
[  106.903075] md: recovery of RAID array md8
[  106.903197] md: minimum _guaranteed_  speed: 5000 KB/sec/disk.
[  106.903310] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
[  106.903487] md: using 128k window, over a total of 530048 blocks.
[  109.052820] md: bind<sdc2>
[  111.114992] md: bind<sdd2>
[  113.212479] md: bind<sde2>
[  113.618298] md: md0 stopped.
[  113.629539] md: md0 stopped.
[  113.834664] md: bind<sdb3>
[  113.834903] md: bind<sdc3>
[  113.835126] md: bind<sdd3>
[  113.835422] md: bind<sde3>
[  113.835722] md: bind<sdf3>
[  113.836073] md: bind<sdg3>
[  113.836399] md: bind<sdh3>
[  113.836618] md: bind<sda3>
[  113.838072] raid5: device sda3 operational as raid disk 0
[  113.838180] raid5: device sdh3 operational as raid disk 7
[  113.838286] raid5: device sdg3 operational as raid disk 6
[  113.838394] raid5: device sdf3 operational as raid disk 5
[  113.838493] raid5: device sde3 operational as raid disk 4
[  113.838591] raid5: device sdd3 operational as raid disk 3
[  113.838689] raid5: device sdc3 operational as raid disk 2
[  113.838787] raid5: device sdb3 operational as raid disk 1
[  113.855208] raid5: allocated 135840kB for md0
[  113.855441] 0: w=1 pa=0 pr=8 m=1 a=2 r=8 op1=0 op2=0
[  113.855543] 7: w=2 pa=0 pr=8 m=1 a=2 r=8 op1=0 op2=0
[  113.855641] 6: w=3 pa=0 pr=8 m=1 a=2 r=8 op1=0 op2=0
[  113.855739] 5: w=4 pa=0 pr=8 m=1 a=2 r=8 op1=0 op2=0
[  113.855837] 4: w=5 pa=0 pr=8 m=1 a=2 r=8 op1=0 op2=0
[  113.855936] 3: w=6 pa=0 pr=8 m=1 a=2 r=8 op1=0 op2=0
[  113.856040] 2: w=7 pa=0 pr=8 m=1 a=2 r=8 op1=0 op2=0
[  113.856143] 1: w=8 pa=0 pr=8 m=1 a=2 r=8 op1=0 op2=0
[  113.856244] raid5: raid level 5 set md0 active with 8 out of 8 devices, algorithm 2
[  113.856410] RAID5 conf printout:
[  113.856501]  --- rd:8 wd:8
[  113.856592]  disk 0, o:1, dev:sda3
[  113.856683]  disk 1, o:1, dev:sdb3
[  113.856776]  disk 2, o:1, dev:sdc3
[  113.856867]  disk 3, o:1, dev:sdd3
[  113.856958]  disk 4, o:1, dev:sde3
[  113.857054]  disk 5, o:1, dev:sdf3
[  113.857150]  disk 6, o:1, dev:sdg3
[  113.857242]  disk 7, o:1, dev:sdh3
[  113.857429] md0: detected capacity change from 0 to 20992903938048
[  115.069886]  md0: unknown partition table
[  115.347567] md: bind<sdf2>
[  115.660630] EXT4-fs (md0): ext4_check_descriptors: Checksum for group 35712 failed (59361!=53007)
[  115.660861] EXT4-fs (md0): group descriptors corrupted!
[  117.464994] md: bind<sdg2>
[  118.043016] bonding: Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
[  118.043222] bonding: MII link monitoring set to 100 ms
[  118.128222] bonding: bond0: enslaving eth0 as an active interface with a down link.
[  118.212282] bonding: bond0: enslaving eth1 as an active interface with a down link.
[  119.795762] md: bind<sdh2>
[  120.993104] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[  121.046033] bonding: bond0: link status definitely up for interface eth0.
[  121.290442] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[  121.346066] bonding: bond0: link status definitely up for interface eth1.
[  125.751284] md: md8: recovery done.
[  125.851810] RAID1 conf printout:
[  125.851917]  --- wd:2 rd:2
[  125.852010]  disk 0, wo:0, o:1, dev:sda2
[  125.852106]  disk 1, wo:0, o:1, dev:sdb2
[  141.161542] active port 0 :139
[  141.161637] active port 1 :445
[  141.161726] active port 2 :20
[  141.222570] warning: `proftpd' uses 32-bit capabilities (legacy support in use)
[  168.327972] rule type=2, num=0
[  168.329766]  Set Adpater:port=0:0 standby to 241 (1800 secs).
[  168.335467]  Set Adpater:port=0:1 standby to 241 (1800 secs).
[  168.341088]  Set Adpater:port=0:2 standby to 241 (1800 secs).
[  168.346714]  Set Adpater:port=0:3 standby to 241 (1800 secs).
[  170.188876] Loading iSCSI transport class v2.0-871.
[  170.262167] iscsi: registered transport (tcp)
[~] #


Code: Select all

[~] # mount /dev/md0 /share/MD0_DATA/ -t ext4
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

[~] #

Dreamweaver
New here
Posts: 5
Joined: Sun Sep 04, 2011 4:42 am

Re: TS-859 Pro+ - RAID5 cannot be mounted after restart...

Post by Dreamweaver » Sat Sep 17, 2011 8:51 am

** yeah... I got a solution!

viewtopic.php?f=25&t=41688&p=224850#p224850

I will send all the #*&%& back to my dealer.

White-Rabbit
Getting the hang of things
Posts: 77
Joined: Wed May 13, 2009 11:20 pm

Re: TS-859 Pro+ - RAID5 cannot be mounted after restart...

Post by White-Rabbit » Tue Sep 11, 2012 7:27 pm

Hello,

I got the same issue with my TS439 Pro

It look like I setup the RAID 5 of my 3x 3TB Drive with the Firmware 3.7.3, but the qnap suddenly down to Firmware to 1.0.2 when I reboot it.

Now I have the same EXT4-fs (md0): group descriptors corrupted! info, and can't access my data anymore.

Even after I updated my system to 3.7.3 again through QFinder.

Any idea how I could repair my system ?
QNAP TS-439 Pro with 4 x HD Seagate 1.5 TB - F/W: 3.4.4
Apple MacBook Air - iMac - on Lion

User avatar
raffe
Know my way around
Posts: 165
Joined: Thu Nov 08, 2007 8:03 pm

Re: TS-859 Pro+ - RAID5 cannot be mounted after restart...

Post by raffe » Wed Oct 31, 2012 12:34 am

Maybe one solution:

I also got an unmounted RAID6 after an automatic firmware update. Web GUI - System Administration - system logs said:

Code: Select all

[RAID6 Disk Volume: Drive 1 2 3 4 5 6 7 8] The file system is not clean. It is suggested that you run "check disk".


If I tried manual mount:

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


and if I tried to start with init:

Code: Select all

/etc/init.d/init_disk.sh start
Starting Disk initialized:
Check config files...start
No need to do recovery.
storage_boot_init 2 ...
mdadm: /dev/md0 not identified in config file.
mdadm: stopped /dev/md0
mdadm: /dev/md0 has been started with 8 drives.
storage_boot_init.c: Start raid device /dev/md0 successfully
md0 : active raid6 sda3[0] sdh3[7] sdg3[6] sdf3[5] sde3[4] sdd3[3] sdc3[2] sdb3[1]
md0 : active raid6 sda3[0] sdh3[7] sdg3[6] sdf3[5] sde3[4] sdd3[3] sdc3[2] sdb3[1]
md0 : active raid6 sda3[0] sdh3[7] sdg3[6] sdf3[5] sde3[4] sdd3[3] sdc3[2] sdb3[1]
md0 : active raid6 sda3[0] sdh3[7] sdg3[6] sdf3[5] sde3[4] sdd3[3] sdc3[2] sdb3[1]
md0 : active raid6 sda3[0] sdh3[7] sdg3[6] sdf3[5] sde3[4] sdd3[3] sdc3[2] sdb3[1]
md0 : active raid6 sda3[0] sdh3[7] sdg3[6] sdf3[5] sde3[4] sdd3[3] sdc3[2] sdb3[1]
md0 : active raid6 sda3[0] sdh3[7] sdg3[6] sdf3[5] sde3[4] sdd3[3] sdc3[2] sdb3[1]
md0 : active raid6 sda3[0] sdh3[7] sdg3[6] sdf3[5] sde3[4] sdd3[3] sdc3[2] sdb3[1]
storage_boot_init.c:     /dev/md0 is active.
storage_boot_init.c: Check filesystem on /dev/md0.
storage_boot_init.c:     Cannot mount /dev/md0.
storage_boot_init.c: check_last_degrade_error...
group block bitmap usage checking...
storage_boot_init 6 ...
storage_boot_init.c: Checking e-sata: [/sys/block/sdy]
Not exist
storage_boot_init.c: Checking e-sata: [/sys/block/sdz]
Not exist


dmesg showed this:

Code: Select all

dmesg | tail
[ 1199.665903]  disk 5, o:1, dev:sdf3
[ 1199.665971]  disk 6, o:1, dev:sdg3
[ 1199.666041]  disk 7, o:1, dev:sdh3
[ 1199.667466] md0: bitmap initialized from disk: read 1/1 pages, set 0 bits
[ 1199.667550] created bitmap (11 pages) for device md0
[ 1199.774875] md0: detected capacity change from 0 to 17993917661184
[ 1201.001772]  md0: unknown partition table
[ 1205.145343] EXT4-fs (md0): ext4_check_descriptors: Checksum for group 55168 failed (23438!=21504)
[ 1205.145484] EXT4-fs (md0): group descriptors corrupted!
[ 1359.047410] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0)


I contacted Qnap support and they replied to me within a hour with Skype text. The nice technician connected to my computer with Teamviewer and did this:

Code: Select all

swapoff /dev/md8
mdadm -S /dev/md8
mkswap /dev/sda2
mkswap /dev/sdb2
mkswap /dev/sdc2
mkswap /dev/sdd2
swapon /dev/sda2
swapon /dev/sdb2
swapon /dev/sdc2
swapon /dev/sdd2
e2fsck_64 -f /dev/md0
mount /dev/md0 /share/MD0_DATA/ -t ext4

After that the RAID6 was up and running again :!:

Thank you Qnap support :D
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[ If you are too open-minded, your brain may fall out ]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

inhum
First post
Posts: 1
Joined: Fri Feb 13, 2015 5:55 pm

Re: TS-859 Pro+ - RAID5 cannot be mounted after restart...

Post by inhum » Fri Feb 13, 2015 6:28 pm

I have had same problen with TS-859 Pro+.
RAID 6 (8 disk spare).
After incorrect poweroff (electricity outage) i got same messages:
md0: unknown partition table
EXT4-fs (md0): ext4_check_descriptors: Checksum for group 35712 failed (59361!=53007)
EXT4-fs (md0): group descriptors corrupted!

The solution from Raffe solved the problem.

Thanks!

kursatuguroglu
New here
Posts: 3
Joined: Wed Nov 24, 2010 6:10 am

Re: TS-859 Pro+ - RAID5 cannot be mounted after restart...

Post by kursatuguroglu » Wed Jan 20, 2016 10:09 pm

any help with TS-410 PRo mentioned in here (http://forum.qnap.com/viewtopic.php?f=25&t=119167) would be appreciated..

crobin
Starting out
Posts: 11
Joined: Mon Aug 15, 2011 7:21 pm

Re: TS-859 Pro+ - RAID5 cannot be mounted after restart...

Post by crobin » Sat Aug 18, 2018 3:10 pm

I had the same problem with a TS-809 that returned as unmounted RAID after a normal reboot via the GUI. Raffe's solution worked for me too! :D

andredemu
First post
Posts: 1
Joined: Fri Jan 18, 2019 6:25 am

Re: TS-859 Pro+ - RAID5 cannot be mounted after restart...

Post by andredemu » Fri Jan 18, 2019 6:40 am

We had the same problem with a TS 659, RAID 6 with 6 dirves. We changed a defunct drive after having powered off the system. The replaced new drive was also defunct (DoA), we put it down again and replaced it with a second new drive. After having booted the system again, the RAID stayed unmounted with no access to the shared directories (not mounted) and all options greyed in the web interface.

We followed Raffe's solution, adapting it to our situation (6 drives instead of 8) :
Apparently, there is a RAID 1 (mounted on md6 if you have 6 drives, md8 if you have 8 drives) created by the system to store some information and the issue here is related to it and one has to clear the swap on it and create it again.
It is not the same RAID as your 'data' RAID. You can see it after having typed the following command via a root ssh : #cat /proc/mdstat

Using a root ssh, execute the following commands on the NAS :
swapoff /dev/md6
mdadm -S /dev/md6
mkswap /dev/sda2
mkswap /dev/sdb2
mkswap /dev/sdc2

swapon /dev/sda2
swapon /dev/sdb2
swapon /dev/sdc2

e2fsck_64 -f /dev/md0 : this one takes a long time to complete, you just have to wait and cross your fingers...

mount /dev/md0 /share/MD0_DATA/ -t ext4

After that, the RAID6 was mounted again and all the shared folders accessible and ready to use !

Thanks !

André

P3R
Guru
Posts: 10673
Joined: Sat Dec 29, 2007 1:39 am
Location: Stockholm, Sweden (UTC+01:00)

Re: TS-859 Pro+ - RAID5 cannot be mounted after restart...

Post by P3R » Fri Jan 18, 2019 8:25 am

andredemu wrote:
Fri Jan 18, 2019 6:40 am
We changed a defunct drive after having powered off the system. The replaced new drive was also defunct (DoA), we put it down again and replaced it with a second new drive.
On Qnaps that support hot swap, never power down when replacing disks. Doing so often cause these kind of problems.

Replace disks hot whenever possible.
RAID have never ever been a replacement for backups. Without backups on a different system (preferably placed at another site), you will eventually lose data!

A non-RAID configuration (including RAID 0, which isn't really RAID) with a backup on a separate media protects your data far better than any RAID-volume without backup.

All data storage consists of both the primary storage and the backups. It's your money and your data, spend the storage budget wisely or pay with your data!

Post Reply

Return to “Hardware & Software Compatibility”