After Frugal-Grub, hdax no more mounted


Forum: HD Install
Topic: After Frugal-Grub, hdax no more mounted
started by: ZoOp

Posted by ZoOp on Oct. 04 2005,21:31
I haven't found out any threads in the forum ('this year') about the following.
After a Lilo frugal install (hda1=winxp; hda2=image; hda5=home, opt, mydsl; hda6=swaps), everything works fine, and hda5 has been automatically mounted at dsl start. However, I installed Grub in order to have a boot window in which I can choose to boot winxp on hda1 too. I restart my machine with dsl-live cd; dsl starts, then I make a frugal install from live cd on hda2. I can't find the other options given in the "normal lilo" install I have just done (/usr/sbin/frugal_install.sh), but it should work however.
When finished, everything seems to be ok, dsl restarts (without cd now), but hda5 remains unmounted... I check menu.lst (/koppix/boot/grub/menu.lst); no way to change it; even logged as root and opening beaver as root, menu.lst remains RO, and it seems impossible to change it/i.e. I don't know how to change it. I mean, I can live with hda5 unmonted at dsl start and mount hda5 manually. But if maybe someone already has had the same problem, I would be very glad to learn a possible solution. I thank you all very much for now
yours
Z

Posted by JO+ on Oct. 04 2005,23:56
Hi ZoOp,
/koppix/boot/grub/menu.lst is the wrong 'menu.lst'. This one is located on the compressed CD-image and thus is RO (as all that starts with /knoppix/...).
The 'menu.lst' you need to modify should be: /mnt/hda2/boot/grub/menu.lst. If this directory doesn't exist there'a a problem with your grub installation - search the forum or the wiki for hints on how to install grub.

If you have the right 'menu.lst' you can add something like:
Code Sample
title DSL
 kernel (hd0,1)/boot/isolinux/linux24 root=/dev/hda2 ro ramdisk_size=100000 init=/etc/init apm=power-off hdb=scsi dma nomce vga=791 fromhd nobootscsi nobootusb frugal home=hda5 opt=hda5 syslog
 initrd (hd0,1)/boot/isolinux/minirt24.gz

