command-line-murders/i-0ce9591c57914129e
by SadServersMore by SadServers
fsck 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:~$
kihei/i-0eacfe699faffbd49 05:33
by SadServers└─nvme0n1p15 259:5 0 124M 0 part /boot/efi nvme2n1 259:2 0 1G 0 disk admin@i-0ee381b106ee6f241:~$ sudo lvdisplay admin@i-0ee381b106ee6f241:~$ df -hT Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 217M 0 217M 0% /dev tmpfs tmpfs 46M 368K 46M 1% /run /dev/nvme0n1p1 ext4 7.7G 6.1G 1.2G 84% / tmpfs tmpfs 228M 12K 228M 1% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock /dev/nvme0n1p15 vfat 124M 5.9M 118M 5% /boot/efi admin@i-0ee381b106ee6f241:~$ sudo mkfs.ext4 /dev/nvme1n1 mke2fs 1.46.2 (28-Feb-2021) /dev/nvme1n1 contains a LVM2_member file system Proceed anyway? (y,N)
kihei/i-0ee381b106ee6f241 07:52
by SadServersalternatives.log auth.log cast cloud-init-output.log daemon.log dpkg.log log runit unattended-upgrades wtmp apt btmp chrony cloud-init.log debug faillog e syslog user.log admin@i-0f97ad3dff720d3cf:/var/log$ cd /home/admin admin@i-0f97ad3dff720d3cf:~$ ls agent data datafile kihei admin@i-0f97ad3dff720d3cf:~$ tail datafile ^C admin@i-0f97ad3dff720d3cf:~$ cd data admin@i-0f97ad3dff720d3cf:~/data$ ls admin@i-0f97ad3dff720d3cf:~/data$ cd .. admin@i-0f97ad3dff720d3cf:~$ tail minio.log tail: cannot open 'minio.log' for reading: No such file or directory admin@i-0f97ad3dff720d3cf:~$ cd /var/log