January 30, 201610 yr I swapped system board, added a new hard drive, and swapped one of two of my cache drives. Now I'm getting "Parity Device is Disabled" I also added a Supermicro AOC-SASLP-MV8. Weird thing is I do not see the option to access it's BIOS at boot up. I attempted to access using "Ctrl+M" however it did not work. So I am not able to confirm that it's not in raid mode nor if INT13 is disabled. I'd like to assume Raid is off due to the fact I am able to add the drives to the array. I did some searching and found this thread https://lime-technology.com/forum/index.php?topic=42806.0 I performed the following in an attempt to resolve the issue. [*]Stop the array [*]Unassign the disk [*]Start the array [*]Stop the array [*]Assign the disk [*]Start the array and parity build should start WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) = Parity drive It'll get to about 1.6% then the status goes to disabled. unRAID Parity disk error: 30-01-2016 16:55 Alert [HYPERION] - Parity disk in error state (disk dsbl) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) unRAID array errors: 30-01-2016 16:55 Warning [HYPERION] - array has errors Array has 6 disks with read errors unRAID Parity sync:: 30-01-2016 16:55 Notice [HYPERION] - Parity sync: finished (431 errors) Duration: unavailable (no parity-check entries logged) Jan 30 19:40:08 Hyperion kernel: sd 1:0:7:0: [sdk] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) Jan 30 19:40:08 Hyperion kernel: sd 1:0:7:0: [sdk] 4096-byte physical blocks Jan 30 19:40:08 Hyperion kernel: sd 1:0:7:0: [sdk] Write Protect is off Jan 30 19:40:08 Hyperion kernel: sd 1:0:7:0: [sdk] Mode Sense: 00 3a 00 00 Jan 30 19:40:08 Hyperion kernel: sd 1:0:7:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 30 19:40:08 Hyperion kernel: sdk: sdk1 Jan 30 19:40:08 Hyperion kernel: sd 1:0:7:0: [sdk] Attached SCSI disk Jan 30 19:40:59 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:40:59 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:40:59 Hyperion emhttp: shcmd (: /usr/local/sbin/set_ncq sdk 1 &> /dev/null Jan 30 19:43:41 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:43:41 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:43:42 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:43:42 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:43:42 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:43:42 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:43:48 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:43:48 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:43:50 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:43:50 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:44:01 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:44:01 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:44:15 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:44:15 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:44:15 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:44:15 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:44:25 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:44:25 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:44:27 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:44:27 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:44:35 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:44:48 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:45:06 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:45:06 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:45:07 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:45:07 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:45:11 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:45:11 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:45:33 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:45:33 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:45:33 Hyperion emhttp: shcmd (252): /usr/local/sbin/set_ncq sdk 1 &> /dev/null Jan 30 20:00:17 Hyperion kernel: sd 1:0:7:0: [sdk] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Jan 30 20:00:17 Hyperion kernel: sd 1:0:7:0: [sdk] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 07 31 28 40 00 00 02 00 00 00 Jan 30 20:00:17 Hyperion kernel: blk_update_request: I/O error, dev sdk, sector 120662080 Jan 30 20:02:37 Hyperion emhttp: shcmd (297): /usr/local/sbin/set_ncq sdk 1 &> /dev/null Jan 30 20:02:38 Hyperion emhttp: shcmd (305): /usr/local/sbin/set_ncq sdk 1 &> /dev/null Jan 30 20:02:42 Hyperion emhttp: shcmd (313): /usr/local/sbin/set_ncq sdk 1 &> /dev/null Jan 30 20:02:42 Hyperion emhttp: shcmd (321): /usr/local/sbin/set_ncq sdk 1 &> /dev/null Any help would be greatly appreciated.
January 31, 201610 yr Community Expert Difficult to tell without more information! The fact the disk gets disabled means that a write to it failed but that could be for a wide variety of reasons. I would suggest that you use the Tools->Diagnostics option and post the resulting zip file.
January 31, 201610 yr Community Expert Looks like the drive has dropped offline. Probably a connection issue. Check SATA and power plugs.
January 31, 201610 yr Community Expert Looks like a controller issue, all disks on the SASLP dropped offline, maybe try it on different slot if available.
January 31, 201610 yr Can you try that controller in another box and see if you can access it's BIOS? The fact you can't access it on your unRAID box is disturbing...
January 31, 201610 yr Community Expert Can you try that controller in another box and see if you can access it's BIOS? The fact you can't access it on your unRAID box is disturbing... I know that in my MB BIOS there is a setting (that defaults to enabled) as to whether or not I see messages from add-on boards during the post + boot sequence. I wonder if the OP has a similar setting that is not enabled?
February 1, 201610 yr Author Thanks to everyone replying. Here's what I've done so far in an attempt to resolve this issue. Flashed my Supermicro AOC-SASLP-MV8 to 3.1.0.15n I also flash my system board (Supermicro A1SA7-2750F) to the latest BIOs version 1.1a I was then able to get into the BIOs of the HBA. I made sure to disable INT13 function and as we all know firmware version 3.1.0.15n does not support Raid therefore that's a non issue. I performed a New Config and added all the drives. Parity check begins however it does not complete the Parity check. Instead it goes back into disabled. So what I tried was switching the Parity disk with the new HD I had installed and still Parity check does not complete and it goes into a disabled state. Now I'm wondering, could it be the breakout cables I'm using? I just bought them I can't imagine being able to access my shares and somehow they're having an issue with a parity check. hyperion-diagnostics-20160131-2005.zip
February 1, 201610 yr Author Here's an other weird thing. After the Parity check fails and marks the Parity disk as disabled, I stop the array. All disks go missing, the only way to get them back is by rebooting. Fresh install of UnRaid did not resolve the issue.
February 1, 201610 yr Just because no one else has asked the question, what power supply are you using
February 1, 201610 yr Community Expert Here's an other weird thing. After the Parity check fails and marks the Parity disk as disabled, I stop the array. All disks go missing, the only way to get them back is by rebooting. Fresh install of UnRaid did not resolve the issue. i had a similar problem at one point and it turned out to be due to the fact the disk controller card was not perfectly seated in the motherboard. It would work most of the time, but occasionally a disk would get a write error and then all disks on the controller were missing. I assume that a momentary disconnect due to vibration meant the controller was lost and this caused the issue. This sounds similar to what you are seeing? the seating issue was due to the backplate tending to lift one edge of the connector slightly. Resolving this stopped my problem. As a general rule any error that takes out all disks on a controller means that you need to look at the controller rather than individual drives.
February 1, 201610 yr Author Here's an other weird thing. After the Parity check fails and marks the Parity disk as disabled, I stop the array. All disks go missing, the only way to get them back is by rebooting. Fresh install of UnRaid did not resolve the issue. i had a similar problem at one point and it turned out to be due to the fact the disk controller card was not perfectly seated in the motherboard. It would work most of the time, but occasionally a disk would get a write error and then all disks on the controller were missing. I assume that a momentary disconnect due to vibration meant the controller was lost and this caused the issue. This sounds similar to what you are seeing? the seating issue was due to the backplate tending to lift one edge of the connector slightly. Resolving this stopped my problem. As a general rule any error that takes out all disks on a controller means that you need to look at the controller rather than individual drives. Awesome I'll give that a try because at this point I have no clue what the hell is going wrong. Just because no one else has asked the question, what power supply are you using I have a 700w PSU.
February 1, 201610 yr Community Expert Just because no one else has asked the question, what power supply are you using I have a 700w PSU. Question should have been "What is the exact model of your power supply."
February 1, 201610 yr Just because no one else has asked the question, what power supply are you using I have a 700w PSU. Question should have been "What is the exact model of your power supply." Details, details. My bad
February 1, 201610 yr Author Just because no one else has asked the question, what power supply are you using I have a 700w PSU. Question should have been "What is the exact model of your power supply." Details, details. My bad Sorry I also should've included those details. I have a Corsair TX750.
February 2, 201610 yr Author Ok so I went ahead and reseat the controller and cables just in case. I kicked off the parity check. Fingers crossed.. Off-topic is there anyway of getting the hdd led to show when the controller is working?
February 3, 201610 yr Author i had a similar problem at one point and it turned out to be due to the fact the disk controller card was not perfectly seated in the motherboard. It would work most of the time, but occasionally a disk would get a write error and then all disks on the controller were missing. I assume that a momentary disconnect due to vibration meant the controller was lost and this caused the issue. This sounds similar to what you are seeing? the seating issue was due to the backplate tending to lift one edge of the connector slightly. Resolving this stopped my problem. As a general rule any error that takes out all disks on a controller means that you need to look at the controller rather than individual drives. itimpi, I would like to thank you for the help and suggestion of reseating the HBA. I appears to have resolved the issue. I can't tell you how happy I am, you're the MAN!
November 8, 20196 yr On 2/1/2016 at 7:31 AM, itimpi said: i had a similar problem at one point and it turned out to be due to the fact the disk controller card was not perfectly seated in the motherboard. It would work most of the time, but occasionally a disk would get a write error and then all disks on the controller were missing. I assume that a momentary disconnect due to vibration meant the controller was lost and this caused the issue. This sounds similar to what you are seeing? the seating issue was due to the backplate tending to lift one edge of the connector slightly. Resolving this stopped my problem. As a general rule any error that takes out all disks on a controller means that you need to look at the controller rather than individual drives. Woah, this solved all my problems. Thanks!
April 24, 20215 yr On 2/1/2016 at 7:31 AM, itimpi said: i had a similar problem at one point and it turned out to be due to the fact the disk controller card was not perfectly seated in the motherboard. It would work most of the time, but occasionally a disk would get a write error and then all disks on the controller were missing. I assume that a momentary disconnect due to vibration meant the controller was lost and this caused the issue. This sounds similar to what you are seeing? the seating issue was due to the backplate tending to lift one edge of the connector slightly. Resolving this stopped my problem. As a general rule any error that takes out all disks on a controller means that you need to look at the controller rather than individual drives. Just had 2 drives become disabled, rebuilt them and then the same thing happen again after a reboot with different drives. This was my issue and I don't think I would have found it if you hadn't posted this, so thanks! You've saved me countless hours of troubleshooting! Due to the HBA only being an 8x and sitting in a 16x slot, the two sata cables if moved have enough force to pull the back of the card out the slot slightly while still being firmly attached at the front. Edited April 24, 20215 yr by Scooshie
October 22, 20223 yr I'm having same issue that parity disk is disabled, no matter what I do. I changed sata cables, also power cables, always the same. Can someone look at my diagnostics files? unraid-diagnostics-20221022-1544.zip
October 22, 20223 yr Community Expert 22 minutes ago, Glavic said: parity disk is disabled SMART for parity looks OK, no connection problems in current syslog. Since it's only parity no possible harm in rebuilding to the same drive. https://wiki.unraid.net/Manual/Storage_Management#What_is_a_.27failed.27_.28disabled.29_drive
November 8, 20232 yr On 1/30/2016 at 5:31 PM, zey said: I swapped system board, added a new hard drive, and swapped one of two of my cache drives. Now I'm getting "Parity Device is Disabled" I also added a Supermicro AOC-SASLP-MV8. Weird thing is I do not see the option to access it's BIOS at boot up. I attempted to access using "Ctrl+M" however it did not work. So I am not able to confirm that it's not in raid mode nor if INT13 is disabled. I'd like to assume Raid is off due to the fact I am able to add the drives to the array. I did some searching and found this thread https://lime-technology.com/forum/index.php?topic=42806.0 I performed the following in an attempt to resolve the issue. [*]Stop the array [*]Unassign the disk [*]Start the array [*]Stop the array [*]Assign the disk [*]Start the array and parity build should start WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) = Parity drive It'll get to about 1.6% then the status goes to disabled. unRAID Parity disk error: 30-01-2016 16:55 Alert [HYPERION] - Parity disk in error state (disk dsbl) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) unRAID array errors: 30-01-2016 16:55 Warning [HYPERION] - array has errors Array has 6 disks with read errors unRAID Parity sync:: 30-01-2016 16:55 Notice [HYPERION] - Parity sync: finished (431 errors) Duration: unavailable (no parity-check entries logged) Jan 30 19:40:08 Hyperion kernel: sd 1:0:7:0: [sdk] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) Jan 30 19:40:08 Hyperion kernel: sd 1:0:7:0: [sdk] 4096-byte physical blocks Jan 30 19:40:08 Hyperion kernel: sd 1:0:7:0: [sdk] Write Protect is off Jan 30 19:40:08 Hyperion kernel: sd 1:0:7:0: [sdk] Mode Sense: 00 3a 00 00 Jan 30 19:40:08 Hyperion kernel: sd 1:0:7:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 30 19:40:08 Hyperion kernel: sdk: sdk1 Jan 30 19:40:08 Hyperion kernel: sd 1:0:7:0: [sdk] Attached SCSI disk Jan 30 19:40:59 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:40:59 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:40:59 Hyperion emhttp: shcmd (: /usr/local/sbin/set_ncq sdk 1 &> /dev/null Jan 30 19:43:41 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:43:41 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:43:42 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:43:42 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:43:42 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:43:42 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:43:48 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:43:48 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:43:50 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:43:50 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:44:01 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:44:01 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:44:15 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:44:15 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:44:15 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:44:15 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:44:25 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:44:25 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:44:27 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:44:27 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:44:35 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:44:48 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:45:06 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:45:06 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:45:07 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:45:07 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:45:11 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:45:11 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:45:33 Hyperion emhttp: WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 (sdk) 2930266584 Jan 30 19:45:33 Hyperion kernel: md: import disk0: [8,160] (sdk) WDC_WD30EFRX-68AX9N0_WD-WCC1T0738873 size: 2930266532 Jan 30 19:45:33 Hyperion emhttp: shcmd (252): /usr/local/sbin/set_ncq sdk 1 &> /dev/null Jan 30 20:00:17 Hyperion kernel: sd 1:0:7:0: [sdk] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Jan 30 20:00:17 Hyperion kernel: sd 1:0:7:0: [sdk] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 07 31 28 40 00 00 02 00 00 00 Jan 30 20:00:17 Hyperion kernel: blk_update_request: I/O error, dev sdk, sector 120662080 Jan 30 20:02:37 Hyperion emhttp: shcmd (297): /usr/local/sbin/set_ncq sdk 1 &> /dev/null Jan 30 20:02:38 Hyperion emhttp: shcmd (305): /usr/local/sbin/set_ncq sdk 1 &> /dev/null Jan 30 20:02:42 Hyperion emhttp: shcmd (313): /usr/local/sbin/set_ncq sdk 1 &> /dev/null Jan 30 20:02:42 Hyperion emhttp: shcmd (321): /usr/local/sbin/set_ncq sdk 1 &> /dev/null Any help would be greatly appreciated. Just wanted to say thanks. I had a similar problem. After a bad shutdown I had two disks showing as disabled but had good SMART. After a Google search this forum post showed first. The whole answer of stop the array...... fixed my issues. I was ready my new disks! So thanks!
April 28, 20242 yr I'm having this same problem and can't figure out what's going on. Here's the diagnostic zip file in case anyone can offer any guidance tower-diagnostics-20240427-2341.zip
April 28, 20242 yr Community Expert Diags are after rebooting so we can't see what happened, but SMART looks fine, check/replace/swap cables to rule that out and re-sync parity, and if it happens again save the diags before rebooting. https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.