On 9/19/20 10:37 PM, Long Wind wrote:
i'm creating FS on problem disk
though it has passed short and long tests by smart tool
i meet bad sector, mkfs complains forever
Ctrl+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 }
One thing to check is whether part of what's happening is driven by the
onboard disk driver. Consumer grade drives try very hard to read bad
blocks, leading to very long timeouts that drag a machine to its knees.
(Learned this the hard way, trying to figure out why a server, with
raided disks, just kept going slower... and slower... and slower.)
By contrast, server-grade drives just give up after the first try -
letting RAID do its thing.
You might want to check the specs on your drive, and run a deep set of
diagnostics, starting with the more intrusive smart diagnostics.
Miles Fidelman
--
In theory, there is no difference between theory and practice.
In practice, there is. .... Yogi Berra
Theory is when you know everything but nothing works.
Practice is when everything works but no one knows why.
In our lab, theory and practice are combined:
nothing works and no one knows why. ... unknown
