Choose style:

Author Topic: Peppermint boots to BusyBox/initramfs.  (Read 1725 times)

0 Members and 1 Guest are viewing this topic.

Offline peppermintcrash

  • nOOb
  • *
  • Posts: 4
  • Karma: 0
  • New Forum User
    • View Profile
  • Peppermint version(s): 7
Peppermint boots to BusyBox/initramfs.
« on: May 06, 2017, 11:01:15 am »
The Peppermint Linux installation is on a a USB drive (SanDisk Ultra USB 3.0 64GB). A couple days back I left my laptop with a download running. When I returned to my laptop a while later, it had failed on around 12% with the error "read-only memory" although the OS and everything seemed to still function fine, so I just dismissed it as a bad download. I shut down the laptop as usual, but when I later booted the system, I get the following error message:

Code: [Select]
error: failure writing sector 0x58c02 to hd0
Press any key to continue..

When I press any key, it prompts me enter my encryption key as usual. It then progresses to the bootscreen, but around ten seconds later shows the following:

Code: [Select]
BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash) 
Enter 'help' for a list of built-in commands.
(initramfs) _

There are no errors shown before this. However, if I type the "exit" command, I get the following:

Code: [Select]
(initramfs) exit
[49.656457] blk_update_request: critical target error, dev sdb, sector 1007616
[49.656507] Buffer I/O error on dev dm-1, logical block 0, lost async page write
[49.656552] Buffer I/O error on dev dm-1, logical block 1, lost async page write
[49.656594] Buffer I/O error on dev dm-1, logical block 2, lost async page write
[49.656635] Buffer I/O error on dev dm-1, logical block 3, lost async page write
[49.658215] blk_update_request: critical target error, dev sdb, sector 1015824
[49.658304] Buffer I/O error on dev dm-1, logical block 1026, lost async page write
[49.659837] blk_update_request: critical target error, dev sdb, sector 34562056
[49.659926] Buffer I/O error on dev dm-1, logical block 4194305, lost async page write
[49.659986] Buffer I/O error on dev dm-1, logical block 4194306, lost async page write
[49.661587] blk_update_request: critical target error, dev sdb, sector 34562176
[49.661673] Buffer I/O error on dev dm-1, logical block 4194320, lost async page write
[49.663237] blk_update_request: critical target error, dev sdb, sector 34562304
[49.663335] Buffer I/O error on dev dm-1, logical block 4194336, lost async page write
[49.663379] Buffer I/O error on dev dm-1, logical block 4194337, lost async page write
[49.664962] blk_update_request: critical target error, dev sdb, sector 34562352
[49.666589] blk_update_request: critical target error, dev sdb, sector 34566128
[49.668211] blk_update_request: critical target error, dev sdb, sector 34566888
[49.669860] blk_update_request: critical target error, dev sdb, sector 34566928
[49.671463] blk_update_request: critical target error, dev sdb, sector 34566984

I can't seem to progress any further than this. Can anyone advise? There is data in the home folder that I really need to recover. I have tried to mount the USB in a live session. It allows me to enter the encryption key, but then fails when trying to mount.

Anyway, any advice is greatly appreciated. Thanks in advance.
« Last Edit: May 06, 2017, 11:02:58 am by peppermintcrash »

Offline Slim.Fatz

  • Trusted User
  • Veteran
  • *****
  • Posts: 1800
  • Karma: 472
  • Where's the mouse?
    • View Profile
  • Peppermint version(s): Peppermint 7, 8.5 & 10 - 64bit
Re: Peppermint boots to BusyBox/initramfs.
« Reply #1 on: May 06, 2017, 02:07:33 pm »
I don't know if this will help, but it is worth reading and perhaps trying in order to salvage your important data:

How to mount an encrypted Linux home directory to salvage data.

I hope it is of use for you.

Regards,

-- Slim

"Life first -- Peppermint a close 2nd!" -- Zeb

