Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Problem with damaged hard drive during bootup Post 302822155 by sai2krishna on Monday 17th of June 2013 05:03:30 AM
Old 06-17-2013
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:
Mod Comment Use code tags please.

Last edited by zaxxon; 06-17-2013 at 06:43 AM.. Reason: check your PMs
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Trying to copy old hard drive to new hard drive.

:confused: ........I have a new hard drive and I need to copy ALL info from the old to the new. I would like to use the dd command. I know the command is as follows...... dd if=/dev/rdsk/c1t1d0s0 of=/dev/rdsk/???????? Where I have the question marks is the problem. How do I find out what the... (4 Replies)
Discussion started by: shorty
4 Replies

2. Filesystems, Disks and Memory

The best partitioning schem for a 250GB Sata hard drive & a 75GB SCSI hard drive

Hi I have 2 75GB SCSI hard drives and 2 250GB SATA hard drives which are using RAID Level 1 respectively. I wana have both FTP and Apache installed on them as services. I'm wondering what's the best partitioning schem? I wana use FC3 as my OS, so, I thought I can use the 75GB hard drive as the /... (0 Replies)
Discussion started by: sirbijan
0 Replies

3. Solaris

Hard Drive error

I have a hard drive that we are trying to jumpstart in a sunblad 1500. we keep getting errors. I placed the drive in my 1500. I want to wipe the drive clean because for some reason it has a partition table. and when i go to format and try to format the drive it says it can not use a program. is... (5 Replies)
Discussion started by: deaconf19
5 Replies

4. SCO

USB hard drive problem

I have a USB hard drive attached to my SCO OSR6 machine I accidently powered it off while it was mounted and now the OS complains when you try to re-mount it and it appears that it is complaining because it has a new device number so it isn't at the original device location anymore. does anyone... (1 Reply)
Discussion started by: garycrow
1 Replies

5. Solaris

routing problem after replacing hard drive

Need to replace hard drive on Ultra 10 running Solaris 2.6. Bought new drive about the same size. Partitioned it differently to solve a space problem. After newfs used tar commands to copy most of the files to the new drive. Installboot took care of the boot file. ufsdump copied /dev and... (3 Replies)
Discussion started by: snorkack59
3 Replies

6. Filesystems, Disks and Memory

How do I check 4 physical damaged on Linux hard disks?

How do I check for physical damage on red hat linux hard disks? I tried smartctl /dev/sdb but it came back so fast saying it was ok. Is there a better linux command to check for bad sectors or physical disks in linux? Is there a good way such as with parted or something else? I normally in HP... (4 Replies)
Discussion started by: taekwondo
4 Replies

7. SCO

Booting problem due to adding hard drive incorrectly

I have tried to (unsuccessfully) add an old drive to get drivers (for the 3Com network card) onto a Sco Openserver 5.1 server. Now it wont boot: I used Sco Admin to do this. It have 3 scuzzi drives I added an IDE I think what I did wrong was add the IDE to existing space, and I should not have... (6 Replies)
Discussion started by: lappies67
6 Replies

8. Filesystems, Disks and Memory

Problem with accessing my 2nd hard drive

Hello I am having a problem with being able to use my 2nd hard drive as my new os doesn't recognize it. it is /dev/hdb2 and it shows as It is still in my system. it is a 73 gb hard drive and it is useless to me now. I used to have windows XP and had no problem with it,I have since changed to... (2 Replies)
Discussion started by: Donald Spauldin
2 Replies

9. UNIX for Beginners Questions & Answers

Problem setting path to external hard drive as a variable

Hello all, I am EXTREMELY new to using bash and I have a bit of a problem: I'm trying to set up a shell script that can 1.) take one of several giant files off of an external hard drive 2.) use it as input for scripts on my laptop's hard drive ... (3 Replies)
Discussion started by: machine_spirit
3 Replies
mt(1)							      General Commands Manual							     mt(1)

