monaco/i-0ccf0dcdab9feba23
by SadServersMore by SadServers
admin@i-06e3508dbb92a146f:~$ sudo lvcreate -n lv -l 100%FREE vg Logical volume "lv" created. admin@i-06e3508dbb92a146f:~$ sudo mkfs.ext4 /dev/vg/lv mke2fs 1.46.2 (28-Feb-2021) Creating filesystem with 522240 4k blocks and 130560 inodes Filesystem UUID: a5fe2a18-cddd-4655-8847-89dc10aad8ef Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912 Allocating group tables: done Writing inode tables: done Creating journal (8192 blocks): done Writing superblocks and filesystem accounting information: done admin@i-06e3508dbb92a146f:~$ ls
kihei/i-06e3508dbb92a146f 00:31
by SadServers< Server: Werkzeug/2.3.7 Python/3.9.2 < Date: Wed, 28 Feb 2024 20:58:43 GMT < Content-Type: text/html; charset=utf-8 < Content-Length: 207 < Connection: close < <!doctype html> <html lang=en> <title>404 Not Found</title> <h1>Not Found</h1> <p>The requested URL was not found on the server. If you entered the URL manualllling and try again.</p> * Closing connection 0 admin@i-045e1170ba04ed4e1:~$ vi mysolution admin@i-045e1170ba04ed4e1:~$ curl localhost:5000/index. -v
paris/i-045e1170ba04ed4e1 05:40
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:~$