Tread lightly: Fluxbox, JWM, i3, Openbox, awesome

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 26082
  • Karma: 2842
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 10
Re: Peppermint boots to BusyBox/initramfs.
« Reply #2 on: May 06, 2017, 08:47:00 pm »
critical target I/O errors are nearly always caused by bad sectors on the hard drive .. which would also explain the failed download.


have you tried running fsck (or e2fsck) across the partition with the -c option which will do a read-only test for bad blocks.

See:
Code: [Select]
man e2fsck
as the -c option isn't mentioned in the "fsck" man page.
« Last Edit: May 06, 2017, 08:48:36 pm by PCNetSpec »
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

Offline peppermintcrash

  • nOOb
  • *
  • Posts: 4
  • Karma: 0
  • New Forum User
    • View Profile
  • Peppermint version(s): 7
Re: Peppermint boots to BusyBox/initramfs.
« Reply #3 on: May 06, 2017, 09:49:55 pm »
I don't know if this will help, but it is worth reading and perhaps trying in order to salvage your important data:

How to mount an encrypted Linux home directory to salvage data.

I hope it is of use for you.

Regards,

-- Slim

Thanks for the guide, I will give this a go tomorrow.

critical target I/O errors are nearly always caused by bad sectors on the hard drive .. which would also explain the failed download.


have you tried running fsck (or e2fsck) across the partition with the -c option which will do a read-only test for bad blocks.

See:
Code: [Select]
man e2fsck
as the -c option isn't mentioned in the "fsck" man page.

Should I do this from the initramfs console? Or from a live session in a terminal?

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 26082
  • Karma: 2842
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 10
Re: Peppermint boots to BusyBox/initramfs.
« Reply #4 on: May 06, 2017, 10:32:03 pm »
I generally run fsck from a live session .. just make sure not to mount the drive first.
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

Offline peppermintcrash

  • nOOb
  • *
  • Posts: 4
  • Karma: 0
  • New Forum User
    • View Profile
  • Peppermint version(s): 7
Re: Peppermint boots to BusyBox/initramfs.
« Reply #5 on: May 07, 2017, 04:06:57 pm »
I don't know if this will help, but it is worth reading and perhaps trying in order to salvage your important data:

How to mount an encrypted Linux home directory to salvage data.

I hope it is of use for you.

Regards,

-- Slim

I attempted to follow this guide today. When I initially insert the USB whilst running the live session, I am prompted to enter the encryption key, then I am presented with the following message:

