I have a pc with dual-boot win10 / ubuntu 18.04
After a Windows update, i can't start Ubuntu, Grub starts in command-line mode.
I start pc with a live version of Ubuntu and these are my attempts:
The partition seems to be recognized, but if i try to mount:
I tried to check and fix with fsck:
and tried to restore superblock from all alternate superblocks given by e2fsck command with -n option. No good results.
Is there hope to restart my Ubuntu or the only solution is to re-install the system?
Thanks for your time and suggestions
After a Windows update, i can't start Ubuntu, Grub starts in command-line mode.
I start pc with a live version of Ubuntu and these are my attempts:
Code:
fdisk -l /dev/sda
Disk /dev/sda: 489.1 GiB, 525112713216 bytes, 1025610768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: BABB2881-5183-4807-8EFE-742DB838FF71
Device Start End Sectors Size Type
/dev/sda1 2048 1023999 1021952 499M Windows recovery environment
/dev/sda2 1024000 1228799 204800 100M EFI System
/dev/sda3 1228800 1261567 32768 16M Microsoft reserved
/dev/sda4 1261568 684606850 683345283 325.9G Microsoft basic data
/dev/sda5 684607488 685764607 1157120 565M Windows recovery environment
/dev/sda6 685766656 1002174463 316407808 150.9G Linux filesystem
/dev/sda7 1002174464 1025609727 23435264 11.2G Linux swap
The partition seems to be recognized, but if i try to mount:
Code:
sudo mount /dev/sda6 partition
mount: /home/ubuntu/partition: wrong fs type, bad option, bad superblock on /dev/sda6, missing codepage or helper program, or other error.
I tried to check and fix with fsck:
Code:
fsck from util-linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
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 <device>
or
e2fsck -b 32768 <device>
Found a gpt partition table in /dev/sda
and tried to restore superblock from all alternate superblocks given by e2fsck command with -n option. No good results.
Is there hope to restart my Ubuntu or the only solution is to re-install the system?
Thanks for your time and suggestions