Parameters above (you decide what to use):
- apm=power-off  (for an old pc w/o ACPI to power-off at shutdown)
- hdb=scsi  (my CD-ROM is on hdb - switch on SCSI emulation)
- dma (enables dma for ALL drives - could be risky!)
- nomce  (sorry, no idea ?)
- vga=791 (high-res, small characters during boot)
- nobootscsi  (skip check for SCSI controller - I don't have one, saves time)
- nobootusb  (skip check for USB stick - saves time)
- home=hda5 (acc. your post)
- opt=hda5
- syslog  (turn on logging to /var/log/messages )

cheers, Jo

Posted by ZoOp on Oct. 05 2005,12:24
Jo,
your are simply the best!
It works wonderfull. I have also learned from you the signification of some cheat codes (those which are unknown of you are also unkown of me, I'm sorry). It simply great to have such a quality support. Thank you  again very very much!
Warmest regards
yours
Z

Posted by robh on Oct. 24 2005,04:06
i'm having this problem too

having done a full hd install (not frugal) to hda1 successfully, i wanted to alter my boot options in

boot/grub/menu.lst

but when i open the file with nano or emelfm it is read only (yes i did sudo su). i then tried to mount the drive but get an error about 'not in fstab or mtab'. hda1 also does not show in the slit panel.

i'm confused??

could you help me in making it possible to mount hda1 and thus be able to edit the files on it?

thanks, rob

Posted by JO+ on Oct. 24 2005,11:51
rob,
as I have a frugal installation I am not quite sure what's going wrong in your case.
For a full HD-install the /boot/grub/menu.lst should be ok - unlike for frugal there is no compressed image and this file should be writable at least by root (sudo su - as you did).
However, this applies only if you have already booted into this installed DSL!!! If you are still working from CDR you still have a compressed image in /boot/grub and you should look into /mnt/hda1/boot/grub. If this is empty, try mounting it with:
Code Sample
sudo mount /dev/hda1 /mnt/hda1


If you have already successfully booted into your HD-DSL, there are a few things you could check:
1.  is your DSL really on hda1? look into /etc/fstab, should contain something like:
Code Sample
proc            /proc           proc    defaults        0       0
/dev/hda1       /               ext2    defaults,errors=remount-ro 0       1

The fstab lists the relation between devices(partitions) and the mountpoints of the filesystem. The single / means the root (not to be mixed up with user 'root') of the filesystem is located on /dev/hda1. If hda1 is listed in fstab, but with a mountpoint different than / then your filesystem's root is not on hda1.
2. try to mount hda1 manually:
Code Sample
sudo mkdir /xyz
sudo mount /dev/hda1 /xyz
cd /xyz
ls -al

if you get an error here there's something wrong with your installation.
(to undo above enter:
cd /
sudo umount /xyz
sudo rmdir /xyz
)
3. To make hda1 appear in your slit panel you probably have to add to  ~/GNUstep/Defaults/mount.app:
Code Sample
 "mountpoint./mnt/hda1" = {
   mountname = hda1;
   eject = no;
   icontype = hd;
   showcapacity = none;
   ignore = no;
 };


If you don't find a solution, please list your fstab in this thread.
Jo

Posted by JO+ on Oct. 24 2005,11:59
Don't know what's wrong with this forum - I logged in - forum welcomes me, but when I added a reply it called me 'guest' again
:(  ?
(not too important though   :;):  )

Posted by JO+ on Oct. 24 2005,12:15
rob,
2 posts are not enough, must be the age  :)

I've forgotten the easiest checks you could do, just enter:
Code Sample
mount

(lists you all that is currently mounted incl. your root filesystem)

Code Sample
df

('disk free' shows also what is mounted + capacities)

Jo

Posted by AwPhuch on Oct. 24 2005,15:31
Quote (JO+ @ Oct. 24 2005,08:15)
rob,
2 posts are not enough, must be the age  :)

I've forgotten the easiest checks you could do, just enter:
Code Sample
mount

(lists you all that is currently mounted incl. your root filesystem)

Code Sample
df

('disk free' shows also what is mounted + capacities)

Jo

df -h is alot easier to read

I have never just tried the mount command...thanks for that one!

Brian
AwPhuch

Posted by robh on Oct. 24 2005,22:05
ok jo, thanks for your detailed reply.

in response here are the thiungs both you and AwPhuch recommended i check

my fstab reads...(RO in emelfm)

/dev/hda1  /  ext2  defaults,errors=remount-ro  0  1
proc   /proc   proc   defaults  0  0
etc etc

and the 'mount' command gives this...

>/dev/hda1  on  /  type ext2  (rw,errors=remount-ro)
>/proc  on  /proc  type proc  (rw)
>/dev/pts  on  /dev/pts  type devpts  (rw)
>/proc/bus/usb  on  /proc/bus/usb  type usbdevfs  (rw,devmode=0666)

and just for completeness
df -h gives.....

Filesystem                 Size   Used   Avail   Use%  Mounted on
/dev/hda1                 473M  273M  177M   61%    /

now i'm really confused as all of the above seems to say that the installed to drive is actually hda1 and  is corrupted somehow. although i could be missing something (hopes).

btw, i am not still running from the cd.

I hope you can help cus i just managed to install jre 1.5.0.05 and limewire lastnight (both from .bin files)  after much trying.

Posted by robh on Oct. 24 2005,22:11
ps i changed my signature as i am now going for the full install... not frugal. just to prevent confusion if you are trying to help me.
Posted by robh on Oct. 26 2005,05:23
can anybody shed some light on my previous posts re. unmounted hd after full install? i did another install today to see if there was something i overlooked, but i can't see it.

the install works ok apart from the drive i installed to (hda1) is read only and no matter what i try i cannot make it rw.

hope someone can help.....

Posted by JO+ on Oct. 26 2005,20:17
Brian,
'df -h'  was new to me and it IS easier to read - thanks for this one!

