After a recent up date and reboot, my system fails to boot up and I have been getting the following,
kernel panic not syncing vfs unable to mount root fs on unknown-block (179,2)
This is my File and VPN server that took me ages to setup and I have many active user, obviously reinstalling is not and option and therefor before I get my hands on it I’d like to get some advice here. I would be very grateful for any help and tips.
Please see the attached photo from the system on boot up. By the way the Dietpi is installed on a ASUS Tinker Board.
Hi, I might have some backup done in past, cannot remember where they are thought! No backup done recently
Yes I do have another system in my network running Dietpi on it, if necessary I’l willing go further and install any OS on that system.
so I connected the SD to system to do some basic file system check and results are below,
root@DietPi:/mnt/sda1# sudo fsck.ext4 /dev/sda1
e2fsck 1.44.5 (15-Dec-2018)
ext2fs_open2: Bad magic number in super-block
fsck.ext4: Superblock invalid, trying backup blocks…
fsck.ext4: Bad magic number in super-block 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
/dev/sda1 contains a vfat file system
root@DietPi:/mnt/sda1#
AND…
root@DietPi:/mnt/sda1# sudo fsck.ext4 /dev/sda2
e2fsck 1.44.5 (15-Dec-2018)
/dev/sda2: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway? yes
fsck.ext4: Input/output error while recovering journal of /dev/sda2
fsck.ext4: unable to set superblock flags on /dev/sda2
/dev/sda2: ********** WARNING: Filesystem still has errors **********