I'd like to avoid doing that as it could remove 6.8.9 as a boot option
I'll update if it's guaranteed to solve my issue.
I'd like to avoid doing that as it could remove 6.8.9 as a boot option
I'll update if it's guaranteed to solve my issue.
So I did that and nothing different happened. I'm sorry to keep taking your time like this do you know of any place, like a Discord server or something, that I can talk with somebody about this in real time.
I'm probably going to give this issue one more day to resolve before I give up and switch to Windows 11.
So I did that and nothing different happened. I'm sorry to keep taking your time like this do you know of any place like a Discord, server or something, that I can talk with somebody about this in real time.
I'm probably going to give this issue one more day to resolve before I give up and switch to Windows 11.
Heres what I got
root@localhost-live:/# ls -ld /home
drwxr-xr-x. 3 root root 4096 Feb 27 11:06 /home
root@localhost-live:/# ls -ld /home/adelie
drwx------. 15 adelie adelie 4096 Feb 27 18:00 /home/adelie
So I ran all three commands including the one /u/Max_P gave. I then changed the fstab and rebooted. I still couldn't login after that.
I then tried to login with TTY. it gave me the same error as in the post. I ran the three commands again and rebooted. still nothing
I logged in with my root account and ran the three commands again, rebooted and still couldn't login. I then fixed the fstab and now I'm back here again.
just to be clear i ran chmod 700 not 755.
Anything I should run in order to check my system? I must've done something wrong. Maybe it has to do with btrfs?
If you wouldn't mind, could you please explain what these command will do.
Also I'm back in the fixed state should I change my fstab back to the broken state before I run this?
I've done this several times and yes I can confirm everything mounted properly. The only issue as far as I can tell is that I can't login. I made an edit on the post to clarify this.
Old drive with current home directory = Drive A
New drive I wish to use a home directory = Drive B, I gave it an extra file named confirm.txt
I did have a root user account, I just didn't know how to boot into it
The first time around I forgot to copy my old home folder into my new home folder, but now I know that wasn't the issue.
After a bit of fiddling I decided to reinstall fedora.
I tried to separate my / and /home from the fedora installer; for some reason fedora wouldn't let me. Any time I tried to set my /home on my 1TB drive fedora would place my / into said drive. Just to clarify I want my / and everything in it to stay in my 500GB nvme and my /home to be in my 1TB ssd.
I just cut my loses and let fedora do it's usual install in Drive A. Drive B was left untouched.
For the new install I decided to do some thing different
In / I made two new partitions /new_home and /old_home
I went into fstab and made both drives mount; Drive A mounted into /home and Drive B into /new_home
I rebooted; Logged in as normal and Drive B successfully mounted
From here I reversed it, Drive A into /old_home and Drive B into /home
I rebooted; I entered into the KDE Login screen as usual. I typed my password correctly but after a short animation I was placed back into the login screen.
I logged in as root and checked if everything mounted correctly. It did. From / my /home would place me into Drive B the one with confirm.txt. And Drive A was in /old_home
So now I'm confused. Everything mounted properly but I still can't login with my account. I'm assuming this might be a KDE problem but I'd like your opinion.
Just to clarify on the proton thing, its an issue I faced on my old 80TJ Lenovo ideapad. I assume it's a hardware issue as Vulkan doesn't seem to work, and it has 4 gigs of ram. There's also the fact its over 9 years old.
I'm not really searching for a solution to my laptops problems, but thanks for the insight.
If you don't mind me asking what difficulties would I face switching desktop environments/ window managers as I'd like to experiment a bit(on my desktop).
Hey I found my solution here https://discussion.fedoraproject.org/t/solved-boot-hang-job-dev-disk-by-x2uuid-no-limit/119111
hope this helps.