Hi guys. I have a problem after resizing root and home partitions. It seems like I can’t log in as usual due to problem with my
/home partition. I’m currently log in to tty in emergency mode with some error messages:
[DEPEND] Dependency failed for Fule System Check on <some-long-UUID>.
[DEPEND] Dependency failed for /home.
[DEPEND] Dependency failed for Local File Systems.
lsblk -f shows that there are no UUID and mountpoints and other column values for my used to home partition. And
etc/fstab shows my used to working partition with all infos including UUID for my boot, root, and home partition.
Please guide me to the right direction. I’m not familiar with the underlying Arch/Manjaro as I only use this OS for work.
sudo blkid -u filesystem /dev/sd*
Hi, thanks for replying! This is the output (sorry, can only provide a screenshot, can’t access from PC)
This is your live USB for Manjaro?
What do you have for storage physically in your computer? Do you know that?
Not live USB. My installed system. It’s the output from tty. I use NVMe.
EDIT: I think what you refer as the live USB is the
dev/sda*, not the machine I’m currently boot from. If so, then yes.
To me it looks like you did something with your partition on sda1 that now is TYPE=iso9660 … Not the what it should be
This looks like the output for a live USB for Manjaro to me.
So if you have NVME the command will not work. I’ll let Bogdan suggest you then.
No, no, please, give us your feedback. I have no experience with NVME.
NVME is not
/dev/sd* it is
/dev/nvme* example for me for
nvme0n1 259:0 0 931,5G 0 disk
|-nvme0n1p1 259:1 0 300M 0 part /boot/efi
`-nvme0n1p2 259:2 0 931,2G 0 part /
/dev/nvme0n1p1: UUID="0B8A-5447" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="a1169e7a-9ebd-3f4f-9abb-4266320289d7"
/dev/nvme0n1p2: LABEL="Manjaro" UUID="6a81f472-9ea9-40f8-85f6-7925c4bbe742" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="8a99d0da-a6c0-0144-9319-b613c12f50d0"
Besides that I don’t know, maybe muhifauzan should go back to basics, and explains what he did, to resize his partition, how he did it.
//EDIT: I never resized partition I don’t know anything about that.
//EDIT2: and I think there is a USB with Manjaro ISO flashed on it, at SDA
I use NVMe so I guess I should run
sudo blkid -u filesystem /dev/nvme* instead. This is the output (I hope I can give you guys better image):
The focus should be at p7 and p8. Those are the root and home partition respectively. There’s no type or UUID on p8. Is there anyway for me to recover it to it’s working state?
What I did with the resizing is I resize my home partition and move it to the right, which left empty space to be reclaimed by my root partition at its left. I did this using KDE partition tool from live USB. A failure happen when moving the resized home to the right with no specific detail. But it appears to be working fine from the tool as the empty space was in the left of the home partition. So I redo the root partition resize process and it proceed successfully. Then I try to reboot and I end up with this problem.
Yes, I have the USB plugged at the moment. To boot to live USB again just in case.
I think the root partition is OK as the UUID match from
etc/fstab, and its info like its type and mountpoint is correct. The home partition on the other hand doesn’t shows any info from
lsblk output. The partition is there, but there’s no info for its UUID, type, endpoints, etc. Can it be recovered?
Then you could do everything from the live USB instead of working from your broken system. Doesn’t solve the issue, but at least you could send proper info instead of unreadable photos of your monitor.
Will do. Sorry, my mistake. Will get back to you guys in a moment.
Outputs from live USB:
nvme0n1p5 is ESP
nvme0n1p6 is swap
The rest is Windows stuff
[manjaro@manjaro ~]$ sudo lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0 squashfs 4.0 0 100% /run/miso/sfs/livefs
loop1 squashfs 4.0 0 100% /run/miso/sfs/mhwdfs
loop2 squashfs 4.0 0 100% /run/miso/sfs/desktopfs
loop3 squashfs 4.0 0 100% /run/miso/sfs/rootfs
sda iso9660 Joliet Extension MANJARO_KDE_2112 2021-09-04-18-07-46-00 0 100% /run/miso/bootmnt
├─sda1 iso9660 Joliet Extension MANJARO_KDE_2112 2021-09-04-18-07-46-00
└─sda2 vfat FAT12 MISO_EFI F9F3-0D0C
├─nvme0n1p1 vfat FAT32 SYSTEM_DRV 6806-D2BE
├─nvme0n1p3 BitLocker 2
├─nvme0n1p4 ntfs WINRE_DRV DC04081D0407F8F2
├─nvme0n1p5 vfat FAT32 6E11-C296
├─nvme0n1p6 swap 1 0cc84f99-d047-4d4a-8783-de32f4c89253
├─nvme0n1p7 ext4 1.0 3c6bc575-270f-4037-9799-60527899ffa9
[manjaro@manjaro ~]$ sudo blkid -u filesystem /dev/nvme*
/dev/nvme0n1: PTUUID="93d6135e-2208-4684-805e-81d60d5b7457" PTTYPE="gpt"
/dev/nvme0n1p1: LABEL="SYSTEM_DRV" UUID="6806-D2BE" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="548e6697-26cb-48ad-9952-ae5d631588f3"
/dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="466d5071-aa63-42c1-9bf0-b78e078fefb1"
/dev/nvme0n1p3: TYPE="BitLocker" PARTLABEL="Basic data partition" PARTUUID="df678c97-c3d1-47a5-87f8-ba16f62dfd7e"
/dev/nvme0n1p4: LABEL="WINRE_DRV" BLOCK_SIZE="512" UUID="DC04081D0407F8F2" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="dd9664f2-20a5-4ef4-8f8a-207b0a5870a1"
/dev/nvme0n1p5: UUID="6E11-C296" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="e81e742a-bf09-4dcc-b95c-22e2c4a8f923"
/dev/nvme0n1p6: UUID="0cc84f99-d047-4d4a-8783-de32f4c89253" TYPE="swap" PARTUUID="21cc456b-0608-4946-82e0-1de12fb6c37d"
/dev/nvme0n1p7: UUID="3c6bc575-270f-4037-9799-60527899ffa9" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="09c9b4f9-3279-43a2-9fd6-0e00851e435e"
nvme0n1p8 property from KDE Partition Manager shows that the partition type is
unformatted, and try to change it to
ext4 gives me a warning that this operation will format the partition. Does that mean I can no longer able to use the partition as
/home without formatting it first?
Please help me find a solution in which I can recover it. There are some ongoing works that haven’t been pushed yet
testdisk to recover your data from that unformatted partition, before you do more changes. Do not apply the changes on KDE Partition Manager !!!
I guess when you resized those partitions, something did not go as planed.
Thanks for the help. I’m not familiar with the tool. Can’t recover anything. Looks like there’s no way around it. It will serves me as a hard slap for not making any backup before doing something risky.
To anyone who read this, be careful before resizing and moving a partition.