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

Questions about SNMP, Power, System, Logs, disk, & RAID.

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

Postby Mr Fusion » Sat Mar 24, 2012 9:32 pm

Hello everyone. I just experienced my first problem with a QNAP device in about two years, and if anyone has any suggestion on how to remedy this I would appreciate it.

(TS559 Pro currently on 3.6.0 B0210T. Upgraded firmware approximately one month ago, and have not rebooted since then).

After sitting idle for a couple of hours, I tried to access QNAP drive shares in windows and was unsuccessful (but was able to connect to web console). I could not see any disks under Volume Management or HDD S.M.A.R.T. I initiated a restart, but after almost half an hour the display on the QNAP still said restarting (and I was still able to access the web console). I tried to initiate a shutdown, but this did nothing either. I then turned off the QNAP using the power button, and after 30 seconds turned it back on.

The QNAP came back online, but I was still unable to access shares or see any disks in Volume Management or HDD S.M.A.R.T. I fired up an SSH connection with Putty, and ran the following:

fdisk -lu
Code: Select all
Disk /dev/sde: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sde1              40     1060289      530125   83  Linux
/dev/sde2         1060296     2120579      530142   83  Linux
/dev/sde3         2120584  3906011969  1951945693   83  Linux
/dev/sde4      3906011976  3907007999      498012   83  Linux

Disk /dev/sdd: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1              40     1060289      530125   83  Linux
/dev/sdd2         1060296     2120579      530142   83  Linux
/dev/sdd3         2120584  3906011969  1951945693   83  Linux
/dev/sdd4      3906011976  3907007999      498012   83  Linux

Disk /dev/sdc: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1              40     1060289      530125   83  Linux
/dev/sdc2         1060296     2120579      530142   83  Linux
/dev/sdc3         2120584  3906011969  1951945693   83  Linux
/dev/sdc4      3906011976  3907007999      498012   83  Linux

Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1              40     1060289      530125   83  Linux
/dev/sdb2         1060296     2120579      530142   83  Linux
/dev/sdb3         2120584  3906011969  1951945693   83  Linux
/dev/sdb4      3906011976  3907007999      498012   83  Linux

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1              40     1060289      530125   83  Linux
/dev/sda2         1060296     2120579      530142   83  Linux
/dev/sda3         2120584  3906011969  1951945693   83  Linux
/dev/sda4      3906011976  3907007999      498012   83  Linux

Disk /dev/sda4: 469 MB, 469893120 bytes
2 heads, 4 sectors/track, 114720 cylinders, total 917760 sectors
Units = sectors of 1 * 512 = 512 bytes

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

Disk /dev/sdx: 515 MB, 515899392 bytes
8 heads, 32 sectors/track, 3936 cylinders, total 1007616 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdx1              32        4351        2160   83  Linux
/dev/sdx2            4352      488959      242304   83  Linux
/dev/sdx3          488960      973567      242304   83  Linux
/dev/sdx4          973568     1007615       17024    5  Extended
/dev/sdx5          973600      990207        8304   83  Linux
/dev/sdx6          990240     1007615        8688   83  Linux

Disk /dev/md9: 542 MB, 542769152 bytes
2 heads, 4 sectors/track, 132512 cylinders, total 1060096 sectors
Units = sectors of 1 * 512 = 512 bytes

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

Disk /dev/md5: 542 MB, 542769152 bytes
2 heads, 4 sectors/track, 132512 cylinders, total 1060096 sectors
Units = sectors of 1 * 512 = 512 bytes

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

Disk /dev/md0: 7995.1 GB, 7995169177600 bytes
2 heads, 4 sectors/track, 1951945600 cylinders, total 15615564800 sectors
Units = sectors of 1 * 512 = 512 bytes

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


mdadm -D /dev/md0
Code: Select all
/dev/md0:
        Version : 00.90.03
  Creation Time : Sat Oct  2 15:34:03 2010
     Raid Level : raid5
     Array Size : 7807782400 (7446.08 GiB 7995.17 GB)
  Used Dev Size : 1951945600 (1861.52 GiB 1998.79 GB)
   Raid Devices : 5
  Total Devices : 5
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Sat Mar 24 18:19:47 2012
          State : active, resyncing
 Active Devices : 5
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 64K

 Rebuild Status : 0% complete

           UUID : efe9edfe:837e9c07:dd73bda5:b7ec1a2c
         Events : 0.6461752

    Number   Major   Minor   RaidDevice State
       0       8        3        0      active sync   /dev/sda3
       1       8       35        1      active sync   /dev/sdc3
       2       8       19        2      active sync   /dev/sdb3
       3       8       51        3      active sync   /dev/sdd3
       4       8       67        4      active sync   /dev/sde3


