Octavian Helm

Long time.

@Oli Oi!

Hola

Uhm, welp

Oh good, my drive is so old that it doesn't even show up on the specs list for that drive line.

if not I can still downgrade I guess

In fact, let's see if there isn't a newer firmware version, maybe it fixes that.

Looks like it should be a downgrade

Now to find out how that's done. Working on it.

even though I bought them together and they're from the same series they on different firmware versions

wew lad

I don't think they have a different firmware.

Same series.

I'm just not sure what I'd gain from that.

technically yes, it would be a pain but yes

well, considering that I have two identical drives in the computer and only one of them shows this behavior, I guess it might be a faulty hard drive

It's the same behavior on different ports

Alright, it seems to be the hard drive

I'll be right back

yep, now to find out why my hard disk won't play nice with my bios

there is a leftover grub install on another disk

cheers

ok, there we go

what exactly will that do?

If the issue persists then it looks like a hard disk issue.

I'll start by switching to another SATA port first.

but where does the grub rescue shell come from if grub is installed on the device that isn't recognized? :D

it certainly is a hardware/bios thing

it is consistently there after a hot reboot

the UUID there is correct, it just isn't available after cold boot

I checked the generated grub.cfg and it does

BUT it doesn't explain why there is a grub rescue

It doesn't get recognized by my BIOS on cold boot, which explains why the partition can't be found

I wasn't sure whether I checked if the disk is there on a cold or hot boot so I just checked again

@kos your initial thought was correct

Alright, this is getting weird.

gonna reboot and try something real quick

and I can't answer that question

:D

how can grub rescue start

I know what you're going to ask now

yea

but I'm not sure if that could cause this particular behavior

I should maybe add that grub is installed on the root partition, so no extra boot partition at the start of that disk

yes

the UUID that it can't find initially is the correct UUID, I just checked manually

I just have no clue what could cause that

upon cold boot, grub complains that it can't find the device with UUID xyz, after a reboot from the grub rescue console it suddenly finds said UUID and boots just fine

ran into something quite interesting

sadly yes