jellis
-
Posts
20 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by jellis
-
-
Hi Everyone,
Does anyone know how to pass the following through without turning on PCI-E ACSD Override?
root@Tower:~# readlink /sys/bus/usb/devices/usb6
../../../devices/pci0000:00/0000:00:01.0/0000:01:00.0/usb6
When I turn on the override the card seems to pass through initially. But then overtime it just disappears. I will not show up again until I I reboot UNRAID but it will not passthrough again.
Here is what I put in my XML:
<hostdev mode='subsystem' type='pci' managed='yes'>
<driver name='vfio'/>
<source>
<address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
</source>
</hostdev>
<memballoon model='virtio'>
-
Oops, sorry I read that wrong.
Usb buses 3 and 4 are the same controller. Separate buses for usb 3.0 and 2.0 using the same physical usb ports (I'm assuming those are all usb3 ports that are backwards compatible)
I guess you can either try and move all existing usb devices to the usb 2.0 only ports (should be buses 1 and 2) and passthrough the usb3 controller,
Or you can get a usb3 pci card and pass that through. They are around $25 on amazon
I also hear there is a new method for passing through usb without the whole bus. Jonp has a thread where he is asking folks to test it
Ok, thanks I will check into Jonp's post again. I looked at it earlier but I didn't quite understand it. With my new found knowledge it may make more sense now.
What is strange though is when I plug in my spare USB drive to what the motherboard shows as USB0 and USB1 it still shows up in lsusb as USB3. Could this be because I am using a USB 2.0 drive and because it is reverse compatible it is assigning it to a different BUS?
-
Try this in your xml
<hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x14' function='0x0'/> </source> </hostdev>
Put it in right between "</video>" and "<memballoon model='virtio'>"
Ok, I will try this but one questions first: It seems my UNRAID USB is on the same slot as the device I am trying to pass. I have moved the UNRAID usb around and no matter which slot I move it to is still gives me ../../../devices/pci0000:00/0000:00:14.0 Any ideas how I can make sure BUS 3 and 4 are not on the same number ../../../devices/pci0000:00/0000:00:14.0/
root@Tower:~# lsusb Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 005: ID 0557:2419 ATEN International Co., Ltd Bus 003 Device 003: ID 0000:0001 Bus 003 Device 002: ID 0781:5583 SanDisk Corp. Bus 003 Device 010: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS Bus 003 Device 012: ID 2109:2813 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@Tower:~# readlink /sys/bus/usb/devices/usb4 ../../../devices/pci0000:00/0000:00:14.0/usb4 root@Tower:~# readlink /sys/bus/usb/devices/usb3 ../../../devices/pci0000:00/0000:00:14.0/usb3 root@Tower:~# readlink /sys/bus/usb/devices/usb2 ../../../devices/pci0000:00/0000:00:1d.0/usb2 root@Tower:~# readlink /sys/bus/usb/devices/usb1 ../../../devices/pci0000:00/0000:00:1a.0/usb1
-
Hi All,
Hoping someone can help me with this.
I am trying to passthrough an Anker 3.0 USB Docking station(https://www.anker.com/products/68ANDOCKS-BA) to a Windows 7 VM. I have attempted this a couple of times but just cant seem to get it to work. I am hoping someone can tell me exactly what I have to put in my xml to pass through the USB based on the below information(this follows the guide I found https://lime-technology.com/forum/index.php?topic=36768.0):
2. my usb controllers
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family US B xHCI (rev 05) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family US B EHCI #2 (rev 05) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family US B EHCI #1 (rev 05)
3. my mother board
I have attached the manual in case that is helpful
4. Unraid is on USB bus
Bus 003 Device 002: ID 0781:5583 SanDisk Corp.
Here is everything:
Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS Bus 003 Device 005: ID 0557:2419 ATEN International Co., Ltd Bus 003 Device 003: ID 0000:0001 Bus 003 Device 002: ID 0781:5583 SanDisk Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
5. plugged in a DataTraveler USB and then I run lsusb again
Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS Bus 003 Device 005: ID 0557:2419 ATEN International Co., Ltd Bus 003 Device 003: ID 0000:0001 Bus 003 Device 002: ID 0781:5583 SanDisk Corp. Bus 003 Device 006: ID 0951:1607 Kingston Technology DataTraveler 100 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Based on the above it appears that the usb port I want to use is running on the same bus. I believe this is an issue and probably why docker and vm freaked out during my first try at this. Can you someone confirm? It seems this should be on bus 004 since that is the 3.0 root hub, correct? If that is the case everything after this point may need to be adjusted after feedback.
ok, so moving on so everything is complete....with the understanding I may need to change the bus
6. ran readlink /sys/bus/usb/devices/usb3
../../../devices/pci0000:00/0000:00:14.0/usb3
8. checked IOMMU Groups
/sys/kernel/iommu_groups/0/devices/0000:00:00.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.0 /sys/kernel/iommu_groups/1/devices/0000:00:01.1 /sys/kernel/iommu_groups/1/devices/0000:02:00.0 /sys/kernel/iommu_groups/2/devices/0000:00:14.0 /sys/kernel/iommu_groups/3/devices/0000:00:1a.0 /sys/kernel/iommu_groups/4/devices/0000:00:1c.0 /sys/kernel/iommu_groups/5/devices/0000:00:1c.2 /sys/kernel/iommu_groups/6/devices/0000:00:1c.3 /sys/kernel/iommu_groups/7/devices/0000:00:1d.0 /sys/kernel/iommu_groups/8/devices/0000:00:1f.0 /sys/kernel/iommu_groups/8/devices/0000:00:1f.2 /sys/kernel/iommu_groups/8/devices/0000:00:1f.3 /sys/kernel/iommu_groups/8/devices/0000:00:1f.6 /sys/kernel/iommu_groups/9/devices/0000:03:00.0 /sys/kernel/iommu_groups/9/devices/0000:04:00.0 /sys/kernel/iommu_groups/10/devices/0000:05:00.0 /sys/kernel/iommu_groups/11/devices/0000:06:00.0
9. the identified device number is part of group 2
/sys/kernel/iommu_groups/2/devices/0000:00:14.0
11. I run into an issue trying to use Hostdev instead of the qemu:arg. It does not save in my XML. Now sure why.......
Using 11a method
Here is my XML code prior to any changes
<domain type='kvm' id='6'> <name>Windows 7 Sandbox</name> <uuid>4d35c4bb-8b42-44dc-b99f-67071d94b17c</uuid> <description>Windows 7 Copy for Sandabox</description> <metadata> <vmtemplate name="Custom" icon="windows7.png" os="windows7"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='3'/> <vcpupin vcpu='1' cpuset='4'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='2' threads='1'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/cache/VM/Windows 7 Sandbox/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/Backup/Software/OS Images/AcronisBootableMedia.iso'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/Backup/Software/UNRAID VM Drivers/virtio-win-0.1.96.iso'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:f1:2d:56'/> <source bridge='br0'/> <target dev='vnet1'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Windows 7 Sandbox.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='vmvga' vram='16384' heads='1'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain>
and here it is after I have added what i think I need to add
<domain type='kvm' id='6'> <name>Windows 7 Sandbox</name> <uuid>4d35c4bb-8b42-44dc-b99f-67071d94b17c</uuid> <description>Windows 7 Copy for Sandabox</description> <metadata> <vmtemplate name="Custom" icon="windows7.png" os="windows7"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> <locked/> </memoryBacking> <vcpu placement='static'>2</vcpu> <cputune> <vcpupin vcpu='0' cpuset='3'/> <vcpupin vcpu='1' cpuset='4'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.3'>hvm</type> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> </hyperv> </features> <cpu mode='host-passthrough'> <topology sockets='1' cores='2' threads='1'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/qemu-system-x86_64</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/cache/VM/Windows 7 Sandbox/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/Backup/Software/OS Images/AcronisBootableMedia.iso'/> <backingStore/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <alias name='ide0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/Backup/Software/UNRAID VM Drivers/virtio-win-0.1.96.iso'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:f1:2d:56'/> <source bridge='br0'/> <target dev='vnet1'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target port='0'/> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/Windows 7 Sandbox.org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='vmvga' vram='16384' heads='1'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/> <qemu:arg value='-device'/> <qemu:arg value='vfio-pci,host=00:14.0,bus=root.1,addr=00.0'/> </qemu:commandline> </domain>
Greatly appreciate you looking at all of this and helping me getting this resolved.
-
Thank you both for your help. I fumbled my way through the recovery process. I ended up purchasing Acronis and it made the whole process a lot easier. I even learned quite a bit about the VM XML. I will try to be more clear about my situation next time.
Thanks!
-
Hi Bob,
Thanks for replying. Sounds like I am attempting something similar. I have a the Windows Install ISO mounted and I am booting into the recovery console. Within this console it asks to point to the image, which I created earlier and it is stored on the network. It does not allow me to "browse" to the file location and instead asks for the file path, but it fails each time I try to point to the image. For example, my image is located here: \\tower\cache\WindowsImageBackUp\UNRAID-Win7\Backup 2016-03-10\ . After entering the image location it asks for the network credentials, it defaults to an odd domain of MININT-AS426KG, so I use a "\" in my username to get out of the domain. Then I get an error saying the domain can not be reached.
So bottom line, I don't think windows is seeing the folder on the network. Anything special I have to enter to get to the network?
-
Hey Guys,
Recently replacemented my cache drive and was able to recover/transfer everything except for my windows VM. I have an image backup of the machine from the windows tool, but am struggling to recover it. On a typical machine I would boot from a windows disk and then point to an attached USB drive and load the image using the windows recovery tool. I am trying the same thing with the VM. I am booting into the windows ISO, but am unable to point to the USB. I have installed an external USB and selected the USB from the VM config so it is seeing it, but does boot/load within recovery console. I have also tried to point to it within the array but unable to connect that way either. Hopefully this all makes sense. Anyone have an idea of how to load my previous windows recovery image onto a new VM in UNRAID? Thanks for you help!!
-
No crash this morning. Thanks again.
-
Yep, I sure do! This makes perfect sense. I have changed the mover to run monthly. This should buy me enough time to swap out the drive. Not looking forward to the long process of clearing the new drive.
Agreed that unRAID is great. I am very happy with it, especially with my plex, tv and home automation needs.
Thanks again for your help guys!
-
Quick update. The server froze again last night. I have not made any changes to the cache drive yet bud did pull the 2 failed drives. Understanding that I have some hardware issues.... there must also be something running in the middle of the night that is causing this? Could it be the CRON job? I was able to grab this screenshot before I restarted the server this morning. Does this make sense to anyone?
I am going to disable all of my dockers and cache drive for now. Hoping to stop the freezing.
-
Thanks guys. I will get to work on the replacement of SATA cables and drives and then see where I stand. Bummer I am losing so many drives....they are getting old though.
-
ok, so on this one, I just replaced the drive about a month ago. What exactly is this error telling me? A sector within the drive is failing to be read and uncorrectable? Thank for your help!
This usually means there are bad sectors, in this case at least 88, you can check by doing an extended SMART test, if it fails with a read error (and I suspect it will) you should replace it, you can then try running a few preclear cycles and see if the pending sectors are reallocated and the number goes to 0.
Ran the smart test and here are the results:
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.18-unRAID] (local build)
Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.14 (AF)
Device Model: ST3000DM001-9YN166
Serial Number: W1F055SX
LU WWN Device Id: 5 000c50 044d6b4a8
Firmware Version: CC46
User Capacity: 3,000,592,982,016 bytes [3.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Wed Mar 16 22:30:23 2016 EDT
==> WARNING: A firmware update for this drive is available,
see the following Seagate web pages:
http://knowledge.seagate.com/articles/en_US/FAQ/207931en
http://knowledge.seagate.com/articles/en_US/FAQ/223651en
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 121) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 575) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 349) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x3085) SCT Status supported.
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 108 079 006 Pre-fail Always - 15312136
3 Spin_Up_Time 0x0003 094 092 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 19
5 Reallocated_Sector_Ct 0x0033 095 095 036 Pre-fail Always - 7016
7 Seek_Error_Rate 0x000f 060 055 030 Pre-fail Always - 309311370372
9 Power_On_Hours 0x0032 073 073 000 Old_age Always - 24250
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 915
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 3311
188 Command_Timeout 0x0032 100 099 000 Old_age Always - 4 4 4
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 061 051 045 Old_age Always - 39 (Min/Max 34/43)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 872
193 Load_Cycle_Count 0x0032 015 015 000 Old_age Always - 171208
194 Temperature_Celsius 0x0022 039 049 000 Old_age Always - 39 (0 24 0 0 0)
197 Current_Pending_Sector 0x0012 100 001 000 Old_age Always - 48
198 Offline_Uncorrectable 0x0010 100 001 000 Old_age Offline - 48
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 12373h+08m+04.612s
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 45133539560702
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 141632493877148
SMART Error Log Version: 1
ATA Error Count: 4327 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 4327 occurred at disk power-on lifetime: 23681 hours (986 days + 17 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 a0 f8 9f 06 Error: WP at LBA = 0x069ff8a0 = 111147168
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 00 e0 ff ff ff 4f 00 23d+12:25:30.513 WRITE FPDMA QUEUED
61 00 e0 ff ff ff 4f 00 23d+12:25:30.311 WRITE FPDMA QUEUED
61 00 e0 ff ff ff 4f 00 23d+12:25:30.223 WRITE FPDMA QUEUED
61 00 e0 ff ff ff 4f 00 23d+12:25:30.067 WRITE FPDMA QUEUED
61 00 e0 ff ff ff 4f 00 23d+12:25:29.770 WRITE FPDMA QUEUED
Error 4326 occurred at disk power-on lifetime: 23681 hours (986 days + 17 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 a0 f8 9f 06 Error: WP at LBA = 0x069ff8a0 = 111147168
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 00 00 ff ff ff 4f 00 23d+12:25:21.472 WRITE FPDMA QUEUED
61 00 00 ff ff ff 4f 00 23d+12:25:21.472 WRITE FPDMA QUEUED
61 00 00 ff ff ff 4f 00 23d+12:25:21.472 WRITE FPDMA QUEUED
61 00 00 ff ff ff 4f 00 23d+12:25:21.472 WRITE FPDMA QUEUED
61 00 00 ff ff ff 4f 00 23d+12:25:21.472 WRITE FPDMA QUEUED
Error 4325 occurred at disk power-on lifetime: 23681 hours (986 days + 17 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 a0 f8 9f 06 Error: UNC at LBA = 0x069ff8a0 = 111147168
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 20 80 71 08 40 00 23d+12:25:13.089 READ FPDMA QUEUED
61 00 e0 f0 92 e0 4d 00 23d+12:25:13.067 WRITE FPDMA QUEUED
61 00 e0 60 49 e0 4c 00 23d+12:25:13.000 WRITE FPDMA QUEUED
61 00 00 60 45 e0 4c 00 23d+12:25:13.000 WRITE FPDMA QUEUED
61 00 e0 38 95 20 4c 00 23d+12:25:12.698 WRITE FPDMA QUEUED
Error 4324 occurred at disk power-on lifetime: 23681 hours (986 days + 17 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 a0 f8 9f 06 Error: WP at LBA = 0x069ff8a0 = 111147168
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 00 a0 ff ff ff 4f 00 23d+12:25:02.559 WRITE FPDMA QUEUED
61 00 20 ff ff ff 4f 00 23d+12:25:02.559 WRITE FPDMA QUEUED
61 00 20 ff ff ff 4f 00 23d+12:25:02.559 WRITE FPDMA QUEUED
61 00 c0 ff ff ff 4f 00 23d+12:25:02.559 WRITE FPDMA QUEUED
61 00 20 ff ff ff 4f 00 23d+12:25:02.559 WRITE FPDMA QUEUED
Error 4323 occurred at disk power-on lifetime: 23681 hours (986 days + 17 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 a0 f8 9f 06 Error: WP at LBA = 0x069ff8a0 = 111147168
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 00 00 ff ff ff 4f 00 23d+12:24:56.323 WRITE FPDMA QUEUED
61 00 00 ff ff ff 4f 00 23d+12:24:56.323 WRITE FPDMA QUEUED
61 00 00 ff ff ff 4f 00 23d+12:24:56.323 WRITE FPDMA QUEUED
61 00 00 ff ff ff 4f 00 23d+12:24:56.323 WRITE FPDMA QUEUED
61 00 00 ff ff ff 4f 00 23d+12:24:56.322 WRITE FPDMA QUEUED
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed: read failure 90% 24247 60855848
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
-
Your cache disk also needs attention:
Device Model: ST3000DM001-9YN166 Serial Number: W1F055SX 197 Current_Pending_Sector 0x0012 100 001 000 Old_age Always - 88 198 Offline_Uncorrectable 0x0010 100 001 000 Old_age Offline - 88
If you have a spare replace it.
ok, so on this one, I just replaced the drive about a month ago. What exactly is this error telling me? A sector within the drive is failing to be read and uncorrectable? Thank for your help!
-
In my experience, and in some cases, a bad disk can crash or make the computer unresponsive, just by being connected, even if not in use.
You should disconnected them and check if the problem goes away.
I removed the drives that had SMART errors. Incidentally, both of which were in the Icy Dock Backplane.
-
Those ata2 errors are probably from a bad sata cable, replace this cable:
Device Model: ST5000DM000-1FK178 Serial Number: W4J04L88 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 177
So this is interesting. This is my parity drive and is plugged into a Icy Dock Backplane:
I will try replacing the sata cable to see if this helps it.
-
Hi Kizer. Sure and thanks! Sometime between the time I go to bed and wake up the system freezes, probably better term than crash. To the point that I am not able to login via root or even connect via telnet. One thing I have not been able to tell is what the screen displays when it freezes. I have connected a monitor so I can get a visual if it happens again. I have connected the diagnostics zip. Thanks for looking at this.
Here is what shows in the error and warnings log:
Mar 16 10:33:22 Tower kernel: ACPI: Early table checksum verification disabled
Mar 16 10:33:22 Tower kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20150410/hwxface-580)
Mar 16 10:33:22 Tower kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20150410/hwxface-580)
Mar 16 10:33:22 Tower kernel: floppy0: no floppy controllers found
Mar 16 10:33:26 Tower rpc.statd[1614]: Failed to read /var/lib/nfs/state: Success
Mar 16 10:33:26 Tower sshd[1634]: Server listening on 0.0.0.0 port 22.
Mar 16 10:33:36 Tower kernel: REISERFS (device md1): replayed 740 transactions in 6 seconds
Mar 16 10:33:36 Tower kernel: REISERFS (device md2): replayed 6 transactions in 0 seconds
Mar 16 10:33:37 Tower kernel: REISERFS (device md3): replayed 6 transactions in 0 seconds
Mar 16 10:33:37 Tower kernel: REISERFS (device md4): replayed 6 transactions in 0 seconds
Mar 16 10:33:37 Tower kernel: REISERFS (device md5): replayed 7 transactions in 0 seconds
Mar 16 10:33:39 Tower kernel: REISERFS (device md6): replayed 77 transactions in 1 seconds
Mar 16 10:33:49 Tower avahi-daemon[11181]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Mar 16 10:33:58 Tower kernel: ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen
Mar 16 10:33:58 Tower kernel: ata2.00: irq_stat 0x08000000, interface fatal error
Mar 16 10:33:58 Tower kernel: ata2.00: failed command: READ DMA EXT
Mar 16 10:33:58 Tower kernel: ata2: hard resetting link
Mar 16 10:34:12 Tower kernel: ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen
Mar 16 10:34:12 Tower kernel: ata2.00: irq_stat 0x08000000, interface fatal error
Mar 16 10:34:12 Tower kernel: ata2.00: failed command: READ DMA EXT
Mar 16 10:34:12 Tower kernel: ata2: hard resetting link
Mar 16 10:37:03 Tower kernel: ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen
Mar 16 10:37:03 Tower kernel: ata2.00: irq_stat 0x08000000, interface fatal error
Mar 16 10:37:03 Tower kernel: ata2.00: failed command: READ DMA EXT
Mar 16 10:37:03 Tower kernel: ata2: hard resetting link
Mar 16 10:37:26 Tower kernel: ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen
Mar 16 10:37:26 Tower kernel: ata2.00: irq_stat 0x08000000, interface fatal error
Mar 16 10:37:26 Tower kernel: ata2.00: failed command: READ DMA EXT
Mar 16 10:37:26 Tower kernel: ata2: hard resetting link
-
Hi Guys,
Would a failed drive, in this case 2 failed drives not assigned to the array, cause crashing? When booting the server I get SMART errors on 2 of my drives that were no assigned. I restarted the server into UNRAID twice and each night the server crashes. Today I removed both drives and then ran a memory test, which passed. Is it as simple as the drives causing this failure? Also, no errors show int he log from the gui that I checked. Thanks for your help!
Model: N/A
M/B: Supermicro - X10SL7-F
CPU: Intel® Xeon® CPU E3-1230 v3 @ 3.30GHz
HVM: Enabled
IOMMU: Enabled
Cache: 256 kB, 1024 kB, 8192 kB
Memory: 16384 MB (max. installable capacity 32 GB)
Network: eth0: 1000Mb/s - Full Duplex
eth1: not connected
Kernel: Linux 4.1.18-unRAID x86_64
OpenSSL: 1.0.1s
Uptime:0 days, 01:07:54
-
Thanks for your input Chris. I did look at that one but was concerned about not having very many PCI Express slots. I guess it does not matter since it will be a true server. In regards to the HDHomeRun it is a separate box plugged into the network. There are plugins available for PLEX that should work for my purposes.
Based on using the X10SL7 this is what I have come up with so far:
SeaSonic SSR-650RM 650W ATX12V / EPS12V SLI Ready CrossFire Ready 80 PLUS GOLD Certified Modular Active PFC Power Supply New 4th Gen CPU Certified Haswell Ready
1 x NORCO RPC-4220 4U Rackmount Server Chassis w/ 20 Hot-Swappable SATA/SAS 6G Drive Bays (Mini SAS Connector)
4 x Rosewill RASA-13005 0.5M SFF-8087 to SFF-8087 Internal Multi-lane SAS Cable
1 x Nippon Labs SATA to Molex Power Adapter SATA-FM SATA 15 Pin male to Molex 4 pin female adaptor for SATA I and SATA II Hard Drive Model SATA-FM
2 x 4tb, 2 x 3tb, 2 x 2tb, 2 x 1.5 Hard Drives = 8 plus be able to expand up to 20
1 x SUPERMICRO MBD-X10SL7-F-O uATX Server Motherboard LGA 1150 Intel C222 DDR3 1600
1 x Intel Intel Xeon E3-1230V3 Haswell 3.3GHz LGA 1150 80W Server Processor BX80646E31230V3
2 x Samsung DDR3-1600 8GB/1Gx72 ECC CL11 Server Memory
What is everyone thoughts? Good? I am struggling a bit with the case though. Not sure if I should go with the Norco or maybe something else. Back to reading the forums!
-
Hi Everyone,
New to building an unRAID box but not building computers in general. I have poured over the forums and have gained a ton of insight on what I would like to build. However, I am struggling to pick a proper MOBO and Processor due to the sheer amount of options. I am not so much concerned with cost as getting something that will last many years to come and allow me to expand where needed.
I am looking to build a system to host PLEX, TV(HDHOMERUN Streaming), Movies, computer backups, storing surveillance images from cameras to start with. Virtualization also interest me and do not want to limit myself to a build that would not allow this or future expandable options. Bottom line I like to tinker with many aspects and would like the server to handle anything I throw at it.
What I have come up with so far is as follows:
unRAID Build
1 x Seasonic SS-660XP2 ATX 12V/EPS 12V, 660W, 80 PLUS PLATINUM Full Modular certified Active PFC Power Supply New 4th Gen CPU Certified Haswell Ready
1 x NORCO RPC-4220 4U Rackmount Server Chassis w/ 20 Hot-Swappable SATA/SAS 6G Drive Bays (Mini SAS Connector)
2 x SUPERMICRO AOC-SAS2LP-MV8 PCI-Express 2.0 x8 SATA / SAS 8-Port Controller Card
- 4 x Rosewill RASA-13005 0.5M SFF-8087 to SFF-8087 Internal Multi-lane SAS Cable
- 1 x Nippon Labs SATA to Molex Power Adapter SATA-FM SATA 15 Pin male to Molex 4 pin female adaptor for SATA I and SATA II Hard Drive Model SATA-FM
2 x 4tb, 2 x 3tb, 2 x 2tb, 2 x 1.5 Hard Drives = 8 plux be able to expand up to 20
Motherboard TBD
Processor TBD
Memory TBD
I appreciate your thoughts on which Motherboard and processor to get? I was looking at the BEAST builds from Raj but those seem to be dated based on the post date. Again, appreciate your help!
[Support] NodeLink
in Docker Containers
Posted
Hello,
Any chance we can get the latest version pushed? 8.4
Thanks!