November 8, 201015 yr Hello, I've installed unRAID 3.5.6 on Slackware 13.1 on my system disc. Everything works fine, as long as the discs are connected to the onboard SATA Controller. All Discs connected the the SASLP-MV8 Controller are unrecognized by unRAID. The Discs are correct recognized by the operating system and can be formated, written etc... May I missed a kernel module or somthing else? lspci tells me 00:00.0 Host bridge: ATI Technologies Inc RS690 Host Bridge 00:01.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (Internal gfx) 00:02.0 PCI bridge: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI Express Graphics Port 0) 00:04.0 PCI bridge: ATI Technologies Inc Device 7914 00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA 00:13.0 USB Controller: ATI Technologies Inc SB600 USB (OHCI0) 00:13.1 USB Controller: ATI Technologies Inc SB600 USB (OHCI1) 00:13.2 USB Controller: ATI Technologies Inc SB600 USB (OHCI2) 00:13.3 USB Controller: ATI Technologies Inc SB600 USB (OHCI3) 00:13.4 USB Controller: ATI Technologies Inc SB600 USB (OHCI4) 00:13.5 USB Controller: ATI Technologies Inc SB600 USB Controller (EHCI) 00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 14) 00:14.1 IDE interface: ATI Technologies Inc SB600 IDE 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) 00:14.3 ISA bridge: ATI Technologies Inc SB600 PCI to LPC Bridge 00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:05.0 VGA compatible controller: ATI Technologies Inc RS690 [Radeon X1200 Series] 01:05.2 Audio device: ATI Technologies Inc Radeon X1200 Series Audio Controller 02:00.0 SCSI storage controller: Marvell Technology Group Ltd. MV64460/64461/64462 System Controller, Revision B (rev 01) 03:00.0 SCSI storage controller: Marvell Technology Group Ltd. MV64460/64461/64462 System Controller, Revision B (rev 01) 04:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link) 04:0f.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit Ethernet (rev 10) lsmod tells me Module Size Used by vboxnetadp 4922 0 vboxnetflt 11982 0 md_mod 39008 0 vboxdrv 126175 2 vboxnetadp,vboxnetflt xor 12605 1 md_mod mvsas 31650 0 i2c_piix4 6816 0 sg 16605 0 r8169 26572 0 mii 2658 1 r8169 k8temp 2303 0 i2c_core 11518 1 i2c_piix4 hwmon 941 1 k8temp /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: WDC WD20EARS-00M Rev: 51.0 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi1 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: SAMSUNG HD103UJ Rev: 1AA0 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi4 Channel: 00 Id: 00 Lun: 00 Vendor: Kingston Model: DataTraveler 2.0 Rev: PMAP Type: Direct-Access ANSI SCSI revision: 00 Host: scsi5 Channel: 00 Id: 00 Lun: 00 Vendor: HL-DT-ST Model: DVDRAM GSA-E10N Rev: JE07 Type: CD-ROM ANSI SCSI revision: 00 Host: scsi6 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: WDC WD800JD-00JN Rev: 05.0 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi7 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: FUJITSU MHT2040B Rev: 0000 Type: Direct-Access ANSI SCSI revision: 05 When I boot unRAID from USB Stick all discs are recognized correct. config.txt
November 8, 201015 yr Did you install the addon kernel modules for the controller card? unRAID uses the following for support -- http://scst.sourceforge.net/. The MVSAS is the module of concern. In the base unRAID 4.5.6 the addon modules are under /lib/modules/2.6.32.9-unRAID/extra. There might be something in particular that emhttp is looking for that the built-in Linux kernel modules don't do or do differently than the SCST ones.
November 8, 201015 yr Author I used the mvsas kernel module built with vanilla kernel without the scst patch. scst compiles and loads fine but the "special" mvsas won't compile yet. I'll tale a look at this tomorrow, hopefully it'll work Thank you for your help, again!
November 9, 201015 yr Author OK, now I tried a clean 2.6.33 Source, patched it with scst_exec_req_fifo-2.6.33.patch of the latest scst trunk. Copied original .config file from unRAID -> make oldconfig -> make menuconfig Changed only to compile my SATA driver an EXT4 FS to compile not as module. -> make -> make modules -> make modules_install -> make install -> reboot everything fine, so far... In SCST Trunk -> make scst -> make scst_install -> modprobe scst dmesg output [2192]: scst: sysfs_work_thread_fn:364:User interface thread started, PID 2192 [2190]: scst: scst_register_device:918:Attached to scsi0, channel 0, id 0, lun 0, type 0 [2190]: scst: scst_register_device:918:Attached to scsi1, channel 0, id 0, lun 0, type 0 [2190]: scst: scst_register_device:918:Attached to scsi4, channel 0, id 0, lun 0, type 0 [2190]: scst: scst_register_device:918:Attached to scsi5, channel 0, id 0, lun 0, type 5 [2194]: scst: scst_cmd_thread:4154:Processing thread scstd0 (PID 2194) started [2195]: scst: scst_cmd_thread:4154:Processing thread scstd1 (PID 2195) started [2196]: scst: scst_init_thread:3909:Init thread started, PID 2196 [2197]: scst: scst_tm_thread:5659:Task management thread started, PID 2197 [2190]: scst: init_scst:2334:SCST version 2.1.0-pre1 loaded successfully (max mem for commands 219MB, per device 87MB) [2190]: scst: scst_print_config:2129:Enabled features: EXTRACHECKS, DEBUG [2198]: scst: scst_global_mgmt_thread:6435:Management thread started, PID 2198 The 4 discs are connected to my internal sata controller. -> make mvsas cd mvsas_tgt && make all make[1]: Entering directory `/usr/src/trunk/mvsas_tgt' make -C /lib/modules/2.6.33.4-unRAID/build SUBDIRS=/usr/src/trunk/mvsas_tgt BUILD_INI=m make[2]: Entering directory `/usr/src/linux-2.6.33.4-unRAID' CC [M] /usr/src/trunk/mvsas_tgt/mv_sas.o /usr/src/trunk/mvsas_tgt/mv_sas.c: In function 'mvs_slave_configure': /usr/src/trunk/mvsas_tgt/mv_sas.c:423: error: too few arguments to function 'sas_change_queue_depth' make[3]: *** [/usr/src/trunk/mvsas_tgt/mv_sas.o] Error 1 make[2]: *** [_module_/usr/src/trunk/mvsas_tgt] Error 2 make[2]: Leaving directory `/usr/src/linux-2.6.33.4-unRAID' make[1]: *** [all] Error 2 make[1]: Leaving directory `/usr/src/trunk/mvsas_tgt' make: *** [mvsas] Error 2 Any ideas how to compile the mvsas module?
November 10, 201015 yr Author I figured out that libsas change_queue_depth API call has changed in 2.6.33 since when mvsas was written ... Now I tried 2.6.32 and everything compiles fine. scst and mvsas modules are loaded while systemboot, disks are recognized by linux. But unRAID still won't recognize them...
December 10, 201015 yr I figured out that libsas change_queue_depth API call has changed in 2.6.33 since when mvsas was written ... Now I tried 2.6.32 and everything compiles fine. scst and mvsas modules are loaded while systemboot, disks are recognized by linux. But unRAID still won't recognize them... Any progress brun0? I've got a SASLP-MV8 and I can't see the disks attached to it. I have done the same on a fresh slackware 13.1 build running a 2.6.32 kernel. I've applied the patch scst_exec_req_fifo-2.6.32.patch and have compiled both SCST and MVSAS separately from http://scst.sourceforge.net. I can modprobe the SCST but not the MVSAS module as it says resource already busy - I'm assuming because I probably built in support via the kernel. Any suggestions?
December 10, 201015 yr Author I was not able to get the discs recognized by unRAID with my own kernel. I installed Slackware 12.2, used the unRAID original Kernel an built my own initrd system. Ok, it's dirty, but works great so far
Archived
This topic is now archived and is closed to further replies.