Rob,
to be honest I am also confused, now let's see...
Your 'mount' says /dev/hda1 is RW at least to the one who has the right to. What exactly are you doing to write to /boot/grub/menu.lst ?

Don't know how familiar you are with Linux and you call yourself a noob, but seems you are seeking for challenges :) : 'managed to install jre 1.5.0.05 and limewire lastnight (both from .bin files)'. So here is step by step, what I would do:

Open a terminal as root (via Fluxbox menu > XShells > Root Access) and:
root@box:~# whoami
root
root@box:~# cd /boot/grub
root@box:/boot/grub# ls -al
drwxrwxr-x    2 root     root         1024 Jul 30 11:47 .
dr-xr-xr-x    4 root     root         1024 Jul 11 21:49 ..
-rw-rw-r--    1 dsl      staff          30 Jul 11 21:41 device.map
-rw-r--r--    1 root     root         7904 Jul 11 21:55 e2fs_stage1_5
-rw-r--r--    1 root     root         7440 Jul 11 21:55 fat_stage1_5
-rw-r--r--    1 root     root         6912 Jul 11 21:55 ffs_stage1_5
-rw-r--r--    1 root     root         8640 Jul 11 21:55 jfs_stage1_5
-rw-rw-r--    1 root     root         1506 Aug  1 11:52 menu.lst
-rw-r--r--    1 root     root         7104 Jul 11 21:55 minix_stage1_5
-rw-r--r--    1 root     root         9568 Jul 11 21:55 reiserfs_stage1_5
-rw-r--r--    1 root     root          512 Jul 11 21:55 stage1
-rw-r--r--    1 root     root        95712 Jul 11 21:55 stage2
-rw-r--r--    1 root     root         6560 Jul 11 21:55 vstafs_stage1_5
-rw-r--r--    1 root     root         9320 Jul 11 21:55 xfs_stage1_5
root@box:/boot/grub# nano menu.lst     (or  vi  menu.lst, whatever you like better)
 
Now do your changes, in nano then  ctrl-O , <enter> , ctrl-X,  (or in vi:  ZZ)  and

root@box:/boot/grub# ls -l menu.lst
-rw-rw-r--    1 root     root         1507 Oct 26 21:48 menu.lst

If for some reason menu.lst is RO, e.g. looks like that
-r--r--r--    1 root     root         1507 Oct 26 21:48 menu.lst
you can change access modes before editing:
root@box:/boot/grub# chmod ug+w menu.lst   (allows write for user and group, however, normally for root this isn't needed )

If for some reason menu.lst has another owner, e.g. looks like that
-rw-r--r--    1 virus    trojan         1507 Oct 26 21:48 menu.lst
you can change user and group before editing:
root@box:/boot/grub# chown root:root menu.lst   (however, normally for root this isn't needed )

And if you see this on the screen:
root@box:/boot/grub# ls -al
drwxr-xr-x    2 root     root           80 Oct 26 21:28 .
drwxr-xr-x    3 root     root          100 Oct 26 21:28 ..
lrwxrwxrwx    1 root     root           29 Oct 26 21:28 device.map -> /KNOPPIX/boot/grub/device.map
lrwxrwxrwx    1 root     root           27 Oct 26 21:28 menu.lst -> /KNOPPIX/boot/grub/menu.lst
then you have a 'frugal HD install' i.s.o. a 'full HD install', but I think we have checked that before with 'mount' :).

Hope this helps in some way,
Jo

Posted by robh on Oct. 26 2005,21:59
now then

thanks again for your response jo. here is where i come with the contrition.

i went to bed late last night, still with the same problem, woke up this morning and cd'd into /boot/grub after sudo su-ing, nano-ed menu.lst and it was writeable. I have tried to emulate what must have been a human error on my part but cannot. so, sorry for the long posts u gave, but thankfully all is well in dsl town. its been a good learning experience tho...

:D

thanks again jo, off to sort out the ess 1869 soundcard now... lol

Powered by Ikonboard 3.1.2a
Ikonboard © 2001 Jarvis Entertainment Group, Inc.