N
some_random_nick
It was something like this:
A: Everybody shut the fuck up I got accepted into NASA
B: mind your language
A: fuck you
B: denys A the scholarship
It's not like the STD vanishes after ~~jumping~~ being pushed.
Fastboot was never enabled to begin with :-/
Ok, I foxed it! I looked around in the log of which I mostly understood nothing, but then I came acress the section where the kernel/shstemd mounts the drives and the error it spits out. Googling it gave me an arch forum post with the identical problem. Windows didn't shutdown correvtly the last time I used it and did something to the partition table. I'll update my post wiy the solution.
Tnx. I will report back tonight when I get around checking.
I'll check the BIOS stuff tonight.
As for the sata port, the new drive was connected to a different one so it can't be it. I did a drive health check and all seemed well and good.
I touhgt the same, but connecting a new drive and getting the same "read-only file system" error is really strange. I used the other drive for qbittorrent and it worked flawlessly before the update. I haven't come around to try any of the suggestions yet. I'll report back tonight.
I checked fstab and it's the same from day one. I tired adding stuff to it and shuffeling parameters around (like phtting rw,exec last), but it did nothing.
I'll give ut a shot first before the other suggestions. Tnx
Where would I start? Any commands I should try or just see if the livecd let's me take control?
Holy hell. Things went from pretty aweful to horendous. I regret having the abilty to read :-/