February 3, 20179 yr Have i overlooked something in the instructions because my cache drive which is on the raid card doesn't auto mount when server restarts. I have to stop the array, add the cache drive and start the array. All works normal after manually mounting the drive.
February 3, 20179 yr Have i overlooked something in the instructions because my cache drive which is on the raid card doesn't auto mount when server restarts. I have to stop the array, add the cache drive and start the array. All works normal after manually mounting the drive. Try using another web browser when adding the cache drive next time.
February 4, 20179 yr Have i overlooked something in the instructions because my cache drive which is on the raid card doesn't auto mount when server restarts. I have to stop the array, add the cache drive and start the array. All works normal after manually mounting the drive. Try using another web browser when adding the cache drive next time. Thanks for the suggestion. I tried chrome,firefox,edge i have also moved from Unraid 6.3.0rc9 to final stable 6.3.0. No automount for the cache drive. My unassigned device for my VM which is mounted from Unassigned Devices plugin (which is also on the raid controller) does mount when booting.
February 4, 20179 yr Have i overlooked something in the instructions because my cache drive which is on the raid card doesn't auto mount when server restarts. I have to stop the array, add the cache drive and start the array. All works normal after manually mounting the drive. Try using another web browser when adding the cache drive next time. Thanks for the suggestion. I tried chrome,firefox,edge i have also moved from Unraid 6.3.0rc9 to final stable 6.3.0. No automount for the cache drive. My unassigned device for my VM which is mounted from Unassigned Devices plugin (which is also on the raid controller) does mount when booting. Why not provide your diagnostics so others can take a look? Need help? Read me first!
February 4, 20179 yr I have to work today,Bosses can be sooo unreasonable sometimes perhaps someone else can take a look? Probably this line in the log 13:06:16 superserver emhttp: Warning: preg_grep() expects parameter 2 to be array, boolean given in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 112 It would be wise to check for plugin updates to UD, and post in the UD thread.
February 5, 20179 yr Cheers guys It wasn't mounting before I installed UD. I use that for VM disk only. I have only a few dockers on there so I will try and diagnose the issue. I will use the mobo SATA port see if it works there like it always has before I added the hba card. I will create a new thread, I clogged this one enough
May 23, 20179 yr I have an ASMedia ASM1061 (Syba SY-PEX40039) that isn't being recognized. Everything I'm reading says that I shouldn't need to do this patch. Any advice? I have the card plugging into a Supermicro X9SCM-F motherboard. I've tried it in the three of the four PCI-E slots. Nothing appears to work. I can't tell if the card isn't even being recognized by the computer or if it's an unRAID thing.
May 23, 20179 yr I have try ASM1061 before, just plug and work. Not sure require or not, I have enable BIOS mainboard AHCI function even no any SATA connect to mainboard. ASM1061 work stable and cool Edited May 23, 20179 yr by Benson
May 23, 20179 yr I have an ASMedia ASM1061 (Syba SY-PEX40039) that isn't being recognized. Everything I'm reading says that I shouldn't need to do this patch. Any advice? I have the card plugging into a Supermicro X9SCM-F motherboard. I've tried it in the three of the four PCI-E slots. Nothing appears to work. I can't tell if the card isn't even being recognized by the computer or if it's an unRAID thing.It should work, probably a bad controller.
May 23, 20179 yr 11 minutes ago, johnnie.black said: It should work, probably a bad controller. May be. Suggest OP check if mainboard BIOS "Interrupt 19 caputre" enable and add-on card BIOS show or not. Usually, I will disable it, this can reduce the boot time.
May 23, 20179 yr I have a STARTECH ASMedia ASM1061 on Supermicro X9SCM-F and it worked right away. I also have it on some HP Micro Severs and it worked with unRAID as well.
June 25, 20179 yr Sorry to resurrect an old thread, but I'm having an issues with my HPT Rocket 62x loading both IDE and SATA drivers after upgrading to V6 using this script. Anyone have any ideas for a fix? I'm about to order a new SATA card, but I thought I'd ask here first. Thanks - details in my previous thread.
August 26, 20178 yr On 01/05/2012 at 1:20 PM, elkay14 said: The attached script will enable a number of AHCI-based SATA controllers without having to recompile the kernel. The following PCI IDs are supported: # 1b4b0640 : Marvell 88SE9128 on HPT RocketRAID 640 # 1b4b9120 : Marvell 88SE9128 found on Rocket 620A (possibly others) # 1b4b9123 : Marvell 88SE9128 found on motherboards and HBAs # 1b4b9125 : Marvell 88SE9125 found on HPT Rocket 62X # 1b4b9172 : Marvell 88SE9172 found on motherboards # 1b4b917a : Marvell 88SE9172 found on motherboards # 1b4b9192 : Marvell 88SE9172 found on motherboards # 1b4b91a3 : Marvell 88SE9128 found on motherboards # 11030620 : HPT RocketRAID 620 # 11030622 : HPT RocketRAID 622 # 11030640 : Marvell 88SE9128 on HPT RocketRAID 640 # 11030641 : HPT RocketRAID 640L # 11030645 : HPT RocketRAID 644L # 1b210612 : ASMedia ASM1061 (Syba SY-PEX40039) If you come across an AHCI adapter that is not listed, send me a PM and I'll add it to the script. To use this, store it on your flash drive (I put it in /boot/config) and add it to your go script before emhttp is started. Then REBOOT. Sample go script excerpt: /boot/config/enable_ahci.sh # Start the Management Utility /usr/local/sbin/emhttp & This script will work on any recent version of unRAID (4.7 and later) and possibly older versions (untested) enable_ahci.zip I'm not sure what i missed and this is a fairly old thread but i cant seem to get my raidrocket 620 to work with unraid. my log shows Aug 26 16:20:48 Tower kernel: ata15: softreset failed (1st FIS failed) Aug 26 16:20:48 Tower kernel: DMAR: DRHD: handling fault status reg 2 Aug 26 16:20:48 Tower kernel: DMAR: [DMA Write] Request device [01:00.1] fault addr 459d60000 [fault reason 05] PTE Write access is not set Aug 26 16:20:48 Tower kernel: DMAR: DRHD: handling fault status reg 2 Aug 26 16:20:48 Tower kernel: DMAR: [DMA Read] Request device [01:00.1] fault addr 459d60000 [fault reason 06] PTE Read access is not set Aug 26 16:20:58 Tower kernel: ata15: softreset failed (1st FIS failed) Aug 26 16:20:58 Tower kernel: DMAR: DRHD: handling fault status reg 2 Aug 26 16:20:58 Tower kernel: DMAR: [DMA Write] Request device [01:00.1] fault addr 459d60000 [fault reason 05] PTE Write access is not set Aug 26 16:20:58 Tower kernel: DMAR: DRHD: handling fault status reg 2 Aug 26 16:20:58 Tower kernel: DMAR: [DMA Read] Request device [01:00.1] fault addr 459d60000 [fault reason 06] PTE Read access is not set Aug 26 16:21:33 Tower kernel: ata15: softreset failed (1st FIS failed) Aug 26 16:21:33 Tower kernel: ata15: limiting SATA link speed to 3.0 Gbps Aug 26 16:21:33 Tower kernel: DMAR: DRHD: handling fault status reg 2 Aug 26 16:21:33 Tower kernel: DMAR: [DMA Write] Request device [01:00.1] fault addr 459d60000 [fault reason 05] PTE Write access is not set Aug 26 16:21:33 Tower kernel: DMAR: DRHD: handling fault status reg 2 Aug 26 16:21:33 Tower kernel: DMAR: [DMA Read] Request device [01:00.1] fault addr 459d60000 [fault reason 06] PTE Read access is not set Aug 26 16:21:38 Tower kernel: ata15: softreset failed (1st FIS failed) Aug 26 16:21:38 Tower kernel: ata15: reset failed, giving up Aug 26 16:20:58 Tower kernel: DMAR: DRHD: handling fault status reg 2 Aug 26 16:20:58 Tower kernel: DMAR: [DMA Read] Request device [01:00.1] fault addr 459d60000 [fault reason 06] PTE Read access is not set Aug 26 16:21:33 Tower kernel: ata15: softreset failed (1st FIS failed) Aug 26 16:21:33 Tower kernel: ata15: limiting SATA link speed to 3.0 Gbps Aug 26 16:21:33 Tower kernel: DMAR: DRHD: handling fault status reg 2 Aug 26 16:21:33 Tower kernel: DMAR: [DMA Write] Request device [01:00.1] fault addr 459d60000 [fault reason 05] PTE Write access is not set Aug 26 16:21:33 Tower kernel: DMAR: DRHD: handling fault status reg 2 Aug 26 16:21:33 Tower kernel: DMAR: [DMA Read] Request device [01:00.1] fault addr 459d60000 [fault reason 06] PTE Read access is not set Aug 26 16:21:38 Tower kernel: ata15: softreset failed (1st FIS failed) Aug 26 16:21:38 Tower kernel: ata15: reset failed, giving up Aug 26 16:24:48 Tower sshd[5139]: Accepted none for root from 10.1.1.14 port 51364 ssh2 Aug 26 16:26:46 Tower emhttp: shcmd (24): rmmod md-mod |& logger Aug 26 16:26:46 Tower kernel: md: unRAID driver removed What I have done so far: I downloaded your script which shows my rocketraid in the list. I added the script to the go file ~# cat /boot/config/go #!/bin/bash # Enable AHCI Mode for e.g. RocketRAID 620 /boot/config/enable_ahci.sh # Start the Management Utility /usr/local/sbin/emhttp & Checking to see if unraid has picked up my devices (I have 2 cards): ~# lspci -nn |grep Rocket 01:00.0 RAID bus controller [0104]: HighPoint Technologies, Inc. RocketRAID 620 2 Port SATA-III Controller [1103:0620] (rev 01) 03:00.0 RAID bus controller [0104]: HighPoint Technologies, Inc. RocketRAID 620 2 Port SATA-III Controller [1103:0620] (rev 01) Both Cards have been tested individually. Both cards work fine and are picked up by windows. I have changed sata cables, different hdd's and i end up with the same error. I feel like its something simple, and right in front of me but im just not winning here. Edited August 26, 20178 yr by Ahmed
August 26, 20178 yr 33 minutes ago, Ahmed said: I feel like its something simple, and right in front of me but im just not winning here. Probably related to this:
August 26, 20178 yr 4 hours ago, johnnie.black said: Probably related to this: Thanks for pointing me to that @johnnie.black but upon trying the suggestion there, it still does not appear to pickup my HDD's. I stopped using that script as it just continued to give me that same error in the logs. I added the "iommu=pt" in the syslinux.cfg and also disabled VT in bios. # cat syslinux.cfg default /syslinux/menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append iommu=pt initrd=/bzroot label unRAID OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui label unRAID OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label unRAID OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest # lspci -k |grep Rocket 01:00.0 RAID bus controller: HighPoint Technologies, Inc. RocketRAID 620 2 Port SATA-III Controller (rev 01) Subsystem: HighPoint Technologies, Inc. RocketRAID 620 2 Port SATA-III Controller 03:00.0 RAID bus controller: HighPoint Technologies, Inc. RocketRAID 620 2 Port SATA-III Controller (rev 01) Subsystem: HighPoint Technologies, Inc. RocketRAID 620 2 Port SATA-III Controller If I understood correctly (from all of what I have read so far), it also appears that the patch was applied some time ago so im not sure adding the iommu=pt is actually making any difference at this stage as i am using Unraid 6.3.5. Just find it odd that the system can see the correct information regarding the cards i have installed, but i cant see the disk/s attached.
August 26, 20178 yr 1 minute ago, Ahmed said: If I understood correctly (from all of what I have read so far), it also appears that the patch was applied some time ago so im not sure adding the iommu=pt is actually making any difference at this stage as i am using Unraid 6.3.5. If it's the Marvell issue disabling VT-d is the only fix to always work, iommu=pt doesn't always work, post your diagnostics with VT-d disable.
August 26, 20178 yr 1 hour ago, johnnie.black said: If it's the Marvell issue disabling VT-d is the only fix to always work, iommu=pt doesn't always work, post your diagnostics with VT-d disable. Here is my diagnostics files. thanks for helping look into this. Edited August 26, 20178 yr by Ahmed
August 26, 20178 yr Just now, Ahmed said: Here is my diagnostics files. thanks for helping look into this. tower-diagnostics-20170826-2225.zip VT-d is still enable.
August 26, 20178 yr 26 minutes ago, johnnie.black said: VT-d is still enable. Yes, sorry I had turned it back on. Its off now. Edited August 26, 20178 yr by Ahmed
August 26, 20178 yr 3 minutes ago, Ahmed said: Yes, sorry I had turned it back on. Its off now. tower-diagnostics-20170826-2303.zip Controller is loading a PATA driver, instead of AHCI, best bet it to get a different controller, LSI are recommended. 01:00.1 IDE interface [0101]: Marvell Technology Group Ltd. 88SE912x IDE Controller [1b4b:91a4] (rev 11) Subsystem: Marvell Technology Group Ltd. 88SE912x IDE Controller [1b4b:91a4] Kernel driver in use: pata_marvell Kernel modules: pata_marvell
August 26, 20178 yr 12 minutes ago, johnnie.black said: Controller is loading a PATA driver, instead of AHCI, best bet it to get a different controller, LSI are recommended. 01:00.1 IDE interface [0101]: Marvell Technology Group Ltd. 88SE912x IDE Controller [1b4b:91a4] (rev 11) Subsystem: Marvell Technology Group Ltd. 88SE912x IDE Controller [1b4b:91a4] Kernel driver in use: pata_marvell Kernel modules: pata_marvell OMG Thanks - that actually helps and makes sense (well sort of). So i had 3 sata controllers 2x AHCI 01:00.0 RAID bus controller: HighPoint Technologies, Inc. RocketRAID 620 2 Port SATA-III Controller (rev 01) Subsystem: HighPoint Technologies, Inc. RocketRAID 620 2 Port SATA-III Controller 03:00.0 RAID bus controller: HighPoint Technologies, Inc. RocketRAID 620 2 Port SATA-III Controller (rev 01) Subsystem: HighPoint Technologies, Inc. RocketRAID 620 2 Port SATA-III Controller and 1 IDE/PATA 05:00.0 RAID bus controller: VIA Technologies, Inc. VT6421 IDE/SATA Controller (rev 50) Subsystem: VIA Technologies, Inc. VT6421 IDE/SATA Controller So when i was enabling the script and got them errors in the log, i guess there was a conflict on who it was trying to bring up and how. Now that i have removed it, its working and i can see both cards as well as the disk's connected to them. Cheers for your help bud!
August 26, 20178 yr 4 minutes ago, Ahmed said: So when i was enabling the script and got them errors in the log, i guess there was a conflict on who it was trying to bring up and how. Now that i have removed it, its working and i can see both cards as well as the disk's connected to them. I assumed you had already removed the script, it's only needed for unRAID v5, but glad it's working now, don't forget you can't enable VT-d
August 26, 20178 yr 1 minute ago, johnnie.black said: I assumed you had already removed the script, it's only needed for unRAID v5, but glad it's working now, don't forget you can't enable VT-d Sorry, I meant i removed the old: VT6421 IDE/SATA PCI Controller. After removing it (with VT-d disabled) i still couldn't see the drives but was watching the logs and noticed that it was still trying to load the IDE drivers. I re-enabled the script which is supposed to start the AHCI driver and then restarted. BOOM it now sees the disk coming out of both Rocketraid controllers. I also left VT-d disabled but removed the "iommu=pt" from the /boot/syslinux/syslinux.cfg file and its working fine. Shame VT-d had to be disabled but at least it will give me time to sort out a new card as you suggested. So at this point, the script still appears to be relevant in some cases. Thanks again for your help, This little project has been fun so far aside a few small hiccups here n there.
Archived
This topic is now archived and is closed to further replies.