edrohler

Unfortunately, no. I had to replace the emulated disk, ensure it never spun down and run unBalance to move everything off. I later swapped out the HDD brand to hitachi. The issue I was having was the Seagate Firmware would not properly mount the disk after it spun down was spun back up in an external JBOD enclosure. Sorry for the late reply on that, btw.

I think I found the issue: All of the disks that I have are ironwolf 8TB drives with a single parity. 4 drives are directly attached to the mother board sata ports and only 1 is using the SFF-8808 min-sas cable in the external enclosure. After a little digging, it is likely this [6.9.2] Ironwolf Drive Disablement and the [6.9.x] LSI Controllers & Ironwolf Disks - Summary & Fix.

WOW! Thank you for this thread. I have been scratching my head about this all week. I posted here. Instead of tweaking the drives, I am just going to disable the spin down delay for any drives in the enclosure and hope for an update to the driver.

Can unBalance be used on when a disk is being emulated and during a rebuild? I need to move about 2TB off of a disk that has an unstable connection which keeps disabling.

Well, it wasn't the cable. I replaced it and the issue still exists. The disk log shows this happening during the synchronizing SCSI cache. However, the disk was originally mounted at sdd and now it is trying to synch sdi. I am not sure why this is happening but it is making me like unraid more and more. I just want to set and forget it. May 8 02:05:00 kernel: sd 7:0:5:0: [sdi] tag#9555 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 May 8 02:05:03 kernel: sd 7:0:5:0: [sdi] Synchronizing SCSI cache May 8 02:05:03 kernel: sd 7:0:5:0: [sdi] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 May 8 02:05:04 kernel: scsi 7:0:5:0: [sdi] tag#9554 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 cmd_age=20s May 8 02:05:04 kernel: scsi 7:0:5:0: [sdi] tag#9554 CDB: opcode=0x88 88 00 00 00 00 02 85 d1 6a 80 00 00 01 00 00 00 May 8 02:05:04 kernel: blk_update_request: I/O error, dev sdi, sector 10835028608 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0 Also, I can't even just re-mount the disk to move the files onto one of the non-SFF-8088 cabled disks. I thought if a data disk fails, we can just mount it and access the files? Now, it seems like I need to wait another 11 hours for the parity-rebuild to finish and then hope it doesn't fail again while I move the files to more stable drives using unbalance and then ditch the 8-bay external enclosure.

Thanks again for the help. I do believe it is how the cable is sitting.

Thank you for the reply. I assume by breakout cabling you mean the external Mini SAS SFF-8088 cable? I am using an 8-bay external enclosure.

Hello, I have ran into an issue with my sata card randomly disabling disks attached to it and I cannot figure out why. Below is the syslog output that I can find. The SMART settings say it is healthy. Any ideas what could cause this? I have had to rebuild the data onto the same disk twice in 2 days now. May 3 02:54:08 kernel: sd 7:0:0:0: attempting task abort!scmd(0x000000007cd90eff), outstanding for 15497 ms & timeout 15000 ms May 3 02:54:08 kernel: sd 7:0:0:0: [sdh] tag#2356 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 May 3 02:54:08 kernel: scsi target7:0:0: handle(0x000a), sas_address(0x5001e677bbe6dfe0), phy(0) May 3 02:54:08 kernel: scsi target7:0:0: enclosure logical id(0x5001e677bbe6dfff), slot(0) May 3 02:54:08 kernel: sd 7:0:0:0: device_block, handle(0x000a) May 3 02:54:10 kernel: sd 7:0:0:0: device_unblock and setting to running, handle(0x000a) May 3 02:54:10 kernel: sd 7:0:0:0: [sdh] Synchronizing SCSI cache May 3 02:54:10 kernel: sd 7:0:0:0: [sdh] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 May 3 02:54:10 rc.diskinfo[8086]: SIGHUP received, forcing refresh of disks info. May 3 02:54:12 kernel: scsi 7:0:0:0: [sdh] tag#7232 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 cmd_age=19s May 3 02:54:12 kernel: scsi 7:0:0:0: [sdh] tag#7232 CDB: opcode=0x88 88 00 00 00 00 02 02 51 49 00 00 00 00 40 00 00 May 3 02:54:12 kernel: blk_update_request: I/O error, dev sdh, sector 8628816128 op 0x0:(READ) flags 0x0 phys_seg 8 prio class 0 May 3 02:54:12 kernel: md: disk4 read error, sector=8628816064 May 3 02:54:12 kernel: md: disk4 read error, sector=8628816072 May 3 02:54:12 kernel: md: disk4 read error, sector=8628816080 May 3 02:54:12 kernel: md: disk4 read error, sector=8628816088 May 3 02:54:12 kernel: md: disk4 read error, sector=8628816096 May 3 02:54:12 kernel: md: disk4 read error, sector=8628816104 May 3 02:54:12 kernel: md: disk4 read error, sector=8628816112 May 3 02:54:12 kernel: md: disk4 read error, sector=8628816120 May 3 02:54:12 kernel: scsi 7:0:0:0: task abort: SUCCESS scmd(0x000000007cd90eff) May 3 02:54:12 kernel: mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x5001e677bbe6dfe0) May 3 02:54:12 kernel: mpt2sas_cm0: removing handle(0x000a), sas_addr(0x5001e677bbe6dfe0) May 3 02:54:12 kernel: mpt2sas_cm0: enclosure logical id(0x5001e677bbe6dfff), slot(0) May 3 02:54:13 kernel: scsi 7:0:2:0: Direct-Access ATA ST8000VN004-2M21 SC60 PQ: 0 ANSI: 6 May 3 02:54:13 kernel: scsi 7:0:2:0: SATA: handle(0x000a), sas_addr(0x5001e677bbe6dfe0), phy(0), device_name(0x0000000000000000) May 3 02:54:13 kernel: scsi 7:0:2:0: enclosure logical id (0x5001e677bbe6dfff), slot(0) May 3 02:54:13 kernel: scsi 7:0:2:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) May 3 02:54:13 kernel: scsi 7:0:2:0: qdepth(32), tagged(1), scsi_level(7), cmd_que(1) May 3 02:54:13 kernel: sd 7:0:2:0: Attached scsi generic sg7 type 0 May 3 02:54:13 kernel: end_device-7:0:2: add: handle(0x000a), sas_addr(0x5001e677bbe6dfe0) May 3 02:54:13 kernel: sd 7:0:2:0: Power-on or device reset occurred May 3 02:54:13 kernel: sd 7:0:2:0: [sdi] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB) May 3 02:54:13 kernel: sd 7:0:2:0: [sdi] 4096-byte physical blocks May 3 02:54:13 kernel: sd 7:0:2:0: [sdi] Write Protect is off May 3 02:54:13 kernel: sd 7:0:2:0: [sdi] Mode Sense: 7f 00 10 08 May 3 02:54:13 kernel: sd 7:0:2:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA May 3 02:54:13 kernel: sdi: sdi1 May 3 02:54:13 kernel: sd 7:0:2:0: [sdi] Attached SCSI disk May 3 02:54:13 rc.diskinfo[8086]: SIGHUP received, forcing refresh of disks info. May 3 02:54:14 unassigned.devices: Disk with serial 'ST8000VN004-2M2101_WRD0FLA6', mountpoint 'ST8000VN004-2M2101_WRD0FLA6' is not set to auto mount. May 3 02:54:15 kernel: br0: received packet on bond0 with own address as source address (addr:38:d5:47:aa:c8:f3, vlan:0)

Are there any specific steps to upgrade to Unraid 6.9 with the existing Nvidia Plugin already working and in use?

Excellent! That is exactly what I needed to understand. I can see that the card is in IT mode. Also, I did mean 9207. My apologies, I transposed the 20 to 02. Is it possible to change the title? I would also like to add closed to it.

Cool. Except, my post was not related to a specific issue. It was more of a question of hardware compatibility since the existing documentation is outdated. But anyway, I think I get it. Thanks.

Can you elaborate why you need diags instead?

Hello, I purchased this HBA card and put it into my Unraid build. The board is an Asus Z-170-Pro which support PCIe 3.0. I don't have any x4 or x8 slots but I do have x16. I have read around that the 9027-8i is supported in IT mode. I don't know what that really means or if it is even related to the 8E but apparently I have to flash the firmware. My question is do I need to flash 9027-8e to work with Unraid in JBOD? If so, how? Also, I plan to buy an 8-bay GG SAS/SATA expander but I want to make sure I can just connect the SFF-8088 cables and add the drives. Is there anything else I should consider? Below is the output of lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07) 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x8) (rev 07) 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31) 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31) 00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31) 00:1b.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #17 (rev f1) 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 (rev f1) 00:1c.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1) 00:1c.7 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #8 (rev f1) 00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Z170 Chipset LPC/eSPI Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31) 00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31) 00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31) 01:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1) 02:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2308 PCI-Express Fusion-MPT SAS-2 (rev 05) 04:00.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 05:00.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 05:01.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 05:02.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 05:04.0 PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] 08:00.0 USB controller: Intel Corporation DSL6540 USB 3.1 Controller [Alpine Ridge] 0a:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection 0b:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection Thank you for you help!

All right. I think it is working now. I did a fresh install without any tuning. Not exactly sure what happened but most likely turning too many knobs unnecessarily. Typical noob. Thanks again for the help.

Awesome. That is good to know. Well, I have recreated the boot image but this time I configured it to add UEFI and use the default BIOS settings. Also, re-start Ed the same array configuration. Hopefully, this solves the issue. Thanks again for the information! I'll post back in about 11 hours with the results.

I imagine it was a plugin or something that I did before configuring the array since I am a newb. I have since just did a fresh install and am actually running a preclear this time. With 6.8 do we need to run the pre-clear on disks?

Agreed. This is very strange behavior. All of the hardware is mostly new/unused. After the memtest, I checked the BIOS and reset it to defaults but now the USB won't boot. Will probably have to do a clean install.

@johnnie.black thanks! I ran the first pass without error. I imagine the crashes are from force shutdowns of the server.

Welp, that didn't work. I have had to do several unclean shutdowns. The interesting thing is that many of my devices on my network also loose internet connectivity. The only docker containers I have is the Krusader. Not even sure what is happening. Here is my syslog file. syslog

Here is my server set up. MOBO: Asus AZ170-PRO RAM: 32Gb Processor: Intel® Core™ i7-6700K CPU @ 4.00GHz Array: 4 Seagate IronWolf Pro 8TB with dual parity

@Squid, thank you. I have enabled the syslog server and started the parity check again. I will report back if the issue happens again. @itimpi, thank you for the plugin recommendation. I will check it out. I think that the issue was coming from the Tips and Tweaks CPU governer settings. I originally had this set as Performance and Enabled the Intel Turbo Boost and have reset it to default. It seems to be working ok for now.

Hello, I cannot run or schedule a parity check without the server becoming unusable. Is this expected? It's a pretty powerful server and I am not sure how to troubleshoot this. Thank you.