• Cannot boot after violent shutdown


    I am still running ddrescue, but it has not yet completed mainly because the person I live with either shuts down the PC now and then or otherwise harms this project.

    This time the PC does not start up properly. It seems to boot partially,
    the messages “starting version”, “Antergos-root clean” and a few “kvm disabled” messages come, but then empty and silent.

    The last message appears when I shut down saying something like:
    system-journald[]: Failed to send stream file descriptor to service

    Any advice is precious.

  • @vpp21 said in Cannot boot after violent shutdown:

    I am still running ddrescue, but it has not yet completed mainly because the person I live with either shuts down the PC now and then or otherwise harms this project.

    This time the PC does not start up properly. It seems to boot partially,
    the messages “starting version”, “Antergos-root clean” and a few “kvm disabled” messages come, but then empty and silent.

    The last message appears when I shut down saying something like:
    system-journald[]: Failed to send stream file descriptor to service

    Any advice is precious.

    The end is:
    … manager: the connection refused"

  • I noticed that behind the scenes the system started to text mode. I could login using a virtual terminal. Then I updated everything, because during ddrescue I didn’t dare to update everything.

    After full update the system started up properly.

    The only problem that remained was that ddrescue cannot continue. It says that

    ddrescue: Last block in mapfile begins past end of input file.
              Use '-C' if you are reading from a partial copy.
    Try 'ddrescue --help' for more information.
    [[email protected]]# ddrescue -C -d /dev/sdc2 /mnt/rescue/usbdiskimage.img usb-rescue.log
    GNU ddrescue 1.21
    Press Ctrl-C to interrupt
    Initial status (read from mapfile)
    (sizes below are limited to the domain 0 B to 67108 kB)
      rescued:   67108 kB,     errsize:        0 B,  errors:       0
    
    Current status
     
     ipos:        0 B, non-trimmed:        0 B,  current rate:       0 B/s
         opos:        0 B, non-scraped:        0 B,  average rate:       0 B/s
    non-tried:        0 B,     errsize:        0 B,      run time:          0s
      rescued:   67108 kB,      errors:        0,  remaining time:         n/a
    percent rescued: 100.00%      time since last successful read:          0s
    Finished
    
  • @vpp21 said in Cannot boot after violent shutdown:

    rescued: 67108 kB, errors: 0, remaining time: n/a
    percent rescued: 100.00%

    looks not good?
    For me looks like 100% rescued?

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    howto-install-antergos
    how to add system logs
    i3 GNOME

  • I am afraid that ddrescue is not in order after the shutdown. It says the map file points beyond the input file. The disk had much more stuff in it. The last numbers I saw were 96.93% rescued. I suppose it refers only to bytes ddrescue was able to read…

    How can I check what ddrescue has saved? Manually mount the disk file? Format?

    It seems I really cannot restart ddrescue?

    I cannot be sure, but I think the job was not complete when the shutdown occurred.

  • usually you can restart ddrescue and it do not harm the process… but as your task is taking much to long time, i would say that the parameter you givin to it are not the best ones…

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    howto-install-antergos
    how to add system logs
    i3 GNOME

  • Thanks @joekamprad for your concern in this issue!

    I tried that -C option but it did not help. What else could I do differently? It didn’t really help either by replacing the map file…

  • I would like to complete that USB disk rescue operation, but after over one month and about three restarts reaching up to 96,93 % saved, it now seems impossible.

    I could still probably start from 0, but how to do that? The parameters and options don’t much tell to me.

  • To clone a faulty or dying drive, run ddrescue twice. First round, copy every block without read error and log the errors to rescue.log.

    # ddrescue -f -n /dev/sdX /dev/sdY rescue.log
    

    Second round, copy only the bad blocks and try 3 times to read from the source before giving up.

    # ddrescue -d -f -r3 /dev/sdX /dev/sdY rescue.log
    

    Now you can check the file system for corruption and mount the new drive.

    # fsck -f /dev/sdY
    

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    howto-install-antergos
    how to add system logs
    i3 GNOME

  • Thanks a lot @joekamprad! I will try those.

  • so first round will be fast because it only reads clean blocks… second one reads 3 times but only bad ones so then at all a bit faster for shure then everything in one…

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    howto-install-antergos
    how to add system logs
    i3 GNOME

  • I hope it will be fast. This morning the estimation was about 20 hours, but I suspect it will take more time. Which option forces ddrescue to read only once in the first command?

    Which option forces ddrescue to read only bad blocks in the second command? For me it looks like it would read all blocks once again with retry.

    At least it is running again. I suppose option -f helped to restart…

  • @joekamprad said in Cannot boot after violent shutdown:

    copy every block without read error

    first command reads only on time but only that blocks that are NOT bad ;)

    -r3 inside the second put the readtimes…

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    howto-install-antergos
    how to add system logs
    i3 GNOME

  • Current status:

    ddrescue -f -n /dev/sdd2 /mnt/rescue/usbdiskimage.img usb-rescue.log

    GNU ddrescue 1.21
    Press Ctrl-C to interrupt
    Initial status (read from mapfile)
    rescued: 67108 kB, errsize: 0 B, errors: 0

    Current status
    ipos: 130813 MB, non-trimmed: 51257 kB, current rate: 30334 B/s
    opos: 130813 MB, non-scraped: 0 B, average rate: 1788 kB/s
    non-tried: 869552 MB, errsize: 0 B, run time: 20h 15m 5s
    rescued: 130464 MB, errors: 0, remaining time: 68d 13h 10m
    percent rescued: 13.04% time since last successful read: 0s
    Copying non-tried blocks… Pass 1 (forwards)

    Quite a long time to wait for completion still…

    The USB disk is now sdd because I had the Antergos boot USB stick mounted when starting up. I was maybe a bad idea to start ddrescue in this situation, because I need to have that stick mounted again, if a restart is required…?!

  • may caus you are producing an image file? for me have to try this for real is long time ago, but last one i rescued was 500GB HD and in total id needs 3 days… but it is mainly depending on all the different interfaces…
    CPU USB-Port HD-Speed amound of bad blocks, state of the harddrive…

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    howto-install-antergos
    how to add system logs
    i3 GNOME

  • I am just hoping I can finish this rescue operation eventually.
    So far so good.

  • it is also possible to clone the drive and do the rescue out of the data with a full functional hd (hardware sided) …

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    howto-install-antergos
    how to add system logs
    i3 GNOME

  • Do you mean ddrescue can interpret the correct data out of the mess in the new hd?

  • Hello,
    current status:

    GNU ddrescue 1.21
    Press Ctrl-C to interrupt
    Initial status (read from mapfile)
    rescued: 67108 kB, errsize: 0 B, errors: 0

    Current status
    ipos: 591173 MB, non-trimmed: 210219 kB, current rate: 11565 B/s
    opos: 591173 MB, non-scraped: 0 B, average rate: 1793 kB/s
    non-tried: 409629 MB, errsize: 0 B, run time: 3d 19h 25m
    rescued: 590229 MB, errors: 0, remaining time: 250d 16h
    percent rescued: 59.01% time since last successful read: 0s
    Copying non-tried blocks… Pass 1 (forwards)

    Sometimes the remaining time has been “a couple of hours” :)

  • @vpp21 said in Cannot boot after violent shutdown:

    Do you mean ddrescue can interpret the correct data out of the mess in the new hd?

    this would be a 1 to 1 copy of all good and bad blocks as they are and speed would be a lot better if the defect hd is causing the slow copy, , , , ,

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    howto-install-antergos
    how to add system logs
    i3 GNOME

violent1 shutdown18 boot175 Posts 42Views 1840
Log in to reply