cat /proc/mdstat
Code: Select all
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath]
md0 : active raid5 sda3[0] sde3[4] sdd3[3] sdb3[2] sdc3[1]
      7807782400 blocks level 5, 64k chunk, algorithm 2 [5/5] [UUUUU]
      [>....................]  resync =  0.1% (2356864/1951945600) finish=2959046.4min speed=10K/sec

md5 : active raid1 sde2[2](S) sdd2[3](S) sdc2[4](S) sdb2[1] sda2[0]
      530048 blocks [2/2] [UU]

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

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

unused devices: <none>


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


cat /etc/raidtab
Code: Select all
raiddev /dev/md0
        raid-level      5
        nr-raid-disks   5
        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
        device  /dev/sde3
        raid-disk       4


df -h
Code: Select all
Filesystem                Size      Used Available Use% Mounted on
/dev/ram                139.5M    111.6M     27.9M  80% /
tmpfs                    64.0M    172.0k     63.8M   0% /tmp
/dev/sda4               310.0M    219.9M     90.1M  71% /mnt/ext
/dev/md9                509.5M     89.3M    420.2M  18% /mnt/HDA_ROOT
/dev/md0                  7.2T      7.1T     32.2G 100% /share/MD0_DATA
tmpfs                    32.0M         0     32.0M   0% /.eaccelerator.tmp
tmpfs                     8.0M         0      8.0M   0% /var/syslog_maildir


