[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


File: 1760689947512.png (6 KB, 118x152)
6 KB
6 KB PNG
fuck GRUB
>>
lol just use uefi and don't install multiple operating systems on the same drive
>>
>>107024611
>there is any alternative to GRUB?
Yes.
>>
dasboot
>>
>>107024611
>That picture

I swear that grub destroyed my hard drive but I can never prove it.

>Dual booting two separate drives, Ubuntu and Windows using Grub.
>Ubuntu updated.
>Couldn't boot, had to fix a catastrophic failure in Grub, took a long time to research and fix.
>Boot into Ubuntu, video and network drivers both don't work, took hours to research and fix with computer having to be plugged into network using a physical ethernet cable.
>Fix the problem on Linux, but so fed up with troubleshooting Linux I decide it's time to uninstall it and only use Windows even though I just fixed it.
>Back up Linux files I need.
>Back up Windows files I need.
>Use Windows command prompt to remove Grub boot entry.
>Reformat Windows drive with new Windows installation with Linux drive unplugged.
>Plug in Linux drive, use disc management in Windows to format it so now it's backup internal storage.
>Windows starts blue screening constantly.
>Reformat again, eventually starts blue screening again, repeat the process.
>Do a disc check on the drive, it's got corrupted sectors, trashed and unusable now.

That's how it happened a few years ago. It was an ssd about six months old, fucking TRASHED. Thankfully just a 500gb. Still though...
>>
File: 1760854109232.jpg (31 KB, 587x516)
31 KB
31 KB JPG
>>107024611
having sex with software is bad for your health.
>>
>>107024768
>Ubuntu
use oracle linux faggot
>>
use systemd-boot
>>
>>107024768
It's because Windows thinks it is appropriate to patch GRUB themselves. I've never had a single issue with GRUB with just GNU/Linux on the drive. That's how it should be - one operating system.
>>
>>107024865
That doesn't work if your system is BIOS.
>>
>>107024768
I'm guessing that by "format" you mean Windows gave you a popup when you connected the device saying "would you like to format this?" and you affirmed it. The problem is that this often only removes or formats some types of partitions and assigns them a new letter path. It doesn't fully wipe the disk the same way a lower level utility like diskpart can.
>>
>>107024866
Yea but it physically destroyed the drive that windows was on dude... Like wtf bro? Short version.
>Windows on drive 1
>Ubuntu on drive 2
>They share Grub in common, nothing else.
>Ubuntu on drive 2 updates.
>This breaks Grub for both drives.
>I fix Grub, was surprised I was even able to.
>Ubuntu on drive 2 has messed up drivers on boot, I then fix that.
>Decide I am done with Linux (at least for now). I back up important stuff from both drives.
>I boot into Windows on drive 1 to remove Grub as a boot entry using the command prompt. I think the first blue screen might have happened sometime around here, I was planning on an imminent reformat already before it happened.
>I reformat and clean install Windows on drive 1, then I plug in drive 2 and format it so it will be internal backup storage.
>Windows shortly thereafter starts blue screening, quite often, sometimes on idle. I clean install it again, same thing.
>Check disc drive 1, it has bad sectors.
>Drive 2 that previously had Ubuntu is unscathed. Drive 1 was the casualty.
>Drive 1 has had several slow type (true) formats, bad sectors every time, it's trashed, not even good for backup storage.

Ubuntu on drive 2 updated, this causes a Grub error, Grub is the only thing in common with drive 1, drive 1 dies PHYSICALLY, broken hardware. This is what happened.
>>
>>107024964
I've formatted the drive in every way that's out there, it's simply busted. Quick, slow, and diskpart using the command prompt. I have tried repairing sectors too. It's so strange but what I'm saying it how it happened.
As an experiment I tried using it as backup storage, can't even do that. If I download a steam game to it for example as the secondary drive, it'll do weird shit like the download of the game might just get stuck. Your game might work for a while but then won't start up anymore. It has bad sectors now, cannot be fixed.

If anyone ever tells me grub ruined their drive I will believe them.
>>
lilo
>>
ZFSBootMenu Portable edition
>>
>>107024611
lots
>>
>>107024611
So many. You can just boot the kernel directly via your fucking firmware if you want.
>>
>>107024875
Its 20-fucking-25, uefi in pcs is 13 years old, who the fuck is still using bios to boot instead of uefi? Get a fucking clue
>>
opencore xd
>>
>>107025924
Only way to have true separation between OS's is to select boot order from bios.
>>
EFISTUB
>>
>>107025979
So? You can select uefi devices to boot too from uefi
>>
syslinux, but GRUB is the comfiest
>>
>>107025924
I do, what the fuck are you gonna do about it fucko? Enjoying your signed bootloaders?
>>
>>107024638
this is the only way

i learned this the hard way too
now I have 4 OSs, each on it's own drive
plus I have other drives for data
>>
>>107024865
>systemd-boot
WTF, this is actually real
>>
>>107024768
I don't understand how you're blaming grub when you are so incompetent.
>>
I use systemd boot but idk what the diference even is. Shit just works for me idc anything else
>>
>>107024768
grub definitely has malware on it
>>
>>107025924
holy fvck, /g/ now has grain fed npc niggercattle grazing the pastures instead of chad x220 and athlon enjoyers, the west truly has fallen.
>>
>>107024611
oldfag, we used to use LILO, now ELILO
>>
>>107024611

PXE
https://en.wikipedia.org/wiki/Preboot_Execution_Environment
>>
i use grub because its the easiest to install. all the others are too complicated
>>
File: IMG_0975.jpg (33 KB, 456x549)
33 KB
33 KB JPG
Systemd boot. Nothing outside systemd.
>>
I've never had any problems in grub before wtf are you anons talking about
>>
>>107024638
>>107027278
Nope. Even when you install multiple operating systems on separate drives, the ESPs will usually be merged if you don't unplug the other OS drive before installation.
>>
>>107025924
If I were a consumer whore, I'd run Windows. Older hardware works completely fine unless you're doing some types of games.
>>
>>107030480
There's being a consumer whore, and then there's daily driving a pre-UEFI system in 2025.
>>
>>107030638
Pre-UEFI systems work just fine, unless you're a Windows weenie. Hand waving doesn't change that any, you're still a consumer whore if you insist people throw away perfectly functional BIOS systems.
>>
>>107024611
why do you even need a bootloader kind sir, just boot an UKI right off the mobo
>>
>>107030909
t. proud UKI user proudly cutting boot times
>>
>>107030896
The point is are you genuinely daily driving a pre-UEFI system, or are you just virtue signalling?
>>
Efistub. Luv efibootmgr and ugrd :DDD
>>
>>107030909
i can't be fucked with managing boot entries or baking UKIs. i just want to point my motherboard to BOOTX64.EFI and have computer go vroom
>>
>>107030936
UEFI is the work of the devil
>>
>>107031833
i'm not a big fan of it either, but that's not really the point of the conversation.
>>
>>107024611
Yes, refind
>>
>>107024611
systemd-boot
i use it on a non-systemd distro and it isn't slow on opening encrypted volumes and doesn't default to us-qwerty layout. though grub can have encrypted boot but only with older KDF.
don't see much reason for downloading GRUB on systemd distros like arch if you're doing it manually, it's already built in.



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.