LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   strategy to replace mobo (https://www.linuxquestions.org/questions/linux-hardware-18/strategy-to-replace-mobo-603975/)

dgermann 12-02-2007 03:47 PM

strategy to replace mobo
 
Hi--

I farkled my mobo last night. Actually had a fire on it while installing new memory!

So: now I am getting a new mobo. Old one was Intel 915GAVL; new one is Intel DG33FB with Intel core 2 duo E4300.

The hardware tech says the bootup sequence (I currently have Ubuntu Dapper 6.06 on the HDD) does not recognize the chipset. Just to be sure I had something that I could put a new OS on, I had him put in a new serial ATA HDD 80 gig drive.

Now my question is how do I go about restoring my system so I have access to what was there before, both data and apps and OS?

1. Do I install Ubuntu Gutsy 7.10 on the new drive, boot from there and then mount the old drive with some new designation, like /olddrive?

2. Do I simply get a live CD, boot from there and then make some changes in config files? Which config files or other changes?

3. Something else entirely?

It might help to know that I have an nvidia graphics card on it and from that am running dual monitors using Twinview.

Thanks!

syg00 12-02-2007 04:11 PM

Grab a liveCD and copy /home out to a new partition - either disk, doesn't matter, but on the new one makes sense.
Grab the "alternate" CD for gutsy, and install onto the new disk, nominating the /home partition (not to be formatted), and install fresh.
You can't upgrade from Dapper, so this would be a good way to do it - and if it all goes to hell, you still have you old disk intact.
You can get the NVIDIA driver on gutsy - easy.

moxieman99 12-02-2007 04:29 PM

Quote:

Originally Posted by dgermann (Post 2977771)
Hi--

I farkled my mobo last night. Actually had a fire on it while installing new memory!

Thanks!

I am DYING to know how you did that.

David1357 12-02-2007 05:25 PM

Quote:

Originally Posted by moxieman99 (Post 2977798)
I am DYING to know how you did that.

He should be forced to provide pics before we help any more.

dgermann 12-02-2007 05:55 PM

syg00--

Thanks for your quick response!

A couple of questions--1. I am guessing that your two lines that start "Grab" are alternatives, not step one and step two of the same thing. Correct?

2. Oops! I got the regular CD. How important is the "alternate CD?" Can I find the same files on the one I grabbed?

3. What does it mean I cannot upgrade from Dapper?

4. How do I make a new partition on the new disk? It has been years since I figured out how to make partitions....

5. Here is some additional info:

As it stands, it will only partially boot: It starts to boot and hangs at "waiting for root file system."

After several minutes it says "PCI: Failed to allocate mem resource #6:" and a bunch of numbers. Then "ALERT! /dev/sda1 does not exist. Dropping to a shell!" Then it gives me a BusyBox shell.

The fire? I shut down the computer, unplugged it. Inserted memory sticks. Powered back on. When I turned the power on, there was a little light that came on near the memory sticks, and near it, a flame! It took me a few seconds to figure out I needed to pull the plug instead of hit switches to shut off the power, but when I did, the fire died away. Tech guy said it could have been just the time for the mobo to give up. Or maybe I put the sticks in incorrectly. Bottom line: I don't know how it happened.

Any idea how to get past that place in the boot sequence?

moxieman99 and David1357--hope that answered your questions about the fire. If not, film at 11:00! (Sorry, no film!)

Thanks folks!

syg00 12-02-2007 09:28 PM

Do everything I suggested. If you get a liveCD with gparted you can do the partitioning from that. It's a GUI similar to partition magic. You need the alternate CD to control the install better - like assigning partitions to mount points. I don't think the normal installer allows expert/advanced options - never used to anyway.

Ubuntu update manager doesn't support skipping level(s) - so to go from 6.06 to 7.10 (skipping 7.04) you have to do a clean install.

To test the boot, take the S-ATA disk out and see if that works.

dgermann 12-02-2007 10:05 PM

syg00--

OK, Thanks!

OK, the new drive (is that SATA? It has a thin red cable, about 1/4 inch wide, while the old one has a flatter, wider--1 1/2 inches--and grey cable) is plugged into both the old drive and the mobo. So do I just disconnect it from the power source and the mobo and try that?

Are there any jumpers or other connections I need to change to see if I can just boot up the old disk?

If it does not make sense to jump from 6.06 to 7.10, then how do I just keep the 6.06 system I have on there? What if I do the download for the 6.06 system?

I think the tech said it would not boot up when he had only the old drive in the machine.

Is it possible it is trying to boot from the completely blank new drive and that is why it complains about no root file system on sda1?

Thanks for your help. I will get back to this tomorrow when I am fresher.

Thanks!

syg00 12-03-2007 07:48 AM

I think I misunderstood - I thought you were trying to boot from the old disk.
If you are seeing this attempting to boot the CD, then it's likely either;
i) you didn't burn the CD as an "image", or
ii) you don't have the CD before the hard disk(s) in the BIOS boot order.

