ketiljo

Anyone? Can you write anything to the flash drive? Yes, everything else works but this.

Anyone?

Thanks for the great work! I get this error when trying to install the plugin: plugin: installing: http://unraid.zeron.ca/plugins/open-vm-tools/openVMTools.plg plugin: downloading http://unraid.zeron.ca/plugins/open-vm-tools/openVMTools.plg plugin: downloading: http://unraid.zeron.ca/plugins/open-vm-tools/openVMTools.plg ... done Warning: simplexml_load_file(): I/O warning : failed to load external entity "/boot/config/plugins/openVMTools.plg" in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 plugin: xml parse error What causes this?

An update: I tried it again, and it only fails loading the SAS driver with 6.2 after a power down of the VM. Just rebooting (before power down) is fine. This is what it sais: mpt2sas_cm0: failure at drivers/scsi/mpt3sas/mptsas_scsih.c:8592/_scsih_probe() According to http://www.spinics.net/lists/linux-scsi/msg95377.html it's a bug in linux kernel 4.4.19. EDIT: Found a fix here https://lime-technology.com/forum/index.php?topic=49481.0

I've encountered a strange issue. I upgraded from 6.1.9 a couple of days ago. Rebooted, no issues. I'm running Unraid as a VM in ESXI 5.1 with a BR10i SAS card in pass through. All (sata) drives in the array are connected to the BR10i. I had to power down the server today and when I powered it up, Unraid didn't start the array. None of the drives was anywhere to be seen. So I rebooted Unraid again, and there's a message during boot saying that the SAS driver can't be loaded. I can't remember exactly what it said but obviously, the SAS card isn't working. Pretty strange since it has been working just fine for a few days. I downgraded to 6.2.9 again and the SAS driver loads as it should. What can cause this?

Hi Have anyone tried Kingston KVR13E9/8HM 8GB modules on the X9SCM yet? If they work, the price seems to come down to reasonable levels. http://www.newegg.com/Product/Product.aspx?Item=N82E16820239135 cheers, Ketil

I'm using Pfsense on an old pc with two network cards. It's a freeBSD distro and very easy to setup and use. I started looking for an alternative to the router I got with the fiber line. So the fiber modem is set in bridge mode and pfsense handles routing and firewalling. Much better and more features than the fiber modem. Ketil

I know, but it's slower. Probably more than fast enough, but still.

Thanks for the answers so far. The on-board LAN controller seems to be working ok with 5beta12. I have a Intel PRO/1000 PCI card I'll try instead and disable the on-board LAN, at least until 5.0 final is ready. I've been looking around to see if the PCI-E 16x slot that is connected directly to the CPU can be used for non-graphic cards. I currently have the BR10i card in that slot, and it seems to be ok. The other 16x slot will only run in 4x mode so I can't use that. 14 sata ports (8+6) should be ok for while I guess. Have disabled everything in BIOS that's not needed. I still have to manually start the array after a clean power down. Slightly annoying.

It's already set to yes, so it's not that. Seems like a loose connection somewhere then. I'll have to look into that.

