March 9, 20179 yr A few days ago I added additional RAID card to my setup and 2 HD cages. SUPERMICRO AOC-SAS2LP-MV8 PCI-Express 2.0 x8 SATA / SAS 8-Port Controller Card SUPERMICRO CSE-M35T-1B 3 x 5.25" to 5 x 3.5" Hot-swap SATA HDD Trays In the cage I added 2 drives a 3TB and a 4TB and added them to the array so it started preclearing them when I left last night. This morning I check on the server and it's completely unresponsive locally on through the website. Didn't see any HD activity either. So power cycle it is. Now the server boots up and sees ALL the HDs during the boot process (even the 2 it shows as missing in unRAID) When I got into the unRAID it had red X's next to the 2 new drives. I started the array and it immediately started Parity check. So I am not really sure what to do at this point. I added a 2nd Parity drive 2 days ago. The Diagnostics are from 21st of Feb. It wont let me generate a new one.. or it runs through the process but I never get a file to download even on a different browser. Thanks! tower-diagnostics-20170221-1035.zip
March 9, 20179 yr Community Expert Did you try getting the diagnostics using the console? If not type diagnostics and upload them.
March 9, 20179 yr Author 7 hours ago, trurl said: Some drives come with it disabled, and you have to turn it on. Search google for smartctl enable. Ugh, fun, got it. In addition I also found this thread: I haven't disabled Int13 like they are talking about at the end of the thread. I am however using the latest 1812 firmware for the new raid card. Should I stop the Parity Check and reboot to disable the Int13? tower-diagnostics-20170309-0747 (1).zip
March 9, 20179 yr Community Expert You don't have a SAS2LP, you are using a LSI2008 based controller, also all your the connected disks are assigned, you have 6 onboard + 8 on the LSI, 14 total, (2 parity + 11 data + cache), where were the other disks connected?
March 9, 20179 yr Author What you're seeing the onboard HDs, correct, then LSI card (on the bottom of the pic) with SAS2LP being the top card. The cables from it go directly into the HD enclosure. On bootup the SAS2LP was working properly yesterday when I started adding them to the array. The card is still showing up on bootup and it does detect the 2 drives that are attached to it. UnRAID just quit seeing them On the SAS2LP card D2 led is the one lit solid Red. Not sure what is the meaning of it since I have no manual or cant find one online.
March 9, 20179 yr Community Expert No SAS2LP being detected by Linux, take out and install it again: 00:00.0 Host bridge [0600]: Intel Corporation 82X38/X48 Express DRAM Controller [8086:29e0] (rev 01) Subsystem: Super Micro Computer Inc 82X38/X48 Express DRAM Controller [15d9:d980] 00:01.0 PCI bridge [0604]: Intel Corporation 82X38/X48 Express Host-Primary PCI Express Bridge [8086:29e1] (rev 01) Kernel driver in use: pcieport 00:06.0 PCI bridge [0604]: Intel Corporation 82X38/X48 Express Host-Secondary PCI Express Bridge [8086:29e9] (rev 01) Kernel driver in use: pcieport 00:19.0 Ethernet controller [0200]: Intel Corporation 82566DM-2 Gigabit Network Connection [8086:10bd] (rev 02) Subsystem: Super Micro Computer Inc 82566DM-2 Gigabit Network Connection [15d9:10bd] Kernel driver in use: e1000e Kernel modules: e1000e 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) Subsystem: Super Micro Computer Inc 82801I (ICH9 Family) USB UHCI Controller [15d9:d980] Kernel driver in use: uhci_hcd 00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02) Subsystem: Super Micro Computer Inc 82801I (ICH9 Family) USB UHCI Controller [15d9:d980] Kernel driver in use: uhci_hcd 00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 02) Subsystem: Super Micro Computer Inc 82801I (ICH9 Family) USB UHCI Controller [15d9:d980] Kernel driver in use: uhci_hcd 00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 02) Subsystem: Super Micro Computer Inc 82801I (ICH9 Family) USB2 EHCI Controller [15d9:d980] Kernel driver in use: ehci-pci 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 02) Subsystem: Super Micro Computer Inc 82801I (ICH9 Family) HD Audio Controller [15d9:d980] 00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 02) Kernel driver in use: pcieport 00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 02) Subsystem: Super Micro Computer Inc 82801I (ICH9 Family) USB UHCI Controller [15d9:d980] Kernel driver in use: uhci_hcd 00:1d.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 02) Subsystem: Super Micro Computer Inc 82801I (ICH9 Family) USB UHCI Controller [15d9:d980] Kernel driver in use: uhci_hcd 00:1d.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 02) Subsystem: Super Micro Computer Inc 82801I (ICH9 Family) USB UHCI Controller [15d9:d980] Kernel driver in use: uhci_hcd 00:1d.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 02) Subsystem: Super Micro Computer Inc 82801I (ICH9 Family) USB2 EHCI Controller [15d9:d980] Kernel driver in use: ehci-pci 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 92) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801IR (ICH9R) LPC Interface Controller [8086:2916] (rev 02) Subsystem: Super Micro Computer Inc 82801IR (ICH9R) LPC Interface Controller [15d9:d980] 00:1f.2 IDE interface [0101]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 4 port SATA Controller [IDE mode] [8086:2920] (rev 02) Subsystem: Super Micro Computer Inc 82801IR/IO/IH (ICH9R/DO/DH) 4 port SATA Controller [IDE mode] [15d9:d980] Kernel driver in use: ata_piix Kernel modules: ata_piix 00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 02) Subsystem: Super Micro Computer Inc 82801I (ICH9 Family) SMBus Controller [15d9:d980] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 00:1f.5 IDE interface [0101]: Intel Corporation 82801I (ICH9 Family) 2 port SATA Controller [IDE mode] [8086:2926] (rev 02) Subsystem: Super Micro Computer Inc 82801I (ICH9 Family) 2 port SATA Controller [IDE mode] [15d9:d980] Kernel driver in use: ata_piix Kernel modules: ata_piix 00:1f.6 Signal processing controller [1180]: Intel Corporation 82801I (ICH9 Family) Thermal Subsystem [8086:2932] (rev 02) Subsystem: Super Micro Computer Inc 82801I (ICH9 Family) Thermal Subsystem [15d9:0000] 03:00.0 Serial Attached SCSI controller [0107]: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:0072] (rev 03) Subsystem: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] [1000:3020] Kernel driver in use: mpt3sas Kernel modules: mpt3sas 05:00.0 PCI bridge [0604]: Intel Corporation 6702PXH PCI Express-to-PCI Bridge A [8086:032c] (rev 09) 05:00.1 PIC [0800]: Intel Corporation 6700/6702PXH I/OxAPIC Interrupt Controller A [8086:0326] (rev 09) Subsystem: Super Micro Computer Inc 6700/6702PXH I/OxAPIC Interrupt Controller A [15d9:d980] 11:01.0 VGA compatible controller [0300]: S3 Graphics Ltd. 86c375 [ViRGE/DX] or 86c385 [ViRGE/GX] [5333:8a01] (rev 01) Subsystem: S3 Graphics Ltd. ViRGE/DX [5333:8a01] 11:03.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] [104c:8023] Subsystem: Super Micro Computer Inc TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] [15d9:ba80] 11:04.0 IDE interface [0101]: Integrated Technology Express, Inc. IT8213 IDE Controller [1283:8213] Subsystem: Integrated Technology Express, Inc. IT8213 IDE Controller [1283:8213] Edited March 9, 20179 yr by johnnie.black
March 9, 20179 yr Author Well, I dunno what else could be wrong. lol I reseated the card. Got into the BIOS and disabled the int13. As you can see in the BIOS it's picking up the 2 "missing" drives. (4TH and 3TB) tower-diagnostics-20170309-1012.zip
March 9, 20179 yr Community Expert Now it's working: 01:00.0 RAID bus controller [0104]: Marvell Technology Group Ltd. 88SE9485 SAS/SATA 6Gb/s controller [1b4b:9485] (rev ff) Kernel driver in use: mvsas Kernel modules: mvsas Almost certainly the problem was caused by the controller stopping to be detected.
March 9, 20179 yr Author Interesting. The drives did not pop up in the unRaid though. I took the SATA card out trying to test it with the 2 drives (no cage) in another PC.
March 9, 20179 yr Community Expert Disks were disabled, so they'll need to be rebuilt. Edited March 9, 20179 yr by johnnie.black
March 9, 20179 yr Author 59 minutes ago, johnnie.black said: Disks were disabled, so they'll need to be rebuilt. What file do you see that it shows detected controller? BTW, I was able to boot up in a random Win7 PC with this raid card and 2 drives. The system saw both of the drives. Just booted up in the unRAID and same thing.., shows no drives available with red x's. Thanks tower-diagnostics-20170309-1221.zip Edited March 9, 20179 yr by dimitriz
March 9, 20179 yr Community Expert On the diagnostics it's lspci.txt in the system folder, you can also go to Tools -> System Devices. BTW, controller is gone again on latest diags.
March 9, 20179 yr Author 31 minutes ago, johnnie.black said: On the diagnostics it's lspci.txt in the system folder, you can also go to Tools -> System Devices. BTW, controller is gone again on latest diags. Just rebooted: [1b4b:9485] 01:00.0 RAID bus controller: Marvell Technology Group Ltd. 88SE9485 SAS/SATA 6Gb/s controller (rev c3) [1000:0072] 03:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) Looks like it picked up 3 drives... (I added another test drive on the 2nd set of 4 ports... and plugged it in outside the HD cage to see if cage maybe a problem) So..., now I am freaking paranoid to try rebooting this thing., lol
March 9, 20179 yr Community Expert There may be some compatibility issue with the SAS2LP, you could also try swapping slots with the LSI controller, but if there's an issue with that slot it will disable a lot of array disks and you'll need to do a new config.
March 9, 20179 yr Author Alrighty. I rebooted and it looks like it stuck... Guess I will see tomorrow if anything is going to happen. lol
Archived
This topic is now archived and is closed to further replies.