Adjust as appropriate.

dgermann 12-03-2007 08:23 PM

syg00--

Nope, you did not misunderstand. I do want to boot from the old drive.

An update: It turns out that both the drives are SATA. The old drive is 200GB, the new is 80GB, if that helps.

They are plugged into slots SATA0 (new drive) and SATA1 (old drive). The schematic says the other two SATA slots are SATA4 and SATA5. The grey cable is for a floppy.

There was a sheet of paper in the mobo box which said that for non-Vista OS installation to go into bios > Advanced > Drive and change it to configure SATA as ide. It had been AHCI. I made this change but it still stopped at Waiting for Root File System

I played around by hitting <es> to go to the Grub menu. The first entry is "root (hd0,0)". I don't think that is something to change.

The second entry is "kernel /boot/vmlinuz-2.6.15-29-386 root=/dev/sda1 ro quiet splash". This looks like it. Changing sda1 to hda1.

Nope, still stalls out at Waiting for root file system.

If I switch to ctrl-alt-F1, I see this error: "[17179570.980000] PCI: Failed to allocate mem resource #6:20000@90000000 for 0000:01:00.0"

This time it says /dev/hda1 does not exist. (Instead of sda1).

Oh, it also says "/bin/sh: can't access tty; job control turned off".

Is any of this any progress?

dgermann 12-03-2007 10:34 PM

Hi all--

I tried a live CD for Gutsy 7.10. Started gparted and it showed partitions on my old drive at sdb1 (had a boot flag), sdb2, and sdb5.

Thinking I had this thing licked, I went in to grub and edited the kernel line that referred to sda1 to sdb1, and no go. Same waiting for root filesystem. Then tried sdb2 and sdb5, with same results.

Are there any clues here?

Thanks!

syg00 12-03-2007 11:22 PM

Quote:

Originally Posted by dgermann (Post 2977771)
The hardware tech says the bootup sequence (I currently have Ubuntu Dapper 6.06 on the HDD) does not recognize the chipset.

Pat that boy on the back.
This is your problem - Feisty has the support (and can thus see {both} the dirves o.k.), but Dapper doesn't.
Install Feisty and you should be able to get at your data o.k. - it'll probably also setup mount-points for both disks for you as well. Maybe - the alternate may not, but you'll have the opportunity to do it as part of the install if you go that way.

dgermann 12-03-2007 11:47 PM

Tried something else:

Used the 7.10 live cd and managed to mount /dev/sdb1 to a mount point /sdb1 as an ext3 file system.

Then I went in there and found all my files, so I know they exist and the machine can see them.

Then in sdb1 I sudo gedited /etc/fstab and /boot/grub/menu.lst to change sda to sdb.

Umounted, rebooted and...it still hung at Waiting, this time saying it could not find sdb1.

Found some posts various places on the Web suggesting changing some files in initramfs, and even running a command to update or re-install that, but I could find no man nor info files on it, so did not want to just jump in and do that.

Is this helping? Surely there is a way to mount from the old drive?

Thanks!

Going to get some sleep now....

dgermann 12-03-2007 11:57 PM

syg00--

OK! You're on to something.

Do you think using Gutsy 7.10 would work, too?

If so, here is what I see as the steps--

1. Install Gutsy or Feisty to the new drive.

2. Mount the old drive under the new system.

3. Somehow (this is where I am lost) upgrade the Dapper 6.06 to now be 7.10.

So how do I do step 3?

What I want to do is preserve my settings and preferences in things like OOo and Evolution (including mail contact lists).

Two other thoughts suggest themselves to me:

A. Just install Gutsy on the new drive, then figure out how to import my files and settings from the old drive.

B. Put the hard drive in another box that has the same configuration as the old computer and mobo, do an upgrade to Gutsy, and then physically reinstall the old drive on this new box.

Does any of this make any sense at this late hour? What would be my best choice, and why?

Thanks for pointing me in the right direction, syg00!

syg00 12-04-2007 12:08 AM

Sorry, I meant Gutsy/gusty/7.10 ... whatever.
See my first response.

dgermann 12-04-2007 10:29 AM

syg00--

Many thanks.

Rereading your first response you say "nominating" the /home partition. I am not sure what you mean by nominating.

Once I have done as you suggested, how do I get my old settings back, say in OOo where I have many custom key combinations and autotexts? Or the addressbooks and archived mail in Evo?

Thanks!

jiml8 12-04-2007 11:20 AM

Quote:

Originally Posted by dgermann (Post 2977870)
syg00--

As it stands, it will only partially boot: It starts to boot and hangs at "waiting for root file system."

After several minutes it says "PCI: Failed to allocate mem resource #6:" and a bunch of numbers. Then "ALERT! /dev/sda1 does not exist. Dropping to a shell!" Then it gives me a BusyBox shell.

While I think that upgrading from 6.06 is a good idea, I don't agree that linux "isn't recognizing your chipset". Instead it appears the boot manager isn't finding your root partition.

