OOOPS! Fallen on my sword - again :(
by business_kid from LinuxQuestions.org on (#514VW)
I know what I did to myself - I had an sdcard with Arch Linux for Arm installed. It was in my sdcard reader, and I was copying over to a backup drive, and something went wrong in the rsync stage. I started getting exec format errors, nothing would work, and I gather I rsync'ed some Arch stuff onto the / drive, from looking in there later. My disk is formatted
sda1 1G /boot
sda2 swap
sda3 / for Slackware
sda4 - extended partition
sda5 /home for Slackware
sda6 / for Mint-19.3 (has the lot) mounted as /media/hd0 in Slackware
sda7 scratch disk & has the VMs mounted as /mnt/virtual in Slackware.
Arch has the standard set of unix directories, and I stopped it quick enough. It boots all the kernels in /boot, I gather it mounts / ro, screen clears, and I get
[CODE]/sbin/e2fsck: Is a directory when trying to mount /
/:
[CODE]
It then gives me this lecture about how it's dropping me to a single-user shell because it can't find a valid ext2/3/4 filesystem and to press Ctrl-D to continue or the root passwd, but the thing is frozen, and I can do nothing.
I have backups. I quickly found Mint-19.3 is spouting errors, but Arch doesn't have /media/hd0 so it can hardly have attacked that. For Slackware, I deleted sda3, remade the parttition, made a new ext4 filesystem and restored my backup from February. I still get that error. /boot seems clean, I can mount sda3 and it's fine. Ny standards, this is a good one
sda1 1G /boot
sda2 swap
sda3 / for Slackware
sda4 - extended partition
sda5 /home for Slackware
sda6 / for Mint-19.3 (has the lot) mounted as /media/hd0 in Slackware
sda7 scratch disk & has the VMs mounted as /mnt/virtual in Slackware.
Arch has the standard set of unix directories, and I stopped it quick enough. It boots all the kernels in /boot, I gather it mounts / ro, screen clears, and I get
[CODE]/sbin/e2fsck: Is a directory when trying to mount /
/:
[CODE]
It then gives me this lecture about how it's dropping me to a single-user shell because it can't find a valid ext2/3/4 filesystem and to press Ctrl-D to continue or the root passwd, but the thing is frozen, and I can do nothing.
I have backups. I quickly found Mint-19.3 is spouting errors, but Arch doesn't have /media/hd0 so it can hardly have attacked that. For Slackware, I deleted sda3, remade the parttition, made a new ext4 filesystem and restored my backup from February. I still get that error. /boot seems clean, I can mount sda3 and it's fine. Ny standards, this is a good one