kihei/i-03f435703b3de22f0
by SadServersMore by SadServers
admin@i-0796b0b18597b116d:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT nvme0n1 259:0 0 8G 0 disk ├─nvme0n1p1 259:1 0 7.9G 0 part / ├─nvme0n1p14 259:2 0 3M 0 part └─nvme0n1p15 259:3 0 124M 0 part /boot/efi nvme1n1 259:4 0 1G 0 disk nvme2n1 259:5 0 1G 0 disk admin@i-0796b0b18597b116d:~$ sfdisk -l sfdisk: cannot open /dev/nvme0n1: Permission denied sfdisk: cannot open /dev/nvme1n1: Permission denied sfdisk: cannot open /dev/nvme2n1: Permission denied admin@i-0796b0b18597b116d:~$
kihei/i-0796b0b18597b116d 02:22
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:~$
kihei/i-0eacfe699faffbd49 05:33
by SadServerssystemd-remount-fs.service loade systemd-sysctl.service loade systemd-sysusers.service loade systemd-tmpfiles-setup-dev.service loade systemd-tmpfiles-setup.service loadeadmin@i-038138133fe07c0bf:~$ docker ps -a bash: docker: command not found admin@i-038138133fe07c0bf:~$ nmap localhost:5000 Starting Nmap 7.80 ( https://nmap.org ) at 2023-11-09 08:13 UTC Failed to resolve "localhost:5000". WARNING: No targets were specified, so 0 hosts scanned. Nmap done: 0 IP addresses (0 hosts up) scanned in 0.05 seconds admin@i-038138133fe07c0bf:~$ nc localhost 5000