Problem with damaged hard drive during bootup | Unix Linux Forums | UNIX for Dummies Questions & Answers

  Go Back    


UNIX for Dummies Questions & Answers If you're not sure where to post a UNIX or Linux question, post it here. All UNIX and Linux newbies welcome !!

Problem with damaged hard drive during bootup

UNIX for Dummies Questions & Answers


Tags
bootup, damaged hdd, driver, frozen, kernel

Closed Thread    
 
Thread Tools Search this Thread Display Modes
    #1  
Old 06-17-2013
sai2krishna sai2krishna is offline
Registered User
 
Join Date: Jan 2013
Last Activity: 13 September 2013, 2:15 AM EDT
Posts: 7
Thanks: 0
Thanked 0 Times in 0 Posts
Ubuntu Problem with damaged hard drive during bootup

Hello,

I have a problem with the hard drive connected to my setup. When I connect the HDD which is damaged, and try to bring up my system, I get some error messages continuously on my console saying


Code:
ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 frozen
ata2.01: failed command: READ DMA
ata2.01: cmd c8/00:08:00:00:00/00:00:00:00:00/f0 tag 0 dma 4096 in
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata2.01: status: { DRDY }
ata2.00: SRST failed (errno=-19)

After some time, the system boots up well. Whenever I try to execute some command related to HDD, it is struck.

How can I avoid the delay that is being taken initially during bootup?

Is there any way in the driver code where we can say kernel not to probe for the HDD if it is not able to recognize it well? Please help me...

Thanks in advance...

Regards,
Sai

Moderator's Comments:
Use code tags please.

Last edited by zaxxon; 06-17-2013 at 05:43 AM.. Reason: check your PMs
Sponsored Links
    #2  
Old 06-17-2013
Corona688 Corona688 is offline Forum Staff  
Mead Rotor
 
Join Date: Aug 2005
Last Activity: 21 October 2014, 6:30 PM EDT
Location: Saskatchewan
Posts: 19,635
Thanks: 816
Thanked 3,335 Times in 3,124 Posts
You should remove the faulty drive.
Sponsored Links
    #3  
Old 06-18-2013
bakunin bakunin is offline Forum Staff  
Bughunter Extraordinaire
 
Join Date: May 2005
Last Activity: 21 October 2014, 5:38 PM EDT
Location: In the leftmost byte of /dev/kmem
Posts: 4,285
Thanks: 45
Thanked 824 Times in 651 Posts
You haven't told us which OS you use, but from the log i guess it is some Linux. (We shouldn't have to guess at all, so please describe always your environment.)

If so, the part probing your hardware is called "udev" and it is rule-based. Basically it scans the system permanently for (new) hardware and then executes some rule-based methods to create "devices" (=respective entries in the "/dev" hierarchy) for newly found hardware. This thing not only managed your harddisks, but also, if you are to put in (or remove) an USB stick, for instance. I suggest you read carefully the man page for "udev" to understand how it works and how certain devices (disks among them) can be "blacklisted" from probing.

If this still leaves questions feel free to ask again.

I hope this helps.

bakunin
    #4  
Old 06-18-2013
sai2krishna sai2krishna is offline
Registered User
 
Join Date: Jan 2013
Last Activity: 13 September 2013, 2:15 AM EDT
Posts: 7
Thanks: 0
Thanked 0 Times in 0 Posts
Ubuntu

Hi Bakunin,

Thanks for your reply. I'm working in Linux environment.

I just wanted to explain more about the problem.

The system is still in the initial state when the delay is considered. I mean, it did not proceed till creating device nodes and all that stuff. Initially when the kernel is checking whether all the devices attached are fine, when it finds the damaged HDD, it is struck. It goes on checking and finally after some time, it reboots and then goes ahead bringing up the system.

I was asking how can we avoid the initial delay when kernel is probing for the damaged HDD?

Thanks and Regards,
Sai.
Sponsored Links
    #5  
Old 06-18-2013
bakunin bakunin is offline Forum Staff  
Bughunter Extraordinaire
 
Join Date: May 2005
Last Activity: 21 October 2014, 5:38 PM EDT
Location: In the leftmost byte of /dev/kmem
Posts: 4,285
Thanks: 45
Thanked 824 Times in 651 Posts
Quote:
Originally Posted by sai2krishna View Post
The system is still in the initial state when the delay is considered.
This is a similar process like "udev", but controlled via "GRUB". You should research the "GRUB" (or "GRUB2", depending on which Linux system you use) documentation how to exempt a certain drive from being scanned.

I hope this helps.

bakunin
Sponsored Links
Closed Thread

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
Problem with accessing my 2nd hard drive Donald Spauldin Filesystems, Disks and Memory 2 05-23-2010 02:20 PM
How do I check 4 physical damaged on Linux hard disks? taekwondo Filesystems, Disks and Memory 4 12-17-2009 08:42 AM
routing problem after replacing hard drive snorkack59 Solaris 3 05-02-2009 11:24 PM
USB hard drive problem garycrow SCO 1 06-12-2008 06:15 PM
The best partitioning schem for a 250GB Sata hard drive & a 75GB SCSI hard drive sirbijan Filesystems, Disks and Memory 0 04-05-2006 02:19 PM



All times are GMT -4. The time now is 09:50 AM.