Hi All,
A long time since I posted here and all because I had a perfectly usable laptop and and a version of Peppermint installed. I have came through the various updates of Peppermint ( I don’t know which version I have now as I can’t log in ) but it all worked until about 4 days ago.
When trying to log in I would experience minor issues and I did various things and got logged in eventually. Yesterday I had a major issue and following some prompts ended at the GNU GRUB version 2.04 screen, from that I chose ‘Advanced Options for Peppermint GNU Linux’, at the top of the next screen was
Peppermint GNU/Linux, with Linux 4.15.0-151-generic
Peppermint GNU/Linux, with Linux 4.15.0-151-generic (recovery mode)
I choose the second option and finally got logged in again.
This morning I am having the same problem logging in but now nothing seems to work.
I have scrolled down to Peppermint GNU/Linux, with Linux 4.15.0-34-generic and pressed Enter but the screen fills with messages like ‘couldn’t get size’, couldn’t get UEFI db list, /dev/sda2/ contains a file system with errors, the root filesystem on /dev/sda2/ requires a manual fsck, and ends with (initrams) with the flashing cursor. I have left it there at the moment and went to my windross machine and sent this help request hoping you can help.
The laptop is rather old now and I may be better cleaning it up and installing the latest peppermint but I need access to passwords etc. before I do that unless I can install a new version and hope I can save passwords etc. ??
take care and stay safe
Don W
Hi Don.
I hesitate to advise on fsck as I am no expert on Linux, and others who have commented recently to similar posts will, I am sure, offer advice.
In the meantime you might like to look at How to Use fsck Command to Check and Repair Filesystem.
The section “Run fsck on Linux Root Partition” (scroll just over half way down) looks promising if you can still select recovery mode.
Keith
Thanks Keith,
I have used fsck as I saw an earlier post about this problem and it was suggested that fsck -fy /dev/sda2/ could be the answer. It worked and I was able to log in. I rebooted and now I can’t log in again, or rather I can log in again but it then goes to a black screen with the arrow pointer but nothing happens, I use a continual press on the On button to shut down.
Don W
On my Ubuntu system, sda2 is an extended (swap) partition and I am guessing that you need fsck -y /dev/sda.
As you have got to the terminal screen I suggest that you back up everything before using fsk. Are you happy with using the copy -a command?
{Again, I emphasise that I am no expert on fsk. Caveat emptor!}
I have logged in again on my Linux machine.
If you like I can try the copy -a command, I was wondering if I should just check out my passwords for my main programmes and make a written copy of them first. Then I could always install the latest version of Peppermint and start again/anew ??
I feel one should always keep backup copies of everything as catastrophes do occur - as you’ve discovered.
To make things easier I have written a script to copy all my files (using rsync), and I do so on a monthly basis.
If you can backup all your files/passwords then installing the latest version of Peppermint might be the simplest way to go, although if you are willing to do that then you lose nothing by trying fsck first. If you do attempt a fresh installation and the installation fails then that might indicate a disc problem has been causing your difficulties.
Keith
I have copied and saved to a pen drive all my passwords etc. that I want.
I have tried what you suggest with fsck and this is the result
don@ldwatson ~ $ fsck -y /dev/sda
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
fsck.ext2: Permission denied while trying to open /dev/sda
You must have r/w access to the filesystem or be root
don@ldwatson ~ $
Would it be ok to send me a copy of the script you have written and I will make a copy of my files and see what to do from there ??
Sorry Don - one needs to enter the command as “root”:
sudo fsck -y /dev/sda
You will be asked for your password.
I get this result
don@ldwatson ~ $ sudo fsck -y /dev/sda
[sudo] password for don:
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
/dev/sda is in use.
e2fsck: Cannot continue, aborting.
don@ldwatson ~ $
What next ? Would I be better installing/upgrading to Peppermint 10 ?
You need to boot into a live USB/CD environment then make sure none of the disks are mounted:
for n in /dev/sda* ; do umount $n ; done
then run fsck as Keith indicated
sudo fsck -y /dev/sda
Note using the -y will answer yes to all fixing suggestions.
perhaps you could just do a dry run first:
sudo fsck -n /dev/sda
Sezo, thank you for coming to the rescue - I had forgotten about un-mounting.
Thanks SeZo. I get this when I do a dry run
don@ldwatson ~ $ sudo fsck -n /dev/sda
[sudo] password for don:
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
Warning! /dev/sda is in use.
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks…
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193
or
e2fsck -b 32768
Found a gpt partition table in /dev/sda
don@ldwatson ~ $
What next ??
I have tried things all day now, after tea I logged in ok and had a read at my posts on the forum, exited LinuxForums and went to my windross machine to play some games. I am back now but only after a bit of trouble. When I came back here the laptop had crashed/ stopped / wasn’t working and I had to shut the laptop down again with the On button.
Warning! /dev/sda is in use.Did you unmount all sda partitions?
Please list partitions (that is lowercase L):
sudo fdisk -l
Then run fsck on partitions other than swap:
sudo fsck -n /dev/sda1
or
sudo fsck -n /dev/sda2
If that still throws the superblock corrupt message then
try running e2fsck with an alternate superblock (replace with /dev/sda1 or sda2):
sudo e2fsck -b 8193 <device>
don@ldwatson ~ $ sudo fdisk -l
[sudo] password for don:
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: F540E3BD-39D7-4D41-ADB4-238E423AC1BE
Device Start End Sectors Size Type
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda2 1050624 976771071 975720448 465.3G Linux filesystem
don@ldwatson ~ $ sudo fsck -n /dev/sda1
fsck from util-linux 2.31.1
fsck.fat 4.1 (2017-01-24)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Automatically removing dirty bit.
Leaving filesystem unchanged.
/dev/sda1: 10 files, 1691/130812 clusters
don@ldwatson ~ $
don@ldwatson ~ $ sudo fsck -n /dev/sda2
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
Warning! /dev/sda2 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/sda2: clean, 2783975/30498816 files, 18432857/121965056 blocks
don@ldwatson ~ $
don@ldwatson ~ $ sudo fdisk -l
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: F540E3BD-39D7-4D41-ADB4-238E423AC1BE
Device Start End Sectors Size Type
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda2 1050624 976771071 975720448 465.3G Linux filesystem
I am afraid I have lost control here and am getting very frustrated. I don’t know what I am doing. The last command I tried gave this result
don@ldwatson ~ $ sudo e2fsck -b 32768 /dev/sda1/
e2fsck 1.44.1 (24-Mar-2018)
e2fsck: Not a directory while trying to open /dev/sda1/
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193
or
e2fsck -b 32768
don@ldwatson ~ $
Would it be easier to just put a new version of Peppermint on this laptop??
Warning! /dev/sda2 is mounted.
Still mounted?
Probably a lot easier if you got nothing to loose
I logged on this morning without problems although it did take 50 seconds before the sign-in screen appeared (it takes 40-50 seconds usually). I would be quite happy to clear this laptop and start again but I don’t know how to go about it. (I have forgotten the steps). I think Mark explained it some time ago, I will have a look.
Don W
Don,
You asked about backing up before re-installing Peppermint. I attach a file for you to print out that might help. I’ve avoided using a script as, although it would be easy to use, it might be difficult for you to set up - we can deal with scripts later when you are back in action.
Let me know if you have any problems.
In the meantime I’ll assemble a method of creating a Peppermint live usb. (Other readers are free to chip in here!)
Keith
Hi Keith,
I don’t see any attachment ??
I have downloaded the Peppermint 10 iso and verified the checksum but I have came to a halt as I need to know how to get the iso onto the USB. I can remember using a quick programme for this but can’t remember what it was. I really need my hand held here.
Don W
PS I have a 2 Tb external hard drive that I can use for backing up if that is needed.
If you go to my previous post (#16) scroll down till you see “Keith” and about 1" below that you will see dons-backup-instructions.odt . Click on that link.
Good to see you have the ISO and verified the checksum. I have to buy some building materials now but will be back later.
Keith, I can see a paperclip at the top of your post but I can’t see the file