not really, I installed bazzite, added another internal drive, been playing games but some shits bei
not really, I installed bazzite, added another internal drive, been playing games but some shits being going wrong
Twas able to reboot, it's booting up now
Twhen you added the other internal drive, did you setup any automount stuff with it?
Tnot sure if that would affect what is going on here
Tbut messing with fstab entries have always been known to break stuff if you made an error
Talso would take the same advice that antheas mentioned
Trun a smart test to see if the drive bazzite is installed to is failing
Asudo smartctl --info /dev/nvme0n1 -aTyeah, I added the 2nd drive to fstab, but I was having issues even before that
Tthen i would enter that command and let it run
Aif your drive is named like that
Astick
| fpaste at the endToh right, yeah you want to make sure it's the correct drive
A90% is
Tand send the link it outputs here too
Tokay I will, one sec, just wanted to let ya know I tried to run the system update after the reboot and it failed with this
Kyour drive is fucked
Kall the confirmation I needed
T
Tyou may want to obtain a new drive if you financially can or use your new internal one as a replacement primary drive
Adont reboot until you backup your data
TI basically don't have any data on it
Aalso post smart test for our curiosity
TTunless I'm missing something it says it passed
KKshe big not happy
KAwtf only 177 power cycles
A100TB reads
Awhat are you doing chia mining
Atbh test looks normal
Amostly
Amine looks like that at least, minus the errors
Tif I'm not mistaken this drive was part of my Plex server, so those reads are from streaming content
A ratios are different
Tso like, definitely don't use this drive?
Tif you do not mind, i would try reinstalling on the other internal drive you put in
Tat least for a test, obviously backup the data for that one
KTI have another nvme I could use, I just gotta make sure it doesn't have anything on it first
Ainconclusive
Tokay shutting down and putting in my other nvme
A lol the legion go does in fact overheat the drive
KSo two things on rebase
K1: rebasing between DEs isn't supported, by us or upstream
K2: rebasing with layered packages can cause issues, but only if the image you're rebasing to has the same packages already or override removed them
K#2 isn't fatal and is easily fixed before or after the rebase
Kso no need to worry, just be aware of it
Kyou got it
