In article ,
Erick Perez - Quadrian Enterprises wrote:
> @tonymountifield
> Does this still hold true?
> https://superuser.com/a/1075837
It wouldn't surprise me. What I take away from those tests is that it is indeed
important to use a bs= setting that corresponds to the disk physical block size,
"It is alive"! Fantastic.
So I got a new SSD (500G) to replace the OLD rotating disk (320G) and
played with trying to copy off the data for days... Finally got that with
everyones help.
Today I copied the data to the new 500G disk and it BOOTED and running.
Monday is way better than Friday was!
T
Thanks everyone for the suggestions. I finally got a completion with this
command:
dd conv=noerror,sync iflag=direct bs=4096 if=/dev/sdb of=disk.img
Copying it now to see if it worked.
Jerry
___
CentOS mailing list
CentOS@centos.org
https://lists.cento
@tonymountifield
Does this still hold true?
https://superuser.com/a/1075837
On Sun, Sep 27, 2020 at 7:21 AM Tony Mountifield wrote:
> In article ,
> Valeri Galtsev wrote:
> >
> >
> > > On Sep 26, 2020, at 8:05 AM, Jerry Geis wrote:
> > >
> > > I have a disk that is flagging errors, attempting
In article ,
Valeri Galtsev wrote:
>
>
> > On Sep 26, 2020, at 8:05 AM, Jerry Geis wrote:
> >
> > I have a disk that is flagging errors, attempting to rescue the data.
> >
> > I tried dd first - if gets about 117G of 320G disk and stops incrementing
> > the save image any more.
>
> did you t
On 9/26/20 12:40 PM, Jerry Geis wrote:
Hello
I did try the "dd conv=noerror …"
The ddrescue - doesnt stop - it just doesnt "continue" past a certain
point. Somewhere around the 117G mark - it just doesnt go past that .
(same with dd, gets to 117G and just doesnt continue.
I have let the dd run a
I will suggest using dmesg -w to monitor during dd the sector numbers that
fail in order to skip them.
Also, perhaps the timeout of each read error is killing you (default 30
seconds) and you may have thousands.
On linux, /sys/block//device/timeout (such as
/sys/block/sda/device/timeout) is the t
Well, I'm not a noted expert on ddrescue, but my limited experience tells
me that when it hits bad spots (or a big cluster of them) it can go very
slowly as it tries multiple times to read each sector (or track, I'm not
sure which, in this case). It keeps a list of bad spots and goes back at
the en
Hello
I did try the "dd conv=noerror …"
The ddrescue - doesnt stop - it just doesnt "continue" past a certain
point. Somewhere around the 117G mark - it just doesnt go past that .
(same with dd, gets to 117G and just doesnt continue.
I have let the dd run all night - did not go past the 117G.
Tha
Also, does ddrescue "stop" (as in quit) or is it just stuck there spending
a lot of time trying to read one or more bad spots? it is intended to keep
trying until it gets something, or gives up and skips to the next
track/sector/whatever. If you let it go for a long time (overnight???) does
it proc
> On Sep 26, 2020, at 8:05 AM, Jerry Geis wrote:
>
> I have a disk that is flagging errors, attempting to rescue the data.
>
> I tried dd first - if gets about 117G of 320G disk and stops incrementing
> the save image any more.
did you try
dd conv=noerror …
this flag makes dd not stop on in
I have a disk that is flagging errors, attempting to rescue the data.
I tried dd first - if gets about 117G of 320G disk and stops incrementing
the save image any more.
Now I'm trying ddrescue and it also stops about the same point
Thoughts on how to continue past that point ?
Thanks,
Jerry
___
12 matches
Mail list logo
