Page 1 of 1

Can't boot, can you help?

Posted: Sat Jul 20, 2019 4:41 pm
by charroo
Ive tried revovery with no success
Screenshot_20190720-233826.jpg
Screenshot_20190720-233826.jpg (62.68 KiB) Viewed 578 times

Re: Can't boot, can you help?

Posted: Sat Jul 20, 2019 4:46 pm
by jglen490
That's not much to go on.

Have you ever been able to boot?
If so, when did it stop?
Some system info would be useful, and since you can't boot at least a description such a CPU, RAM, disk(s) number and size, what version of Mint and other similar specs.

Re: Can't boot, can you help?

Posted: Sat Jul 20, 2019 4:48 pm
by deepakdeshp
Boot from live USB and post output of

Code: Select all

inxi -Fxz;lsblk
in code tags.

Re: Can't boot, can you help?

Posted: Sun Jul 21, 2019 1:52 pm
by charroo
is that helps to help?
Selection_090.jpg
Selection_090.jpg (45.82 KiB) Viewed 531 times

Re: Can't boot, can you help?

Posted: Sun Jul 21, 2019 2:39 pm
by deepakdeshp
First command is

Code: Select all

inxi -Fxz
. Please copy paste.

Re: Can't boot, can you help?

Posted: Sun Jul 21, 2019 3:51 pm
by charroo

Code: Select all

mint@mint:~$ inxi -Fxz
System:
  Host: mint Kernel: 4.15.0-20-generic x86_64 bits: 64 compiler: gcc 
  v: 7.3.0 Desktop: Cinnamon 4.0.8 Distro: Linux Mint 19.1 Tessa 
  base: Ubuntu 18.04 bionic 
Machine:
  Type: Desktop Mobo: Gigabyte model: H81M-S2H v: x.x serial: <filter> 
  BIOS: American Megatrends v: F1 date: 08/19/2014 
CPU:
  Topology: Dual Core model: Intel Core i3-4160 bits: 64 type: MT MCP 
  arch: Haswell rev: 3 L2 cache: 3072 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28733 
  Speed: 1192 MHz min/max: 800/3600 MHz Core speeds (MHz): 1: 939 2: 962 
  3: 943 4: 961 
Graphics:
  Device-1: Intel 4th Generation Core Processor Family Integrated Graphics 
  vendor: Gigabyte driver: i915 v: kernel bus ID: 00:02.0 
  Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel Haswell v: 4.5 Mesa 18.0.5 
  direct render: Yes 
Audio:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
  driver: snd_hda_intel v: kernel bus ID: 00:03.0 
  Device-2: Intel 8 Series/C220 Series High Definition Audio 
  vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  Sound Server: ALSA v: k4.15.0-20-generic 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Gigabyte driver: r8169 v: 2.3LK-NAPI port: e000 bus ID: 02:00.0 
  IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 1.15 TiB used: 94.9 MiB (0.0%) 
  ID-1: /dev/sda vendor: Crucial model: CT250BX100SSD1 size: 232.89 GiB 
  temp: 30 C 
  ID-2: /dev/sdb vendor: Seagate model: ST1000DM003-1ER162 size: 931.51 GiB 
  temp: 31 C 
  ID-3: /dev/sdc type: USB vendor: SanDisk model: Cruzer Fit size: 14.91 GiB 
Partition:
  ID-1: / size: 3.84 GiB used: 94.9 MiB (2.4%) fs: overlay source: ERR-102 
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 177 Uptime: 2h 07m Memory: 7.68 GiB used: 817.6 MiB (10.4%) 
  Init: systemd runlevel: 5 Compilers: gcc: 7.3.0 Shell: bash v: 4.4.19 
  inxi: 3.0.27

Re: Can't boot, can you help?

Posted: Sun Jul 21, 2019 4:05 pm
by Tomgin5
It looks to me like the OP could use another install. Either from a dvd or maybe the live flash drive the OP is using to get the information. something got missed, or deleted, in the install.

This user is running a HP Mini circa 2008, 2 gb RAM, single core N270 processor XFCE 19.1 - 32 bit!

Re: Can't boot, can you help?

Posted: Sun Jul 21, 2019 4:15 pm
by deepakdeshp
Boot from USB and run fsck on the partition on which Mint is installed. Run on /home too if it's a different partition.

Code: Select all

 sudo fsck -y /dev/sdxy
where x is a or b and y is 1 or 2 depending on the partition.
Where is Mint installed? Which partition?

Re: Can't boot, can you help?

Posted: Sun Jul 21, 2019 4:17 pm
by deepakdeshp
Tomgin5 wrote:
Sun Jul 21, 2019 4:05 pm
It looks to me like the OP could use another install. Either from a dvd or maybe the live flash drive the OP is using to get the information. something got missed, or deleted, in the install.

This user is running a HP Mini circa 2008, 2 gb RAM, single core N270 processor XFCE 19.1 - 32 bit!
He has i3 4th gen and 8gb memory. Decent specs.

Re: Can't boot, can you help?

Posted: Sun Jul 21, 2019 4:25 pm
by charroo
thanks all

i don't know on which partition mint is installed

Code: Select all

mint@mint:~$ sudo fsck -y /dev/sdxy
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
fsck.ext2: No such file or directory while trying to open /dev/sdxy
Possibly non-existent device?
this is not a new installation.

maybe all the problem is due to the home directory ws encrypted upon installtion back then?

if i install it freshly again all my files will be deleted

Re: Can't boot, can you help?

Posted: Sun Jul 21, 2019 4:31 pm
by deepakdeshp
In the previous post run fsck on sda2 and sdb1. I don't know about encrypted partition ,somebody else may help.