Code: [Select]
Error mounting /dev/dm-1 at /media/ubuntu/0033cd39-2c93-4bbb-a5bb-0a27a21e8c6f: Command-line `mount -t "ext4" -o "uhelper=udisks2,nodev,nosuid" "/dev/dm-1" "/media/ubuntu/0033cd39-2c93-4bbb-a5bb-0a27a21e8c6f"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/mapper/peppermint--vg-root,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

From being unable to mount, I knew I wouldnt be able to follow the guide. I tried anyway, which showed the following in the terminal:

Code: [Select]
ubuntu@ubuntu:~$ sudo ecryptfs-recover-private /media/e5420998-d9e3-43da-8706-4ce7046b7360/home/.ecryptfs/peppermint/.private
INFO: Searching for encrypted private directories (this might take a while)...
INFO: Hint: click 'Places' and select your hard disk, then run this again.
ERROR: No private directories found; make sure that your root filesystem is mounted.
ubuntu@ubuntu:~$

Does the error message give anymore clues as to what the issue is?

critical target I/O errors are nearly always caused by bad sectors on the hard drive .. which would also explain the failed download.


have you tried running fsck (or e2fsck) across the partition with the -c option which will do a read-only test for bad blocks.

See:
Code: [Select]
man e2fsck
as the -c option isn't mentioned in the "fsck" man page.

As you can see from above, I was unable to mount the device anyway. When I plug in the USB, I am presented with two partitions. One 500MB grub/boot partition, and a 58GB system partition. I unmounted the boot partition to be on the safe side of things.

I was able to get the UUID for the system partition from gparted since the system didnt even show it when running df -h, most likely because it failed to mount. From there I run fsck with the following result:

Code: [Select]
ubuntu@ubuntu:~$ fsck -c UUID=e5420998-d9e3-43da-8706-4ce7046b7360
fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
fsck.ext2: Permission denied while trying to open /dev/sdc5
You must have r/w access to the filesystem or be root
ubuntu@ubuntu:~$ sudo fsck -c UUID=e5420998-d9e3-43da-8706-4ce7046b7360
fsck from util-linux 2.20.1
fsck: fsck.crypto_LUKS: not found
fsck: error 2 while executing fsck.crypto_LUKS for /dev/sdc5

Any ideas on how to progress from here?

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 26082
  • Karma: 2842
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 10
Re: Peppermint boots to BusyBox/initramfs.
« Reply #6 on: May 07, 2017, 05:58:40 pm »
see the answer that starts with "Your volume is probably encrypted with LUKS, here's how to mount it:" here:-
https://askubuntu.com/questions/63594/mount-encrypted-volumes-from-command-line

Hopefully that'll get it mounted so you can recover your data.
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

Offline peppermintcrash

  • nOOb
  • *
  • Posts: 4
  • Karma: 0
  • New Forum User
    • View Profile
  • Peppermint version(s): 7
Re: Peppermint boots to BusyBox/initramfs.
« Reply #7 on: May 09, 2017, 08:07:16 pm »
see the answer that starts with "Your volume is probably encrypted with LUKS, here's how to mount it:" here:-
https://askubuntu.com/questions/63594/mount-encrypted-volumes-from-command-line

Hopefully that'll get it mounted so you can recover your data.

Thanks for your suggestion. I followed the answers as per following:

Code: [Select]
ubuntu@ubuntu:~$ sudo cryptsetup luksOpen /dev/sdc5 my_encrypted_volume
Enter passphrase for /dev/sdc5:
ubuntu@ubuntu:~$ sudo mkdir /media/my_device2
ubuntu@ubuntu:~$ sudo mount /dev/mapper/my_encrypted_volume /media/my_device2
mount: unknown filesystem type 'LVM2_member'

I followed one of the responses regarding the LVM2 error:

Code: [Select]
ubuntu@ubuntu:~$ sudo lvscan
  ACTIVE            '/dev/peppermint-vg/root' [53.68 GiB] inherit
  ACTIVE            '/dev/peppermint-vg/swap_1' [3.68 GiB] inherit
ubuntu@ubuntu:~$ sudo vgchange -ay
  2 logical volume(s) in volume group "peppermint-vg" now active
ubuntu@ubuntu:~$ sudo mount /dev/mapper/my_encrypted_volume /media/my_device2
mount: unknown filesystem type 'LVM2_member'
ubuntu@ubuntu:~$

As you can see, it still produced the same error. Unless I am doing something wrong? Now you may be able to tell that I am far from literate with linux, but I attempted the following method to access root:

Code: [Select]
ubuntu@ubuntu:~$ ls /dev/
autofs           fb0    loop1               null           ram4    sdc2      tty13  tty29  tty44  tty6       ttyS16  ttyS31   vcs6
block            fd     loop2               peppermint-vg  ram5    sdc5      tty14  tty3   tty45  tty60      ttyS17  ttyS4    vcs7
bsg              full   loop3               port           ram6    sg0       tty15  tty30  tty46  tty61      ttyS18  ttyS5    vcsa
btrfs-control    fuse   loop4               ppp            ram7    sg1       tty16  tty31  tty47  tty62      ttyS19  ttyS6    vcsa1
bus              hpet   loop5               psaux          ram8    sg2       tty17  tty32  tty48  tty63      ttyS2   ttyS7    vcsa2
char             i2c-0  loop6               ptmx           ram9    shm       tty18  tty33  tty49  tty7       ttyS20  ttyS8    vcsa3
console          i2c-1  loop7               pts            random  snapshot  tty19  tty34  tty5   tty8       ttyS21  ttyS9    vcsa4
core             i2c-2  loop-control        ram0           rfkill  snd       tty2   tty35  tty50  tty9       ttyS22  uhid     vcsa5
cpu              i2c-3  mapper              ram1           rtc     stderr    tty20  tty36  tty51  ttyprintk  ttyS23  uinput   vcsa6
cpu_dma_latency  i2c-4  mcelog              ram10          rtc0    stdin     tty21  tty37  tty52  ttyS0      ttyS24  urandom  vcsa7
cuse             i2c-5  media0              ram11          sda     stdout    tty22  tty38  tty53  ttyS1      ttyS25  v4l      vfio
disk             i2c-6  mei0                ram12          sda1    tty       tty23  tty39  tty54  ttyS10     ttyS26  vcs      vga_arbiter
dm-0             input  mem                 ram13          sda2    tty0      tty24  tty4   tty55  ttyS11     ttyS27  vcs1     vhci
dm-1             kmsg   memory_bandwidth    ram14          sdb     tty1      tty25  tty40  tty56  ttyS12     ttyS28  vcs2     vhost-net
dm-2             kvm    net                 ram15          sdb1    tty10     tty26  tty41  tty57  ttyS13     ttyS29  vcs3     video0
dri              log    network_latency     ram2           sdc     tty11     tty27  tty42  tty58  ttyS14     ttyS3   vcs4     zero
ecryptfs         loop0  network_throughput  ram3           sdc1    tty12     tty28  tty43  tty59  ttyS15     ttyS30  vcs5
ubuntu@ubuntu:~$ ls /dev/peppermint-vg
root  swap_1
ubuntu@ubuntu:~$ ls /dev/peppermint-vg/root
/dev/peppermint-vg/root
ubuntu@ubuntu:~$

But no dice!

Again attempting to access /root:

Code: [Select]
ubuntu@ubuntu:~$ ls /dev/mapper/
control  my_encrypted_volume  peppermint--vg-root  peppermint--vg-swap_1
ubuntu@ubuntu:~$ ls /dev/mapper/peppermint--vg-root
/dev/mapper/peppermint--vg-root
ubuntu@ubuntu:~$

Just seems to relay the directory I attempted to access? From here I tried to mount the root directory but it produces the same error as the GUI method from one of my previous posts:

Code: [Select]
ubuntu@ubuntu:~$ ls /dev/mapper/
control  my_encrypted_volume  peppermint--vg-root  peppermint--vg-swap_1
ubuntu@ubuntu:~$ ls /dev/mapper/peppermint--vg-root
/dev/mapper/peppermint--vg-root
ubuntu@ubuntu:~$ udisksctl mount -b /dev/mapper/peppermint--vg-root
Error mounting /dev/dm-1: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/dm-1 at /media/ubuntu/0033cd39-2c93-4bbb-a5bb-0a27a21e8c6f: Command-line `mount -t "ext4" -o "uhelper=udisks2,nodev,nosuid" "/dev/dm-1" "/media/ubuntu/0033cd39-2c93-4bbb-a5bb-0a27a21e8c6f"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/mapper/peppermint--vg-root,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

ubuntu@ubuntu:~$

At this point, I was trying various methods again from the guide you linked. Attempting the unlock command with udisksctl showed it was already unlocked as dm-0, so I tried to see if could access any files that way:

Code: [Select]
ubuntu@ubuntu:~$ udisksctl unlock -b /dev/sdc5
Passphrase:
Error unlocking /dev/sdc5: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Device /dev/sdc5 is already unlocked as /dev/dm-0
ubuntu@ubuntu:~$ ls /dev/dm-0
/dev/dm-0
ubuntu@ubuntu:~$

Again, nothing.

Trying to mount dm-0 shows an unmountable file system:

Code: [Select]
ubuntu@ubuntu:~$ udisksctl mount -b /dev/dm-0
Object /org/freedesktop/UDisks2/block_devices/dm_2d0 is not a mountable filesystem.
ubuntu@ubuntu:~$

Im trying pretty much anything I can.

Is there anything else to be tried at this point? I saw something regarding bad superblocks whilst looking for a solution. Could that be worth a try?

Thanks again.