If you want to boot from your old drive, you have to tell grub where to look for the root filesystem.

From your other posts, it seems clear that there is some confusion about what drive is where. So, what is your exact drive topology? You have a new SATA drive? Is it sda? Is sdb your old drive? What kind of drive is your old drive? SATA? SCSI?

I suggest you boot with a live CD then run fdisk -l to get a listing of what is connected to your system. Once that is clear, sorting your boot troubles out won't be a big problem.

dgermann 12-04-2007 04:01 PM

jiml8--

Many thanks.

Here is what I get from fdisk -l: nothing, just another command line prompt.

However, gparted reports these:

/dev/sda 74.53 GiB unallocated
/dev/sdb1 184.89 GiB ext3 / flag is boot
/dev/sdb2 extended 1.42 GiB
/dev/sdb5 linux-swap 1.42 GiB

So sda appears to be the new 80 gig, and sdb the old 200 gig.

Both are SATA Western Digital.

I have tried to boot using sdb1, 2, and 5 and none get me anywhere. It simply tells me that it cannot find sdb1 or 2 or 5.

Oh! Just ran sudo fdisk -l and got this additional info: sda does not contain a valid partition table. Also sdb1 has an Id 83, sdb2 has 5, and sdb5 has 82, if those mean anything. It also shows that sdb1 starts at cylinder 1; 2 starts at 24137, as does 5 (gparted had shown 5 indented under 2).

Thanks for jumping in here with your note of hope!

syg00 12-04-2007 04:32 PM

The boot-loader has done it's job and loaded the kernel - it is the kernel that mounts the root.
To test booting the old drive, merely pull the cable out of the new drive - interface or power, doesn't matter. That way the old drive will be /dev/sda again.

As for my comment, when (if) you use the alternate CD you specify the partition/mountpoint you want assigned. As I suggested, you need to do this if you want "/home" as a separate partition.
If you do this (and use the same user/password), all your old configuration data will be available to you on the new system.

dgermann 12-04-2007 10:41 PM

As I am writing this, I am on the second download that syg00 suggested. I will try his install after I have had some sleep, unless someone stops me!

Tonight I tried all these things, with these results:

1. with livecd, put fstab and menu.lst back to sda1 from sdb1; next pull data cable on the new drive; reboot: Waiting for root file system. This was a test to see if it would boot without the new drive running. It failed this test.

2. Question: What is that "PCI: Failed to allocate mem resource #6" stuff all about?

3. Rebooted with live cd: sudo gparted shows now just /dev/sda1 with the same info as before for sdb. So this tells me I pulled the cable on the correct one.

4. mkdir /606; mount -t ext3 /dev/sda1 /606; cd /606; sudo chroot /606 /bin/bash; apt-get update; apt-get install udev: already have the latest udev

sudo nano -w /etc/hosts and changed 127.0.0.1 from doug2 to ubuntu; sudo mount -o remount,rw /; sudo /sbin/evms_activate; nano and changed back to doug2; reboot: Waiting for root file system;

tried the two mount and evms_activate commands from the command line after "/dev/sda1 does not exist". mount gave “Cannot read /etc/fstab: No such file or directory”; evms gave: “Engine: Unable to open the control node for Device-Mapper. The Engine will run without Device-Mapper support.” Rebooted: Waiting for root file system.

These tell me that the evms_activate stuff I found on evms.sourceforge did not help.

5. reboot with live cd: mounted the sda1 partition and did du -h: 23G. So there is probably room on the new 80 gig drive for this.

dgermann 12-04-2007 11:04 PM

syg00--

Quote:

Originally Posted by syg00 (Post 2977788)
Grab a liveCD and copy /home out to a new partition - either disk, doesn't matter, but on the new one makes sense.
Grab the "alternate" CD for gutsy, and install onto the new disk, nominating the /home partition (not to be formatted), and install fresh.

When you say copy /home out, I am guessing you mean to copy /home from the old drive to the new location, not the one from the live cd. Right?

So I would suspect I need to format the new disk to enable the copy. Does gparted handle this? Or can I copy to here without that step and then let the alternate CD handle partitioning, formatting, etc.?

jiml8 12-05-2007 10:40 AM

what does it say in /boot/grub/menu.lst ?

dgermann 12-05-2007 12:58 PM

jiml8--

Please note that I had edited this to change the first two references to sdb1 (as well as changing the references in /etc/fstab the same way). That did not work--still got Waiting for root filesystem message--and so I put them back.

Code:

# added by NeTraverse - DO NOT REMOVE THIS LINE, it's used for uninstall
# default 5
# end added by NeTraverse - DO NOT REMOVE THIS LINE, it's used for uninstall
# menu.lst - See: grub(8), info grub, update-grub(8)
#            grub-install(8), grub-floppy(8),
#            grub-md5-crypt, /usr/share/doc/grub
#            and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.         

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout                3

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line)  and entries protected by the
# command 'lock'
# e.g. password topsecret
#      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title                Windows 95/98/NT/2000
# root                (hd0,0)
# makeactive
# chainloader        +1
#
# title                Linux
# root                (hd0,1)
# kernel        /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
##      kopt_2_6_8=root=/dev/hdc1 ro
##      kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=/dev/sda1 ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
##      alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
##      lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
##      altoptions=(recovery mode) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
##      howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
##      memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## ## End Default Options ##

title                Ubuntu, kernel 2.6.15-29-386
root                (hd0,0)
kernel                /boot/vmlinuz-2.6.15-29-386 root=/dev/sda1 ro quiet splash
initrd                /boot/initrd.img-2.6.15-29-386
savedefault
boot

title                Ubuntu, kernel 2.6.15-29-386 (recovery mode)
root                (hd0,0)
kernel                /boot/vmlinuz-2.6.15-29-386 root=/dev/sda1 ro single
initrd                /boot/initrd.img-2.6.15-29-386
boot

title                Ubuntu, kernel 2.6.15-28-386
root                (hd0,0)
kernel                /boot/vmlinuz-2.6.15-28-386 root=/dev/sda1 ro quiet splash
initrd                /boot/initrd.img-2.6.15-28-386
savedefault
boot

title                Ubuntu, kernel 2.6.15-28-386 (recovery mode)
root                (hd0,0)
kernel                /boot/vmlinuz-2.6.15-28-386 root=/dev/sda1 ro single
initrd                /boot/initrd.img-2.6.15-28-386
boot

title                Ubuntu, kernel 2.6.15-27-386
root                (hd0,0)
kernel                /boot/vmlinuz-2.6.15-27-386 root=/dev/sda1 ro quiet splash
initrd                /boot/initrd.img-2.6.15-27-386
savedefault
boot

title                Ubuntu, kernel 2.6.15-27-386 (recovery mode)
root                (hd0,0)
kernel                /boot/vmlinuz-2.6.15-27-386 root=/dev/sda1 ro single
initrd                /boot/initrd.img-2.6.15-27-386
boot

title                Ubuntu, kernel 2.6.15-26-386
root                (hd0,0)
kernel                /boot/vmlinuz-2.6.15-26-386 root=/dev/sda1 ro quiet splash
initrd                /boot/initrd.img-2.6.15-26-386
savedefault
boot

title                Ubuntu, kernel 2.6.15-26-386 (recovery mode)
root                (hd0,0)
kernel                /boot/vmlinuz-2.6.15-26-386 root=/dev/sda1 ro single
initrd                /boot/initrd.img-2.6.15-26-386
boot

title                Ubuntu, kernel 2.6.15-25-386
root                (hd0,0)
kernel                /boot/vmlinuz-2.6.15-25-386 root=/dev/sda1 ro quiet splash
initrd                /boot/initrd.img-2.6.15-25-386
savedefault
boot

title                Ubuntu, kernel 2.6.15-25-386 (recovery mode)
root                (hd0,0)
kernel                /boot/vmlinuz-2.6.15-25-386 root=/dev/sda1 ro single
initrd                /boot/initrd.img-2.6.15-25-386
boot

title                Ubuntu, kernel 2.6.12-10-386
root                (hd0,0)
kernel                /boot/vmlinuz-2.6.12-10-386 root=/dev/sda1 ro quiet splash
initrd                /boot/initrd.img-2.6.12-10-386
savedefault
boot

title                Ubuntu, kernel 2.6.12-10-386 (recovery mode)
root                (hd0,0)
kernel                /boot/vmlinuz-2.6.12-10-386 root=/dev/sda1 ro single
initrd                /boot/initrd.img-2.6.12-10-386
boot

title                Ubuntu, kernel 2.6.12-9-386
root                (hd0,0)
kernel                /boot/vmlinuz-2.6.12-9-386 root=/dev/sda1 ro quiet splash
initrd                /boot/initrd.img-2.6.12-9-386
savedefault
boot

title                Ubuntu, kernel 2.6.12-9-386 (recovery mode)
root                (hd0,0)
kernel                /boot/vmlinuz-2.6.12-9-386 root=/dev/sda1 ro single
initrd                /boot/initrd.img-2.6.12-9-386
boot

title                Ubuntu, kernel 2.6.10-5-386
root                (hd0,0)
kernel                /boot/vmlinuz-2.6.10-5-386 root=/dev/sda1 ro quiet splash
initrd                /boot/initrd.img-2.6.10-5-386
savedefault
boot

title                Ubuntu, kernel 2.6.10-5-386 (recovery mode)
root                (hd0,0)
kernel                /boot/vmlinuz-2.6.10-5-386 root=/dev/sda1 ro single
initrd                /boot/initrd.img-2.6.10-5-386
boot

title                Ubuntu, memtest86+
root                (hd0,0)
kernel                /boot/memtest86+.bin
boot

### END DEBIAN AUTOMAGIC KERNELS LIST
 
# added by NeTraverse - DO NOT REMOVE THIS LINE, it's used for uninstall
title Win4Lin
root                (hd0,0)
kernel /boot/win4lin root=/dev/sda1 ro quiet splash pci=noacpi ide=reverse
# end added by NeTraverse - DO NOT REMOVE THIS LINE, it's used for uninstall

Thanks for taking a look, jiml8!

jiml8 12-05-2007 04:37 PM

Well, if sdb is your old drive and has the root file system on it, then you need code in grub that looks like this:
Code:

title                Ubuntu, kernel 2.6.15-29-386
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.15-29-386 root=/dev/sdb1 ro quiet splash
initrd                /boot/initrd.img-2.6.15-29-386
savedefault
boot

You are not booting from drive 0, you are booting from drive 1. So you have to change all references of hd0 to hd1, as well as changing all sda1 to sdb1.

Also take a look at /boot/grub/device.map to make sure you aren't getting some funky drive remapping (you probably aren't).

dgermann 12-05-2007 09:35 PM

jiml8--

Ahh! I wondered what that hd(0,0) might be for!

Despite all your great help, I am still stuck. Can you help me further?

Here is my menu.lst (I did a search and replace on sda1 and hd0, and I think it got all of them):

Code:

# added by NeTraverse - DO NOT REMOVE THIS LINE, it's used for uninstall
# default 5
# end added by NeTraverse - DO NOT REMOVE THIS LINE, it's used for uninstall
# menu.lst - See: grub(8), info grub, update-grub(8)
#            grub-install(8), grub-floppy(8),
#            grub-md5-crypt, /usr/share/doc/grub
#            and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.         

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout                3

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line)  and entries protected by the
# command 'lock'
# e.g. password topsecret
#      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title                Windows 95/98/NT/2000
# root                (hd1,0)
# makeactive
# chainloader        +1
#
# title                Linux
# root                (hd1,1)
# kernel        /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
##      kopt_2_6_8=root=/dev/hdc1 ro
##      kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=/dev/sdb1 ro

## default grub root device
## e.g. groot=(hd1,0)
# groot=(hd1,0)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
##      alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
##      lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
##      altoptions=(recovery mode) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
##      howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
##      memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## ## End Default Options ##

title                Ubuntu, kernel 2.6.15-29-386
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.15-29-386 root=/dev/sdb1 ro quiet splashinitrd               
/boot/initrd.img-2.6.15-29-386
savedefault
boot

title                Ubuntu, kernel 2.6.15-29-386 (recovery mode)
# root                (hd1,0)
# kernel                /boot/vmlinuz-2.6.15-29-386 root=/dev/sdb1 ro single
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.15-29-386 root=/dev/sdb1 ro single
initrd                /boot/initrd.img-2.6.15-29-386
boot

title                Ubuntu, kernel 2.6.15-28-386
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.15-28-386 root=/dev/sdb1 ro quiet splash
initrd                /boot/initrd.img-2.6.15-28-386
savedefault
boot

title                Ubuntu, kernel 2.6.15-28-386 (recovery mode)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.15-28-386 root=/dev/sdb1 ro single
initrd                /boot/initrd.img-2.6.15-28-386
boot

title                Ubuntu, kernel 2.6.15-27-386
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.15-27-386 root=/dev/sdb1 ro quiet splash
initrd                /boot/initrd.img-2.6.15-27-386
savedefault
boot

title                Ubuntu, kernel 2.6.15-27-386 (recovery mode)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.15-27-386 root=/dev/sdb1 ro single
initrd                /boot/initrd.img-2.6.15-27-386
boot

title                Ubuntu, kernel 2.6.15-26-386
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.15-26-386 root=/dev/sdb1 ro quiet splash
initrd                /boot/initrd.img-2.6.15-26-386
savedefault
boot

title                Ubuntu, kernel 2.6.15-26-386 (recovery mode)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.15-26-386 root=/dev/sdb1 ro single
initrd                /boot/initrd.img-2.6.15-26-386
boot

title                Ubuntu, kernel 2.6.15-25-386
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.15-25-386 root=/dev/sdb1 ro quiet splash
initrd                /boot/initrd.img-2.6.15-25-386
savedefault
boot

title                Ubuntu, kernel 2.6.15-25-386 (recovery mode)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.15-25-386 root=/dev/sdb1 ro single
initrd                /boot/initrd.img-2.6.15-25-386
boot

title                Ubuntu, kernel 2.6.12-10-386
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.12-10-386 root=/dev/sdb1 ro quiet splash
initrd                /boot/initrd.img-2.6.12-10-386
savedefault
boot

title                Ubuntu, kernel 2.6.12-10-386 (recovery mode)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.12-10-386 root=/dev/sdb1 ro single
initrd                /boot/initrd.img-2.6.12-10-386
boot

title                Ubuntu, kernel 2.6.12-9-386
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.12-9-386 root=/dev/sdb1 ro quiet splash
initrd                /boot/initrd.img-2.6.12-9-386
savedefault
boot

title                Ubuntu, kernel 2.6.12-9-386 (recovery mode)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.12-9-386 root=/dev/sdb1 ro single
initrd                /boot/initrd.img-2.6.12-9-386
boot

title                Ubuntu, kernel 2.6.10-5-386
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.10-5-386 root=/dev/sdb1 ro quiet splash
initrd                /boot/initrd.img-2.6.10-5-386
savedefault
boot

title                Ubuntu, kernel 2.6.10-5-386 (recovery mode)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.10-5-386 root=/dev/sdb1 ro single
initrd                /boot/initrd.img-2.6.10-5-386
boot

title                Ubuntu, memtest86+
root                (hd1,0)
kernel                /boot/memtest86+.bin
boot

### END DEBIAN AUTOMAGIC KERNELS LIST
 
# added by NeTraverse - DO NOT REMOVE THIS LINE, it's used for uninstall
title Win4Lin
root                (hd1,0)
kernel /boot/win4lin root=/dev/sdb1 ro quiet splash pci=noacpi ide=reverse
# end added by NeTraverse - DO NOT REMOVE THIS LINE, it's used for uninstall

Here is the device.map file. This one I am not sure of how it should be (I added the second line; I tried it once with the first line commented out, but it did not work that way either):

Code:

(hd0)        /dev/sda
(hd1)        /dev/sdb

Here is my /etc/fstab file, again changed for sda/b. I am not sure of what the CD should be called, but I suspect that makes no difference for mounting the hdd:
Code:

# /etc/fstab: static file system information.
#
# <file system> <mount point>  <type>  <options>      <dump>  <pass>
proc            /proc          proc    defaults        0      0
# /dev/sdb1      /              ext3    defaults,errors=remount-ro 0      1
# /dev/sda5      none            swap    sw              0      0
# /dev/hda        /media/cdrom0  udf,iso9660 ro,user,noauto  0      0
/dev/sdb1      /              ext3    defaults,errors=remount-ro 0      1
/dev/sdb5      none            swap    sw              0      0
/dev/hda        /media/cdrom0  udf,iso9660 ro,user,noauto  0      0
/dev/fd0        /media/floppy0  auto    rw,user,noauto  0      0
##############
#samba1:/vol22  /sam/vol22      nfs    rw,hard,intr        0      0
earth:/exports        /sam/earth                nfs        rw,hard,rsize=8192,wsize=8192,timeo=14,intr        0        0
##############
//samba1/vol22        /sam/vol22  cifs    rw,user,credentials=/root/.smbcredentials,uid=doug,gid=data      0      0
//samba1/vol12        /sam/vol12  cifs    rw,user,credentials=/root/.smbcredentials,uid=doug,gid=apps      0      0
//samba1/doug2        /sam/doug2  cifs    rw,user,credentials=/root/.smbcredentials,uid=doug,gid=doug      0      0
##############
#//earth/vol2        /sam/vol22  cifs    rw,user,credentials=/root/.smbcredentials,uid=doug,gid=data      0      0
#//earth/vol1        /sam/vol12  cifs    rw,user,credentials=/root/.smbcredentials,uid=doug,gid=apps      0      0
#//earth/doug2        /sam/doug2  cifs    rw,user,credentials=/root/.smbcredentials,uid=doug,gid=doug      0      0

One curious thing: when I choose this kernel in grub, and hit e, it still shows the kernel root line as sda1. It makes no difference if I change it to sdb1 or not: it still hangs at "Waiting for root file system."

It may be important for you to know that I installed 7.10 on the new drive, sda1. Grub gives that as the default choice and lists this kernel as the first of "other file systems."

Are we getting any closer, jiml8? Thanks for all your help. I feel like we are getting closer....

jiml8 12-06-2007 12:22 AM

Quote:

It may be important for you to know that I installed 7.10 on the new drive, sda1. Grub gives that as the default choice and lists this kernel as the first of "other file systems."
I thought that sda was unformatted, per your message 17 above.

Yes, that changes things considerably. What does your menu.lst on that drive say? That is the one being used to boot, apparently.

Also, now tell me what your goal is. You want to boot from the old drive or the new one?

David1357 12-06-2007 01:38 PM

Quote:

Originally Posted by dgermann (Post 2981591)
One curious thing: when I choose this kernel in grub, and hit e, it still shows the kernel root line as sda1. It makes no difference if I change it to sdb1 or not: it still hangs at "Waiting for root file system."

You need to run fdisk on sda and toggle the bootable flag (the "a" command") to off. BIOS will then skip that drive and boot from sdb.

dgermann 12-06-2007 08:22 PM

jiml8--

Here is the menu.lst for sda1:

Code:

# menu.lst - See: grub(8), info grub, update-grub(8)
#            grub-install(8), grub-floppy(8),
#            grub-md5-crypt, /usr/share/doc/grub
#            and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default                0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout                10

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
#hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line)  and entries protected by the
# command 'lock'
# e.g. password topsecret
#      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title                Windows 95/98/NT/2000
# root                (hd0,0)
# makeactive
# chainloader        +1
#
# title                Linux
# root                (hd0,1)
# kernel        /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
##      kopt_2_6_8=root=/dev/hdc1 ro
##      kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=54c0ade6-e8dc-4ed3-866f-fd6c7d831868 ro

## Setup crashdump menu entries
## e.g. crashdump=1
# crashdump=0

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
##      alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
##      lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
##      lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
##      altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
##      howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
##      memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title                Ubuntu 7.10, kernel 2.6.22-14-generic
root                (hd0,0)
kernel                /boot/vmlinuz-2.6.22-14-generic root=UUID=54c0ade6-e8dc-4ed3-866f-fd6c7d831868 ro quiet splash
initrd                /boot/initrd.img-2.6.22-14-generic
quiet

title                Ubuntu 7.10, kernel 2.6.22-14-generic (recovery mode)
root                (hd0,0)
kernel                /boot/vmlinuz-2.6.22-14-generic root=UUID=54c0ade6-e8dc-4ed3-866f-fd6c7d831868 ro single
initrd                /boot/initrd.img-2.6.22-14-generic

title                Ubuntu 7.10, memtest86+
root                (hd0,0)
kernel                /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

# This is a divider, added to separate the menu items below from the Debian
# ones.
title                Other operating systems:
root


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title                Ubuntu, kernel 2.6.15-29-386 (on /dev/sdb1)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.15-29-386 root=/dev/sda1 ro quiet splash
initrd                /boot/initrd.img-2.6.15-29-386
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title                Ubuntu, kernel 2.6.15-29-386 (recovery mode) (on /dev/sdb1)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.15-29-386 root=/dev/sda1 ro single
initrd                /boot/initrd.img-2.6.15-29-386
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title                Ubuntu, kernel 2.6.15-28-386 (on /dev/sdb1)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.15-28-386 root=/dev/sda1 ro quiet splash
initrd                /boot/initrd.img-2.6.15-28-386
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title                Ubuntu, kernel 2.6.15-28-386 (recovery mode) (on /dev/sdb1)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.15-28-386 root=/dev/sda1 ro single
initrd                /boot/initrd.img-2.6.15-28-386
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title                Ubuntu, kernel 2.6.15-27-386 (on /dev/sdb1)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.15-27-386 root=/dev/sda1 ro quiet splash
initrd                /boot/initrd.img-2.6.15-27-386
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title                Ubuntu, kernel 2.6.15-27-386 (recovery mode) (on /dev/sdb1)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.15-27-386 root=/dev/sda1 ro single
initrd                /boot/initrd.img-2.6.15-27-386
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title                Ubuntu, kernel 2.6.15-26-386 (on /dev/sdb1)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.15-26-386 root=/dev/sda1 ro quiet splash
initrd                /boot/initrd.img-2.6.15-26-386
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title                Ubuntu, kernel 2.6.15-26-386 (recovery mode) (on /dev/sdb1)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.15-26-386 root=/dev/sda1 ro single
initrd                /boot/initrd.img-2.6.15-26-386
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title                Ubuntu, kernel 2.6.15-25-386 (on /dev/sdb1)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.15-25-386 root=/dev/sda1 ro quiet splash
initrd                /boot/initrd.img-2.6.15-25-386
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title                Ubuntu, kernel 2.6.15-25-386 (recovery mode) (on /dev/sdb1)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.15-25-386 root=/dev/sda1 ro single
initrd                /boot/initrd.img-2.6.15-25-386
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title                Ubuntu, kernel 2.6.12-10-386 (on /dev/sdb1)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.12-10-386 root=/dev/sda1 ro quiet splash
initrd                /boot/initrd.img-2.6.12-10-386
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title                Ubuntu, kernel 2.6.12-10-386 (recovery mode) (on /dev/sdb1)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.12-10-386 root=/dev/sda1 ro single
initrd                /boot/initrd.img-2.6.12-10-386
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title                Ubuntu, kernel 2.6.12-9-386 (on /dev/sdb1)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.12-9-386 root=/dev/sda1 ro quiet splash
initrd                /boot/initrd.img-2.6.12-9-386
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title                Ubuntu, kernel 2.6.12-9-386 (recovery mode) (on /dev/sdb1)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.12-9-386 root=/dev/sda1 ro single
initrd                /boot/initrd.img-2.6.12-9-386
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title                Ubuntu, kernel 2.6.10-5-386 (on /dev/sdb1)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.10-5-386 root=/dev/sda1 ro quiet splash
initrd                /boot/initrd.img-2.6.10-5-386
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title                Ubuntu, kernel 2.6.10-5-386 (recovery mode) (on /dev/sdb1)
root                (hd1,0)
kernel                /boot/vmlinuz-2.6.10-5-386 root=/dev/sda1 ro single
initrd                /boot/initrd.img-2.6.10-5-386
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title                Ubuntu, memtest86+ (on /dev/sdb1)
root                (hd1,0)
kernel                /boot/memtest86+.bin 
savedefault
boot


# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/sdb1.
title                Win4Lin (on /dev/sdb1)
root                (hd1,0)
kernel                /boot/win4lin root=/dev/sda1 ro quiet splash pci=noacpi ide=reverse
savedefault
boot

So I can see where it is getting the sda1 in there, despite the fact that I changed it on sdb1.

Yes, sda1 was unformatted in message 17; but since this is a production machine, I needed to get it up and running, so I proceeded in line with message 19 and syg00's original post to install 7.10 Gutsy to that drive. My goal is still to get the original drive working again, because I'd feel better with more room in the larger drive.

David1357--

Am trying that now. Will get back to you with the results.

<pause>

Nope, did not go. It did not seem to even get as far. It stopped with an Error 15.

dgermann 12-06-2007 09:00 PM

Hi--

One more thing. Someone suggested that changing the AHCI/IDE toggle in BIOS might have been a culprit?

Any wisdom on that question?

Thanks!

David1357 12-06-2007 09:03 PM

Quote:

Originally Posted by dgermann (Post 2982684)
David1357

Am trying that now. Will get back to you with the results.

<pause>

Nope, did not go. It did not seem to even get as far. It stopped with an Error 15.

My bad. I did not look at this before:

Code:

title                Ubuntu 7.10, kernel 2.6.22-14-generic
root                (hd0,0)
kernel                /boot/vmlinuz-2.6.22-14-generic root=UUID=54c0ade6-e8dc-4ed3-866f-fd6c7d831868 ro quiet splash
initrd                /boot/initrd.img-2.6.22-14-generic
quiet

title                Ubuntu 7.10, kernel 2.6.22-14-generic (recovery mode)
root                (hd0,0)
kernel                /boot/vmlinuz-2.6.22-14-generic root=UUID=54c0ade6-e8dc-4ed3-866f-fd6c7d831868 ro single
initrd                /boot/initrd.img-2.6.22-14-generic

title                Ubuntu 7.10, memtest86+
root                (hd0,0)
kernel                /boot/memtest86+.bin
quiet

It is trying to boot using these entries, which still point at (hd0,0) and use a UUID to identify the boot partition. You need to comment out these lines.

dgermann 12-06-2007 09:20 PM

David1357--

Those entries you quote are on the new drive, sda, and it had the boot flag removed. When Grub came up, it showed only the Grub entries from sdb.

A day or so ago, I even unplugged the data cable from sda, and still it was the same "Waiting for...."

So will commenting these out on sda help with this Error 15?

(It is getting to be a long thread, so it is hard to keep up with all the things that are in there right now! I could say I am getting confused, but I was to start! So no problem if someone not living with the problem misses what is the current state of things, David!)

Thanks, David!

David1357 12-07-2007 07:25 AM

Quote:

Originally Posted by dgermann (Post 2982728)
Those entries you quote are on the new drive, sda, and it had the boot flag removed. When Grub came up, it showed only the Grub entries from sdb.

I am confused about which drive you are currently trying to boot from.

Whichever drive you are trying to boot, the partition with "/boot" on it must have the "bootable" flag turned on.

Once you have that sorted out, you should mount the file system you want to boot from (e.g. using System Rescue CD or equivalent) and run

# grub-install --root-directory=/mnt/system --recheck /dev/sdX
where "/mnt/system" is replaced by where you mount the file system, and "X" is replaced by the letter of the drive you are trying to boot from.

This will re-install GRUB, and hopefully fix the "Error 15" problem.

dgermann 12-12-2007 10:01 PM

David1357--

Thank you for your very prompt and helpful reply. Wish I had been as prompt in getting back to you. I have been busy working till too late at night to feel safe in tackling this again. I apologize to you for taking so long.

Now re-installing grub makes a lot of sense to me. Sounds like it ought to work, but after this saga, who knows?

I am more confused than you, for sure! But in any case, I want to boot from sdb1 (the old drive); but as of the moment I am only able to boot from sda1 (the new drive).

Will try your idea (hopefully soon) and report back.

Thank you, thank you very much, David1357!

dgermann 01-12-2008 06:42 PM

Hi--

Thank you all who responded to my plea for help. I really appreciate the quick and authoritative help I got here, and always get here!

Since all is working fine at the moment, I have decided to leave well enough alone. My present plan is that sometime in May I will probably install the new release of Ubuntu and at that time install it to the sdb drive, perhaps even switching the boot order. That should give me what I want and may be a lot less painful than continuing on this path

This thread will be my resource for doing that work.

Thank you all, very, very much. You are life savers and grand people!


All times are GMT -5. The time now is 03:19 AM.