This has been a tried and true method for Windows because it is finicky with hardware changes without a reinstall (eg BSOD on boot is what happens 9/10 times unless you move to the same hardwar). Surprisingly, if you use a QEMU VM and do a standard install, it has worked in every system I've thrown the drive in afterwards. So the play is this, use a USB SSD, physical SATA drive plugged internally or for convenience, you could use a SATA to USB adapter on another computer to perf........

You might assume you have a bad drive or the SATA interface/cable is bad, or the power supply is bad/weak to the drive. These are all possible issues, but definitely check your SATA cable for "twisting". It is a big issue because until the error stops or times out, your system will not boot (in my case this was the case even though the drive with the issue was not part of the OS or booting process at all). If you run an open rig that you move around often that ha........

Before you try to install and dual boot it is very important to understand the concept of "what boot mode your BIOS is in" and "what mode you booted the installer to". Then follow the example of Linux Mint (but most Linux installers are very similar)to carefully understand WHERE you are installing your Boot Loader to whether that be MBR or EFI. How Am IBooted? First it's important to check your BIOS to see........

If you've come here, don't be embarraassed, working in IT, this is the MOST common computer problem that almost everyone will encounter. The reason why I'm doing this post is because I've seen an increase from colleagues and admins having this problem and many times it's not even your fault. A common scenario is that someone acquires a new or used computer which they weren't given the password for. Fortunately Ihave a detailed list of all the options whether free or pa........

This is the closest way to disabling it without using the "libata.force=noncq" kernel boot option is to set the queue to a depth of 1 which doesn't actually disable it. Change the sdc below to match the device you want to disable NCQ for. [root@officebox ~]# echo "1" > /sys/block/sdc/device/queue_depth Errors that indicate you are having a performance issue are these in messages or dmesg relating to N........

The key thing is that you must use a "machine"id of "pc-1.3" or it will say your hardware is not supported. Additionally you MUST use a virtio disk or you will get a ks_pre.sh error as soon as the install starts (a look at logs will show it can't find a disk). This is funny because even though the OS finds the disk and an fdisk -l shows it, it looks like the script looks for a /dev/vda device (virtio) and nothing else, so if you didn't use Virtio as you........

#to show all VBoxManage list vms #show ONLY running vms VBoxManage list runningvms VBoxManage storageattach test --storagectl "SATA" --port 0 --device 0 --type hdd --medium iscsi --server 192.168.1.91 --target "iqn.2018-12.local.abcrandom.target:sdb" --initiator "iqn.1982-01.ca.bla.tld:abc123" --t........

I've never seen this before in all of my years. Ihave some very old CDs and DVDs 12-15 years old that seem not to work in this BD-R/DVD-R/CD-R Asus drive. The discs are fine actually and ironically they even work fine on a normal LG USB based BD-R drive! Here are the errors in Linux: [2914936.884924] attempt to access beyond end of device [2914936.884927] loop1: rw=0, want=730424, limit=688384 [2914954.556873] attempt to........

This is a VIA made VL805 USB 3.0 Chipset with 4-ports and MOLEX powered. First of all this unit was cheap at about only 9 USD with fast shipping. My biggest concern was if this was a quality unit and would it really give you full USB 3.0 speeds (some people reported with similar cards that for some weird r........

When running cudaminer once it tries to initialize the card the entire screen freezes. The computer itself is still running but the Xorg is done for, you cannot even switch to another console window and must reboot (even an mdm or Xorg restart does not help). At first cudaminer will give you these errors: stratrum_recv_line failed ...retry after 15 seconds GPU #0: Geforce 210 with compute ca........

Normally the below would indicate a failing or failed drive. In this case the SATA port was unplugged and sometimes the Linux kernel/motherboard even with AHCIjust don't play nice and can't handle it. What happened is Iplugged in a new drive after removing another one. However the log shows that after the old drive was plugged in the Linux kernel kept complaining thinking the drive was there but not responding properly. This continued even with reseating........

In short the two drives in the array were /dev/sdd and /dev/sde. The kernel sees they were unplugged and have gone down as you can see below. mdadm caught the first one being unplugged /dev/sde and disabled the missing drive. However when the final drive that was part of the array is unplugged it didn't notice at all. Instead it complains about an IO error later for drives that the kernel knows do not exist anymore. [45817.162728] ata4: exception........

I keep reading these drives are slower, but they are cheap and still SSDand work very fast for my needs. As you can see the sequential read is 481-491MB/s, if I put them in MDADM RAID10 mode (normal RAID1) they should give me well over 900MB/s and with redundancy and being very cheap for what they offer. [1232206.315622] scsi 8:0:1:0: Direct-Access ATA ADATA SU800&........

At first my BIOS said the card may not work right because there is no more option ROM space. I disabled the Option ROM for both LSI 1068 and 2008 chipsets, Network Boot ROM and most other PCI slots, Serial Port, etc... and the message went away but the card still does not work properly. But it still cannot initialize the card properly(does not work): [ 33.943272] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:........

[ 2868.041375] ata1: EH in SWNCQ mode,QC:qc_active 0x40 sactive 0x40 [ 2868.041554] ata1: SWNCQ:qc_active 0x40 defer_bits 0x0 last_issue_tag 0x6 [ 2868.041556] dhfis 0x40 dmafis 0x40 sdbfis 0x20 [ 2868.041874] ata1: ATA_REG 0x41 ERR_REG 0x84 [ 2868.042013] ata1: tag : dhfis dmafis sdbfis sactive [ 2868.042163] ata1: tag 0x6: 1 1 0 1 [ 2868.042301] ata1.00: exception Emask 0x1 SAct 0x40 SErr 0x400000 action 0x6 frozen [........

Fortunately the format is EATX so an EATX case will work and the screw layout is standard. You will need to remove the HEX/TORX screws that are connecting the stock HP standoffs (meant to slide into an HP case). XW9400 Motherboard Issues Size: 12" x 13" Proprietary Power Connector Proprietary CPU Power Connector Proprietary Memory Power Connector Fan connectors are 4 pin so you will need some kind of adapter.........

0000:00:00.0 RAM memory: NVIDIA Corporation MCP55 Memory Controller (rev a2) 0000:00:01.0 ISA bridge: NVIDIA Corporation MCP55 LPC Bridge (rev a3) 0000:00:01.1 SMBus: NVIDIA Corporation MCP55 SMBus (rev a3) 0000:00:02.0 USB controller: NVIDIA Corporation MCP55 USB Controller (rev a1) 0000:00:02.1 USB controller: NVIDIA Corporation MCP55 USB Controller (rev a2) 0000:00:05.0 IDE interface: NVIDIA Corporation MCP55 SATA Controller (rev a3) 0000:00:05.1 I........

Motherboard: Gigabyte GA-3CESL: http://b2b.gigabyte.com/products/product-page.aspx?pid=2658#dl Dell Part Numbers for the motherboard: R1232 R1232L R2232S SERVER MOTHERBOARD GENUINE 408P9 CN-0408P9 GA-3CESL Manual Download here RAMSlots: 16 (8 controlled by each CPU) RAMType: DDR2 ECC 5300P........

Dell CS24SC Info 0000:00:00.0 Host bridge: Intel Corporation 5100 Chipset Memory Controller Hub (rev 90) 0000:00:02.0 PCI bridge: Intel Corporation 5100 Chipset PCI Express x8 Port 2-3 (rev 90) 0000:00:03.0 PCI bridge: Intel Corporation 5100 Chipset PCI Express x4 Port 3 (rev 90) 0000:00:04.0 PCI bridge: Intel Corporation 5100 Chipset PCI Express x16 Port 4-7 (rev 90) 0000:00:05.0 PCI bridge: Intel Corporation 5100 Chipset PCI Express x4 Port 5 (rev 90)........

0000:00:00.0 Host bridge: Intel Corporation 5000P Chipset Memory Controller Hub (rev b1) 0000:00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 2-3 (rev b1) 0000:00:03.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 (rev b1) 0000:00:04.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 4-5 (rev b1) 0000:00:05.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4........

[3805108.257042] sd 0:0:0:0: [sda] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB) [3805108.257052] sd 0:0:0:0: [sda] Write Protect is off [3805108.257054] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [3805108.257066] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [3805108.257083] sd 0:0:0:0: [sda] 1953525168 512-byte hardware sectors: (1.00 TB/931 GiB) [3805108.257090] sd 0:0:0:0: [sda] Write Protect is off........

The first is a dual CPU AMD Opteron 2373EE (4 cores x 2) and I think it did bad because it has some old 250GB SATAs which can only do about 65MB/s max sequential reads. I think it should have blown away the second (AMD X4 640 Quad Core). [root@fs12home unixbench-4.1.0-wht-2]# ./Run make all make[1]: Entering directory `/root/unixbench-4.1.0-wht-2' Checking distribution of files ./pgms exists ./src exists........

I've got one of these for testing projects from work at home and got more than I bargained for with the time I've spent on it due to the storage handing/Perc 6/i cards. My particular model came with the following: 2U Rack Mount Server with Rails 2xOpteron 2373 EE (Quad Core, there is a 6-core version that can be found at times) 16GB RAM 2 x 250GB Seagate SATA 2 x Dell Perc 6/i (horrible and a nightmare to work........

The results are not bad, the Hitachi performs the same as it does in a SATA2 motherboard. However, the 2TB is much different, on a similar 2TB Toshiba I get about 198MB/s on a different motherboard vs the 2TB Hitachi which should produce similar results. This Dell Perc 6/i is on a PCI x8 riser card and is connected to a 12-port backplane. Adapter #0 Enclosure Device ID: 32 Slot Number: 0 Enclosure position: N/A De........

LSi Megaraid At first it was configured as a RAID 0, then I deleted the Virtual Disk Group. I thought both drives would be shown and detected in Linux as sda and sdb but it actually shows nothing. To make them work you have to hit Ctrl+R before the system boots (when prompted) and create a Virtual Disk Group. In my case I created each one as RAID 0 (with a single drive only) as I just wanted JBOD but there is no such option or default in these Dell Pe........

These drives seem to die very easily during shipping: sd 0:0:0:0: [sda] Unhandled error code sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK sd 0:0:0:0: [sda] CDB: Read(10): 28 00 18 8b 65 e0 00 00 08 00 end_request: I/O error, dev sda, sector 411788768 sd 0:0:0:0: [sda] Unhandled error code sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK sd 0:0:0:0: [sda] CDB: Read(10): 28 00 18 8b........

Another new drive bad from the start: Jun 2 15:14:18 one-desktop kernel: [15895.386779] ata2.00: exception Emask 0x50 SAct 0x1 SErr 0x280900 action 0x6 frozen Jun 2 15:14:18 one-desktop kernel: [15895.386782] ata2.00: irq_stat 0x08000000, interface fatal error Jun 2 15:14:18 one-desktop kernel: [15895.386784] ata2: SError: { UnrecovData HostInt 10B8B BadCRC } Jun 2 15:14:18 one-desktop kernel: [15895.386788] ata2.00: cmd 60/0........

This is the most I can get when plugging in a hard drive hot and only on some power connectors. [71656.314271] ata5: exception Emask 0x50 SAct 0x0 SErr 0x90a02 action 0xe frozen [71656.314277] ata5: irq_stat 0x00400000, PHY RDY changed [71656.314285] ata5: SError: { RecovComm Persist HostInt PHYRdyChg 10B8B } [71656.314294] ata5: hard resetting link [71660.360686] ata5: softreset failed (device not ready) [71660.360694] ata5: applying........

[1433128.139339] sd 5:0:1:0: [sde] Unhandled error code [1433128.139343] sd 5:0:1:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [1433128.139348] sd 5:0:1:0: [sde] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00 [1433128.139360] end_request: I/O error, dev sde, sector 0 [1433128.139410] sd 5:0:1:0: [sde] Unhandled error code [1433128.139414] sd 5:0:1:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK [1433128.139420] sd 5:0:1........

I like badblocks and don't know a better more reliable way of checking the drive. If there are no errors from badblocks and dmesg doesn't produce any SATA related errors, the drive should be good (for now at least). I also prefer to do read and write mode, yes it takes ages but it is really the best way of doing it. This gives me the most confidence in knowing that a drive, especially a new one is at least OK at the moment. To test in read only mode........

[ 12.460014] ata1: SRST failed (errno=-16) [ 17.626677] ata1: link is slow to respond, please be patient (ready=0) [ 22.480011] ata1: SRST failed (errno=-16) [ 27.646681] ata1: link is slow to respond, please be patient (ready=0) [ 38.106817] ata1.01: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) [ 48.266676] ata1: link is slow to respond, please be patient (ready=0)........

dd if=/dev/sda of=/dev/null creates ever increasing load every second. After minutes the load has moved up to 4.79 I've tried with two different discs in my system. I wonder if it's a delay or problem with the SATA bus because one drive I have connected has recently failed. I notice when drives fail that you get some IO/blocking issue when they don't respond properly. Yes I believe it was, because here's the same disc after removing the dead........

I like dd, although it only reads it, usually a read test of the entire disk will uncover if your hard drive is bad in some parts. This is a good thing to do at least once a month, a lot of times bizarre program behavior, laginess and crashing/unnmounting problems etc.. are due to a failing disc and SMART won't know it or indicate a problem: We must also remember there's never a guarantee, I've found that ever since we moved to larger and more platters per drive with 1TB drives........

I had one of these shipped and it was not recognized when plugged in, here's what a dead drive looks like (I assume it's teh circuit board which is dead): ata1: link is slow to respond, please be patient (ready=0) ata1: softreset failed (device not ready) ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1: link online but device misclassified, retrying ata1: link is slow to respond, please be patient (ready=0) ata1: softreset f........

My Samsung drive failed on me, at first I thought it was the enclosure but a direct SATA connection causes the same problems for discs that are inserted. It will work fine for a few minutes but then starts spewing the errors below. I've never been a fan of Korean made optical drives and have always had trouble with them. The problem is that I don't believe NEC and Lite-ON make drives anymore, and I considered them the leaders. Apr 7 11:58:48 bo........

[137392.910057] ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x80000 action 0x6 frozen [137392.910077] ata4: SError: { 10B8B } [137392.910095] ata4.00: cmd 60/20:00:00:00:00/00:00:00:00:00/40 tag 0 ncq 16384 in [137392.910099] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [137392.910122] ata4.00: status: { DRDY } [137392.910135] ata4: hard resetting link [137393.440060] ata4: SATA link........

I wanted to Import/Use a .vmdk hard disk image file from VMWare. Generally you can just "point" VirtualBox to it and use it and it will work but I found an exception. One of my Centos 4.4 x64 images wouldn't boot. I had two copies, an older one and the newer one. The older one booted as normal (once I changed the VirtualBox driver to IDE from SATA). The newer one stopped at the "GRUB loading" message no matter what I tried. As far as........

I separated the 2 drives in the RAID 1 array. 1 is the old one /dev/sda and is out of date, while the separated other one /dev/sdc was in another drive and mounted and used with more data (updated). I wonder how mdadm will handle this: usb-storage: device scan complete md: md127 stopped. md: bind md: md127: raid array is not clean -- starting background reconstruction raid1: raid set md127 active with 1 out of 2 m........

smartctl -a -d ata -T permissive --smart=on /dev/sda -d ata is usually required for most SATA drives or you get an error. -T permissive is required if it's the first time you are running SMART on this device (it's not enough just to enable SMART in the BIOS) --smart=on is also required for the first time........

From the package "parted" you can use the command "partprobe" to re-read the partition table. I really hate rebooting, and that's what Iloved to hear about AHCI motherboards, that they allow hotswap so you don't have to reboot. But that's only as good as the OS, if the OS does not reload the partition table you won't be able to do anything with that new drive you attached without rebooting. Yes, even without re-reading the partiton table Linux will........

NewEgg is one of the few companies that stocks this great right angle 1U SATA power cable. I've purchased some no-name ones and they face the wrong way (towards the bottom of the chassis) which makes it worse/impossible than standard SATA connectors. The price is high but if you're building a 1U server and want SATA disks and don't have much space (eg. the 1U Supermicro cases) then these are simply a must and........

I was starting to panic because suddenly my 1TB Seagate SATA drive wasn't working,I thought it was a BIOS issue because it seemed to have happened after I tried overclocking my Desktop too much. I tried powering down and waiting, but I still couldn't hear the drive spin up at all. I tried a second 1TB hard drive and it wouldn't work either. I checked all power connections again and again until one of the pins in the MOLEX connector popped completely loose. Th........

Inever saved any of the logs, but basically no matter what OS (Linux)I used, I could not get my 1000GB hard drive to work (Seagate SATA). The BIOS recognizes the drive and fdisk -l shows the hard drive as it should. The tricky thing is that different OS's will give you different results, but don't be fooled. You can't use these larger drives for long. Iwas getting all kinds of seek/IOerrors and also messages that the port could not be read.........

This is the Intel Atom 330 motherboard with integrated Realtek Gigabit NIC (Intel Desktop Board D945GCLF2 Motherboard W/ Atom 330 1.6 GHz Dual Core Processor - Mini-ITX) I cannot achieve more than 15 MB/s, even doing a local transfer through eth0 to it's own IP. 100% 95MB 15.9MB/s 00:06 So this is not a cabling, switch or hardware issue, it seems like a driver or chipset limitation problem. Here is my........

When trying to even cd or ls the mounted OCFS2 partition it crashes. Ithink this is a combination of VMWare Server's problem and the way I mounted and symlinked to it. More than anything this shows the problem and lack of forsight with VMWare, but also that OCFS2 is easily crashed if you do strange things. Output of /var/log/messages for OCFS2 Apr 10 15:57:45 localhost kernel: [84331.691258] Modules linked in: vmnet vmci vmmon ocfs2_stac........