[ubuntu] Disk error: ata3.00: status: { DRDY ERR

ata1:00: Status: DRDY ERR
ata1.00: UNC error
ata1:00: Exception mask 0x0 SAct 0x0 SErr 0x0 0x0
ata1:00: measures BMDMA 0x25 statistics
ata1:00: Failed to manage: DMA

indicates a read command that READ ATA dma to the drive forwarding ATA port 1 failed (status includes ERR for errors). probably Port is a hard drive error and also indicates the desired problem. Now the DMA part can be skipped; DMA is direct memory access which is the main transfer mode these days and while you have RAM or RAM bus issues while you repeat something like this you will probably see more errors per ton if the whole body couldn’t work at all.

end_request: fatal target error, dev sda, marketplace 32839936
Error EXT4_fs: (device sda5): ext4_find_entry: 935: inode #393217: comm init: reading send pages lblock 0
INIT: Inittab file not found

currently indicates there is a problem in /dev/sda part 32839936 which physically adds 512-byte sectors to the end associated with the /dev/sda5 partition which adds what is device with mounts sda5< /code> as reported by the file driver processmy system. The error reported by init, together with the details of the specific file system driver error, indicates a problem with the directory system that makes /etc/inittab difficult to access (less or more likely) and unreadable. This could mean that the current list of root directories, the /etc directory, or the /etc/inittab file entry is somehow related to the corruption. Given the variety of inodes, I would try /etc/inittab as the specific culprit until proven otherwise.

Suspecting a hard drive failure, I removed it and used it on another as a USB PC and an external hard drive, I can mount and view all the partitions and files on it. So I'm assuming the drive is in good condition. Suppose

I think your assumption is unfounded. The computer clearly has other problems; I hope this can be easily fixed.

The first thing I could do in your situation would be to update my backup right where it is on this drive. Make sure you don't overwrite or even delete anything from your current save, thow you may need the situation. Perhaps the best option is to create a fresh backup of everything you have access to on your new drive (or whatever you've previously used yours for your own backups). Expect S I/O errors when you copy create, source where. recovery

Attempt takes second place. Hopefully, given the bugs, this will be seen as one or more sectors where the disease caused a small volume indicating corruption in the file system, in which case e2fsck will be able to replace most of the corruption. Some of your files may be missing, but with any luck you may find them in /lost+found under the root filesystem setup. e2fsck did everything he could. If not, compare with the most recent backup prior to the onset of symptoms, and restore the appropriate files from the backup from there. (Did I mention that backups are useful when bad things happen that are inevitable?)

Third, the question is whether the reader can really be trusted in the future. I would say thata few bad sectors aren't a disaster from a disk point of view, but spinning drives around 100GB don't refill today in many form factors, suggesting you can use this relatively old hard drive. Personally, I'd probably just accept that the reader's control life is preserved at this point and get a replacement, again, I'm pretty paranoid when it comes to my data; Your mileage can vary very well. You have to weigh the cost of the trip to replace with the risk of complete drive failure and subsequent loss of all data on the drive.

View Full Version: [ubuntu] disk Error Ata3 disk:.00: Status: DRDY ERR

Powered by vBulletin® version 4.2.2 Copyright VBulletin © 2022 Solutions, Inc. All rights reserved. .All .

I .always .use .firewood .with .my .system .with .these .spams:

.News ...........
68489.756311] ata3.00: Status: DRDY ERR
[68489.756314] ata3.00: Error: UNC
[68489.951583] ata3.00: designed for UDMA/133
[68489.951604] ata3: EH completed
[68492.671124] ata3.00: emask exception 0x0 0x0 sact SErr Action 0x0 0x0
[68492.671133] ata3.00: stats 0x24 BMDMA
[68492.671140] ata3.00: cmd c8/00:08:55:e8:8d/00:00:00:00:00/e2 0 Dma registration In
[68492 4096.671142] resolution (error 51/40:00:56:e8:8d/00:00:00:00:00/02, drdy err unc media error 0x9)
[68492 emask.671145] ata3.00: Status: DRDY ERR
[68492.671148] ata3.00: Error: UNC
[68492.899657] ata3.00: configured for UDMA/133
[68492.899678] ata3: EH finished
[68495.610841] ata3.00: Emask Exception 0x0 sact 0x0 0x0 serr Action 0x0
[68495.610851] ata3.00: stats 0x24 BMDMA
[68495.610857] ata3.Cmd 00:c8/00:08:55:e8:8d/00:00:00:00:00/e2 label Dma 0 4096 in
[68495.610859] 51/40:00:56:e8:8d/00:00:00:00:00/02 res Emask (media error 0x9)
[68495.610863] ata3.00: Status: DRDY ERR
[68495.610865] ata3.00: Error: UNC
[68495.799599] ata3.00: configured for UDMA/133
[68495.Sd 2:0:0:0: 799620] [sda] Result: driverbyte=DRIVER_SENSE,SUGGEST_OK
[68495 hostbyte=DID_OK.Sd 799626] 2:0:0:0: [sda] Recognition key: average error [current] [handle]
[68495.Details 799631] descriptor values ​​with descriptors value Hex):
[68495 (in.799633] 72 03 04 11 50 00 0c 00 00 0a 00 sixty 00 00 00 double zero
[68495.799643] 8d 02 E8
[68495 60.799647] sd 2:0:0:0: [sda] Add. Meaning: Read Error Resolved - Failed to remap Cars and Trucks
[68495.799653] end_request:I/O error, development sda, field 42854486
[68495.799675] ata3: EH completed
[68495.800096] sd 2:0:0:0:625142448 [sda] (hardware capacity MB, 320073 512 bytes)
[68495.817023] sd 2:0:0:0: [sda] write protection disabled
[68495.817030] sd 2:0:0:0: [sda] Mode 00 detection: 3a 00
[68495 50.819042] 2:0:0:0: SD cache [sda]: write, simple read cache: enabled, no DPO or FUA support
[68495.826120] 2:0:0:0: [sda] sd 625142448 512 hardware sectors (320073 bytes MB)

I just replaced the hard drive, but the spam messages are still systemic. Can anyone help me? I am also attaching the log from the dmesg command output.

You app From 8 ubuntu.10 II
Processor 3 GHz
320 GB Fixed Disk
2 GB memory

This is kernel bug in ata acpi
Set libata options to /etc/modprobe noacpi=1.d/options
solved this problem too

I have the same problem with an XPS M1330 between Dell and this exact same error. I even tried to install Intrepid Funny thing is that a well configured OS takes time to boot up when an error occurs which leads me to believe it will be a bad disk, well how can I assume your hardware is bad when I can uninstall the OS(Hardy 8.04) with which it ships. OH BOY.know

You that last night my laptop was working fine, it happens right after installing new updates. Aren't these people testing these updates?

However, a failed hard drive may exist and you may have a bad cable connection, cables may or may not have obstructions, microscopic be prepared for many hard drive problems!