Re: Can't boot, can you help?

Posted: Mon Jul 22, 2019 5:23 am
by charroo

Code: Select all

sudo fsck -y /dev/sda2
the command should be like so?

Re: Can't boot, can you help?

Posted: Mon Jul 22, 2019 6:02 am
by deepakdeshp
charroo wrote:
Mon Jul 22, 2019 5:23 am

Code: Select all

sudo fsck -y /dev/sda2
the command should be like so?
Yes and sdb1 too.

Re: Can't boot, can you help?

Posted: Mon Jul 22, 2019 6:07 am
by deepakdeshp

Code: Select all

 sudo mount /dev/sda2 /mnt
.Please do this after fsck. Now backup your data from /mnt residing in sda2.
After backup

Code: Select all

 sudo umount /mnt; mount /dev/sdb1 /mnt
.Backup sdb1 data to ext drive .
You can reinstall Mint now as your data is backed up.
Good Luck.

Re: Can't boot, can you help?

Posted: Mon Jul 22, 2019 8:07 am
by charroo

Code: Select all

mint@mint:~$ sudo fsck -y /dev/sda2
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
/dev/sda2 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found.  Fix? yes

Inode 8388716 was part of the orphaned inode list.  FIXED.
Inode 8388941 was part of the orphaned inode list.  FIXED.
Inode 8389285 was part of the orphaned inode list.  FIXED.
Inode 8389298 was part of the orphaned inode list.  FIXED.
Inode 8391172 was part of the orphaned inode list.  FIXED.
Inode 8392037 was part of the orphaned inode list.  FIXED.
Inode 8393426 was part of the orphaned inode list.  FIXED.
Deleted inode 8396686 has zero dtime.  Fix? yes

Inode 8782486 passes checks, but checksum does not match inode.  Fix? yes

Inode 12451870 was part of the orphaned inode list.  FIXED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences:  -(34133979--34133985) -(36841494--36841507) -(36841550--36841563) -(36841578--36841584) -(36841613--36841619) -(36841662--36841668)
Fix? yes

Free blocks count wrong for group #1041 (14625, counted=14632).
Fix? yes

Free blocks count wrong for group #1124 (28418, counted=28467).
Fix? yes

Free blocks count wrong (50845520, counted=50805771).
Fix? yes

Inode bitmap differences:  -8388716 -8388941 -8389285 -8389298 -8391172 -8392037 -8393426 -8396686 -12451870
Fix? yes

Free inodes count wrong for group #1024 (63, counted=71).
Fix? yes

Free inodes count wrong for group #1520 (3334, counted=3335).
Fix? yes

Free inodes count wrong (13838387, counted=13808303).
Fix? yes


/dev/sda2: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda2: 1428817/15237120 files (0.3% non-contiguous), 10112501/60918272 blocks
^[[Amint@mintsudo fsck -y /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.
Performing changes.
/dev/sda1: 12 files, 1558/130812 clusters
mint@mint:~$ 
should i try to rebbot before backing up and making a new installation?

edit:
i've made a reboot and now it is functioning without a fresh install

Re: Can't boot, can you help?

Posted: Mon Jul 22, 2019 8:48 am
by deepakdeshp
charroo wrote:
Mon Jul 22, 2019 8:07 am

Code: Select all

mint@mint:~$ sudo fsck -y /dev/sda2
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
/dev/sda2 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found.  Fix? yes

Inode 8388716 was part of the orphaned inode list.  FIXED.
Inode 8388941 was part of the orphaned inode list.  FIXED.
Inode 8389285 was part of the orphaned inode list.  FIXED.
Inode 8389298 was part of the orphaned inode list.  FIXED.
Inode 8391172 was part of the orphaned inode list.  FIXED.
Inode 8392037 was part of the orphaned inode list.  FIXED.
Inode 8393426 was part of the orphaned inode list.  FIXED.
Deleted inode 8396686 has zero dtime.  Fix? yes

Inode 8782486 passes checks, but checksum does not match inode.  Fix? yes

Inode 12451870 was part of the orphaned inode list.  FIXED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Good that the problem is solved.fsck has worked.
Its a good idea to backup your data to external drive You =can fall back in case of disaster.
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences:  -(34133979--34133985) -(36841494--36841507) -(36841550--36841563) -(36841578--36841584) -(36841613--36841619) -(36841662--36841668)
Fix? yes

Free blocks count wrong for group #1041 (14625, counted=14632).
Fix? yes

Free blocks count wrong for group #1124 (28418, counted=28467).
Fix? yes

Free blocks count wrong (50845520, counted=50805771).
Fix? yes

Inode bitmap differences:  -8388716 -8388941 -8389285 -8389298 -8391172 -8392037 -8393426 -8396686 -12451870
Fix? yes

Free inodes count wrong for group #1024 (63, counted=71).
Fix? yes

Free inodes count wrong for group #1520 (3334, counted=3335).
Fix? yes

Free inodes count wrong (13838387, counted=13808303).
Fix? yes


/dev/sda2: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda2: 1428817/15237120 files (0.3% non-contiguous), 10112501/60918272 blocks
^[[Amint@mintsudo fsck -y /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.
Performing changes.
/dev/sda1: 12 files, 1558/130812 clusters
mint@mint:~$ 
should i try to rebbot before backing up and making a new installation?

edit:
i've made a reboot and now it is functioning without a fresh install

Re: Can't boot, can you help?

Posted: Tue Aug 06, 2019 1:21 pm
by charroo
after a while. again i'm getting this boot error on the same computer
Selection_101.png
. what is going on?