O Error Err_mask 0x1
Contents |
HCL Search Reviews Search ISOs Go to Page... LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware [SOLVED] Failing harddrive? User Name Remember Me? Password Linux - Hardware This forum is for Hardware issues. Having trouble installing a piece of hardware? Want to revalidation failed (errno=-5) know if that peripheral is compatible with Linux? Notices Welcome to LinuxQuestions.org, a friendly and active ata failed to identify (i/o error err_mask=0x4) Linux Community. You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our
Did_bad_target
newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today! Note that registered members see fewer ads, and ContentLink is completely disabled once you log
Exception Emask 0x0 Sact 0x0 Serr 0x0 Action 0x6 Frozen
in. Are you new to LinuxQuestions.org? Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here. Having a problem logging in? Please visit this page to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward result hostbyte did_error driverbyte driver_ok new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Click Here to receive this Complete Guide absolutely free. Search this Thread 05-14-2011, 07:53 AM #1 vibes LQ Newbie Registered: Oct 2008 Posts: 9 Rep: Failing harddrive? Hi, I have a server thats running debian 6 (squeeze) amd64, the other day the server become unresponsive, the thing is someone setup this server for me, 3 have 3 hard drives in it one SSD 60gb drive that holds the root and also a partition for mysql, Below is a log of the crash but it lists sda as failing but towards the bottom it also hints at sdc failing, could it infact be something else? Iv run badblocks on the drives and it reports no errors also smartctrl reports no problems. Can anyone help in figuring out whats going on? Code: uname -a Linux server1 2.6.32-5-openvz-amd64 #1 SMP Mon Mar 7 22:25:57 UTC 2011
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
Terminate Command Early Due To Bad Response To Iec Mode Page
Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login failed command: write fpdma queued 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 failed command: read fpdma queued 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 http://www.linuxquestions.org/questions/linux-hardware-18/failing-harddrive-880698/ 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 https://ubuntuforums.org/showthread.php?t=883335 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 the line to grub. This got me through the install and everything. I started to copy all my data from one sata drive to the other (about 320ish GB) and it is telling me that I will need to wait 44hours!!!!!! Obviously there is a performance hit when you use the all_generic_ide option. Can someone possibly explain how to actually fix this issue? the way I see it, I can research this for 2 days and if we can figure it out I'll still come out ahead! Thanks! Let me know what other information I can post! Last edited by mortalic; August 9th, 2008 at 06:44 AM. Reason: SOLVED Adv Reply August 8th, 2008 #2 mc4man View Profile View Forum Posts Private Message . Join Date Jun 2007 Beans 15,566 Re: ERROR: ata1.00 FAILED TO IDENTIFY I've never had any issues with drives ect. so if this is a dumb response I do apologize. Now that yo
very different issues. Some experience in analyzing these errors is therefore recommended, because the steps to resolve the problem are https://lime-technology.com/wiki/index.php/The_Analysis_of_Drive_Issues highly dependent on what the real problem is. For example, some errors point to a bad cable, other very similar messages point to a failing drive, and others may point to a bad disk controller, poor or incorrect driver, bad or insufficient power to the drive, etc. There have been too many cases of drives thrown out or returned by an RMA o error process, when the problem was just a bad cable! This page has been designed to help with the analysis of drive problems, and often to recommend what steps to take. The two most important tools for initial analysis are the syslog and the SMART report. Getting the syslog Use UnMENU, go to the Syslog plugin and view and download the syslog o error err_mask from there Capturing your syslog Viewing the System Log As of version 4.5beta2 of unRAID: - May now read syslog directly via browser by referencing 'http://tower/log/syslog' (substitute 'tower' with your server name). Getting the SMART report Troubleshooting page, Obtaining a SMART report section Contents 1 Drive problems by keyword 2 Drive problems by error message 2.1 Drive Interface Issues 2.1.1 Drive interface issue #1 2.1.2 Drive interface issue #2 2.1.3 Drive interface issue #3 2.1.4 Drive interface issue #4 2.2 Physical Drive Issues 2.2.1 Drive media issue #1 2.3 Other Drive Issues 2.3.1 Unexpected loss of removable drive 2.3.2 Unexpected loss of hard drive 2.3.3 File system errors 3 Additional references Drive problems by keyword These words or phrases are found within the syslog within lines including and following the phrase "exception EMASK". Some are error flags, some are not. Look up the words you see in the list below, to help you determine what kind of issue you have, and possible steps to take. Drive issues are primarily either drive interface issues (the disk controller, drivers, cables, and power to the drive)