similar to: Using CentOS 7 to attempt recovery of failed disk

In article <E02FA554-9D6D-4E7D-8A78-5FBDE1DE939D at kicp.uchicago.edu>, Valeri Galtsev <galtsev at kicp.uchicago.edu> wrote: > > > > On Sep 26, 2020, at 8:05 AM, Jerry Geis <jerry.geis at gmail.com> 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

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 end to try again to read something from them. Of course, if you've had, eg. a head crash,

@tonymountifield Does this still hold true? https://superuser.com/a/1075837 On Sun, Sep 27, 2020 at 7:21 AM Tony Mountifield <tony at softins.co.uk> wrote: > In article <E02FA554-9D6D-4E7D-8A78-5FBDE1DE939D at kicp.uchicago.edu>, > Valeri Galtsev <galtsev at kicp.uchicago.edu> wrote: > > > > > > > On Sep 26, 2020, at 8:05 AM, Jerry Geis

> On Sep 26, 2020, at 8:05 AM, Jerry Geis <jerry.geis at gmail.com> 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 input error. Whatever is irrecoverable is irrecoverable,

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. Thanks for any suggestions. Jerry

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

Folks I posted this question on (OpenSolaris - Help) without any replies http://opensolaris.org/jive/thread.jspa?threadID=129436&tstart=0 and am re-posting here in the hope someone can help ... I have updated the wording a little too (in an attempt to clarify) I currently use OpenSolaris on a Toshiba M10 laptop. One morning the system wouldn''t boot OpenSolaris 2009.06 (it was simply

Hello, when testing FreeBSD-7.1-BETA i discovered that the floppy disk controller doesn't work correctly. Trying to format a floppy (perhaps with bad blocks) i get: Processing fdformat: ioctl(FD_FORM): Device not configured instead of the normal E letter. I then checked the same problem is present on FreeBSD-6.3 and it has been reported by Beech Rintoul (*) in 2006! Of course the floppy disk

Dear All I needed to clone my disk to another hard drive . I did it as the following : #dd if=/dev/sdb of=/dev/sdc But after a while, the procedure ended with the "writing to /dev/sdc input/output error" message. Can you please let me know how can I overcome this as the fdisk now returns as " #fdisk /dev/sdc "I do not know how to handle files with mode 81a4 must set

Hi folks, I have come sort of corruption on my hard disk, but it is difficult to find documentation on how to deal with it. The system is an old AMD K6/400 running Redhat 7.2 with 2.4.9. Disk is clipped to 33Mb due to old disk controller, and is running ext3. Some time back I suffered a number of cases where the machine hard locked up and I had to power cycle it to get control back. However, I

A few fixes and a possible enhancement to the ddrescue filter. If you think these are all OK, I will squash it into your patch and push it. Rich.

This allows to overlay bad sectors according to the mapfile generated by ddrescue, to then see where sectors are used using fsck and trying to copy files around. Signed-off-by: Fran?ois Revol <revol at free.fr> --- configure.ac | 2 + filters/ddrescue/Makefile.am | 75 +++++++ filters/ddrescue/ddrescue.c | 211

This allows to overlay bad sectors according to the mapfile generated by ddrescue, to then see where sectors are used using fsck and trying to copy files around. Signed-off-by: Fran?ois Revol <revol at free.fr> --- configure.ac | 2 + filters/ddrescue/Makefile.am | 75 +++++++ filters/ddrescue/ddrescue.c | 218

On 13/12/17 21:42, Leon Fauster wrote: > Am 13.12.2017 um 22:31 schrieb martin.wagner at mailbit.io: > >> I have a Centos server that crashed, it would no longer boot. I thought it was the disk with the OS that was the problem so I bought a new one and did a fresh install and now the computer is again up and running. But I'm having problems with accessing the old failed disk. I

On 14/12/17 18:57, Warren Young wrote: > On Dec 13, 2017, at 5:15 PM, J Martin Rushton <martinrushton56 at btinternet.com> wrote: >> >> # dd if=/dev/sdc of=/home/dd-copy-of-sdc > > Better, use ddrescue: > > https://www.gnu.org/software/ddrescue/ > > dd will do unfortunate things like quit early on I/O errors, even if later blocks would read just fine.

Hi all, I know this is the EXT3 list, and my problem is with an EXT2 filesys, but I cannot seem to find a more suitable list on this server, and I have seen a lot of knowledge go by on this list and in the archives, so I thought I'd give it a try anyway... Here goes nothing: I am in a terrible problem: My data disk on my Linux server has gone bad, with approx 18 GB of data on it, and I

On 2020-04-27 18:45, Jeremy Allison via samba wrote: > On Mon, Apr 27, 2020 at 10:27:17AM +0200, A L via samba wrote: >> On 2020-04-26 19:46, Jeremy Allison via samba wrote: >>> On Sun, Apr 26, 2020 at 11:51:42AM +0200, A L via samba wrote: >>>> * Connected from a Windows 10 computer over 1G ethernet. * Copy >>>> data using Windows Explorer and

Hello rsync people Today I was recovering data from a beginning-to-fail external USB hard disk. I started with my usual 'rsync -av --ignore-errors <source> <dest>', and that was fine until it got to the first I/O errors. It paused but continued after the first couple of errors, but then the disk started buzzing and rsync gave error messages for every file (I'm afraid

On Fri, October 30, 2015 9:31 pm, Mark LaPierre wrote: > On 10/30/15 17:30, Max Pyziur wrote: >> >> Greetings, >> >> I have three drives; they are all SATA Seagate Barracudas; two are >> 500GB; the third is a 2TB. >> >> I don't have a clear reason why they have failed (possibly due to a >> deep, off-brand, flakey mobo; but it's still

Dear centos community, I was in the process of loading the latest 5.5 release of centos in a VMWARE ESX 4.1 host as my first virtual machine, suddenly while booting I got a panic error with the following on screen. Can someone point me in the right direction. This machine has 24 cores and I allocated 1 for Centos to use with 1024MB of memory. Any clues or workaround to solve this problem? Thank