Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

zey

Members
  • Joined

  • Last visited

Everything posted by zey

  1. 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!
  2. 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?
  3. 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.
  4. 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. I have a 700w PSU.
  5. 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.
  6. 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
  7. Here ya go. hyperion-diagnostics-20160130-2006.zip
  8. 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.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.