Help-Raid5 Disapeared-Failed not enough Devices

harpo3223 · 7. April 2014

The Storage Folders shows as follows:

Disk show up in Physical Disk area however no raid is visible in Raid Management all blank. The Filesystems shows as follows - device n/a, Mounted Yes, and Status missing.
All was working find then started acting up 3days ago and finally just stopped working Today. File folders show up in windows explorer but can not access files. I have tried searching but some of the prior post do not match my situation
if this topic has been answered somewhere else a link would be appreciated.

When I run the following command I get:
root@OMV:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
unused devices: <none>
root@OMV:~#

ryecoaaron · 7. April 2014

What about:

fdisk -l
blkid

harpo3223 · 7. April 2014

Thanks for your quick reply here is what I get

root@OMV:~# fdisk -l

Disk /dev/sda: 40.0 GB, 40000000000 bytes
255 heads, 63 sectors/track, 4863 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00072afa

Device Boot Start End Blocks Id System
/dev/sda1 * 1 4660 37428224 83 Linux
/dev/sda2 4660 4863 1631233 5 Extended
/dev/sda5 4660 4863 1631232 82 Linux swap / Solaris

Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

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

Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

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

Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

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

Disk /dev/sde: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

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

Disk /dev/sdf: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

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

Disk /dev/sdg: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

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

Disk /dev/sdh: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

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

Disk /dev/sdi: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/sdi doesn't contain a valid partition table
root@OMV:~#

harpo3223 · 7. April 2014

With the command blkid this is what I get

root@OMV:~# blkid
/dev/sda1: UUID="cfe08dc0-a0a2-4281-8e5a-fb5668928dbf" TYPE="ext4"
/dev/sda5: UUID="9c96be74-c8db-41d2-b5ca-0dc8e1fa199d" TYPE="swap"
/dev/sdf: UUID="34d9fefa-619e-26a0-e363-f8994dd01d34" LABEL="OMV:StorageR5" TYPE="linux_raid_member"
/dev/sdg: UUID="34d9fefa-619e-26a0-e363-f8994dd01d34" LABEL="OMV:StorageR5" TYPE="linux_raid_member"
/dev/sdh: UUID="34d9fefa-619e-26a0-e363-f8994dd01d34" LABEL="OMV:StorageR5" TYPE="linux_raid_member"
/dev/sdi: UUID="34d9fefa-619e-26a0-e363-f8994dd01d34" LABEL="OMV:StorageR5" TYPE="linux_raid_member"
root@OMV:~#

ryecoaaron · 7. April 2014

Looks like four of your drives aren't recognized. Bad power connector or cable maybe? I would turn it off, reseat all the connectors on drives and motherboard, turn back on. Make sure your bios recognizes the drives. Report back.

harpo3223 · 7. April 2014

Forgive me ryecoaaron I should of had said that I have a total of 8 drives on adaptec card none hardware raid the first set of 4 Drives on Ch0 which I have intentional removed it from Raid10 and the disks have been cleared this is why they show this way they are Hitachi drives

The raid5 is the second set of 4 drives is where I am having problems, these are western digital Green and are on Ch1. Should I disconnect the Hitachi drives to avoid confusion since those do work find and I can see them when I place them in raid form?

connector are fine on all 8 drives the Hitachi drives are not formatted or partitioned.

My apologies please advice if you would like me to disconnect the Hitachi drives.

davidh2k · 7. April 2014

Is the raid5 managed by the adaptec controller? Then my bet would be that the lack of TLER on the greens forced all of your drives out of the controller.

Greetings
David

ryecoaaron · 7. April 2014

No need to disconnect the other drives. I would try:

Code

mdadm --assemble --run --force /dev/md0 /dev/sd[fghi]

harpo3223 · 7. April 2014

I ran the command as requested here is the output
Am I right to assume one of my drives are bad?

Last login: Sun Apr 6 15:59:59 2014 from 192.168.1.22
root@OMV:~# mdadm --assemble --run --force /dev/md0 /dev/sd[fghi]
mdadm: forcing event count in /dev/sdi(1) from 1035808 upto 1035850
mdadm: /dev/md0 has been started with 3 drives (out of 4).
root@OMV:~#

