You are not logged in.
no, i didnt sudo rm -rf /
what i did may be just as bad, i edited the partitions on the disk i was currently booting arch from, and now whenever i turn it on, it just gets stuck starting "/dev/disk/by-uuid/98aea665-Za53-425d-a47a-2174a8035b27"
and the partitions look fine when i check them with fdisk from an endeavour usb
i just need to know if this is fixable or not
Offline
Altering the partitions might/will have changed the UUID?
lsblk -f
Offline
as it turns out, the uuid was the uuid of my root partition, so im not sure what i should do about that
and a critical piece of information i left out: i removed my swap partition and put that space on my root partition, thats what i was doing editing my partitions
Last edited by inchrys (2024-11-20 21:57:54)
Offline
Yes, of course that *was* the UUID of the root partition, the question is what is the UUID of your your partition *now* since it very likely has changed.
Offline
so how should i go about finding out the new uuid
Last edited by inchrys (2024-11-20 22:05:31)
Offline
lsblk -f
Offline
seth wrote:lsblk -f
already did that and got the same uuid, thought there was something else i should have done
Offline
Post the output of lsblk -f, remove the quiet parameter from the kernel commandline, boot the system and link a picture of the stall.
Offline
Offline
You could have posted that as text, only the stalled boot will be hard to share in that form.
Also https://bbs.archlinux.org/misc.php?action=rules - EOS isn't supported here.
The UUID however still matches your OP, but the drive is an MMC and you might lack the relevant kernel modules in the initramfs, try the fallback image.
Offline
my bad about the endeavour thing
and uh, it still doesnt boot with the fallback image
Offline
Ah, imgur is an album.
The device is found, you're probably fsck'ing it.
From the live distro, try to mount the partition, if that fails run an fsck and just a quick guess: did you grow the partition but not the filesystem?
Offline
Ah, imgur is an album.
The device is found, you're probably fsck'ing it.From the live distro, try to mount the partition, if that fails run an fsck and just a quick guess: did you grow the partition but not the filesystem?
yeah i did
Offline
Did what?
Resize the FS, not resize the FS, mount the partition, fsck, it …
Offline
As I understanding it well, inchrys wanted to remive his swap partition. Then the Pc does not more boot.
UUID and PARTUID (not the same) are well shown with command blkid
As seth has suggested, try fsck the partition:
fsck.ext4 /dev/mmcblk0p2
And what is you lsblk output?
When you have removed your swap partition, have you removed the swap entry in your fstab?
Mount the parition with the root file system end check your /etc/fstab. Comment the swap line out.
Wait... mmcblk0p2? SD-card? Is that an Raspberry Pi?
Offline