Unterhaltung
Nachrichten
-
well, 395211 MB copied, out of about 1.1TB... no errors so far, but every now and then it... *pauses*, or seems to: that suggests it has trouble reading some sectors, though it ultimately succeeds. nothing I can do about that,and I do…
-
@mk you can check with dmesg if Linux had difficulties at reading from a disk
-
@mcscx I know it tells me about IO errors, but I've never seen anything about needing retries to successfully read
-
@mk by now (the next morning) ddrescue has made it past the data area (total data about 1.1TB, it's now copied 2389 GB); it also shows 'errsize: 3559 kB errors: 6'; more interesting, read speed has considerably slowed down: the *curre…
-
@mk I think I've seen messages when a drive is trying hard to reread a block, but not sure. Also interesting: smartctl -a /dev/...
-
@mcscx I remember low-level tools under DOS (MS or DR) could reveal these retries; for a floppy the standard was up to 5 attempts before the OS would get a signal: these tools would talk directly to the controller, I think. Then there…
-
@mcscx another last-resort technique can be used if the bad blocks are localized near each other: partition "around" them, by creating 2 or more partitions that avoid the bad area. That's another technique I've used successfully under…
-
@mk the first 'sweep' of ddrescue is now finished - still "6 errors" which (going by the log file) are 6 areas *between* the completely "finished" blocks. The next "sweep" will now try to "fill in" blocks inside those error areas (tho…
-
@mk actually, that was super-fast: it merely "consolidated" the bad/unsplit areas into single bad blocks. So, now we let e2fsck loose on the 'rescued' result...
-
@mk you can partition around areas of bad blocks in Linux. But disks with bad blocks tend to get more bad blocks.
-
@mk I think I have seen reread messages in dmesg at with (IDE?) cdrom drives - but I'm not sure anymore and you may be right.
-
@mcscx you can do that in any partitioning tool on any OS - you just need to know where the bad blocks *are*. But given that bad blocks can have different causes, that may, or may not be sufficient - whether there will be more bad blocks depends on the cause
-
@mk Maybe you can refresh magnetisation w/ "badblocks -n". It reads each block,does some write tests & finally rewrites the original content
-
@mcscx yes, as a non-desctructive approach. but as I already have pulled off all the data that can be pulled off, I'm going to do a 'scrub' instead. But even my previous test run may have improved things a little - I just don't have a…
-
@mcscx I vaguely remember some DOS tool that literally showed you a counter for each read - up to the default maximum of 5 - on floppies this was quite remarkable, you could see it "aging". What was even more remarkable was that as it…
-
Alle Inhalte und Daten von 1w6 uRPG sind unter der