Computer wont boot

seth · 2022-10-29 21:09:15

So the FS is ~195MB bigger than the partition.
When you restored the partitions after trying to grow the root partition, did you restore the *exact* previous sizes?

Try to use one of the alternative superblocks, https://wiki.archlinux.org/title/File_recovery#e2fsck

dumpe2fs -h /dev/sda3
fsck.ext4 -n -b #superblock position here#

Kxed · 2022-10-29 21:11:25

seth wrote:

So the FS is ~195MB bigger than the partition.
When you restored the partitions after trying to grow the root partition, did you restore the *exact* previous sizes?
Try to use one of the alternative superblocks, https://wiki.archlinux.org/title/File_recovery#e2fsck
dumpe2fs -h /dev/sda3
fsck.ext4 -n -b #superblock position here#

All I said when restoring it was just 1000GB, because it didn’t tell me the exact size it was before…

Kxed · 2022-10-29 21:17:22

Also, how do I actually determine the superblock position?
(also, the filesystem state also said clean with errors. what.)

seth · 2022-10-29 21:39:22

The error is that the FS is configure to be bigger than the actual partition - if you're super lucky, that's all.
You can list the alternative suprtblocks w/ "dumpe2fs -h /dev/sda3" - I noted the command and linked the wiki entry detailing on it…

Kxed · 2022-10-29 21:42:00

seth wrote:

The error is that the FS is configure to be bigger than the actual partition - if you're super lucky, that's all.
You can list the alternative suprtblocks w/ "dumpe2fs -h /dev/sda3" - I noted the command and linked the wiki entry detailing on it…

I already did the command, i just dont know where it is…

Kxed · 2022-10-29 23:27:13

No, seriously, I did the command but I don’t know how to find the superblocks…

cfr · 2022-10-30 00:11:46

Kxed wrote:

No, seriously, I did the command but I don’t know how to find the superblocks…

Post the output if you're not sure how to interpret it.

Kxed · 2022-10-30 00:17:06

cfr wrote:

Kxed wrote:
No, seriously, I did the command but I don’t know how to find the superblocks…
Post the output if you're not sure how to interpret it.

Ok, I will. Sorry for posting another one of these…
https://share.icloud.com/photos/03bW72g … pfQK_u_pjQ

cfr · 2022-10-30 00:40:02

Sorry, I don't know how to use that output to locate the superblocks either. I would try this instead

dumpe2fs /dev/sda3 | grep superblock

The output with -h seemed to tell me everything but superblock locations, even though the manual page claims it will tell me only those.

seth · 2022-10-30 06:30:58

Either there're no backup superblocks or dumpe2fs (no longer) prints them (seems the latter since it doesn't here either)

mkfs.ext4 -n /dev/sda3

will also print the backup superblocks.
The "-n" is VERY!!! important, otherwise you'll create a new filesystem and your data is gone!

Do you already have a backup of the disk?
If you have a backup, you can just fsck /dev/sda3 and have it repair the filesystem. It was created on october 7th and last mounted and written to on october 29th, 15:12 - what was probably around the time of your last posts on the forum…

Kxed · 2022-10-30 12:15:25

seth wrote:

Either there're no backup superblocks or dumpe2fs (no longer) prints them (seems the latter since it doesn't here either)
Do you already have a backup of the disk?
If you have a backup, you can just fsck /dev/sda3 and have it repair the filesystem. It was created on october 7th and last mounted and written to on october 29th, 15:12 - what was probably around the time of your last posts on the forum…

I’m not sure if I do have a backup. I don’t know how to check if I do either. I remember one on the other disk, but I’m not sure…

seth · 2022-10-30 12:18:54

The idea would be to have you make an image of sda3 *now* before you manipulate it, so if the manipulation makes things worse, you can at least return to the current status quo.

Kxed · 2022-10-30 13:07:19

Unfortunately, there’s no more space on the other hard drive. Should I do it anyway?

seth · 2022-10-30 13:23:38

Only you can answer that question, depending on how problematic data loss on sda3 would be for you (in comparism to waiting to get a new backup drive first)
From the overall situation I don't think having fsck clean the FS will result in a disaster BUT: idk that for sure either.

cfr · 2022-10-30 17:51:36

seth wrote:

Either there're no backup superblocks or dumpe2fs (no longer) prints them (seems the latter since it doesn't here either)