NAME
mt - Magnetic tape manipulating program SYNOPSIS
mt [-f tape_device] command [count] The mt program gives commands to a magnetic tape drive. OPTIONS
This option specifies the tape device to be manipulated. This option specifies the number of times that the operation is to be repeated. DESCRIPTION
If you do not specify a tape name with the -f option, the TAPE environment variable is used; if TAPE does not exist, mt uses the /dev/ntape/tape0_d0 device. Note that tape_device must refer to a raw (not block) tape device. By default, mt performs the requested operation once. You can perform operations more than once using the count option. The following commands are available: Backspaces count files. Backspaces count records. Writes count End-of-File marks at the current position on the tape. Forward spaces count files. Forward spaces count records. This option prepares a SCSI tape for loading into the device. Not all SCSI tape drives support this command. Rewinds the tape and places the tape unit offline (count is ignored). Bring a SCSI tape to the ready state if a tape is in the tape path. Currently, this command is only supported in the SCSI/CAM tape driver. Not all SCSI tape drives support this functionality. Rewinds the tape (count is ignored). Sets the tape at the specified read position coordi- nates. The data obtained when using the rdpos option can be used as an argument to the seek or seekds commands. Use the following options with the rdpos command: The read position short format. This option requires a tape coordinate argument in the following syntax: # mt -f /dev/ntape/tape1 rdpos s READ POSITION short format First block: 3 (0x3) Last block: 0 (0x0) Number of blocks: 0 (0x0) Number of bytes: 0 (0x0) The preceding example provides the following information: The block address associated with the current logical position. The block address associated with the next block to be transferred from the buffer to the medium. The number of data blocks that have not been written to the medium. The number of data bytes that have not been written to the medium. In addition to the information provided by the preceding example, the rdpos s option may display additional messages. Availability of these additional messages depends on the capabilities of the tape drive device. You will only see such error messages if the tape device is configured to detect the error state and to display the appropriate message: An error has occurred and the tape posi- tion cannot be returned. An error has occurred as the device is incapable of reporting block locations. Number of bytes in the buffer field does not represent the actual number of bytes in the buffer. Number of blocks in the buffer field does not represent the actual number of blocks in the buffer. The logical unit is positioned between early-warning and the end of media (EOM). The logical unit is at the beginning of media (BOM). The read position long format. This option requires an argument in the following syntax: # mt -f /dev/ntape/tape1 rdpos l READ POSITION long format File number: 0 (0x0) Block number: 3 (0x3) The following information is returned: The number of file marks between BOM and current logical position. The number of logical blocks between BOM and the current logical position. In addition to the information provided by the preceding example, the rdpos l option may display additional messages. Availability of these additional messages depends on the capabilities of the tape drive device. You will only see such error messages if the tape device is configured to detect the error state and to display the appropriate message: An error has occurred as the device is incapable of reporting block locations. File Number and Set Number are unknown The logical unit is positioned between early-warning and the end of media (EOM). The logical unit is at the beginning of media (BOM). The read position short format, with device-spe- cific addresses. This option only works on certain devices and requires a tape coordinate argument as for the s option. The output will be the same format as for the s option, although the device-specific data bytes may differ if the device supports its own format. Not all devices support their own format. If the d option is not supported by the device, the following error mes- sage will be displayed: MTIOCRDPOS (dev_specific): I/O error Space to end of recorded data. Currently, this command is only supported in the SCSI/CAM tape driver. Not all SCSI tape drives sup- port this functionality. Positions a tape at the specified coordinates. The output of the rdpos command may be used as an argument to this command. You can specify the value from the First block field when using the s option. Positions a tape at the specified coordinates. You can use the output from the rdpos command as an argument, and the syntax is as for the seek command. Unlike the general seek command, the seekds command is device-specific. Some tape devices provide a device-specific format for accessing the media position, which differs from the SCSI logical block format defined by the SCSI standard. The device-specific format may provide a faster way of seeking to a particular position on the tape. Prints status information about the tape unit. Prepares a SCSI tape for removal from the device. Not all SCSI tape drives support this functionality. Only as many characters as are required to uniquely identify a command need to be specified. EXIT STATUS
The mt command returns the following exit status: Success. Command was unrecognized. Operation failed. FILES
Raw magnetic tape interface with no rewind when closed. Raw magnetic tape interface with rewind when closed. SEE ALSO
Commands: dd(1) Functions: ioctl(2) mt(1)
All times are GMT -4. The time now is 04:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy