Re: Now lost boot dir
> David Baron wrote:
> >
> > Diagnostics failed in attemts to reach you, trying emial with .com
> >
>
> Your e-mail arrived as one continuous long line. There
> were no line
> breaks whatsoever. I don't know what tool you used, but
> please try
> to fine a more user-friendly tool next time. I had to manually
> reformat the whole thing. Also, you sent the e-mail to me only
> and did not copy the list.
>
Never saw anything like that. This stuff was simply cut and paste from a kde3 konsole window into the on-line mailer of my provider (I am running off a live CD, though kmail might be OK). The original that did not make it through was done in kwrite and that probably formatted OK. Sorry 'bout that. (But wait, doesn't the whole world handle line breaks like ... Windows (CR + LF))? I will inform the provider about what happened!)
> > Note: I am not using an initrd so update-initramfs is not relevant!
> >
>
> That's right, I forgot about that.
>
> > $ cat /mnt/hdb2/etc/fstab
> > # /etc/fstab: filesystem table.#
> > # filesystem mountpoint type options
> dump pass
> > # ROOT/dev/sdb2 / ext3 defaults,errors=remount-ro
> 0 1
> > # BOOT/dev/sdb1 /boot ext3 defaults,errors=remount-ro 0 2
> > /dev/sda4 none swap sw 0 0
> > /dev/sdb3 none swap sw 0 0
> > proc /proc proc defaults 0 0
> > /dev/fd0 /floppy vfat
> defaults,user,noauto,sync,exec,umask=022 0 0
> > #second master is now on /dev/hdc
> > # maintaining older mount directories for convenience
> > #changed by david baron
> > #/dev/hdb /mnt/hdc iso9660
> defaults,user,noexec,noauto,unhide 0 0
> > # Added by KNOPPIX, made auto by david (I am taking out auto
> for summer)
> > /dev/sda1 /mnt/hda1 vfat
> auto,user,exec,umask=000,uid=david,gid=david 0 0
> > # SHARED DATA (left this way for convenience)
> > /dev/sda5 /mnt/hda6 vfat
> auto,user,exec,umask=000,uid=david,gid=david 0 0
> > # AUDIO was on hdb--changed to hdc, keep older directories for
> convenience> /dev/sdc5
> > /mnt/hdb5 vfat noauto,user,exec,umask=000,uid=david,gid=david
> 0 0
> > # Do I need such as this?
> >
> none /proc/bus/usb usbfs defaults 0 0
> > # temporary memory for qemu, et al?
> > none /dev/shm tmpfs rw,size=512m 0 0
> > # mount win98 image to my test folder
> > /mnt/hda6/win98.img /home/david/test auto
> noauto,loop,offset=32256,umask=022,user> # mount mp3 player
> > #/dev/sda /mnt/mp3player auto
> defaults,user,noauto 0 0
> > #/dev/sdb /mnt/pictureframe auto defaults,user,noauto 0 0
> > # mount cell phone usb
> > #/dev/sda1 /mnt/phone auto
> defaults,user,noauto 0 0
> > #/dev/sdb1 /mnt/phone-sd auto
> defaults,user,noauto 0 0
> > #/dev/sdd1 /mnt/phone-sd auto
> defaults,user,noauto 0 0
> > # NEW STUFF FOR LVM/dev/DB-
> LVM/LV_OPT /opt ext3 defaults 1 2
> > /dev/DB-
> LVM/LV_USR /usr ext3 defaults 1 2
> > /dev/DB-
> LVM/LV_VAR /var ext3 defaults 1 2
> > /dev/DB-
> LVM/LV_HOME /home ext3 defaults 1 2
> > #/dev/DB-
> LVM2/LV_AUX /mnt/aux ext3 defaults 1 2
>
> I'm really confused. As I've said before, I don't know
> anything about LVMs,
> so that may be part of the problem. But I don't see
> anything mounted as /.
> I also see a bunch of stuff that is confusing. I see stuff
> mounted on pass 0,
> for example, that I would expect to see mounted on pass 2.
> And you're not
> using any uuids in /etc/fstab. Maybe with this
> information, someone else
> who is familiar with LVMs can make sense of this.
>
The LVM are added by the lvm system config program and I seriously doubt if they are the problem. If there be no root, those LVM volumes are irrelevant. The lines:
# ROOT
/dev/sdb2 / ext3 defaults,errors=remount-ro 0 1
are this way in the actual file! That was one line break you missed in all the mess!
Those numbers 0 0, et al, were placed by the original Knoppix hard-disk installation. I might have copied and so propagated them in a few places. If you feel that some of them are not proper, they can be easily enough changed. I do not fully understand them so just left them as-is.
> >
> > Here are more. Note from knoppix-5 CD, paths reference hd...
> rathern than sd... disk device names.
> > This is why other sd stuff was commented above as will need to
> be changed.
> >
> > $ ls -Al /dev/disk/by-id/
> > total 0
> > lrwxrwxrwx 1 root root 9 Aug 30 10:00 ata-WDC_WD400BB-
> 00DEA0_WD-WMAD19873947 -> ../../hda
> > lrwxrwxrwx 1 root root 10 Aug 30 10:00 ata-WDC_WD400BB-
> 00DEA0_WD-WMAD19873947-part1 -> ../../hda1
> > lrwxrwxrwx 1 root root 10 Aug 30 10:00 ata-WDC_WD400BB-
> 00DEA0_WD-WMAD19873947-part2 -> ../../hda2
> > lrwxrwxrwx 1 root root 10 Aug 30 10:00 ata-WDC_WD400BB-
> 00DEA0_WD-WMAD19873947-part3 -> ../../hda3
> > lrwxrwxrwx 1 root root 10 Aug 30 10:00 ata-WDC_WD400BB-
> 00DEA0_WD-WMAD19873947-part4 -> ../../hda4
> > lrwxrwxrwx 1 root root 10 Aug 30 10:00 ata-WDC_WD400BB-
> 00DEA0_WD-WMAD19873947-part5 -> ../../hda5
> > lrwxrwxrwx 1 root root 10 Aug 30 10:00 ata-WDC_WD400BB-
> 00DEA0_WD-WMAD19873947-part6 -> ../../hda6
> > lrwxrwxrwx 1 root root 9 Aug 30 10:00 ata-WDC_WD800JB-
> 00ETA0_WD-WCAHL5220676 -> ../../hdb
> > lrwxrwxrwx 1 root root 10 Aug 30 10:00 ata-WDC_WD800JB-
> 00ETA0_WD-WCAHL5220676-part1 -> ../../hdb1
> > lrwxrwxrwx 1 root root 10 Aug 30 10:00 ata-WDC_WD800JB-
> 00ETA0_WD-WCAHL5220676-part2 -> ../../hdb2
> > lrwxrwxrwx 1 root root 10 Aug 30 10:00 ata-WDC_WD800JB-
> 00ETA0_WD-WCAHL5220676-part3 -> ../../hdb3
> > lrwxrwxrwx 1 root root 10 Aug 30 10:00 ata-WDC_WD800JB-
> 00ETA0_WD-WCAHL5220676-part4 -> ../../hdb4
> > lrwxrwxrwx 1 root root 10 Aug 30 10:00 ata-WDC_WD800JB-
> 00ETA0_WD-WCAHL5220676-part5 -> ../../hdb5
> > lrwxrwxrwx 1 root root 10 Aug 30 10:00 ata-WDC_WD800JB-
> 00ETA0_WD-WCAHL5220676-part6 -> ../../hdb6
>
> Based on this, if you want lilo's stage 1 boot loader installed
> to the master boot record,
> it looks like you would specify
>
> boot=/dev/disk/by-id/ata-WDC_WD400BB-00DEA0_WD-WMAD19873947
>
I tried doing that and that is what shot me down so I went back to regular direct /dev/ references.
The bootloader does get to /dev/sda just fine.
> in /etc/lilo.conf. Speaking of which, I asked for a copy
> of that file also, which you did not
> provide.
Here is the lilo.conf. I will delete most of the comments to keep it short and rebreak the lines:
$ sudo cat /mnt/hdb2/etc/lilo.conf
# Generated by liloconfig
# This allows booting from any partition on disks with more than 1024
# cylinders.
lba32
# If the special name CURRENT is used, the root device is set to the
# .....
# kernel image is used. It can be changed with the rdev program.
root=/dev/sdb2
# Specifies the boot device
boot=/dev/sda
# Enables map compaction:
#....
# floppy disk.
#compact
# Default menu for Debian. (Using the images from debian-bootscreen)
# from Philipp Wolfer <phil@newswriter.org>.
bitmap=/boot/debian.bmp
bmp-colors=1,,0,2,,0
bmp-table=120p,173p,1,15,17
bmp-timer=254p,432p,1,0,0
# Install the specified file as the new boot sector.
# LILO supports built in boot sectory, you only need
# to specify the type, choose one from 'text', 'menu' or 'bitmap'.
#.....
#install=menu
#menu-title="David's Computer"
install=bmp
# Specifies the number of _tenths_ of a second LILO should
# wait before booting the first image. LILO
# doesn't wait if DELAY is omitted or if DELAY is set to zero.
# delay=20
# Prompt to use certaing image. If prompt is specified without timeout,
# boot will not take place unless you hit RETURN
prompt
timeout=50
# Specifies the location of the map file. If MAP is
# omitted, a file /boot/map is used.
map=/boot/map
# Specifies the VGA text mode that should be selected when
# booting. The following values are recognized (case is ignored):
# .....
# can be obtained by booting with vga=ask and pressing [Enter].
vga=6
# things can get a little too big
ramdisk=8129
image=/boot/vmlinuz-2.6.34-davidb
#initrd=/boot/initrd.img-2.6.34-davidb
label=2.6.34
append="nmi_watchdog=0"
read-only
(I took out all the others since I did not reinstall them...)
*******
> Please provide the /etc/lilo.conf file too, and please, somebody
> who knows LVMs
> give this guy some help. This is out of my area of expertise.
Reply to: