Hi, I just want to install kahelos which was released few days ago. But at Grub install after selecting no software raid disk, the whole machine gets frozen.
This is not the first time I try a linux distribution ( I used Archlinux few times), but never had such problem ever. I have MSI Wind Nettop 120 XP .
Grub problems
(26 posts) (17 voices)-
Posted 8 months ago #
-
htraki:
Hi.. A couple of questions:
a. is the system totally frozen or just seems to have hung? please try opening another virtual terminal, maybe we can try something from there...
b. how big is your /boot partition?
Posted 8 months ago # -
a. is the system totally frozen or just seems to have hung? please try opening another virtual terminal, maybe we can try something from there...
Maybe it is just a hung, because I can reboot with Ctrl+Alt+Del (but can not do anything else), and its getting stuck at umounting devices when rebboting.
b. how big is your /boot partition?
It was 300M, but I tried to do same thing without any separate /boot partition ( formatted / as ext3). No change, still getting hung at grub install.
Posted 8 months ago # -
I have the same problem, trying to dual boot with Win XP via uNetbootin/USB. I can format my partitions (creating primary partitions /dev/sda1 as ext4 and /dev/dsa2 as swap, I'm not creating seperate partitions for home, root, boot, etc), the packages install to sda1, I make it through configuration, my menu.lst looks fine (I just need to uncomment the Windows bootloader), it shows the right root for Kahel (hd0), I write it out, it shows 57 lines written, I exit, chose location for Grub as sda1, No to raid device, the system hangs. I can Ctrl+Alt+F2 to drop to shell, but if I reboot and run the installer but skip to the steps for Grub it returns "Can't find /boot/grub/menu.lst, are you sure Grub is installed?"
Frustrating, as I have the feeling I'm very close. Checking the new partition with Parted Magik shows that data has been written to the new partition, so it looks like it's just Grub getting me hung up. BTW, I've tried booting the partition using Super Grub Disc but it's not working.
Posted 8 months ago # -
^Sorry, the new partitions are sda2 and sda3, of course.
Posted 8 months ago # -
Well, I was able to get Grub going by running the installer, dropping to shell and entering "grub", "root (hd0,1)", "setup (hd0)", and rebooting. Then I get the Kahel Grub screen, but if I choose either the normal or safe mode version the system starts to boot but my monitor shuts off within a few seconds. Windows boots fine from there.
Posted 8 months ago # -
my system froze too after selecting no software raid disk. Fortunatley I had enough free space on my hard disk for another linux distribution. I installed Fedora 12 with grub and can boot both Linux systems and windows (after installing Fedora, I just had to add the entry for Kahel OS in the menu.lst file of fedora). Kahel OS boots up really fast now.
I used following partitions for Kahel OS; sda6 as boot 110 MB (ext3 filesystem), sda7 as root (ext4), sda8 home (BTRFS), sda9 swap about 2GB
Posted 8 months ago # -
i tried ext3 and ext 4 for my 256 mb boot partition ..and it casued them both to hang..
howver , when i selected ext2 for my boot partition , all when well and smooth..wierdPosted 8 months ago # -
correct :-) i forgot to mention that i always use ext2 for /boot, /tmp and root since it really doesn't make sense to journalize static portions of the fs. i use journaling fs on home and var only. this comes from server discipline/paradigm.
also i've research on this matter, but it seem that grub ext3/4 support isn't that thoroughly stable.
Posted 8 months ago # -
After I read your posts, I decided to give a second chance to kahelos, and tried to install it again.
Well folks, I am writing from kahelos :))) . Here is the recipe:/boot partition has to be ext2 formatted and I gave 500M size. Everything else can be formatted to any type of partition (I made / to ext4).
I can not wait till the guys make their own repository to work.
Posted 8 months ago # -
I'm currently investigating this issue, and there are currently 3 solutions.
1. increase the size of /boot partition. (256MB or higher)
2. bind /mnt/boot with actual installer /boot then install grub. Here's how to do the 2nd solution.
# run through the installer, then when installing grub, don't select anything on the raid 'yes or no' dialog, press 'ctrl-alt-f2', login as 'root' then type
$ mkdir /boot
$ mount -o bind /mnt/boot /boot
$ /sbin/grub-install --no-floppy --recheck --grub-shell=/mnt/sbin/grub --root-directory=/mnt /dev/sda #assuming /dev/sda is where to install grub. (no partition number means install to MBR)
$ umount /boot # then unmount the binded /boot3. When grub-install hangs, kill grub-install then perform the 2nd solution.
# press 'ctrl-alt-f2', login as 'root' then type
$ kill $(ps aux | grep -i grub-install | awk '{ print $2 }');
$ ## perform the second solution here.. ##then if everything goes fine, just type 'reboot' to reboot.
Happy New Year everyone!
Posted 8 months ago # -
htraki:
glad it finally worked out for you. aside from fewer boot problems on sticking to ext2 on static fs portions, you also gain read speed advantages. ext2 is already one of the old, thoroughly tested and stable technology. a lot of benchmarks from phoronix confirm this.
happy new year kaheling everyone.. :-)
Posted 8 months ago # -
Just wanted to post that I tried solution 2 and it still didn't work. I got the message "Probing devices to guess BIOS drives. This may take a long time..." After an hour it still hadn't done anything, no indication of activity on the hard drive or usb drive, so I powered down.
Posted 8 months ago # -
Corrections, it should be
/sbin/grub-install --no-floppy --recheck --grub-shell=/mnt/sbin/grub --root-directory=/boot /dev/sda
Posted 8 months ago # -
@joelbryan, thank you very much for posting this correction. As I have Ubuntu Karmic set up perfectly right now and it works for me, I'm going to wait till till fplolz releases his Live CD alpha to see if my wireless adapter works. But if Karmic messes up on me, I won't hesitate to try it!
Thanks again for posting. I'm still checking these forums daily. Please let me know if I can help with testing or English translations by posting here.
Posted 7 months ago # -
Corrections, it should be
/sbin/grub-install --no-floppy --recheck --grub-shell=/mnt/sbin/grub --root-directory=/boot /dev/sdaThis is why I can't be a RHCT because of these so called Command Line code or whatever you say. These are the things that I love the most when it comes to typing the command in Linux.
Posted 7 months ago # -
Thanks, guys, for this thread. As always, I install my Linux servers 'the Ubuntu/CentOS way' without much hitches. I've encountered this problem last night and almost gave up on Kahel for a server box. Tried again this morning and got the same frozen state issue at grub install step, then I thought of logging in to check the forum.
Posted 7 months ago # -
Congratulations to all the developers of the Kahel OS! I am always proud of Filipinos who excel in their own turfs and careers. With the emergence of a lot of Linux Distros, i always had the question in my mind if Filipino ITs were contributors to those many distros. The Kahel OS is the answer.
I downloaded the Kahel OS 64 bit ISO files yesterday. Burned the ISo files in a dvd. I was so excited to try it in my spare hardisk, a blank but formatted Maxtor with 320gb of space.
Pardon my word because I dont know what could be a lesser word for disappoinment or disappointed, but yes I was kind of disappointed to find out the ISO files I burned is'nt in a LIVE CD format. It had been my habit to try all linux distros first as live cd/dvd before I decide to install.
But really wanting to try it out, I clicked on the install. Here my disappointment became bigger. Installing the Kahel OS is like going back several years ago in my attempts to install Red Hat Linux and the Mandrake, with all those typings and clickings in the DOS mode.
I had tried the installing and using Ubuntu, from ver.7, ver.8, and now the latest version 9.10. My other drive in the same desktop is with Linux MInt 8. I also tried installing several other distros like Open Suse, Mandriva, Fedora, Linux Vixta, GOS,PC Linux OS,Knoppix,and even the OpenSolaris.
Installing those OSes was so easy, I could say it was a breeze installing them. The GRUB menu installation installed by itself with their own installers.
I am not a computer software expert, but I am an enthusiast. I dont want to be troubled with installation technicalities but I want to try using the Kahel OS.
So I hope with your "Open To Change" slogan, you will consider my suggestion to make the installation of the Kahel OS as easy as ABC.
Thank you very much and Kudos to all of you.Posted 6 months ago # -
I have downloaded the latest build of KahelOS (http://downloads.sourceforge.net/kahelos/kahel-desktop-050110-i686.iso) and the problem still exist.
And the only solution for me is to create /boot as EXT2, / as EXT4, then swap. I don't have a separate home.
Posted 4 months ago # -
How come you can't see that new "/boot" EXT2 partition with Nautilus ???
Posted 4 months ago # -
I am also having the computer freezing after selecting no software raid.
I have XP, PCLinuxOS and Ubuntu installed on my HD, and I have already created a swap partition.The PCLinuxOS grub is in my MBR. I wanted to leave the PCLinuxOS grub there and edit the PCLinuxOS grub to chainload Kahel OS. My intention is to install Kahel OS on my sda 8. I therefore tried to install the Kahel OS grub on sda 8 so that it would not go into my MBR. I also tried to install /home in sda 8. My sda8 is formatted to ext 4 and has 300+ Gb of free space.
The installation process went smoothly until it came to the software raid part. I am no expert in computers so any assistance will be greatly appreciated.
One final stupid question: will it work if I choose not to install grub?
Many thanks.
Posted 4 months ago # -
I am the one who posted the previous message. Based on what I have read in this thread, I reformatted my sda 8 to ext 2...and it worked! I have been able to install Kahel OS without any more problems. In fact I am sending this message from my shining, new Kahel OS! So please ignore my previous message.
To everyone who made this distro possible...THANK YOU!
Posted 4 months ago # -
@searcher1,
We are more than glad to hear that you were able to download, install and use KahelOS smoothly. Spread the word and let others benefit from it as well...
In fact, the brigade for donating blank cd's for reproduction has just began and we are very happy to let you know that voluntary donations are picking at a pace...
thank you very much.
Posted 4 months ago # -
Today I installed KahelOS at work and experienced the same problem (a DELL 760). But as described here, creating a /boot with ext2 solved that issue. The strange thing is that on my laptop I dont't have a boot-partition and although the installer friezed, the system went up after a cold reboot.
If I remember well, this was a known issue too on Fedora when they introduced ext4 using grub 0.97, it was compulsory creating a /boot partition with ext2.Greetz
Posted 4 months ago # -
I also had problems with GRUB installation, but I solved thanks to your solution. Still, I cant access GRUB and I get an "error: no such device grub rescue. I tried installing GRUB in sda where the Ubuntu GRUB should be and in my /boot partition. Any ideas? I would prefer if I could somehow recover it from my Ubuntu Live CD. Here's what my disks and partitions look like.
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x3cdf04a4Device Boot Start End Blocks Id System
/dev/sda1 * 1 12748 102398278+ 7 HPFS/NTFS
/dev/sda2 12749 38244 204796620 7 HPFS/NTFS
/dev/sda3 38245 60800 181181070 f W95 Ext'd (LBA)
/dev/sda5 38245 60800 181181038+ 7 HPFS/NTFSDisk /dev/sdc: 82.3 GB, 82348277760 bytes
255 heads, 63 sectors/track, 10011 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xa506a506Device Boot Start End Blocks Id System
/dev/sdc1 * 1 10010 80405293+ 7 HPFS/NTFSDisk /dev/sdb: 80.0 GB, 80000000000 bytes
255 heads, 63 sectors/track, 9726 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000a824cDevice Boot Start End Blocks Id System
/dev/sdb1 1 249 2000061 83 Linux
/dev/sdb2 * 250 285 289170 83 Linux
/dev/sdb3 286 1744 11719417+ 83 Linux
/dev/sdb4 1745 9726 64115415 83 LinuxDisk /dev/sdd: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x8f9c798aDevice Boot Start End Blocks Id System
/dev/sdd1 1 30401 244196001 c W95 FAT32 (LBA)Posted 4 months ago # -
hey thanx for replying I was kinda left without a pot to **** in because no one I know uses linux they're all the "theres another OS that isnt windows!?!? type
1. Proccesor: AMD Duron, 803MHz
RAM: 256mbs
Motherboard Model: Micro-star MS-6330
chippset: VIA VT8363a KT133A
Monitor: tatung
Graphics card: Radeon 8500 series
Sound card: VIA AC'97 Audio
Drives: liton dvdrw, creative cd
Hard drive: 150GBThis is not a dell PC this is a PC that I built myself (As you can see I have rather limited funds ).
I have succesfully burnt and run a live distro of kubunto with this pc which worked perfectly.
2. Yeah I just used the fedora core 4 partitioning utility im pretty sure that when i let it set up the partitions automatically it set a boot partition. But ive just gone to check recently and im dont think I can find one called \boot but im pretty sure there was one originally maybe when I fixed the MBR using windows recovery cd it got rid of it.
3. I didnt defrag the windows partition so that may be the problem.
4. I Picked Fedora to boot first
[Edited by Glorioso on 2005-07-24 06:21:40]Posted 3 months ago #
Reply
You must log in to post.