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

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

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

If you remove the white label on the chip (near the CMOS battery) you will find the following details about it: SST 49LF080A 33-4C-NHE It is the PLCC32 type and can be pried and removed safely (but be very careful) with an eye glass flat head screw driver. If you just have a bad flash you may be able to reprogram your original or just buy another one with the part# above and reprogram it. This is great news for people who have bricked th........

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

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

I'm using ecryptfs and was suddenly unable to access or even ls my home directory (but every subfolder is accessible). It just hangs and throws this message in messages/dmesg: Either the lower file is not in a valid eCryptfs format, or the key could not be retrieved. Plaintext passthrough mode is not enabled; returning -EIO I read somewhere that perhaps some file or folder is owned by root somehow, sure enough there are some and sudoing to root allows me to........

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

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

NOTICE[11389]: rtp.c:1808 ast_rtp_read: Unknown RTP codec 100 received from I've found that trying several times may work, but I also read changing your Sipura VOIP adapter settings as follows helps (but it still fails for me sometimes): In adapter change the following under SIP/Advanced Codec to G711a from G711u Passthru Method from: NSE to ReINVITE FAX CED Detect Enable: Yes FAX CNG Detect........

This really made me nervous but notice the mdstat says "check". This is because in Ubuntu there is a scheduled mdadm cronscript that runs everyday on Sunday at 00:57 that checks your entire array. This is a good way because it prevents gradual but unnoticed data corruption which Inever thought of. As long as the check completes properly you have peace of mind knowing that your data integretiy is assured and that your hard drives are functioning properly (I'........

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

The solution is simple but it's a wonder why VBOX doesn't address it directly? Perhaps newer versions will but you have to add your user to the "vboxusers" group and then login and logout and you'll see the devices you wanted but couldn't access are now available. The weird thing is that the grayed out issue doesn't happen with all devcies but one notable thing is the Apple iPhone especially in DFU or Recovery Mode which is an big issue for some people.........

I finally decided to look into some utils that did this, and the first one I found is "mp3burn". It is unbelievable simple and perfect. *2017-11 update and mp3burn is still available in standard repos such as Ubuntu 14/16 so this is a current and working project. Just install the package and it gets all required libraries to convert and then burn's on the fly. And you won't believe how simple it is. I just want to a directory that had the MP3's I wanted t........

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

The binary "iostat" comes from the package "sysstat" and is available on all Linux/Unix like platforms. Use the "-m" option to give you what you probably want, which is to see in MB/s how much bandwidth each disk is doing. iostat -m Linux 2.6.24.2 ((none)) 04/16/10 avg-cpu: %user %nice %system %iowait %steal %idle ........

Starting/Creating Serviceshttp://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-starting-services.html That might help........

top - 09:34:12 up 2 days, 20:57, 2 users, load average: 1.83, 1.99, 2.03 Tasks: 59 total, 2 running, 57 sleeping, 0 stopped, 0 zombie Cpu(s): 0.3%us, 0.0%sy, 0.0%ni, 0.0%id, 99.7%wa, 0.0%hi, 0.0%si, 0.0%st That 99.7% wa is iowait, it means the server is waiting for a process to complete an IOoperation or in plain English, there is a delay in........