#can't boot into arch
322 messages · Page 1 of 1 (latest)
Cool thanks
So this is my problem
#quick-questions message
Well that's where I'm at
This is my problem
#quick-questions message
Everything here looks alright? (Installing grub)
Then why this happens?
Any ideas?
Idk... Reinstall Linux kernel?
I feel like there's a better way to fix it
This failed
Failed how?
In the last line it says - must be writable, it seems like permission issue.
installation process requires write access to this file.
change directory permssion like - sudo chmod -R 755 /boot/EFI/Linux/....
or change directory ownership...
Would this change anything? It says upgrade size is 0mb
I still don't know what the issue is. Why it's causing this problem and how exactly to fix it.
https://bbs.archlinux.org/viewtopic.php?pid=2182932
Followed this and ran
grub-install /dev/nvme0n1 --removable
grub-mkconfig -o /boot/grub/grub.cfg
Now I am able to see arch in grub
However I'm stuck at the terminal loading screen and it just says Loading Linux Linux...
Stuck on this screen for so long. How would I fix this?
Try this again
I ran pacman -Syyu. Is pacman -S linux linux-headers necessary?
@unreal owl don't syyu, syu is just fine
By installing the kernel again, the pacman hooks will rebuild the intramfs again for you
And you told me to run chmod -R 755 /boot/EFI/Linux ?
It's basically a roundabout way to run mkinitcpio -P but atleast it's making sure that everything is fine
Just these two?
Help?
It seems like size issue then, it's recommended to use 1 gb boot partition size if you want to have multiple kernal
The -R flag in the chmod command is used for recursion, meaning it will change the permissions of the directory and all its contents (subdirectories and files).
you can do as per advised by @kindred ice
Yeah so the permissions aren't an issue then right? It should've applied to all the subdirectories too
Alright so I guess I expand nvme0n1p1 to 1gb
Which is reinstalling linux and linux-headers ?
you can try out zen ker, headers is for installing modules to kernal
What's the best way expand nvme0n1p1 to 1GiB? I also plan on making a swap partition too. Though, I don't want to ruin the data in my main drive in nvme0n1p2.
Expanding it is gonna be annoying ngl
Best bet is to just reinstall everything 
Nah bro I got too many precious stuff on there. There has to be another way
Any other possible issue this could mean? How do I fix?
look like you need to go through a normal install which usually requires wiping a drive. i would suggest you buy a drive to install arch to.
And resize the end of your root partition to make some room
That sounds doable
So basically moving the EFI from the start of your drive to the end
But that would mean resizing p2 right?
Would that erase all data in p2. Resizing and formatting it all?
And it's just a conjecture
It shouldn't
Just resizing
I wanna avoid this
resizing can
Data loss. I don't Iike data loss
There's probably some precautions we can make here
Like making sure that all the data is in the start of the partition
But I'm not sure how to do it on Linux yet
Or if it even is necessary
You can just use testdisk and make a backup of the partition
Just to be safe
Then resize it with something easy like gpartef
By this I mean testdisk will make a backup of how your system was partitioned before
Or if you have btrfs, then you prob won't need to do anything
But idk
Don't have btrfs
Anyways
Although there's always a risk
If that was me, I'm going to be pretty comfy doing it on my own system
Deleting p1 and making another partition at the end and format it to efi?
And are you sure that's the problem?
And p2/root
I mean.. this is your goal right?
Well the problem is I have this
how long did you wait
Have we tried reinstalling grub yet?
Yep
Uh idk a few minutes. How long should I wait?
Yeah I did the whole grub-install thing
Grub-inst.. etc
Documented it somewhere in this chat
is the second partition a current linux install?
Wait a minute
Here is me reinstalling grub
is this a partition recovery?
vfat for uefi
Confused. What are you talking about
Filesystem
Looks fine to me. I believe that was the option once I selected EFI filesystem in cfdisk
Can you do mkfs.fat -F 32 /dev/xxx
That makes it fat32
I don't see how that will change anything
Did a little reading and it says vfat has backwards compatibility with fat
Seems ok to me
fat32 is kinda the old school file system
you can use a couple different filesystems for efi now
Yeah, I can use btrfs with it too but
vfat is usually more robust for efi partitions
Wait lemme check the wiki
This is from the grub manual
Vfat isn't listed there but
According to this, sometimes some apps think fat32 is vfat
So idk too why he'd have a vfat on an arch install
here's what the wiki says as well
And https://wiki.archlinux.org/title/GRUB#Unsupported_file_systems leads us to grub not being able to read the uuid
So maybe try changing grub cfg to use /dev/xxx as a trial?
uuid is usually a better idea
Anyways, I laid out the logic behind my thought so it's up to you guys now I guess
Yeah, but please read the wiki link I sent about unsupported file systems
It specifically recommended doing this
Because of this
🤷
Dw, we're both guessing
, trying to make sense of why he can't access his boot when it should've been possible
Idk man. I was just chilling on my computer, then all of a sudden it froze. I managed to fix this issue by reinstalling grub.
This was what I used to fix it. Idk if this caused any problems
I would feel like 512MiB would be enough
@unreal owl try it and see
1GB you said?
@fiery mango do I have to delete p1 or can I just keep it, make p3 and make p3 my boot
@fiery mango
i would suggest deleting partition 1 and recreating partition 1. making partition 3 would require resizing partition 1 to some small amount that would accommodate the size you need for partition 3. after that you would need to set the boot flags for partition 3 and reinstall to the new boot target.
Hopefully this doesn't break p2
if you dont touch partition 2 then it should be fine
what was the total space used for part 2 in percentage?
yeah thats just what is allocated
since its done we will have to roll with it
if the drive isnt 50% full it should be fine
but we can also use testdisk to try to recover anything that might have been lost
since the size is 1.8t i believe you will be ok
if you continue to have boot errors/issues, we can also walk you through smart tests.
He should've made a backup first but
Ehh
We'll see
I have a problem with expanding the p1 partition
it kinda caps out at 512MB
Tried making it 513MiB, wouldn't work
so this doesn't work
whats the total free space
Because the rest is occupied by p2
Which is why I suggested to shrink p2 and make a p3 to mount as your boot
Moving around partitions is a slippery slope that can lead to dataloss
But
It's your choice in the end anyways
ah ok. I swear one of you said to resize p1 and continue to use p1
sound like the changes have not been committed, like resizing your part 2.
What I suggested before was to reformat p1 to fat32
wait I thought we are making another EFI partition because my 512 p1 efi boot is too small
We're making another partition because you want to 
Expanding it to 1gb is fraught with dangers, but make a new one should be easier
Well Ayu said it was a size issue
Wellp, there we go then
Which was because of this command resulting in the writable error?
Yeah, "boot must be writeable"
but I think I was mounted to p2
Yeah
is that an issue?
No?
Damn. Wtf
dmesg
Yeah it said something about the geometry of p2
So I probably messed something up when shrinking it
Maybe
Try fsck or if you did backup the partition, do try to restore it
I don't believe I backed it up
Oh damn, I forgot to backup my 3d print files somewhere else
I think for this particular one yeah
I previously had done it manually and I think it broke or something and so I wanted to test out the archinstall script
I see
Then
Can you install dosfstools
And mount p1 to /boot
Then retry mkinitcpio -P
I'm just curious
Don't think I can install this without mounting to p2 can I
Can you even chroot without first mounting p2 /mnt?
No worries tho, testdisk can restore this, since you have this picture
So fsck did not do anything?
You can state the file system type
Some file systems will keep their attribute tables at the end of the partition. Fsck is also not recommended for some types of file systems. Your fstab should have a fsck flag to check or not, while it is mounting.
What was the file system?
Probably ext4
I would manually tell mount the file system type to try and help with mounting and also disable fsck on mounting
You are probably getting errors
Uh, turns out I need some files from the computer. Is there a way for me to mount and copy those files over to another drive?
@fiery mango didn't work
Testdisk
Please run
smartctl -t offline /dev/yourdrive
I will have to check the syntax
@unreal owl
uhh accidentally ran advanced scanning in TestDesk. This might take a while
Testdisk can copy files from one failing disk or disk being audited to another disk for chain of custody or good working new disk to replace the failing one
I will run this right after. Scan is at 40% right now
Yes please
@fiery mango
ok using testdisk I can find my files
doesn't seem to be deleted. can I move them to my other drive?
Yes
I can't seem to select another drive
Got a picture?
wtf
I tried copying and now all my files are missing from testdisk
from my /documents directory
It might not be in the same path that you are thinking
I'm so confused
I can't find the directory with all my files
This is what I see
It's supposed to have a bunch of files and directories in there
that was the last file I pressed "c" on too. idk if I accidentall deleted everything else
oh found them
in the Analyze menu
ok so I didn't accidentally delete anything that's good
so how do I copy these files to a different drive
@fiery mango
You will have to designate the source and destination in order to get the copy function
Read the bottom
Then read the top
C for copy mode
Select destination
C when destination is correct
yeah I did the same thing last time and when I pulled out the drive to check on another computer, it wasn't copied
Are you changing devices when you select destination?
yeah let me check again. I think this time it said 1 OK
Yeah sorry it's not an easier process
nah it could be worse. this tool seems alright
This software is usually for advanced or expert users so ease of use is not a concern
After you copy your files, can we check the drive health of your nvme with smartctl -H /dev/your device?
Are you able to select a different device for your destination during copy mode?
yeah I thought I did. I selected dev/sdb1 hopefully that was the correct selection
What's the file size?
43145 bytes looks like
Good it's not zero
I wonder if I'm choosing the correct directory
is there any other way?
I don't think I'm copying to the correct directory
Yeah sorry, there is not much I can assist here
and I can't just simply cp it because I can't mount and chroot it
hmm ok it says dev/sdb1 is not a directory
how else do I accesss my drive
Couldn't get copy to work but here's the smartctl. It passed as expected
@fiery mango
Before you get into testdisk please mount your sdb to /moveme and then you can copy to a directory
@unreal owl
is that possible? what do you mean like mount /dev/sdb /moveme?
Can't find ext4 filesystem, invalid fs_name, failed to read boot sector, failed to recognize exfat type
@fiery mango
hey, how much progress ?
Please make sure the p1 or partition numbers are correct or included
Also the mounting directories should be simple
@unreal owl
yo what happened to @fiery mango ? they're not in the thread anymore
oh they just popped up
yeah ima just use my arch laptop for now. Hopefully this doesn't break. Maybe I'll get back to solving the problem in another week. I'm kind of busy the upcoming week. Tryna get my sec+ cert
hmm where was I. Had a bit of a break
Oh yeah I was in the process of using testdisk to copy my system to another drive
what are the important directories again? home and something in etc
yeah etc and home
holy fuck so many failed files
hmmmmmm