Hi I finished my unraid server some days ago and I'm migrating data from the old server. This is my hardware setup: Motherboard: ASUS 8PH67-V CPU: Intel G620 RAM: 2x2GB SATA controller: IBM BR10i (LSI SAS 1068E) in the PCIe x16. Flashed with IT firmware as in http://lime-technology.com/forum/index.php?topic=12767.0 unRaid 5.0-beta 12 Here's a mymain screenshot: Disk2 and disk4 has some reallocated sectors, but I guess that's ok as long as it doesn't increase. Parity, disk1, 2 and 3 is connected to the motherboard SATA connectors and disk4 hangs on port0 on the BR10i card. For some reason, mymain won't display SMART info for disk4. In a telnet window, I get this: root@Tower:~# smartctl -a -d ata /dev/sdf smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. terminate called after throwing an instance of 'int' Aborted root@Tower:~# smartctl -A /dev/sdf smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 119 099 006 Pre-fail Always - 231116623 3 Spin_Up_Time 0x0003 095 095 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 48 5 Reallocated_Sector_Ct 0x0033 098 098 036 Pre-fail Always - 84 7 Seek_Error_Rate 0x000f 076 060 030 Pre-fail Always - 45427125 9 Power_On_Hours 0x0032 081 081 000 Old_age Always - 16992 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 43 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 078 078 000 Old_age Always - 22 190 Airflow_Temperature_Cel 0x0022 072 051 045 Old_age Always - 28 (Min/Max 19/28) 194 Temperature_Celsius 0x0022 028 049 000 Old_age Always - 28 (0 12 0 0) 195 Hardware_ECC_Recovered 0x001a 046 015 000 Old_age Always - 231116623 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 156031866913371 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 1989695539 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 2899967634 root@Tower:~# So some SMART info can be shown for disk4, but not the way mymain does it. How can I fix this? The normal device status window (at port 80) shows temp for all disks, but mymenu won't for disk4. EDIT: Fixed this with the info in this thread: http://lime-technology.com/forum/index.php?topic=9337.msg141761#msg141761 Now, the syslog (attached) shows some errors around 21:00. What are these and do I have to be worried? Any other issues I have to look out for? EDIT: Here's the errors: Sep 13 20:59:28 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen (Errors) Sep 13 20:59:28 Tower kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors) Sep 13 20:59:28 Tower kernel: ata1: SError: { UnrecovData Handshk } (Errors) Sep 13 20:59:28 Tower kernel: ata1.00: failed command: WRITE DMA EXT (Minor Issues) Sep 13 20:59:28 Tower kernel: ata1.00: cmd 35/00:00:e0:53:d3/00:04:03:00:00/e0 tag 0 dma 524288 out (Drive related) Sep 13 20:59:28 Tower kernel: res 50/00:00:5f:53:d3/00:00:03:00:00/e0 Emask 0x10 (ATA bus error) (Errors) Sep 13 20:59:28 Tower kernel: ata1.00: status: { DRDY } (Drive related) Sep 13 20:59:28 Tower kernel: ata1: hard resetting link (Minor Issues) Sep 13 20:59:28 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) (Drive related) Sep 13 20:59:28 Tower kernel: ata1.00: configured for UDMA/133 (Drive related) Sep 13 20:59:28 Tower kernel: ata1: EH complete (Drive related) Sep 13 20:59:58 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen (Errors) Sep 13 20:59:58 Tower kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors) Sep 13 20:59:58 Tower kernel: ata1: SError: { UnrecovData Handshk } (Errors) Sep 13 20:59:58 Tower kernel: ata1.00: failed command: WRITE DMA EXT (Minor Issues) Sep 13 20:59:58 Tower kernel: ata1.00: cmd 35/00:60:88:05:e5/00:02:03:00:00/e0 tag 0 dma 311296 out (Drive related) Sep 13 20:59:58 Tower kernel: res 50/00:00:87:05:e5/00:00:03:00:00/e0 Emask 0x10 (ATA bus error) (Errors) Sep 13 20:59:58 Tower kernel: ata1.00: status: { DRDY } (Drive related) Sep 13 20:59:58 Tower kernel: ata1: hard resetting link (Minor Issues) Sep 13 20:59:58 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) (Drive related) Sep 13 20:59:58 Tower kernel: ata1.00: configured for UDMA/133 (Drive related) Sep 13 20:59:58 Tower kernel: ata1: EH complete (Drive related) Sep 13 21:00:02 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen (Errors) Sep 13 21:00:02 Tower kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors) Sep 13 21:00:02 Tower kernel: ata1: SError: { UnrecovData Handshk } (Errors) Sep 13 21:00:02 Tower kernel: ata1.00: failed command: WRITE DMA EXT (Minor Issues) Sep 13 21:00:02 Tower kernel: ata1.00: cmd 35/00:80:88:c4:e7/00:02:03:00:00/e0 tag 0 dma 327680 out (Drive related) Sep 13 21:00:02 Tower kernel: res 50/00:00:07:c4:e7/00:00:03:00:00/e3 Emask 0x10 (ATA bus error) (Errors) Sep 13 21:00:02 Tower kernel: ata1.00: status: { DRDY } (Drive related) Sep 13 21:00:02 Tower kernel: ata1: hard resetting link (Minor Issues) Sep 13 21:00:02 Tower kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) (Drive related) Sep 13 21:00:02 Tower kernel: ata1.00: configured for UDMA/133 (Drive related) Sep 13 21:00:02 Tower kernel: ata1: EH complete (Drive related) Sep 13 21:00:42 Tower kernel: ata1: limiting SATA link speed to 3.0 Gbps (Drive related) Sep 13 21:00:42 Tower kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen (Errors) Sep 13 21:00:42 Tower kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors) Sep 13 21:00:42 Tower kernel: ata1: SError: { UnrecovData Handshk } (Errors) Sep 13 21:00:42 Tower kernel: ata1.00: failed command: WRITE DMA EXT (Minor Issues) Sep 13 21:00:42 Tower kernel: ata1.00: cmd 35/00:00:50:4b:fd/00:04:03:00:00/e0 tag 0 dma 524288 out (Drive related) Sep 13 21:00:42 Tower kernel: res 50/00:00:4f:4b:fd/00:00:03:00:00/e0 Emask 0x10 (ATA bus error) (Errors) Sep 13 21:00:42 Tower kernel: ata1.00: status: { DRDY } (Drive related) The server was rebooted 19:17 and disk4 was added. For some reason I couldn't add it to the array, so I left it for a while and tried again 22:45 with success. Are the 21:00 errors related to this? Nothing was done between 19:17 and 22:45. I also have a few errors 09:40 (segfault) Another thing is that I have to manually start the array every time I reboot. Parity is fine and I use the powerdown script. How can I fix this? Thanks for all help. regards, Ketil syslog-2011-09-14.txt