April 21, 201115 yr My server consists of: unraid 4.7 CPU: AMD Athlon II X2 245 2.9GHz Socket AM3 $60 http://www.newegg.com/Product/Product.aspx?Item=N82E16819103687 Mobo: ASUS 6 internal SATA ports, AMD SB850 SB, 2 PCI-E slots, 1 eSATA $149 http://www.newegg.com/Product/Product.aspx?Item=N82E16813131631 Memory: GSkill DDR3 1333 4GB $40 http://www.newegg.com/Product/Product.aspx?Item=N82E16820231394 PSU: Corsair 650W 80+ Cert. $90 http://www.newegg.com/Product/Product.aspx?Item=N82E16817139005 I installed the Super Micro AOC-SASLP-MV8 and was having issues booting so I followed the instructions listed here and downgraded my firmware and was able to boot to unraid. Only problem is that it does not detect ANY discs correctly. It detects my two IDE drives, my eSATA HDD and the two SATA drives attached to the Supermicro card. Every HDD that is connected to the SATA ports on the MOBO are not detected. What happened? All help if greatly appreciated in advance.
April 21, 201115 yr Author Did you read the stickies at the top of the General Support forum? Yup, can't post a syslog till I get home. Obviously something is causing unraid to ignore my SATA controller on my MOBO and default to the Supermicro SATA controller.
April 22, 201115 yr It sounds like a BIOS issue. Do the MB SATA ports work again if the AOC card is removed?
April 22, 201115 yr Author It sounds like a BIOS issue. Do the MB SATA ports work again if the AOC card is removed? Not a BIOS issue as all drives are detected by the BIOS. unraid refuses to detect the MOBO connected SATA drives.
April 22, 201115 yr Author I ran a live CD of Ubuntu last night and it detected all my drives. So this is not a hardware issue.
April 22, 201115 yr I ran a live CD of Ubuntu last night and it detected all my drives. So this is not a hardware issue. You might try the 5.0beta6a release as it has additional drivers for newer hardware.
April 22, 201115 yr Author That was my next plan. Just wanted to be 100% sure I shouldn't have to worry about data loss.
April 22, 201115 yr That was my next plan. Just wanted to be 100% sure I shouldn't have to worry about data loss. 5.0beta6a will not automatically start the array. It will tell you if it recognizes the disks. If you see any that say "MBR undefined" follow the instructions in the announcement thread to dump the contents of the MBR for analysis. You'll not lose data unless you format the drives. An un-recognized partition is easily fixed. Do NOT start the array if there are disks with data that say MBR unknown. Any HPA issue will need to be resolved before you can move to 5.0beta6a, but no matter what, you'll be able to see if the disks show up in the list of potential disks and if the disk controller ports are recognized. Before doing anything, make a screen shot of your existing disk configuration and also make a copy of your current "config" folder after first stopping your array so you can restore to it if you revert back to 4.7. Instead of overwriting the existing bzroot and bzimage file with the 5.X versions, re-name them to bzroot.47 and bzimage.47. That way reverting is as simple as naming them back their original names and rebooting. Joe L.
April 22, 201115 yr 1. It is a BIOS issue / settings in your current configuration (there are three new BIOS releases in the last month) - what is your BIOS revision right now. 1/4 of the Newegg reviewers rate this board with 3 or less stars - so you are not alone. All the drives/controllers are visible in Unraid but with your current settings the onboard SATA3 ports share IRQ with the IDE controller that you are using and the SM card shares IRQ with the onboard eSATA jMicron controller. Apr 20 21:32:31 TheHub kernel: ahci 0000:00:11.0: version 3.0 Apr 20 21:32:31 TheHub kernel: ahci 0000:00:11.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 Apr 20 21:32:31 TheHub kernel: ahci 0000:00:11.0: irq 29 for MSI/MSI-X Apr 20 21:32:31 TheHub kernel: ahci 0000:00:11.0: AHCI 0001.0200 32 slots 6 ports 6 Gbps 0x3f impl SATA mode and Apr 20 21:32:31 TheHub kernel: jmicron 0000:04:00.1: IDE controller (0x197b:0x2361 rev 0x02) Apr 20 21:32:31 TheHub kernel: JMicron IDE 0000:04:00.1: enabling device (0000 -> 0001) Apr 20 21:32:31 TheHub kernel: JMicron IDE 0000:04:00.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19 Apr 20 21:32:31 TheHub kernel: jmicron 0000:04:00.1: 100%% native mode on irq 19 Apr 20 21:32:31 TheHub kernel: mvsas 0000:02:00.0: mvsas: driver version 0.8.4 Apr 20 21:32:31 TheHub kernel: mvsas 0000:02:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 Apr 20 21:32:31 TheHub kernel: mvsas 0000:02:00.0: setting latency timer to 64 Apr 20 21:32:31 TheHub kernel: /usr/src/sas/trunk/mvsas_tgt/mv_spi.c 124:identify failed Apr 20 21:32:31 TheHub kernel: /usr/src/sas/trunk/mvsas_tgt/mv_spi.c 491:Init flash rom ok,flash type is 0x103. and Apr 20 21:32:31 TheHub kernel: ahci 0000:04:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 Apr 20 21:32:31 TheHub kernel: ahci 0000:04:00.0: JMB361 has only one port, port_map 0x3 -> 0x1 Apr 20 21:32:31 TheHub kernel: ahci 0000:04:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps 0x1 impl SATA mode I believe (just based on observations here) that 0x103 is indicator for the Supermicro SASLP firmware 21N. You sure that you downgraded this one. 2. The two IDE hard drives are reported with HPA and I believe HPA was no go for Unraid 4.7 Apr 20 21:32:31 TheHub kernel: hda: Host Protected Area detected. Apr 20 21:32:31 TheHub kernel: ^Icurrent capacity is 312579695 sectors (160040 MB) Apr 20 21:32:31 TheHub kernel: ^Inative capacity is 312581808 sectors (160041 MB) Apr 20 21:32:31 TheHub kernel: hdb: Host Protected Area detected. Apr 20 21:32:31 TheHub kernel: ^Icurrent capacity is 586112591 sectors (300089 MB) Apr 20 21:32:31 TheHub kernel: ^Inative capacity is 586114704 sectors (300090 MB) You should upgrade to the latest BIOS, load the "default" configuration, then change the onboard SATA to SATA2 and AHCI mode and disable any hardware feature on your motherboard that you are not going to use - serial and par. ports, audio, firewire, floppy drive controller, etc. If needed disable even the USB3 (some of the negative reviews on Newegg are in relation to USB3 and ASPI). Do not forget to run a single pass with Memtest to be sure that the new BIOS "likes" the memory or you will have to set them manually. And perhaps you have to fix the HPA too.
April 22, 201115 yr If you see any that say "MBR undefined" follow the instructions in the announcement thread to dump the contents of the MBR for analysis. I think Joe meant to say "MBR unknown", not "MBR undefined".
April 22, 201115 yr Author That was my next plan. Just wanted to be 100% sure I shouldn't have to worry about data loss. 5.0beta6a will not automatically start the array. It will tell you if it recognizes the disks. If you see any that say "MBR undefined" follow the instructions in the announcement thread to dump the contents of the MBR for analysis. You'll not lose data unless you format the drives. An un-recognized partition is easily fixed. Do NOT start the array if there are disks with data that say MBR unknown. Any HPA issue will need to be resolved before you can move to 5.0beta6a, but no matter what, you'll be able to see if the disks show up in the list of potential disks and if the disk controller ports are recognized. Before doing anything, make a screen shot of your existing disk configuration and also make a copy of your current "config" folder after first stopping your array so you can restore to it if you revert back to 4.7. Instead of overwriting the existing bzroot and bzimage file with the 5.X versions, re-name them to bzroot.47 and bzimage.47. That way reverting is as simple as naming them back their original names and rebooting. Joe L. Thanks a lot. I extremely appreciate your post! I'm going to try to make sure I have the latest revision of the BIOS before I take this next step.
April 22, 201115 yr Author 1. It is a BIOS issue / settings in your current configuration (there are three new BIOS releases in the last month) - what is your BIOS revision right now. 1/4 of the Newegg reviewers rate this board with 3 or less stars - so you are not alone. All the drives/controllers are visible in Unraid but with your current settings the onboard SATA3 ports share IRQ with the IDE controller that you are using and the SM card shares IRQ with the onboard eSATA jMicron controller. Apr 20 21:32:31 TheHub kernel: ahci 0000:00:11.0: version 3.0 Apr 20 21:32:31 TheHub kernel: ahci 0000:00:11.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 Apr 20 21:32:31 TheHub kernel: ahci 0000:00:11.0: irq 29 for MSI/MSI-X Apr 20 21:32:31 TheHub kernel: ahci 0000:00:11.0: AHCI 0001.0200 32 slots 6 ports 6 Gbps 0x3f impl SATA mode and Apr 20 21:32:31 TheHub kernel: jmicron 0000:04:00.1: IDE controller (0x197b:0x2361 rev 0x02) Apr 20 21:32:31 TheHub kernel: JMicron IDE 0000:04:00.1: enabling device (0000 -> 0001) Apr 20 21:32:31 TheHub kernel: JMicron IDE 0000:04:00.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19 Apr 20 21:32:31 TheHub kernel: jmicron 0000:04:00.1: 100%% native mode on irq 19 Apr 20 21:32:31 TheHub kernel: mvsas 0000:02:00.0: mvsas: driver version 0.8.4 Apr 20 21:32:31 TheHub kernel: mvsas 0000:02:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 Apr 20 21:32:31 TheHub kernel: mvsas 0000:02:00.0: setting latency timer to 64 Apr 20 21:32:31 TheHub kernel: /usr/src/sas/trunk/mvsas_tgt/mv_spi.c 124:identify failed Apr 20 21:32:31 TheHub kernel: /usr/src/sas/trunk/mvsas_tgt/mv_spi.c 491:Init flash rom ok,flash type is 0x103. and Apr 20 21:32:31 TheHub kernel: ahci 0000:04:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 Apr 20 21:32:31 TheHub kernel: ahci 0000:04:00.0: JMB361 has only one port, port_map 0x3 -> 0x1 Apr 20 21:32:31 TheHub kernel: ahci 0000:04:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps 0x1 impl SATA mode I believe (just based on observations here) that 0x103 is indicator for the Supermicro SASLP firmware 21N. You sure that you downgraded this one. 2. The two IDE hard drives are reported with HPA and I believe HPA was no go for Unraid 4.7 Apr 20 21:32:31 TheHub kernel: hda: Host Protected Area detected. Apr 20 21:32:31 TheHub kernel: ^Icurrent capacity is 312579695 sectors (160040 MB) Apr 20 21:32:31 TheHub kernel: ^Inative capacity is 312581808 sectors (160041 MB) Apr 20 21:32:31 TheHub kernel: hdb: Host Protected Area detected. Apr 20 21:32:31 TheHub kernel: ^Icurrent capacity is 586112591 sectors (300089 MB) Apr 20 21:32:31 TheHub kernel: ^Inative capacity is 586114704 sectors (300090 MB) You should upgrade to the latest BIOS, load the "default" configuration, then change the onboard SATA to SATA2 and AHCI mode and disable any hardware feature on your motherboard that you are not going to use - serial and par. ports, audio, firewire, floppy drive controller, etc. If needed disable even the USB3 (some of the negative reviews on Newegg are in relation to USB3 and ASPI). Do not forget to run a single pass with Memtest to be sure that the new BIOS "likes" the memory or you will have to set them manually. And perhaps you have to fix the HPA too. MANY thanks! I see what you mean that the IRQ is being occupied by two devices. The only thing that makes me wonder is why was ubuntu able to detect the internal SATA drives? I'm going to load the latest BIOS as soon as I get home and I'll disable pretty much everything not required by my setup. I'll post results later tonight.
April 22, 201115 yr Author I just updated my bios to the latest version from ASUS's site. It no longer detects the MOBO SATA drives in the BIOS, but detects the ports. Their is still an IRQ conflict after I looked through the syslog. It looks as if 18 and 19 are both occupied by two devices each. As far as I know I have downgraded the Micro card to .15n as it says thats the version when it POSTs. Going to do a little more digging to see if I can get anything to work correctly. Edit: My first step was to boot with the Micro card without any drives attached and looks like it worked. Booted for the first time with the Micro card in with no errors. I uploaded the working systems syslog for comparisson with the other syslog. syslog.txt
Archived
This topic is now archived and is closed to further replies.