paris/i-0de7a2efeec7e6379
by SadServersMore by SadServers
Physical volume "/dev/nvme1n1" successfully created. Physical volume "/dev/nvme2n1" successfully created. root@i-0353e493b4516ec3d:~# lsblk -l NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT nvme1n1 259:0 0 1G 0 disk nvme0n1 259:1 0 8G 0 disk nvme0n1p1 259:2 0 7.9G 0 part / nvme0n1p14 259:3 0 3M 0 part nvme0n1p15 259:4 0 124M 0 part /boot/efi nvme2n1 259:5 0 1G 0 disk root@i-0353e493b4516ec3d:~# vgcreate vg /dev/nvme1n1 /dev/nvme2n1 Volume group "vg" successfully created root@i-0353e493b4516ec3d:~# lvcreate -n lv -l 100%FREE vg Logical volume "lv" created. root@i-0353e493b4516ec3d:~#
kihei/i-0353e493b4516ec3d 01:47
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 SadServersadmin@i-037d1dae64cf5faa3:/usr/lib$ ^C admin@i-037d1dae64cf5faa3:/usr/lib$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT nvme0n1 259:0 0 8G 0 disk ├─nvme0n1p1 259:2 0 7.9G 0 part / ├─nvme0n1p14 259:3 0 3M 0 part └─nvme0n1p15 259:4 0 124M 0 part /boot/efi nvme1n1 259:1 0 1G 0 disk nvme2n1 259:5 0 1G 0 disk admin@i-037d1dae64cf5faa3:/usr/lib$ admin@i-037d1dae64cf5faa3:/usr/lib$ admin@i-037d1dae64cf5faa3:/usr/lib$ admin@i-037d1dae64cf5faa3:/usr/lib$ admin@i-037d1dae64cf5faa3:/usr/lib$ admin@i-037d1dae64cf5faa3:/usr/lib$ sudo lsbl