ooimo

No, the OS is booting from a different disk. When I connect the disk after boot up it is not detected by the OS. Below is the output when booting without the faulty disk connected. I have also tried running the following command which should scan for disks. james@linuxws:~$ for host in /sys/class/scsi_host/*; do echo "- - -" | sudo tee $host/scan; ls /dev/sd* ; done - - - /dev/sda /dev/sda1 /dev/sda2 - - - /dev/sda /dev/sda1 /dev/sda2 - - - /dev/sda /dev/sda1 /dev/sda2 - - - /dev/sda /dev/sda1 /dev/sda2 - - - /dev/sda /dev/sda1 /dev/sda2 - - - /dev/sda /dev/sda1 /dev/sda2 james@linuxws:~$ lsblk -S NAME HCTL TYPE VENDOR MODEL REV TRAN sda 4:0:0:0 disk ATA SAMSUNG MZMTD128 1K0Q sata

I'm getting the same response from the drive using a different controller james@linuxws:~$ sudo hdparm -N /dev/sda /dev/sda: max sectors = 16777215/15628053168, HPA is enabled james@linuxws:~$ sudo hdparm -N 15628053168 /dev/sda /dev/sda: setting max visible sectors to 15628053168 (temporary) SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 53 00 00 21 04 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 max sectors = 16777215/15628053168, HPA is enabled Is there a way to decode the response?

Hi All, Recently I had the configuration issue plugin tell me that HPA was enabled on my data and parity drives. When I went through the process of removing it by running the hdparm command I found that it was in my controller having issues and wrongly reporting on the drives and not HPA. Issuing the hdparm command through the faulty controller has set the HPA at 8Gb into the drives and when I attempt to fix this I get an error shown below. james@linuxws:~$ sudo hdparm -N /dev/sda /dev/sda: max sectors = 16777215/15628053168, HPA is enabled james@linuxws:~$ sudo hdparm -N p15628053168 /dev/sda /dev/sda: setting max visible sectors to 15628053168 (permanent) SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 04 53 00 00 21 04 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 max sectors = 16777215/15628053168, HPA is enabled I realise this was pretty stupid and I shouldn't have rushed into sending dangerous hdparm commands, but if there is another way to fix the drives I am all ears. I have already tried ATA tool from a windows machine and made sure the drive is not frozen. Loss of data is not an issue due to the tested backups I have. Cheers,

Hi! I've been having problems with my USB devices disconnecting at random intervals, from a few minutes to a few days. No amount of my googling has been able to solve this problem. This has happened on multiple installs of both Windows 10 and Windows 8.1 and in multiple storage configurations. I'm able to get the devices back by manually running "virsh attach-device Windows <device>.xml". Any help would be appreciated, thanks! My Hardware is as follows: Supermicro X10SLM+-F Samsung M391B1G73QH0-YK0 RAM Intel Xeon E3 1231 V3 ServeRAID M1015 R9 290 DirectCU II The Syslog from the time it happens: Apr 15 09:24:09 Tower kernel: usb 3-4: USB disconnect, device number 3 Apr 15 09:24:09 Tower kernel: usb 3-4.4: USB disconnect, device number 5 Apr 15 09:24:09 Tower kernel: usb 3-4.4.2: USB disconnect, device number 7 Apr 15 09:24:09 Tower kernel: usb 3-4.4.3: USB disconnect, device number 8 Apr 15 09:24:09 Tower kernel: usb 3-4.4.4: USB disconnect, device number 9 Apr 15 09:24:09 Tower kernel: usb 3-4: new high-speed USB device number 10 using xhci_hcd Apr 15 09:24:09 Tower kernel: hub 3-4:1.0: USB hub found Apr 15 09:24:09 Tower kernel: hub 3-4:1.0: 4 ports detected Apr 15 09:24:09 Tower kernel: usb: failed to peer 3-4-port4 and usb4-port6 by location (3-4-port4:none) (usb4-port6:usb3-port4) Apr 15 09:24:09 Tower kernel: usb 3-4-port4: failed to peer to usb4-port6 (-16) Apr 15 09:24:10 Tower kernel: usb 3-4.4: new high-speed USB device number 11 using xhci_hcd Apr 15 09:24:10 Tower kernel: hub 3-4.4:1.0: USB hub found Apr 15 09:24:10 Tower kernel: hub 3-4.4:1.0: 4 ports detected Apr 15 09:24:10 Tower kernel: usb 3-4.4.2: new full-speed USB device number 12 using xhci_hcd Apr 15 09:24:10 Tower kernel: usb 3-4.4.3: new full-speed USB device number 13 using xhci_hcd Apr 15 09:24:10 Tower kernel: input: USB Leopard as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.4/3-4.4.3/3-4.4.3:1.0/0003:04D9:0141.0012/input/input18 Apr 15 09:24:10 Tower kernel: hid-generic 0003:04D9:0141.0012: input,hidraw2: USB HID v1.11 Leopard [uSB Leopard] on usb-0000:00:14.0-4.4.3/input0 Apr 15 09:24:10 Tower kernel: hid-generic 0003:04D9:0141.0013: hiddev0,hidraw3: USB HID v1.11 Device [uSB Leopard] on usb-0000:00:14.0-4.4.3/input1 Apr 15 09:24:10 Tower kernel: input: USB Leopard as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.4/3-4.4.3/3-4.4.3:1.2/0003:04D9:0141.0014/input/input19 Apr 15 09:24:10 Tower kernel: hid-generic 0003:04D9:0141.0014: input,hidraw4: USB HID v1.11 Mouse [uSB Leopard] on usb-0000:00:14.0-4.4.3/input2 Apr 15 09:24:10 Tower kernel: usb 3-4.4.4: new full-speed USB device number 14 using xhci_hcd Apr 15 09:24:10 Tower kernel: input: La-VIEW Technology SteelSeries Sensei as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.4/3-4.4.4/3-4.4.4:1.0/0003:1038:1361.0015/input/input20 Apr 15 09:24:10 Tower kernel: hid-generic 0003:1038:1361.0015: input,hidraw5: USB HID v1.00 Mouse [La-VIEW Technology SteelSeries Sensei] on usb-0000:00:14.0-4.4.4/input0 Apr 15 09:24:10 Tower kernel: input: La-VIEW Technology SteelSeries Sensei as /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4.4/3-4.4.4/3-4.4.4:1.1/0003:1038:1361.0016/input/input21 Apr 15 09:24:11 Tower kernel: hid-generic 0003:1038:1361.0016: input,hiddev0,hidraw6: USB HID v1.0 The VM log: 2016-04-12 09:07:09.644+0000: starting up libvirt version: 1.2.18, qemu version: 2.3.0 Domain id=4 is tainted: high-privileges Domain id=4 is tainted: custom-argv Domain id=4 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) 2016-04-15T01:24:09.353160Z qemu-system-x86_64: libusb_release_interface: -4 [NO_DEVICE] 2016-04-15T01:24:09.353188Z qemu-system-x86_64: libusb_release_interface: -4 [NO_DEVICE] 2016-04-15T01:24:09.353192Z qemu-system-x86_64: libusb_release_interface: -4 [NO_DEVICE] 2016-04-15T01:24:09.359949Z qemu-system-x86_64: libusb_release_interface: -4 [NO_DEVICE] 2016-04-15T01:24:09.359961Z qemu-system-x86_64: libusb_release_interface: -4 [NO_DEVICE] 2016-04-15T01:24:09.362048Z qemu-system-x86_64: libusb_release_interface: -4 [NO_DEVICE] 2016-04-15T01:24:09.362060Z qemu-system-x86_64: libusb_release_interface: -4 [NO_DEVICE] libusb: error [_open_sysfs_attr] open /sys/bus/usb/devices/3-4.4.2/bConfigurationValue failed ret=-1 errno=2