dumpe2fs prints them if I don't use -h.

seth · 2022-10-30 19:33:17

Indeed, https://wiki.archlinux.org/title/Talk:F … uperblocks

Kxed · 2022-11-18 23:25:06

Alrighty, the second hard drive has arrived. I will check if it’s a fraud tomorrow and then, if it’s real and fast, use it on the computer to copy everything to. I will update you on the situation later.

Edit: LMAOOOOO IT WAS AN ENCLOSURE, HOW COULD I BE SO DUMB

Last edited by Kxed (2022-11-22 13:52:28)

Kxed · 2022-12-06 02:28:08

https://share.icloud.com/photos/0ebWMD0 … VOTCjC0h5w Does this mean that it was fixed?
Edit: i checked fdisk again and the end of the drive didnt change… how do i find where my partition originally ended?

Last edited by Kxed (2022-12-06 02:33:11)

seth · 2022-12-06 07:32:17

Post an updated output of "lsblk -f", testdisk should™ be able to recover previous partitions.
In doubt post its findings as well.

Kxed · 2022-12-06 13:26:32

Here’s the output of lsblk -f: https://share.icloud.com/photos/04a1AdQ … ocogB9BrJg
And the output of the testdisk file structure checker. https://share.icloud.com/photos/032WNEt … NHKECKjncA Maybe i found the correct disk size now?

Kxed · 2022-12-06 13:49:18

Since i think i found the correct partition end, does fdisk delete data when you delete and remake a partition to make more space?

seth · 2022-12-06 14:20:45

The partitions weren't mouted when you ran lsblk.

Does the testdisk result differ from the current layout (fdisk -l /dev/sda)

Please avoid posting photos of your monitor - if you've working internet

fdisk -l | curl -F 'file=@-' 0x0.st

will upload the output to a pastebin service.

Edit: fdisk writes the partition table - it does in and by itself not touch your filesystem.
Those would be later errors.

Last edited by seth (2022-12-06 14:22:39)

Kxed · 2022-12-06 15:07:25

seth wrote:

Does the testdisk result differ from the current layout? (fdisk -l /dev/sda)

Yes actually, it does! http://0x0.st/oDoX.txt

Kxed · 2022-12-06 15:15:57

Alrighty, so I set the drive end to the one shown in testdisk, but i still cant boot into arch! What else is going on here?

Last edited by Kxed (2022-12-06 15:16:17)

seth · 2022-12-06 15:18:56

Something went wrong on the 0x0.st post

What errors do you get for the failing boot and what does fsck now report?

Arch Linux

#26 2022-10-29 21:09:15

Re: Computer wont boot

#27 2022-10-29 21:11:25

Re: Computer wont boot

#28 2022-10-29 21:17:22

Re: Computer wont boot

#29 2022-10-29 21:39:22

Re: Computer wont boot

#30 2022-10-29 21:42:00

Re: Computer wont boot

#31 2022-10-29 23:27:13

Re: Computer wont boot

#32 2022-10-30 00:11:46

Re: Computer wont boot

#33 2022-10-30 00:17:06

Re: Computer wont boot

#34 2022-10-30 00:40:02

Re: Computer wont boot

#35 2022-10-30 06:30:58

Re: Computer wont boot

#36 2022-10-30 12:15:25

Re: Computer wont boot

#37 2022-10-30 12:18:54

Re: Computer wont boot

#38 2022-10-30 13:07:19

Re: Computer wont boot

#39 2022-10-30 13:23:38

Re: Computer wont boot

#40 2022-10-30 17:51:36

Re: Computer wont boot

#41 2022-10-30 19:33:17

Re: Computer wont boot

#42 2022-11-18 23:25:06

Re: Computer wont boot

#43 2022-12-06 02:28:08

Re: Computer wont boot

#44 2022-12-06 07:32:17

Re: Computer wont boot

#45 2022-12-06 13:26:32

Re: Computer wont boot

#46 2022-12-06 13:49:18

Re: Computer wont boot

#47 2022-12-06 14:20:45

Re: Computer wont boot

#48 2022-12-06 15:07:25

Re: Computer wont boot

#49 2022-12-06 15:15:57

Re: Computer wont boot

#50 2022-12-06 15:18:56

Re: Computer wont boot

Board footer