110 Replies
there we go
Plug in your other usb
yeah, and then
mount /dev/sdc1 /mnt, cd to /mntWait
ok I assume we are trying to get the gparted iso onto her other (fedora) usb drive?
No if its not ventoy
It is ventoy
wait
They both are
do you have the log_replay error?
with btrfs
hold on
they're both ventoy as it was mentioned earlier
So yeah do the mount
i want my hands on a screwed up log_replay btrfs partition
so i can bpftrace its mount for lore.kernel
😦
Ok let's recap
kernel devs want this
Cuz im getting confused
just boot gparted live
she can't rn
do a
btrfs check /dev/<partitoin>
then btrfs rescue zero-log /dev/<partition>Plug in second usb
thats all
I'm currently on the tty2 bazzite uso
Do
mount /dev/sdc1 /mntSecond usb just plugged
the thing making this more complicated is no backup computer, its just the not booting bazzite computer and the non live iso on a ventoy usb + a not working fedora 36 live usb as the tools to work with here
that's so complicated, at least she have another usb
Yeah if i new there was a live iso this would have been resolved way earlier
*a non-working fedora 36 live usb that is also on ventoy,
Rn im in the bazzite non live iso tty2
then the solution is to find the process keeping the block device busy and killing it
lsof /dev/sda3Input/output error
🫠
Keep in mind I'm still in the tty2
You ran my command?
try
fuser /dev/sda3From which usb
The one I'm currently on?
Yes
the one you're in
Ok
Done
Good
cd to /mnt
cd /mntand then wget that iso
Yes
Ok what was the link
Wait
lsIt shows my files yes
Its correct
your isos?
The fedora iso is on there too?
Yea
Good
wget then
yup, seems fine
wget https://downloads.sourceforge.net/gparted/gparted-live-1.7.0-8-amd64.isoSegmentation fault
the what
Is it because you unplugged and replugged your usb or something
Well try curl instead
curl will not output the file automatically
hold on
curl -O https://downloads.sourceforge.net/gparted/gparted-live-1.7.0-8-amd64.iso
(o, not zero)Input/Output error
damn
I assume we are trying to download the iso to the non-live bazzite usb drive, reboot and select the gparted iso in ventoy?
Does ping work
wait
Yes
does curl or wget even work?
Yes
yup
bro the bazzite iso is so bugged in tty
wtf
is it still even mounted?
since you had a segfault
mount check thiscan we even sort it out?
we can
i think the usb just unmounted itself from a connection error
what does
mount outputYeah since it mounted itself I would try a reboot
Since it doesn't appear here
Okay
Back on the iso yes?
i think another approach might be better here
I just want my disk back
😔
we're trying :dispair:
we'll get there
boot the bazzite iso
we'll try to instead make the device not busy
so you can just run the btrfs command
Okay
"the device" in this case means your main borked installation of bazzite btrfs partition of bazzite on the internal drive
the btrfs partition
known issue
a good idea is to after you are in tty2
to show output of
mount
shows everything that is mountedOk I'm back
What should i do first
Mount?
just
mountthe output of
mountmount and photo the output
it will just show a list of mounts and its targets
try
umount -f /dev/sda3
then try to btrfs check /dev/sda3
ayyyyy
now do
btrfs rescue zero-log /dev/sda3
What does this mean
Reboot into bazzite
Gonna get a blue screen on Linux
Wow, instead of a blue screen i got a boot screen
yesss
now download gparted live iso just in case
Damn. So it was simpler than I thought
I was thinking of downloading the iso live
Yeah I guess the bazzite iso also worked for it
Download both lmao
No harm in doing so
I'll make some space
Thanks everyone
You will have a lot of space after deleting bazzite non live iso
.side quest
Its not screwed up anymore
ah
probably also a good idea to update so it doesnt break again. Kyle mentioned this should be fixed in latest
it's always better to update your system even if you think there's no issues
no the issue is still ongoing in lkml
afaik
oh darn, I was going off this: https://discord.com/channels/1072614816579063828/1087140957096517672/1397626486566948945
if its not fixed and this is a 6.15 regression, is there consideration to reverting to 6.14? its eol, but idk what issue it could possibly have that is worse then failing to boot after hard shutdown
its eol and it doesn't have the big amd tsa mitigation
ltierally can't
also antheas would have to backport everything
oof fair enough
we have custom kernel
ik you do, but afaik the previous releases are all still tagged. ah I see crowdstrike flagged the new spectre variant as critical too 😦 I had seen amd's evaluation that they were low/med severity. Between a rock and a hard place I suppose
it mostly affects people who need to hard reset
which sucks, watchdog should catch that and force a reboot
but sometimes kernel is fine but you can't do anything
and t hen your only way out is force reset