GRUB inactivity on full HDD install

[Zeno Arrow]

Tried installing Wolvix 2.0.0 beta 2 on HD through Wolvix Control Panel GUI. Installing on HDD partitioned following way (1: Windows 2000, 2: EXT3, 3: EXT3, 4:SWAP). Partitions 2 and 3 were both initially setup as EXT4, but GUI installer did not have EXT4 option so chose to overwrite with EXT3. PC has two HDDs but only one HDD was involved in installation.

Installation process appeared successful until after questions for GRUB setup were asked (two menu options should have been created, one for Windows 2000, one for Wolvix). After requesting GRUB menu items, installer activity seemed to stop (last line on installer log was 'Configuring GRUB boot loader ...'). CPU activity dropped to around 3% (I left PC at this point for a few minutes), Wolvix DVD stopped spinning as fast. Computer was still fully responsive throughout.

Have included output from ls /boot, ls /boot/grub, cat /var/log/messages and dmesg in file 'wolvix commands.txt', which is attached to this bug report. Did not try running 'wolvix-control-panel' from command line, will be trying this next.

[Paul Tagliamonte (paultag)]

Thank you for taking the time to report this bug.

If you could please post the boot and boot grub from the target drive that would help -- also the correct way to run that is without in ( ls /boot, not ls in boot )

If you could attach /mnt/hda2 ( assuming wolvix target is hda2 ) data

most likely:

ls /mnt/hda2/boot
ls /mnt/hda2/boot/grub
cat /mnt/hda2/boot/grub/menu.lst

That would help a great deal

Thanks!

[Zeno Arrow (chopstickboogie)]

Hi Paul,

Details from ls /boot are in text file, I realised I typed in commands incorrectly and did them again before doing dmesg and the rest.

I will attach the other details you requested. In the mean time I can tell you about when I tried to run wolvix-control-panel from the terminal. The output indicates that the bug is related to inability to write to hda2 (or at least that's what it looks like to me). I've attached the output I could capture to this e-mail (will attach it to the bug report too). Let me know what you think.

Thanks,
Tom

________________________________
From: Paul Tagliamonte <email address hidden>
To: <email address hidden>
Sent: Wednesday, 24 June, 2009 23:32:06
Subject: [Bug 391835] Re: GRUB inactivity on full HDD install

Thank you for taking the time to report this bug.

If you could please post the boot and boot grub from the target drive
that would help -- also the correct way to run that is without in ( ls
/boot, not ls in boot )

If you could attach /mnt/hda2 ( assuming wolvix target is hda2 ) data

most likely:

ls /mnt/hda2/boot
ls /mnt/hda2/boot/grub
cat /mnt/hda2/boot/grub/menu.lst

That would help a great deal

Thanks!

--
GRUB inactivity on full HDD install
https://bugs.launchpad.net/bugs/391835
You received this bug notification because you are a direct subscriber
of the bug.

Status in Wolvix GNU/Linux: New

Bug description:
Tried installing Wolvix 2.0.0 beta 2 on HD through Wolvix Control Panel GUI. Installing on HDD partitioned following way (1: Windows 2000, 2: EXT3, 3: EXT3, 4:SWAP). Partitions 2 and 3 were both initially setup as EXT4, but GUI installer did not have EXT4 option so chose to overwrite with EXT3. PC has two HDDs but only one HDD was involved in installation.

Installation process appeared successful until after questions for GRUB setup were asked (two menu options should have been created, one for Windows 2000, one for Wolvix). After requesting GRUB menu items, installer activity seemed to stop (last line on installer log was 'Configuring GRUB boot loader ...'). CPU activity dropped to around 3% (I left PC at this point for a few minutes), Wolvix DVD stopped spinning as fast. Computer was still fully responsive throughout.

Have included output from ls /boot, ls /boot/grub, cat /var/log/messages and dmesg in file 'wolvix commands.txt', which is attached to this bug report. Did not try running 'wolvix-control-panel' from command line, will be trying this next.

[Zeno Arrow (chopstickboogie)]

Hi Paul,

Details from ls /boot are in the 'wolvix commands.txt' text file, I realised I typed in commands incorrectly and did them again before doing dmesg and the rest.

I will attach the other details you requested. In the mean time I can tell you about when I tried to run wolvix-control-panel from the terminal. The output indicates that the bug is related to inability to write to hda2 (or at least that's what it looks like to me). I've attached the output I could capture to the bug report (wolvix output.rtf). Let me know what you think.

Thanks,
Tom

[Zeno Arrow (chopstickboogie)]

Output for commands ls /mnt/hda2/boot, ls /mnt/hda2/boot/grub, cat /mnt/hda2/boot/grub/menu.lst shown in file 'wolvix more commands.txt'. Commands were performed after try to run full HDD installer.

[Paul Tagliamonte (paultag)]

Ah yes!

This issue is you have ran out of disk space on the install.

You should try creating a bigger partition to install on.

The installer is bombing, as the drive can not hold any more data -- this seems to not be an issue at all. Solution:

Allocate more HD space to the partition Wolvix is targeting.

[Paul Tagliamonte (paultag)]

Taking bug on while the issue is resolved

[Paul Tagliamonte (paultag)]

If you could also please post the following:

df -h
fdisk -l /dev/hda

[Paul Tagliamonte (paultag)]

OP has installed, after moving size up to 5 GB.