Failed To Identify I Error Err_mask 0x4
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct Ubuntu Wiki Community Wiki Other Support Launchpad Answers Ubuntu IRC Support AskUbuntu Official Documentation User Documentation Social Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support Hardware [ubuntu] ERROR: ata1.00 FAILED TO IDENTIFY Having an Issue With Posting ? Do you want to help us debug the posting issues ? < is the place to report it, thanks ! Results 1 to 5 of 5 Thread: ERROR: ata1.00 FAILED TO IDENTIFY Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode August 8th, 2008 #1 mortalic View Profile View Forum Posts Private Message 5 Cups of Ubuntu Join Date May 2007 Beans 21 SOLVED: ERROR: ata1.00 FAILED TO IDENTIFY Ok all you hardware uber geeks, I am stuck and need your help. I recently wiped 7.04 and installed 8.04 on my storage/printer server. The install failed trying to boot the live CD, drops me out to busybox with the following error over and over again: ata1.00 FAILED TO IDENTIFY (I/O ERROR. ERR_MASK=0X4) failed to recover some devices unable to find a medium containing a live file system After a fair amount of searches I found out that the Dell Vostro's suffer from this same issue and there are two workarounds. You can change your Bios Sata type to RAID (even if you don't have a raid) or you can add all_generic_ide to the grub menu.lst file. The bios option did not appear to work (I don't have a dell, it's an asus A8V-MX motherboard) so I added
Technology - unRAID Server Community » Legacy Support (unRAID 5 and Older) » General Support (V5 and Older) » Is error log showing HDD Problems? [SOLVED] « previous next » Send this topic Print Pages: [1] Go Down Author Topic: Is error log showing HDD Problems? [SOLVED] (Read 7927 times) Kandinsky Member Posts: 28 Is error log showing HDD Problems? [SOLVED] « on: May 19, 2013, 05:29:16 AM » Dear Experts,I am getting the errors below which seem to be repeating themselves over a short period of time. Should I be worried, if so how can I identify which https://ubuntuforums.org/showthread.php?t=883335 drive is looking dodgy please? I am using the latest 12a release.Now with full syslog attached. Not sure which drive I need to give any smart report on since I don't know which one it is.May 19 12:20:10 GOOGOLPLEX kernel: ata1.00: exception Emask 0x50 SAct 0x0 SErr 0x800 action 0x6 frozen (Errors)May 19 12:20:10 GOOGOLPLEX kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors)May 19 12:20:10 GOOGOLPLEX kernel: ata1: SError: http://lime-technology.com/forum/index.php?topic=27491.0 { HostInt } (Errors)May 19 12:20:10 GOOGOLPLEX kernel: ata1.00: failed command: IDENTIFY DEVICE (Minor Issues)May 19 12:20:10 GOOGOLPLEX kernel: ata1.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in (Drive related)May 19 12:20:10 GOOGOLPLEX kernel: res 50/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x50 (ATA bus error) (Errors)May 19 12:20:10 GOOGOLPLEX kernel: ata1.00: status: { DRDY } (Drive related)May 19 12:20:10 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues)May 19 12:20:20 GOOGOLPLEX kernel: ata1: softreset failed (1st FIS failed) (Minor Issues)May 19 12:20:20 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues)May 19 12:20:30 GOOGOLPLEX kernel: ata1: softreset failed (1st FIS failed) (Minor Issues)May 19 12:20:30 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues)May 19 12:20:31 GOOGOLPLEX kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related)May 19 12:20:31 GOOGOLPLEX kernel: ata1.00: link online but device misclassified (Drive related)May 19 12:20:36 GOOGOLPLEX kernel: ata1.00: qc timeout (cmd 0xec) (Drive related)May 19 12:20:36 GOOGOLPLEX kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) (Errors)May 19 12:20:36 GOOGOLPLEX kernel: ata1.00: revalidation failed (errno=-5) (Minor Issues)May 19 12:20:36 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues)May 19 12:20:46 GOOGOLPLEX kernel: ata1: softreset failed (1st FIS failed) (Minor Issues)May 19 12:20:46 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues)May 19 12
Post #1 of 2 (1225 views) Permalink ata errors on startup (I/O error, err_mask=0x4) Hello, I've recently made a few changes to my machine, and one of the unfortunate side effects http://www.gossamer-threads.com/lists/gentoo/user/226964 is the following error. Mar 5 17:15:32 localhost kernel: [ 7.396912] ata14.00: qc timeout (cmd 0xa1) Mar 5 17:15:32 localhost kernel: [ 7.398906] ata14.00: failed to IDENTIFY (I/O error, err_mask=0x4) Mar 5 17:15:32 localhost kernel: [ https://devtalk.nvidia.com/default/topic/969972/jetson-tx1/sata-controller-marvell-9230-doesn-t-work-on-tx1/ 7.706463] ata14: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Mar 5 17:15:32 localhost kernel: [ 17.691838] ata14.00: qc timeout (cmd 0xa1) Mar 5 17:15:32 localhost kernel: [ 17.742749] ata14.00: failed to IDENTIFY (I/O error, failed to err_mask=0x4) Mar 5 17:15:32 localhost kernel: [ 17.792643] ata14: limiting SATA link speed to 1.5 Gbps Mar 5 17:15:32 localhost kernel: [ 18.098235] ata14: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Mar 5 17:15:32 localhost kernel: [ 48.103265] ata14.00: qc timeout (cmd 0xa1) Mar 5 17:15:32 localhost kernel: [ 48.154184] ata14.00: failed to IDENTIFY (I/O error, err_mask=0x4) Mar 5 17:15:32 localhost kernel: [ 48.509669] ata14: SATA link up 1.5 Gbps (SStatus failed to identify 113 SControl 310) This causes my boot to pause while the kernel probes ports, which I'm fairly confident do not exist. I have x5 sata devices attached to my computer. They are all reported, and work great. I'm not sure where it's getting "ata14 from". I recently RMA'd my motherboard, and one of the first side effects I noticed was my ethernet (eth0) was completely missing. Through google, I found out udev had written the old device info from my previous motherboard in /etc/udev/rules.d/70-persistent-net.rules. Simply deleting this file and rebooting fixed that. Is it possible something very similar is going on here, but with my ata devices? I also swapped out a few disks today. I dropped an old raid0 in favor of an ssd, but everything went fine as far as I can tell. I'm not positive, but I think this error existed before I did this. Thanks for your time, Alan bluemoonshine at gmail Mar5,2011,11:04PM Post #2 of 2 (1177 views) Permalink Re: ata errors on startup (I/O error, err_mask=0x4) [In reply to] I was able to stop the errors by disabling the Marvell controller from within my bios. Thanks, Alan On Sat, Mar 05, 2011 at 06:45:33PM -0600, Alan Warren wrote: > Hello, > I've recently made a few changes to my machine,