paris/i-0437e5e96664de44e
by SadServersMore by SadServers
root 570 0.1 6.0 107132 28456 ? Ss 20:44 0:00 /usr/bin/pyth.py root 574 0.0 0.9 220796 4352 ? Ssl 20:44 0:00 /usr/sbin/rsyroot 579 0.0 1.4 13500 6772 ? Ss 20:44 0:00 /lib/systemd/root 582 0.0 0.3 2872 1676 tty1 Ss+ 20:44 0:00 /sbin/agetty 1 linux root 583 0.0 0.4 4396 2104 ttyS0 Ss+ 20:44 0:00 /sbin/agetty 15200,57600,38400,9600 ttyS0 vt220 root 584 0.0 1.5 13352 7184 ? Ss 20:44 0:00 sshd: /usr/sbf 10-100 startups _chrony 586 0.0 0.7 10852 3700 ? S 20:44 0:00 /usr/sbin/chr_chrony 588 0.0 0.1 10724 552 ? S 20:44 0:00 \_ /usr/sbinroot 589 0.0 3.6 26612 17248 ? Ss 20:44 0:00 /usr/bin/pyth-upgrades/unattended-upgrade-shutdown --wait-for-signal admin@i-07f79c3179505d899:~$
paris/i-07f79c3179505d899 03:35
by SadServersudev 217M 0 217M 0% /dev tmpfs 46M 368K 46M 1% /run /dev/nvme0n1p1 7.7G 6.1G 1.2G 84% / tmpfs 228M 12K 228M 1% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock /dev/nvme0n1p15 124M 5.9M 118M 5% /boot/efi admin@i-00e339adeade5921e:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT nvme0n1 259:0 0 8G 0 disk ├─nvme0n1p1 259:3 0 7.9G 0 part / ├─nvme0n1p14 259:4 0 3M 0 part └─nvme0n1p15 259:5 0 124M 0 part /boot/efi nvme1n1 259:1 0 1G 0 disk nvme2n1 259:2 0 1G 0 disk admin@i-00e339adeade5921e:~$
kihei/i-00e339adeade5921e 00:26
by SadServersfsck from util-linux 2.36.1 e2fsck 1.46.2 (28-Feb-2021) 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/nvme2n1p1 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> admin@i-0eacfe699faffbd49:~$