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........

This is the reason that I don't like the new ADATA USB drives such as the UV128/64GB or 128GB drives and other ones that look to be the same style (the green sliding USB connector). They just don't work well from new and never work properly at any point. [ 788.242463] usb 1-1.2: new high-speed USB device number 16 using ehci-pci [ 788.339816] usb 1-1.2: New USB device found, idVendor=125f, idProduct=db8a [ 7........

sudo pip3 install python-docx [sudo] password for : Downloading/unpacking python-docx Downloading python-docx-0.8.10.tar.gz (5.5MB): 5.5MB downloaded Running setup.py (path:/tmp/pip_build_root/python-docx/setup.py) egg_info for package python-docx no previously-included directories found matching 'docs/.build' warning: no previously-included files matching '.DS_Store' foun........

growisofs -Z /dev/sr0 critical.tar.gz.gpg Executing 'genisoimage critical.tar.gz.gpg | builtin_dd of=/dev/sr0 obs=32k seek=0' I: -input-charset not specified, using utf-8 (detected in locale settings) File critical.tar.gz.gpg is larger than 4GiB-1. -allow-limited-size was not specified. There is no way do represent this file size. Aborting. :-( write failed: Input/output error #remember to us........

Before getting into the output here is my typical experience with SMART, there is what I call a "bad disk" with pending and uncorrectable sectors that cannot be reallocated. It has caused a kernel panic and system crash repeatedly as we can see from the logs. But SMART says it has "PASSED" its self assessment. SMART is still useful to me but it is more about looking at Current_Pending_Sector. Any time I have had anything but 0 for that attribute it........

dvd+rw-mediainfo /dev/sr0 INQUIRY: [ASUS ][BW-16D1HT ][3.00] GET [CURRENT] CONFIGURATION: Mounted Media: 11h, DVD-R Sequential Media ID: RITEKF1&n........

This is a 8TB Seagate external USB 3.0 device apparently newer kernels use a module called "UAS" instead of "USB Storage" which causes issues as a lot of devices are not properly supported in UAS mode by the kernel driver. The solution some say is to disable UAS specifically for your USB device but I'd rather just disable UAS altogether. Solution blacklist UAS: *do not do this it does not work and just causes your USB 3.0........

Here is a simple MP3 player and now there's a reason to understand why the supplied cable has some kind of capacitor and is very short. These devices can be VERY finicky and any voltage fluctuation or difference is enough to cause issues. Take for example the error messages from Linux Mint: [804829.895414] usb 1-1: USB disconnect, device number 11 [806961.109030] usb 1-1: new high-speed USB device number 12 using xhci_hcd........

These errors believe it or not are simply because of not being the root user or running with sudo! However if you didn't know to try as root you'd think there was a problem with your burner or disc Essentially it looks like without root you cannot send the required scsi commands to continue writing. Ithink cdrecord should have built-in tests or safeguards to see if it has the permissions to run the required commands. I guess for more advanced users the idea is simila........

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........

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........

This is just trying to read 5GB off the drive with dd and the drive initially tested ok but shortly after I wondered why I was seeing 2MB/s read speeds. Notice the "current_pending_sector", anytime I've seen it at anything above 0 even with no other bad fields/attributes, it means the drive is bad. ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0 ata1.00: irq_stat 0x40000008 ata1.00: failed command: READ FPDMA QUEUED ata1.00: cmd 60/00:00:........

[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........

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........