July 17, 20187 yr i shutdown my system and plugged in a new drive i just got back after a hard drive failure. that was installed about 8 hours ago and tonight another disk9 just went into disabled with a heap of errors never had an issue with the drive before. Is this disk dead? Smart is coming back saying everything is ok which seems a bit odd. I never touched the cables where that drive was located so i know i didn't disturb the sata connection. both the drive i am preclearing and this disk9 are on the same LSI 9211-8i PCI Express card but are on different SAS connection bundles. Could it be a data throughput issue? i know i am hitting it with a lot of writes about 20 minutes before this happened and its also zeroing with the preclear. Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954416 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954424 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954432 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954440 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954448 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954456 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954464 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954472 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954480 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954488 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954496 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954504 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954512 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954520 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954528 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954536 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954544 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954552 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954560 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954568 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954576 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954584 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954592 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954600 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954608 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954616 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954624 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954632 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954640 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954648 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954656 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954664 Jul 17 22:29:37 Vault kernel: md: disk9 write error, sector=4637954672 Jul 17 22:30:39 Vault kernel: ata5: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen Jul 17 22:30:39 Vault kernel: ata5: irq_stat 0x00400040, connection status changed Jul 17 22:30:39 Vault kernel: ata5: SError: { HostInt PHYRdyChg 10B8B DevExch } Jul 17 22:30:39 Vault kernel: ata5: hard resetting link Jul 17 22:30:44 Vault kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 17 22:30:44 Vault kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jul 17 22:30:44 Vault kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jul 17 22:30:44 Vault kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jul 17 22:30:44 Vault kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jul 17 22:30:44 Vault kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jul 17 22:30:44 Vault kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jul 17 22:30:44 Vault kernel: ata5.00: configured for UDMA/133 Jul 17 22:30:44 Vault kernel: ata5: EH complete Jul 17 22:30:48 Vault kernel: ata5: limiting SATA link speed to 3.0 Gbps Jul 17 22:30:48 Vault kernel: ata5.00: exception Emask 0x50 SAct 0x0 SErr 0x4890800 action 0xe frozen Jul 17 22:30:48 Vault kernel: ata5.00: irq_stat 0x0c400040, interface fatal error, connection status changed Jul 17 22:30:48 Vault kernel: ata5: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch } Jul 17 22:30:48 Vault kernel: ata5.00: failed command: READ DMA EXT Jul 17 22:30:48 Vault kernel: ata5.00: cmd 25/00:90:60:ad:9e/00:03:14:01:00/e0 tag 9 dma 466944 in Jul 17 22:30:48 Vault kernel: res 50/00:00:5f:ad:9e/00:00:14:01:00/e0 Emask 0x50 (ATA bus error) Jul 17 22:30:48 Vault kernel: ata5.00: status: { DRDY } Jul 17 22:30:48 Vault kernel: ata5: hard resetting link Jul 17 22:30:53 Vault kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Jul 17 22:30:53 Vault kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jul 17 22:30:53 Vault kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jul 17 22:30:53 Vault kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jul 17 22:30:53 Vault kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jul 17 22:30:53 Vault kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jul 17 22:30:53 Vault kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jul 17 22:30:53 Vault kernel: ata5.00: configured for UDMA/133 Jul 17 22:30:53 Vault kernel: ata5: EH complete Jul 17 22:31:58 Vault kernel: ata5.00: exception Emask 0x50 SAct 0x0 SErr 0x4890800 action 0xe frozen Jul 17 22:31:58 Vault kernel: ata5.00: irq_stat 0x0c400040, interface fatal error, connection status changed Jul 17 22:31:58 Vault kernel: ata5: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch } Jul 17 22:31:58 Vault kernel: ata5.00: failed command: READ DMA EXT Jul 17 22:31:58 Vault kernel: ata5.00: cmd 25/00:d8:f8:ad:ac/00:03:14:01:00/e0 tag 7 dma 503808 in Jul 17 22:31:58 Vault kernel: res 50/00:00:f7:ad:ac/00:00:14:01:00/e0 Emask 0x50 (ATA bus error) Jul 17 22:31:58 Vault kernel: ata5.00: status: { DRDY } Jul 17 22:31:58 Vault kernel: ata5: hard resetting link Jul 17 22:32:03 Vault kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Jul 17 22:32:03 Vault kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jul 17 22:32:03 Vault kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jul 17 22:32:03 Vault kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jul 17 22:32:03 Vault kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jul 17 22:32:03 Vault kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jul 17 22:32:03 Vault kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jul 17 22:32:03 Vault kernel: ata5.00: configured for UDMA/133 Jul 17 22:32:03 Vault kernel: ata5: EH complete Jul 17 22:34:10 Vault kernel: ata5: exception Emask 0x10 SAct 0x0 SErr 0x4090000 action 0xe frozen Jul 17 22:34:10 Vault kernel: ata5: irq_stat 0x00400040, connection status changed Jul 17 22:34:10 Vault kernel: ata5: SError: { PHYRdyChg 10B8B DevExch } Jul 17 22:34:10 Vault kernel: ata5: hard resetting link Jul 17 22:34:15 Vault kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Jul 17 22:34:15 Vault kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jul 17 22:34:15 Vault kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jul 17 22:34:15 Vault kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jul 17 22:34:15 Vault kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jul 17 22:34:15 Vault kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jul 17 22:34:15 Vault kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jul 17 22:34:15 Vault kernel: ata5.00: configured for UDMA/133 Jul 17 22:34:15 Vault kernel: ata5: EH complete Jul 17 22:35:36 Vault sshd[15284]: Accepted password for root from 10.0.10.251 port 51236 ssh2 Jul 17 22:36:49 Vault kernel: ata5: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen Jul 17 22:36:49 Vault kernel: ata5: irq_stat 0x00400040, connection status changed Jul 17 22:36:49 Vault kernel: ata5: SError: { HostInt PHYRdyChg 10B8B DevExch } Jul 17 22:36:49 Vault kernel: ata5: hard resetting link Jul 17 22:36:55 Vault kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Jul 17 22:36:55 Vault kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jul 17 22:36:55 Vault kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jul 17 22:36:55 Vault kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jul 17 22:36:55 Vault kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jul 17 22:36:55 Vault kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jul 17 22:36:55 Vault kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jul 17 22:36:55 Vault kernel: ata5.00: configured for UDMA/133 Jul 17 22:36:55 Vault kernel: ata5: EH complete Jul 17 22:37:51 Vault kernel: ata5: limiting SATA link speed to 1.5 Gbps Jul 17 22:37:51 Vault kernel: ata5: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen Jul 17 22:37:51 Vault kernel: ata5: irq_stat 0x00400040, connection status changed Jul 17 22:37:51 Vault kernel: ata5: SError: { HostInt PHYRdyChg 10B8B DevExch } Jul 17 22:37:51 Vault kernel: ata5: hard resetting link Jul 17 22:37:56 Vault kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jul 17 22:37:56 Vault kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jul 17 22:37:56 Vault kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jul 17 22:37:56 Vault kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jul 17 22:37:56 Vault kernel: ata5.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jul 17 22:37:56 Vault kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jul 17 22:37:56 Vault kernel: ata5.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jul 17 22:37:56 Vault kernel: ata5.00: configured for UDMA/133
July 17, 20187 yr Community Expert Looks like a connection problem, replace or swap cables with a different disk and see if it holds up.
July 17, 20187 yr Author Checked the cables everything seems fine rebuilding disk 9. When I started up disk 7 did the same thing threw errors and went into disabled. Maybe it was from the same event nothing else has put out errors. Will wait for disk 9 to rebuild won't touch anything. At the edge of my raid redundancy. My preclear errored so assuming the LSI 9211 8i didn't like all disks writing while preclearing I did see the bandwidth drop from 120Mbps to 31Mbps a minute before this all happened. I've never run the LSI card with 8 drives 7 at full copy write from cache to array while 1 is preclearing. Guess that's just too much data moving. Oddly Disk 7 and Disk 9 are the only disks in one of my shares that had a data read at the time this happened. Edited July 17, 20187 yr by Maticks
July 17, 20187 yr Author i guess the question is do i stop the disk 9 rebuild and do disk 9 and disk 7 at the same time. or keep doing along and do disk 9 then redo disk 7 later.
July 18, 20187 yr Community Expert 8 hours ago, Maticks said: Checked the cables everything seems fine I would recommend replacing or swapping cables so you can rule them out, or else there will always be doubts. 8 hours ago, Maticks said: My preclear errored so assuming the LSI 9211 8i didn't like all disks writing while preclearing I did see the bandwidth drop from 120Mbps to 31Mbps a minute before this all happened. I've never run the LSI card with 8 drives 7 at full copy write from cache to array while 1 is preclearing. That's not a problem, if all was working correctly they can handle all the disks, I have 24 disks (using expanders) connected to the same LSI HBA, and all are accessed simultaneously during for a example a parity check or disk rebuild.
July 18, 20187 yr Author Thanks Johnnie. The repair finished so i shutdown my system checked the SATA cables and powered the system back up. disk 7 and disk9 threw errors again. So it must be the SAS to 4xSATA cable. they are a bit crappy and i have removed them twice to move things around in my server. I've just ordered some replacements, i really need to keep a spare in stock of these things. im going to rebuild it one last time and not shutdown the system till the cable gets here and replace it then. probably the safest way for the mean time keeping things operational.
July 18, 20187 yr Author And then there were three failed drives... the Parity Drive started getting read errors on the lsi card with the other sas cable, I shut the system down and moved the lsi card to another pci express slot. No more errors. It’s rebuilding. Maybe it’s the motherboard slot. that second lsi cable hasn’t been touched in 6months it goes into the p100 lower chassis, must be the motherboard causing this. Array rebuilding twice the speed in another pci slot without problem at the moment. dont know how I had two failed drives and a Parity throwing errors. i assumed the array would be dead.
July 19, 20187 yr Author my parity drive is on the onboard controller not the lsi card and its still getting errors while rebuilding. The rebuilt has moved from 18 hours to 7 days. I assume this isn't going to finish given i have 3 disks with issues? i think the motherboard is having issues if the onboard IO is problematic as well.
July 19, 20187 yr Community Expert With all those errors it's rebuilding a corrupt disk, no point in continuing, also not a good sign that both disks are unmountable, when disks drop by suspect cable/controller issues it's usually best to re-enable them instead of rebuilding, as the latter may cause more damage instead of fixing the problem.
July 19, 20187 yr Author Should i power down the system and try rebuild one disk at a time check sata data cable on Parity1 drive. try that again. It disabled disk 7 and disk 9 on me, rebuild seemed the only option. Sounds like the data on disk 7 and 9 is gone to me.
July 19, 20187 yr Community Expert Ideally you'd need to fix whatever it's causing the random errors first, but you replace the parity cables, then unassign both disabled disks and see if the file system can be fixed before rebuilding.
July 19, 20187 yr Community Expert That's bad news, if parity is really failed you may still try and re-enable the disabled disks, since there's no way to rebuild them now and nothing to lose, but likely there's a lot of damage done.
July 19, 20187 yr Author its weird all the disks are going click then resetting. maybe all the drives are failing ? i can't seem to rebuild anything here
July 19, 20187 yr Community Expert It could also be a failing power supply, and it would also explain the previous issues.
July 19, 20187 yr Author just dropped the suspect parity drive. disk 7 and disk 9 dropped them as well. did a new config rebuilding using the one good parity drive i know is good. no clicking now and its rebuilding that parity drive. fingers crossed. I think after this is finished ill have to preclear disk 7 and disk 9 along with the suspect parity drive work out which ones are faulty or dying. smart is saying everything is good for disk 7 and disk 9. but the parity drive showing the errors was saying its not even spinning in the smart section. so maybe this is all from bad parity drive data causing issues. yes i lost disk 7 and disk 9 data, but i have a backup of those folders and i pair folders in my shares in 2-4 disk sets so not to concerned. Some of these other disks i don't have a backup of.. so scraficing the two disks for the rest. I see ata5,6,2 resetting in the logs. But it doesn't tell me the serial numbers.
July 19, 20187 yr Author pulled the power out of three drives no more clicking noises. i think one of the 3 are good 2 are dead. they are 4 years old.. so.. i guess end of life and a parity rebuild killed them. death in the masses.
July 19, 20187 yr 24 minutes ago, Maticks said: pulled the power out of three drives no more clicking noises. i think one of the 3 are good 2 are dead. they are 4 years old.. so.. i guess end of life and a parity rebuild killed them. death in the masses. Just as @johnnie.black, I suspect you have a bad PSU that can't supply enough power or stable enough voltages anymore. So don't do anything destructive with the disks until you have considered a different PSU. It isn't common to get three disks to go bad and start to click at the same time - but bad power can make multiple disk enter a boot loop. With a bad PSU, you can manage to have the machine working with less active drives. But if you do have a PSU going bad, then even worse things can happen down the line.
July 19, 20187 yr Author ill try new power cables.. im getting read errors rebuilding the parity now on more drives arrggg
July 19, 20187 yr Author pulled out the newly installed hard drive i was going to add in. though i doubt a new harddrive could have caused this ? changed out the power leads on the hard drives and split some more between sata power leads. installed another string of sata power to my RM850 power supply. unplugged all the power leads not in use i am about 4 drives down to what i use to have plugged in so the power draw should be less. but its 140Watts on an 850Watt power supply its hardly stressed i did install these sata power connectors 2 months ago but i haven't had an issue till now. they were better than the SATA $3 Y splitters i used from ebay before. https://www.scorptec.com.au/product/Cables/Internal-Power-Cables/44390-SST-CP06?gclid=CjwKCAjw7cDaBRBtEiwAsxprXd9nnqkcLkelJXSJ0RPF8f0BmPba96yC6LtiYRiZBttcgH8J2M3RzRoC9pQQAvD_BwE after reading more online, i think the clicking was staved for power hard drives, it seems they do that when they can't spin up. i had 8 drives plugged into one sata 4 connector. I guess 8 is too many for a sata plug from the power supply, the speed has gone from 700Mbps rebuilding the parity drive to 1.3Gbps. Not a single clicking noise or error so far. I feel like an idiot. I guess it looks cleaner but not good for power delivery. Thanks for the help guys i appreciate it Edited July 19, 20187 yr by Maticks
July 19, 20187 yr 51 minutes ago, Maticks said: I guess 8 is too many for a sata plug from the power supply That's about 16 ampere when all 8 tries to start up. Lots of voltage drop in the cable resulting in drives not getting a stable voltage and ending up in a boot loop. For every reboot, you get a click from the heads, and depending on how far the unit got in the bootup you also get the platters spinning up partially before stopping and then spinning up again.
July 19, 20187 yr Author no making a parity disk here it seems ul 19 22:21:42 Vault kernel: md: disk1 read error, sector=1034079200 Jul 19 22:21:42 Vault kernel: md: disk4 read error, sector=1034079200 Jul 19 22:21:42 Vault kernel: md: disk5 read error, sector=1034079200 Jul 19 22:21:42 Vault kernel: md: disk9 read error, sector=1034079200 Jul 19 22:21:42 Vault kernel: md: disk1 read error, sector=1034079208 Jul 19 22:21:42 Vault kernel: md: disk4 read error, sector=1034079208 Jul 19 22:21:42 Vault kernel: md: disk5 read error, sector=1034079208 Jul 19 22:21:42 Vault kernel: md: disk9 read error, sector=1034079208 Jul 19 22:21:42 Vault kernel: md: disk1 read error, sector=1034079216 Jul 19 22:21:42 Vault kernel: md: disk4 read error, sector=1034079216 Jul 19 22:21:42 Vault kernel: md: disk5 read error, sector=1034079216 Jul 19 22:21:42 Vault kernel: md: disk9 read error, sector=1034079216 Jul 19 22:21:42 Vault kernel: md: disk1 read error, sector=1034079224 Jul 19 22:21:42 Vault kernel: md: disk4 read error, sector=1034079224 Jul 19 22:21:42 Vault kernel: md: disk5 read error, sector=1034079224 Jul 19 22:21:42 Vault kernel: md: disk9 read error, sector=1034079224 Jul 19 22:21:42 Vault kernel: md: disk1 read error, sector=1034079232 Jul 19 22:21:42 Vault kernel: md: disk4 read error, sector=1034079232 Jul 19 22:21:42 Vault kernel: md: disk5 read error, sector=1034079232 Jul 19 22:21:42 Vault kernel: md: disk9 read error, sector=1034079232 Jul 19 22:21:42 Vault kernel: md: disk1 read error, sector=1034079240 Jul 19 22:21:42 Vault kernel: md: disk4 read error, sector=1034079240 Jul 19 22:21:42 Vault kernel: md: disk5 read error, sector=1034079240 Jul 19 22:21:42 Vault kernel: md: disk9 read error, sector=1034079240 Jul 19 22:21:42 Vault kernel: md: disk1 read error, sector=1034079248 Jul 19 22:21:42 Vault kernel: md: disk4 read error, sector=1034079248 Jul 19 22:21:42 Vault kernel: md: disk5 read error, sector=1034079248 Jul 19 22:21:42 Vault kernel: md: disk9 read error, sector=1034079248 Jul 19 22:21:42 Vault kernel: md: disk1 read error, sector=1034079256 Jul 19 22:21:42 Vault kernel: md: disk4 read error, sector=1034079256 Jul 19 22:21:42 Vault kernel: md: disk5 read error, sector=1034079256 Jul 19 22:21:42 Vault kernel: md: disk9 read error, sector=1034079256 Jul 19 22:21:42 Vault kernel: md: disk1 read error, sector=1034079264 Jul 19 22:21:42 Vault kernel: md: disk4 read error, sector=1034079264 Jul 19 22:21:42 Vault kernel: md: disk5 read error, sector=1034079264 Jul 19 22:21:42 Vault kernel: md: disk9 read error, sector=1034079264
July 19, 20187 yr Author should i xfs repair somehow these drives in maintenance mode ? or is the data corrupted on the data drive
Archived
This topic is now archived and is closed to further replies.