ryecoaaron · 7. April 2014

That is somewhat good. Maybe a bad drive. What is the output of cat /proc/mdstat now?

harpo3223 · 7. April 2014

here you go..

root@OMV:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active (auto-read-only) raid5 sdi[1] sdh[3] sdf[2]
5860538880 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/3] [_UUU]

unused devices: <none>
root@OMV:~#

ryecoaaron · 7. April 2014

Looks like sdg might be having problems... Any errors in dmesg?

harpo3223 · 7. April 2014

Davidh2k thanks for your input and help

Unintentionally I have heard about The "lack of TLER on the greens" but I am ashamed to admit I don't truly know what that means.
or if there is a fix and if so hopefully some what easy for a LINUX newbie.

harpo3223 · 7. April 2014

ryecoaaron

Forgive me but how can I get you that data you need ( dmesg?)

ryecoaaron · 7. April 2014

Type:
dmesg
or
cat /var/log/messages

harpo3223 · 7. April 2014

Code

[15687.861465] ata24: error=0x04 { DriveStatusError }
[15687.861472] ata24: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15687.861487] ata24.00: device reported invalid CHS sector 0
[15687.861490] ata24: status=0x01 { Error }
[15687.861493] ata24: error=0x04 { DriveStatusError }
[15687.861499] ata24: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15687.861514] ata24.00: device reported invalid CHS sector 0
[15687.861517] ata24: status=0x01 { Error }
[15687.861520] ata24: error=0x04 { DriveStatusError }
[15687.861542] sd 10:0:13:0: [sdh] START_STOP FAILED
[15687.861544] sd 10:0:13:0: [sdh] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[15687.861548] sd 10:0:13:0: [sdh] Sense Key : Aborted Command [current] [descriptor]
[15687.861553] sd 10:0:13:0: [sdh] Add. Sense: No additional sense information
[15837.232237] ata25.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133
[15837.232242] ata25.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[15837.236339] ata25.00: configured for UDMA/133
[15837.236441] scsi 10:0:14:0: Direct-Access     ATA      WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5
[15837.236714] sd 10:0:14:0: [sdh] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[15837.237557] sd 10:0:14:0: [sdh] Write Protect is off
[15837.237561] sd 10:0:14:0: [sdh] Mode Sense: 00 3a 00 00
[15837.237605] sd 10:0:14:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[15837.237787]  sdh: unknown partition table
[15837.250412] sd 10:0:14:0: [sdh] Attached SCSI disk
[15848.325225] sd 10:0:14:0: [sdh] Synchronizing SCSI cache
[15848.325252] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.325272] ata25.00: device reported invalid CHS sector 0
[15848.325274] ata25: status=0x01 { Error }
[15848.325278] ata25: error=0x04 { DriveStatusError }
[15848.325294] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.325310] ata25.00: device reported invalid CHS sector 0
[15848.325312] ata25: status=0x01 { Error }
[15848.325315] ata25: error=0x04 { DriveStatusError }
[15848.325322] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.325337] ata25.00: device reported invalid CHS sector 0
[15848.325339] ata25: status=0x01 { Error }
[15848.325342] ata25: error=0x04 { DriveStatusError }
[15848.325349] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.325368] ata25.00: device reported invalid CHS sector 0
[15848.325370] ata25: status=0x01 { Error }
[15848.325373] ata25: error=0x04 { DriveStatusError }
[15848.325380] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.325395] ata25.00: device reported invalid CHS sector 0
[15848.325398] ata25: status=0x01 { Error }
[15848.325401] ata25: error=0x04 { DriveStatusError }
[15848.325407] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.325423] ata25.00: device reported invalid CHS sector 0
[15848.325425] ata25: status=0x01 { Error }
[15848.325428] ata25: error=0x04 { DriveStatusError }
[15848.325655] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.325673] ata25.00: device reported invalid CHS sector 0
[15848.325676] ata25: status=0x01 { Error }
[15848.325679] ata25: error=0x04 { DriveStatusError }
[15848.325691] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.325709] ata25.00: device reported invalid CHS sector 0
[15848.325711] ata25: status=0x01 { Error }
[15848.325714] ata25: error=0x04 { DriveStatusError }
[15848.325721] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.325736] ata25.00: device reported invalid CHS sector 0
[15848.325739] ata25: status=0x01 { Error }
[15848.325742] ata25: error=0x04 { DriveStatusError }
[15848.325748] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.325764] ata25.00: device reported invalid CHS sector 0
[15848.325766] ata25: status=0x01 { Error }
[15848.325769] ata25: error=0x04 { DriveStatusError }
[15848.325824] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.325840] ata25.00: device reported invalid CHS sector 0
[15848.325843] ata25: status=0x01 { Error }
[15848.325846] ata25: error=0x04 { DriveStatusError }
[15848.325853] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.325868] ata25.00: device reported invalid CHS sector 0
[15848.325870] ata25: status=0x01 { Error }
[15848.325874] ata25: error=0x04 { DriveStatusError }
[15848.325890] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.325906] ata25.00: device reported invalid CHS sector 0
[15848.325908] ata25: status=0x01 { Error }
[15848.325911] ata25: error=0x04 { DriveStatusError }
[15848.325921] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.325937] ata25.00: device reported invalid CHS sector 0
[15848.325940] ata25: status=0x01 { Error }
[15848.325943] ata25: error=0x04 { DriveStatusError }
[15848.325949] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.325965] ata25.00: device reported invalid CHS sector 0
[15848.325968] ata25: status=0x01 { Error }
[15848.325971] ata25: error=0x04 { DriveStatusError }
[15848.325977] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.325994] ata25.00: device reported invalid CHS sector 0
[15848.325996] ata25: status=0x01 { Error }
[15848.325999] ata25: error=0x04 { DriveStatusError }
[15848.326006] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.326021] ata25.00: device reported invalid CHS sector 0
[15848.326023] ata25: status=0x01 { Error }
[15848.326026] ata25: error=0x04 { DriveStatusError }
[15848.326033] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.326048] ata25.00: device reported invalid CHS sector 0
[15848.326050] ata25: status=0x01 { Error }
[15848.326053] ata25: error=0x04 { DriveStatusError }
[15848.326063] sd 10:0:14:0: [sdh] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[15848.326067] sd 10:0:14:0: [sdh] Sense Key : Aborted Command [current] [descriptor]
[15848.326072] sd 10:0:14:0: [sdh] Add. Sense: No additional sense information
[15848.326077] sd 10:0:14:0: [sdh] Stopping disk
[15848.326085] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.326101] ata25.00: device reported invalid CHS sector 0
[15848.326103] ata25: status=0x01 { Error }
[15848.326106] ata25: error=0x04 { DriveStatusError }
[15848.326116] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.326131] ata25.00: device reported invalid CHS sector 0
[15848.326133] ata25: status=0x01 { Error }
[15848.326136] ata25: error=0x04 { DriveStatusError }
[15848.326143] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.326159] ata25.00: device reported invalid CHS sector 0
[15848.326161] ata25: status=0x01 { Error }
[15848.326164] ata25: error=0x04 { DriveStatusError }
[15848.326170] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.326188] ata25.00: device reported invalid CHS sector 0
[15848.326190] ata25: status=0x01 { Error }
[15848.326193] ata25: error=0x04 { DriveStatusError }
[15848.326200] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.326215] ata25.00: device reported invalid CHS sector 0
[15848.326217] ata25: status=0x01 { Error }
[15848.326220] ata25: error=0x04 { DriveStatusError }
[15848.326227] ata25: translated ATA stat/err 0x01/04 to SCSI SK/ASC/ASCQ 0xb/00/00
[15848.326242] ata25.00: device reported invalid CHS sector 0
[15848.326244] ata25: status=0x01 { Error }
[15848.326247] ata25: error=0x04 { DriveStatusError }
[15848.326256] sd 10:0:14:0: [sdh] START_STOP FAILED
[15848.326258] sd 10:0:14:0: [sdh] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[15848.326262] sd 10:0:14:0: [sdh] Sense Key : Aborted Command [current] [descriptor]
[15848.326267] sd 10:0:14:0: [sdh] Add. Sense: No additional sense information
[23322.818129] ata26.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133
[23322.818135] ata26.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[23322.822225] ata26.00: configured for UDMA/133
[23322.822304] scsi 10:0:15:0: Direct-Access     ATA      WDC WD20EARS-00M 51.0 PQ: 0 ANSI: 5
[23322.822514] sd 10:0:15:0: [sdh] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[23322.822601] sd 10:0:15:0: [sdh] Write Protect is off
[23322.822604] sd 10:0:15:0: [sdh] Mode Sense: 00 3a 00 00
[23322.822632] sd 10:0:15:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[23322.822813]  sdh: unknown partition table
[23322.836097] sd 10:0:15:0: [sdh] Attached SCSI disk
[65470.348078] ata1: soft resetting link
[65470.501577] ata1: EH complete
[65470.506969] ata2: soft resetting link
[65470.671466] ata2: EH complete
[65470.681627] ata3: hard resetting link
[65471.004017] ata3: SATA link down (SStatus 0 SControl 300)
[65471.004025] ata3: EH complete
[65471.009204] ata4: hard resetting link
[65471.496020] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[65471.498920] ata4.00: configured for UDMA/133
[65471.498924] ata4: EH complete
[65471.513438] ata7: hard resetting link
[65471.840022] ata7: SATA link down (SStatus 0 SControl 300)
[65471.840030] ata7: EH complete
[65471.845267] ata8: hard resetting link
[65472.168034] ata8: SATA link down (SStatus 0 SControl 300)
[65472.168042] ata8: EH complete
[65472.173115] ata9: hard resetting link
[65472.493027] ata9: SATA link down (SStatus 0 SControl 300)
[65472.493037] ata9: EH complete
[65472.498109] ata10: hard resetting link
[65472.816028] ata10: SATA link down (SStatus 0 SControl 300)
[65472.816038] ata10: EH complete
[65755.098475] md: md0 stopped.
[65755.101649] md: bind<sdg>
[65755.101894] md: bind<sdf>
[65755.102112] md: bind<sdh>
[65755.145852] md: bind<sdi>
[65755.145879] md: kicking non-fresh sdg from array!
[65755.145886] md: unbind<sdg>
[65755.157015] md: export_rdev(sdg)
[65755.197436] raid5: device sdi operational as raid disk 1
[65755.197439] raid5: device sdh operational as raid disk 3
[65755.197442] raid5: device sdf operational as raid disk 2
[65755.198032] raid5: allocated 4282kB for md0
[65755.198071] 1: w=1 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
[65755.198075] 3: w=2 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
[65755.198079] 2: w=3 pa=0 pr=4 m=1 a=2 r=4 op1=0 op2=0
[65755.198082] raid5: raid level 5 set md0 active with 3 out of 4 devices, algorithm 2
[65755.198100] RAID5 conf printout:
[65755.198102]  --- rd:4 wd:3
[65755.198104]  disk 1, o:1, dev:sdi
[65755.198106]  disk 2, o:1, dev:sdf
[65755.198109]  disk 3, o:1, dev:sdh
[65755.198141] md0: detected capacity change from 0 to 6001191813120
[65755.199612]  md0: unknown partition table
root@OMV:~#

Alles anzeigen

ryecoaaron · 7. April 2014

Lots of errors on two drives. Something is definitely wrong. Not sure if it is the drives, raid card, or motherboard. Might just need the backports kernel.

harpo3223 · 7. April 2014

When I ran some testing earlier (yesterday) I was able to run the other Hitachi good drives on Both Ch0 and CH1 of Adaptec Card (not a hard Raid card) and they ran fine. Now as far as a backports kernel I do not even know what that means.
Sorry! you got me stomped there. Are the errors coming form - sdh?

harpo3223 · 7. April 2014

I have 2 spare drives same size but are Seagates will i be able to recover from the two existing good drives?

ryecoaaron · 7. April 2014

OMV up to 0.5.x is based on Debian Squeeze which comes with the 2.6.32 kernel. The backports kernel is from Wheezy and is 3.2 meaning newer drivers and everything else. It sometimes helps with problems like this.

sdh does have errors from the logs...

software raid is not picky about drive manufacturer. Just size of the drive.

Jetzt mitmachen!