[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: linux isn't robust enough to handle bad sector??



Long Wind wrote: 
> i'm creating FS on problem disk 
> though it has passed short and long tests by smart tooli meet bad sector, mkfs complains foreverCtrl+C can't kill it, what should i do NOW??
> [ 2719.089156] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
> [ 2719.089171] ata4.00: failed command: WRITE DMA EXT
> [ 2719.089185] ata4.00: cmd 35/00:00:18:68:e1/00:08:0c:00:00/e0 tag 0 dma 1048576 out
> ?????????????????????????????????????????????? res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
> [ 2719.089192] ata4.00: status: { DRDY }
> [ 2719.089209] ata4: hard resetting link
> [ 2719.404384] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> [ 2719.412162] ata4.00: configured for UDMA/33
> [ 2719.412199] ata4: EH complete
> [ 2749.813187] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
> [ 2749.813201] ata4.00: failed command: WRITE DMA EXT
> [ 2749.813208] ata4.00: cmd 35/00:00:18:68:e1/00:08:0c:00:00/e0 tag 0 dma 1048576 out
> ?????????????????????????????????????????????? res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
> [ 2749.813212] ata4.00: status: { DRDY }
> 


In order of most likely to least likely:

- replace the disk
- replace the cabling to the disk
- replace the disk controller
- replace the power supply

You can scan for bad blocks with the badblocks tool, but if you
have repeated problems like this, the disk is probably not reliable.

If you need your data to survive events like this later in the
disk's life, you will need backups, RAID, ZFS, or similar
measures.

-dsr-


Reply to: