[Closed] Issue after improper resizing

Nima0908 · 2025-02-18 16:13:08

Hello,

recently I started a project for which i needed a seprate partition. So i resized my main partition to make room for the new one, but I forgot to resize the filesystem and didnt realize it till it was too late. I then rebooted into the arch usb and tried to first make the filesystem smaller with

resize2fs

but it didnt work and told me to do

e2fsck -f

which i did multiple times but it always failed. Then i realized i can just backup my other partition and merge it back into the main one and thats what i did (after 1 failed attempt idk what went wrong) and did

e2fsck -f /dev/nvme0n1p3

and then pressed

. This worked so i did

resize2fs -f

which worked too. I then rebooted into my system and got a complete blackscreen. No error, just a blackscreen. When i forced a shutdown it said

could find device to continue

. I thought it was because i accidentally formatted the partition but i booted back into the usb, mounted

/dev/nvme0n1p3

and did

ls /mnt

and it showed what it should have. Any idea how i can fix this?

Last edited by Nima0908 (2025-02-20 16:46:42)

V1del · 2025-02-18 16:40:47

Did the UUIDs change? Compare lsblk -f and your /etc/fstab as well as bootloader config. If any mismatch you need to fix the mismatches and fix your bootloader config and regenerate your initramfs with mkinitcpio.

Nima0908 · 2025-02-18 18:08:28

This was sadly not the issue. The UUIDs stayed the same. I updated fstab, the bootloader and the initramfs anyways but sadly the same issue eprsists

Head_on_a_Stick · 2025-02-18 18:46:31

Nima0908 wrote:

I updated fstab, the bootloader and the initramfs

That's a bit vague. Can you provide more detail? Which bootloader is this?

Nima0908 · 2025-02-18 19:30:05

Sorry, i forgot.I use grub. Also i dualboot windows. When booting up, i get the grub selector and if i bootminto arch, it loads the initramfs into ram, then it blackscreens and shows absolutely nothing, not even the cursor. When i forced a shutdown a shutdown i get the previously named error before its shutting down. It also shows that files are on /dev/nvme0n1p3 but it shows something like files: 10000/30000 but as far as ive seen it it shows the correct number of blocks

Head_on_a_Stick · 2025-02-18 20:48:42

Have you tried running the grub-install command again, just as you did during installation? How about grub-mkconfig?

Nima0908 · 2025-02-18 21:27:20

I tried grub-mkconfig but not grub-install. I dont fully understand why you think it should be a grub issue though because i can boot the windows bootloader just fine

seth · 2025-02-18 22:59:30

Remove quiet and any splash stuff from the kernel commandline in grub.cfg, add "nomodeset systemd.unit=multi-user.target" instead, can you boot the system?

Nima0908 · 2025-02-19 14:50:36

Now it says:

No resume Device found. Exiting

. Then it blackscreens and does nothing till i force a shutdown with the powerbutton. Then i see the same thing again and then its off.

seth · 2025-02-19 15:21:50

It tries to resume from hibernation, did you try to set that up?
Did you hibernate the system?

Most likely

Also i dualboot windows.

=> 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Nima0908 · 2025-02-19 15:50:28

Hello,
i havent set up hibernation. I whanted to and addet the resume hook in mkinitcpio but stopped afetr this. Also iam sorry for the incorrect informations, i was dumb. The previous settings you gave me with nomodeset… brought me to the tty, but i wasnt able to do more there. I remofved the resume hook and the nomodeset + systemd.unit=multi-user. target again and got back to the same issue as previously. When shutting down it showed that sddm was running, but i didnt see it becasue of the same blackscreen. I cant boot windows rn, even though I mounted the windows efi partition to /boot/efi while in arch-chroot os-prober didnt detect it and always just told me it couldnt find a efi thing on my usb (idk why). Faststart should be deaktivated though

seth · 2025-02-19 16:27:44

but i wasnt able to do more there

What does that mean, can you login and post a journal?

sudo journalctl -b | curl -F 'file=@-' 0x0.st

What if you omit nomodeset but keep "systemd.unit=multi-user.target"?

Nima0908 · 2025-02-19 16:43:49

Without nomodeset i get to the tty again. With i cant do more i meant i cant login. I put in my login, but it just tells me Login incorrect

seth · 2025-02-19 16:47:49

Keyboard layout? Have you tested to enter your password instead of your username (so you can see what you're typing there)?

Nima0908 · 2025-02-19 16:56:25

yes, i tried to enter the passwrod instead of the user name, it didnt work. The keyboardlayout is correct

Nima0908 · 2025-02-20 16:48:45

Hello,
i decided to mark the post closed, because i decided to just backup my partition using

dd if/dev/nvme0n1p3 of=/mnt/linux/nvme_backup.img bs=4M status=progress

and just reinstall the entire system and move over the files I want later on manually. I hope thats ok for you all

seth · 2025-02-20 20:56:38

"closed" specifically is used by mods to lock threads, sorry didn't get a notification for your latest post but would then assume that your /etc/{passwd,shadow} got damaged.
Other than that it's entirely your call how to deal with the situation.

Nima0908 · 2025-02-22 09:40:34

I just used [closed] because idk what else to use. Also while fixing ive accidentally overwritten /etc/passwd

Lone_Wolf · 2025-02-22 11:19:08

Prepending the title with [Gave Up] or [Abandoned] is acceptable and seems appropriate.

Arch Linux

#1 2025-02-18 16:13:08

[Closed] Issue after improper resizing

#2 2025-02-18 16:40:47

Re: [Closed] Issue after improper resizing

#3 2025-02-18 18:08:28

Re: [Closed] Issue after improper resizing

#4 2025-02-18 18:46:31

Re: [Closed] Issue after improper resizing

#5 2025-02-18 19:30:05

Re: [Closed] Issue after improper resizing

#6 2025-02-18 20:48:42

Re: [Closed] Issue after improper resizing

#7 2025-02-18 21:27:20

Re: [Closed] Issue after improper resizing

#8 2025-02-18 22:59:30

Re: [Closed] Issue after improper resizing

#9 2025-02-19 14:50:36

Re: [Closed] Issue after improper resizing

#10 2025-02-19 15:21:50

Re: [Closed] Issue after improper resizing

#11 2025-02-19 15:50:28

Re: [Closed] Issue after improper resizing

#12 2025-02-19 16:27:44

Re: [Closed] Issue after improper resizing

#13 2025-02-19 16:43:49

Re: [Closed] Issue after improper resizing

#14 2025-02-19 16:47:49

Re: [Closed] Issue after improper resizing

#15 2025-02-19 16:56:25

Re: [Closed] Issue after improper resizing

#16 2025-02-20 16:48:45

Re: [Closed] Issue after improper resizing

#17 2025-02-20 20:56:38

Re: [Closed] Issue after improper resizing

#18 2025-02-22 09:40:34

Re: [Closed] Issue after improper resizing

#19 2025-02-22 11:19:08

Re: [Closed] Issue after improper resizing

Board footer