kihei/i-07f4849a9d187ab57
by SadServersMore by SadServers
admin@i-0eb2b2fb37bbcf158:~$ mkdir /tmp/kihei admin@i-0eb2b2fb37bbcf158:~$ ^[[200~mount -t tmpfs -o size=2G tmpfs /tmp/kihei bash: $'\E[200~mount': command not found admin@i-0eb2b2fb37bbcf158:~$ mount -t tmpfs -o size=2G tmpfs /tmp/kihei mount: /tmp/kihei: must be superuser to use mount. admin@i-0eb2b2fb37bbcf158:~$ sudo mount -t tmpfs -o size=2G tmpfs /tmp/kihei
kihei/i-0eb2b2fb37bbcf158 00:44
by SadServersps _chrony 593 1 0 03:44 ? 00:00:00 /usr/sbin/chronyd -F 1 root 600 1 0 03:44 ? 00:00:00 /usr/bin/python3 /usr/share/ended-upgrade-shutdown --wait-for-signal _chrony 601 593 0 03:44 ? 00:00:00 /usr/sbin/chronyd -F 1 root 684 2 0 03:45 ? 00:00:00 [kworker/u4:4+events_unboundadmin 714 563 0 03:45 pts/0 00:00:00 bash -l admin 718 714 2 03:45 pts/0 00:00:00 /usr/bin/python3 /usr/bin/as0901153058fcbfd -q -i 2 /var/log/cast/i-0e0901153058fcbfd admin 721 718 0 03:45 pts/0 00:00:00 /usr/bin/python3 /usr/bin/as0901153058fcbfd -q -i 2 /var/log/cast/i-0e0901153058fcbfd admin 722 718 0 03:45 pts/1 00:00:00 sh -c /bin/bash admin 723 722 0 03:45 pts/1 00:00:00 /bin/bash admin 727 723 0 03:45 pts/1 00:00:00 ps -eafww admin@i-0e0901153058fcbfd:~$ curl -v http://localhost:500
paris/i-0e0901153058fcbfd 00:39
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:~$