dmesg
Code: Select all
d: bind<sde3>
[   89.517778] md: bind<sda3>
[   89.519391] raid5: md0 is not clean -- starting background reconstruction
[   89.519528] raid5: device sda3 operational as raid disk 0
[   89.519634] raid5: device sde3 operational as raid disk 4
[   89.519740] raid5: device sdd3 operational as raid disk 3
[   89.519845] raid5: device sdb3 operational as raid disk 2
[   89.519951] raid5: device sdc3 operational as raid disk 1
[   89.532457] raid5: allocated 85344kB for md0
[   89.532672] 0: w=1 pa=0 pr=5 m=1 a=2 r=5 op1=0 op2=0
[   89.532782] 4: w=2 pa=0 pr=5 m=1 a=2 r=5 op1=0 op2=0
[   89.532887] 3: w=3 pa=0 pr=5 m=1 a=2 r=5 op1=0 op2=0
[   89.532991] 2: w=4 pa=0 pr=5 m=1 a=2 r=5 op1=0 op2=0
[   89.533138] 1: w=5 pa=0 pr=5 m=1 a=2 r=5 op1=0 op2=0
[   89.533244] raid5: raid level 5 set md0 active with 5 out of 5 devices, algorithm 2
[   89.533410] RAID5 conf printout:
[   89.533505]  --- rd:5 wd:5
[   89.533601]  disk 0, o:1, dev:sda3
[   89.533699]  disk 1, o:1, dev:sdc3
[   89.533796]  disk 2, o:1, dev:sdb3
[   89.533893]  disk 3, o:1, dev:sdd3
[   89.533991]  disk 4, o:1, dev:sde3
[   89.534190] md0: detected capacity change from 0 to 7995169177600
[   89.534709] md: delaying resync of md0 until md5 has finished (they share one or more physical units)
[   90.638448]  md0: unknown partition table
[   91.029208] md: bind<sdc2>
[   93.111543] md: bind<sdd2>
[   94.180952] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 88605329
[   94.214649] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 88605378
[   94.250810] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 88605310
[   94.293450] EXT4-fs (md0): ext4_orphan_cleanup: truncating inode 48103444 to 13230099718 bytes
[   94.333695] EXT4-fs (md0): 3 orphan inodes deleted
[   94.333873] EXT4-fs (md0): 1 truncate cleaned up
[   94.471097] EXT4-fs (md0): recovery complete
[   94.584883] EXT4-fs (md0): mounted filesystem with ordered data mode
[   95.178552] md: bind<sde2>
[   97.346545] bonding: Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
[   97.346738] bonding: MII link monitoring set to 100 ms
[   97.431051] bonding: bond0: enslaving eth0 as a backup interface with a down link.
[   97.521074] bonding: bond0: enslaving eth1 as a backup interface with a down link.
[  100.554145] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[  100.649025] bonding: bond0: link status definitely up for interface eth0.
[  100.649146] bonding: bond0: making interface eth0 the new active one.
[  100.649487] bonding: bond0: first active interface up!
[  115.672377] md: md5: recovery done.
[  115.693744] md: resync of RAID array md0
[  115.693873] md: minimum _guaranteed_  speed: 5000 KB/sec/disk.
[  115.693998] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for resync.
[  115.694208] md: Resyncing started: md0
[  115.694332] md: using 128k window, over a total of 1951945600 blocks.
[  115.745760] RAID1 conf printout:
[  115.745891]  --- wd:2 rd:2
[  115.746005]  disk 0, wo:0, o:1, dev:sda2
[  115.746124]  disk 1, wo:0, o:1, dev:sdb2
[  116.050655] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[  116.050977] NFSD: starting 90-second grace period
[  135.818718] active port 0 :139
[  135.818841] active port 1 :445
[  135.818958] active port 2 :20
[  136.891632] warning: `proftpd' uses 32-bit capabilities (legacy support in use)
[  137.955157] nfsd: last server has exited, flushing export cache
[  143.466723] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[  143.466915] NFSD: starting 90-second grace period
[  174.033980] rule type=2, num=0
[  177.303725] nfsd: last server has exited, flushing export cache
[  182.835500] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[  182.835689] NFSD: starting 90-second grace period
[  187.259981] Loading iSCSI transport class v2.0-871.
[  187.351345] iscsi: registered transport (tcp)
[  223.787403] ata6.00: exception Emask 0x0 SAct 0x10 SErr 0x0 action 0x0
[  223.787521] ata6.00: irq_stat 0x40000008
[  223.787623] ata6.00: failed command: READ FPDMA QUEUED
[  223.787735] ata6.00: cmd 60/00:20:08:fa:79/01:00:c6:00:00/40 tag 4 ncq 131072 in
[  223.787738]          res 41/40:00:2f:fa:79/0e:01:c6:00:00/00 Emask 0x409 (media error) <F>
[  223.788058] ata6.00: status: { DRDY ERR }
[  223.788209] ata6.00: error: { UNC }
[  223.926280] ata6.00: configured for UDMA/133
[  223.926410] ata6: EH complete
[  229.921615] ata6.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
[  229.921733] ata6.00: irq_stat 0x40000008
[  229.921835] ata6.00: failed command: READ FPDMA QUEUED
[  229.921947] ata6.00: cmd 60/00:00:08:fa:79/01:00:c6:00:00/40 tag 0 ncq 131072 in
[  229.921950]          res 41/40:00:30:fa:79/0e:01:c6:00:00/00 Emask 0x409 (media error) <F>
[  229.922294] ata6.00: status: { DRDY ERR }
[  229.922395] ata6.00: error: { UNC }
[  229.959015] ata6.00: configured for UDMA/133
[  229.959159] ata6: EH complete
[  233.695277] ata6.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
[  233.695401] ata6.00: irq_stat 0x40000008
[  233.695504] ata6.00: failed command: READ FPDMA QUEUED
[  233.695617] ata6.00: cmd 60/00:00:08:fa:79/01:00:c6:00:00/40 tag 0 ncq 131072 in
[  233.695620]          res 41/40:00:30:fa:79/0e:01:c6:00:00/00 Emask 0x409 (media error) <F>
[  233.695940] ata6.00: status: { DRDY ERR }
[  233.696070] ata6.00: error: { UNC }
[  233.732694] ata6.00: configured for UDMA/133
[  233.732825] ata6: EH complete
[  237.479103] ata6.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
[  237.479221] ata6.00: irq_stat 0x40000008
[  237.479322] ata6.00: failed command: READ FPDMA QUEUED
[  237.479434] ata6.00: cmd 60/00:00:08:fa:79/01:00:c6:00:00/40 tag 0 ncq 131072 in
[  237.479437]          res 41/40:00:30:fa:79/0e:01:c6:00:00/00 Emask 0x409 (media error) <F>
[  237.479753] ata6.00: status: { DRDY ERR }
[  237.479851] ata6.00: error: { UNC }
[  237.516545] ata6.00: configured for UDMA/133
[  237.516667] ata6: EH complete
[  242.269925] ata6.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
[  242.270088] ata6.00: irq_stat 0x40000008
[  242.270208] ata6.00: failed command: READ FPDMA QUEUED
[  242.270321] ata6.00: cmd 60/00:00:08:fa:79/01:00:c6:00:00/40 tag 0 ncq 131072 in
[  242.270324]          res 41/40:00:30:fa:79/0e:01:c6:00:00/00 Emask 0x409 (media error) <F>
[  242.270644] ata6.00: status: { DRDY ERR }
[  242.270744] ata6.00: error: { UNC }
[  242.297196] ata6.00: configured for UDMA/133
[  242.297328] ata6: EH complete
[  247.050583] ata6.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
[  247.050701] ata6.00: irq_stat 0x40000008
[  247.050803] ata6.00: failed command: READ FPDMA QUEUED
[  247.050915] ata6.00: cmd 60/00:00:08:fa:79/01:00:c6:00:00/40 tag 0 ncq 131072 in
[  247.050918]          res 41/40:00:30:fa:79/0e:01:c6:00:00/00 Emask 0x409 (media error) <F>
[  247.051255] ata6.00: status: { DRDY ERR }
[  247.051356] ata6.00: error: { UNC }
[  247.088005] ata6.00: configured for UDMA/133
[  247.088157] sd 5:0:0:0: [sda] Unhandled sense code
[  247.088262] sd 5:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  247.088409] sd 5:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]
[  247.088657] Descriptor sense data with sense descriptors (in hex):
[  247.088798]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[  247.089497]         c6 79 fa 30
[  247.089762] sd 5:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
[  247.089997] sd 5:0:0:0: [sda] CDB: Read(10): 28 00 c6 79 fa 08 00 01 00 00
[  247.090564] end_request: I/O error, dev sda, sector 3329882672
[  247.090713] ata6: EH complete
[12043.125797] usb 2-2: USB disconnect, address 3


There are no errors in the system log (just warnings related to resyncing due to my ungraceful shutdown.
Image

Any ideas on how to fix this?

Thanks!
Mr Fusion
New here
 
Posts: 5
Joined: Sat Jul 17, 2010 7:26 pm
Location: Brisbane, Australia
NAS Model: TS-259 Pro

Re: Disk /dev/md0 doesn't contain a valid partition table

Postby revaaron » Wed Jul 03, 2013 1:22 am

did you fix this? I have the same issue...
revaaron
Getting the hang of things
 
Posts: 88
Joined: Mon Apr 13, 2009 11:01 am
NAS Model: TS-419U

Re: Disk /dev/md0 doesn't contain a valid partition table

Postby Mr Fusion » Wed Jul 03, 2013 12:15 pm

Hi revaaron,

In the end it turned out that the first disk had partially failed (even though it passed SMART tests), and replacing it kicked off a raid re-build and everything started working again.

The advice from QNAP support in Taiwan was to format all disks and restore from backup - which I am glad I did not have to do.

Good luck, I hope your problem is fixed as easily as mine was (eventually).
Mr Fusion
New here
 
Posts: 5
Joined: Sat Jul 17, 2010 7:26 pm
Location: Brisbane, Australia
NAS Model: TS-259 Pro

Re: Disk /dev/md0 doesn't contain a valid partition table

Postby revaaron » Wed Jul 03, 2013 2:37 pm

hm.. I already did that.. ** it... I have another RED 3TB coming that should be here on 7/9. I guess I will try that when it comes. Maybe I can talk to tech support. Best thing is that I JUST finished synching to a back up all the stuff from that RAID before it went down and I've been able to make a second copy since then.
revaaron
Getting the hang of things
 
Posts: 88
Joined: Mon Apr 13, 2009 11:01 am
NAS Model: TS-419U

Re: Disk /dev/md0 doesn't contain a valid partition table

Postby Mr Fusion » Wed Jul 03, 2013 2:47 pm

So you have already replaced the first disk with a new one (that hasn't been in the NAS before)? Did you reboot after installing the new disk? From memory I had to power cycle the NAS after installing the new disk before it all kicked off again.
Mr Fusion
New here
 
Posts: 5
Joined: Sat Jul 17, 2010 7:26 pm
Location: Brisbane, Australia
NAS Model: TS-259 Pro

Re: Disk /dev/md0 doesn't contain a valid partition table

Postby revaaron » Wed Jul 03, 2013 11:41 pm

yeah, I've rebooted it bunches. It also rebooted itself bunches.
revaaron
Getting the hang of things
 
Posts: 88
Joined: Mon Apr 13, 2009 11:01 am
NAS Model: TS-419U


Return to System & Disk Volume Management

Who is online

Users browsing this forum: pksw, schumaku, Varsh and 10 guests