You are not logged in.
A few months back I installed arch with grub legacy (I've previously had trouble with grub2, so I went with what I "knew").
Now, when removing ubuntu, I thoughtlessly moved and resized my arch partition (sda5), which held /boot. This naturally broke grub pretty bad.
Tools at my disposal: Super Grub2 Disk and GParted live disc.
Using sgd, I can boot windows 7, but not arch (I'm thinking whatever config it's reading is wrong).
I'm afraid I've installed grub 2, perhaps to both MBR and sda5, so all in all I have no idea what is going on by now.
Even when googling around, I have had huge trouble because all the guides I find are for legacy grub.
I would really appreciate some help in this matter, as I have lost the overview of the situation to such extend that I can't even figure out what guide to use.
Last edited by Bladtman242 (2012-05-02 18:52:23)
Offline
Since your current setup of grub is broken, why not try just reinstalling grub using the instructions on the arch wiki. Or, if you really feel that grub hates you, syslinux is really quite good and may be worth a try. Just read the wiki instructions as these are quite good.
Offline
I would, but the guide asumes you are running from the os you wish to boot, which I can't do.
I considered syslinux, but I seem to remember reading somewhere that dual-booting with windows is a bit complivated? Maybe I'm wrong?
Offline
I would, but the guide asumes you are running from the os you wish to boot, which I can't do.
Offline
For Windows 7 you need to point whatever bootloader you go with at its 100 MB "System Reserved" partition (if you use one).
Run "fdisk -l" from one of those live distributions and post it here.
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
Right, so i've successfully booted singleuser mode (I think). It said something about not beeing able to check the filesystem.
But now I still can't figure out how to install grub? the wiki says to run grub-install --directory=.... but I just get an error saying the --directory flag isn't recognized?
I'll post the result of fdisk -l in a short while.
Offline
That's good. You're almost there.
It said something about not beeing able to check the filesystem.
https://bbs.archlinux.org/viewtopic.php … 8#p1092548
Last edited by DSpider (2012-05-02 14:57:26)
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
Ahh, for some reason I can't even boot now.
Some kind of auto-rescue ran, and on next boot it completely stalled on acpid.
So, I removed the acpid entries from rc.conf but now it just stalls without acpid.
I'm starting to consider a complete fresh install, unless you have any good ideas?
Offline
Stalls on what? What does it say?
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
Says and does nothing. I just get a black screen with a grey cursor, nothing else and I can't type anything.
Offline
What if you put acpid back in rc.conf? In other words, back the way it was.
Or did you do something else in the mean time?
If you do too much at once, you can't pinpoint the problem.
Last edited by DSpider (2012-05-02 15:34:22)
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
maybe acpi=off in the kernel line will help?
ezik
Offline
DSpider: samething with acpid back on, it just writes out some acpid stuff first. Something like taking the first event and the waiting for events.
I didn't change anything else.
Offline
So I gather GRUB is now fixed? Because this sounds like a different issue... You should probably chroot again (from a live distribution) and update your system.
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
No
Still booting from the super grub2 disk. I don't know if it's booting in single user mode or not, but X certainly does not start so i figure I'm still pretty screwed?
Offline
I installed grub legacy again and now it works.
Thanks to all of you for the effort
Some day I'll have to learn the grub2 way.
It just really is a mystery to me.
Offline
GRUB 2 isn't that bad (huge wiki article tho, which might put you off at first). It uses two places for configuring: /etc/default/grub and the stuff in the /etc/grub.d/ folder. After you edit those you just run this to generate a grub.cfg:
$ sudo grub-mkconfig -o /boot/grub/grub.cfg
I used GRUB 2 for two years and a few months ago I switched to Syslinux. Much, much easier to work with. Like GRUB Legacy, there's just one file to configure, not several. And while GRUB 2 has 250+ files in /boot, Syslinux has like 5 (including the background image).
You should try it some time.
Last edited by DSpider (2012-05-03 08:25:31)
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
I'll be sure to check it out the next time I need to install or reconfigure a bootloader. Thanks
Offline