#Fresh secureblue install takes up to 1 hour 30 mins to boot????
1 messages · Page 1 of 1 (latest)
Heres the full journalctl logs to my knowledge but any ideas as to what its even hanging on?
I'm assuming the point where it jumps from 02:39 to 10:39 is just the time zone being set or something, and if so, the logs you posted only cover a timespan of about 15 minutes
so if it took much longer than that to boot, it seems likely that the problem is before the kernel even started
at a glance, the one thing that stands out in the logs is the repeated occurrence of "kernel: critical medium error, dev sdc..." errors, which looks like some sort of hardware problem
Weird
Any idea how id further diagnosis it?
The drive the os is installed to should be fine
And then what lets it seem to just.... work eventually?
Anyway to narrow it down? Its a fresh install the ssd is of full health to my knowledge and it doesnt explain why nixos booted fine either
yeah idk
does it happen consistently or just the once?
Nope happens consistantly
Didnt happen with a kubuntu install
Didnt happen withthe nixos install
No fucking clue happens every restart
💀
This computer has historically had a bit of unexplained jank but it otherwise should run fine
Every other OS does
I have no idea where id start to figure out why secureblue in particular is bitching
wait so just to clarify, how does the timestamp at the start of this log file compare to the time when the computer started booting?
Well i didnt keep track because this is the first time i even login to the fucke thing thinking a restart would
But iirc lemme see
Approximitly 17 minutes
So then wtf....
Wait.... dev sdc?
is /dev/sdc not your main drive?
.... 2:39 is exactly when
the journalctl starts
so that must mean it isnt evewn fucking booting into the kernal
till 17~ later
i think
nono it is
lemme se
`sda 8:0 0 931.5G 0 disk
├─sda1 8:1 0 812.3G 0 part /run/media/user/5b5869a6-e6a2-4353-aca6-2e6261bf5297
└─sda2 8:2 0 119.2G 0 part
sdb 8:16 0 111.8G 0 disk
├─sdb1 8:17 0 600M 0 part /boot/efi
├─sdb2 8:18 0 2G 0 part /boot
└─sdb3 8:19 0 109.2G 0 part
└─luks-6163915e-21fa-4f54-a4b4-ba97619688a5 252:0 0 109.2G 0 crypt /var/home
/var
/sysroot/ostree/deploy/default/var
/sysroot
/etc
sdc 8:32 0 3.6T 0 disk
sdd 8:48 0 931.5G 0 disk
└─sdd1 8:49 0 931.5G 0 part
zram0 251:0 0 8G 0 disk [SWAP]
anything look off here?
yeah its this FUCKEN DRIVE
SDC
LITTLE FUCKER
is that an external HD or something?
Ok.... now this fomputer doesnt boot at all
Why
Nothings on that drive
Nothing is installed there
Why the fuck
Now this is really bricked
Why the fuck what is it even usinf that drive for?????
The ufei wont even boot anymore
W h a t ?
can you disconnect that drive?
Thats what i did
It just bricked it
Is the bios on....
No
No it isnt
Ho...
Nooooo
Nooooo
That wouldent make any sense
litertally how
...do you already have backups of any data you care about? because this is getting to a level of stuff not working where my next step would probably be to wipe the drive, reinstall the OS, and restore data from backup
also given that there are error messages suggesting hardware problems it'd be a good idea to have backups anyway
Nope i dknt
But
I cant reinstall the OS
If it doesnt even BOOT ONTO UFEI
Why is the UFEI ON THIS DRRIIIIIIVE
There are many like it
But this spaghetti mess is mine
Fucken decade old
Wtf it doesnt even boot with the drive
Wtf got loose
How and why did moving it make it not boot at all
Bruh
Did i just.....
I think i did
Welp
Fml
NOW its actually completely bricked
FUUUUUUUUCK
Welp
It was good knowing you
You served me very well
But due to my mistake you are now ultra bricked
You lasted over a fucken decade
Through fried ram
And janky full hardwate replacement
Off thrift store drives
And spaghetti cables
And 5 different oses multiple reinstalls
🫡
It was an honoe
Cleaely irs time for this thing to fucken rest lmao
Issues solved
Its dead like dead dead now