(SOLVED) bootloader or device issues after dual boot install xp and pclos

[Old-Polack]

I'm sorry. My bad. Remember earlier I installed mepis, then reistalled pclos? I must have chosen Reiser instead of ext3. Here is what the fstab now looks like: ( I didn't change anything - this is how it is currently installed ):

# Entry for /dev/hda2 :
UUID=84573e86-4a30-40a1-afb3-c4c0772d8950 / reiserfs defaults 1 1
none /proc proc defaults 0 0
# Entry for /dev/hda3 :
UUID=86de8aae-7a36-4c62-9a37-f0bfac2ed848 swap swap defaults 0 0
none /dev/pts devpts mode=0620 0 0

Do I need to update you again with more info??
Sorry,
 Jaybee

The first question is whether it boots now? The UUID numbers are totally different from what the original posting of the fstab entries were, so it's rather hard to determine what exactly is going on, on your end. Where did you get the first fstab output from?

Perhaps a slightly different approach is necessary. First try to boot the OS. If that doesn't work, we'll run an fsck on the partition, from the liveCD, to find out for sure what format is used. Then we can try regular /dev/<whatever> or partition labels to get the proper partition to boot.

[pags]

I'm sorry. My bad. Remember earlier I installed mepis, then reistalled pclos? I must have chosen Reiser instead of ext3. Here is what the fstab now looks like: ( I didn't change anything - this is how it is currently installed ):

# Entry for /dev/hda2 :
UUID=84573e86-4a30-40a1-afb3-c4c0772d8950 / reiserfs defaults 1 1
none /proc proc defaults 0 0
# Entry for /dev/hda3 :
UUID=86de8aae-7a36-4c62-9a37-f0bfac2ed848 swap swap defaults 0 0
none /dev/pts devpts mode=0620 0 0

Do I need to update you again with more info??
Sorry,
 Jaybee

The first question is whether it boots now? The UUID numbers are totally different from what the original posting of the fstab entries were, so it's rather hard to determine what exactly is going on, on your end. Where did you get the first fstab output from?

Perhaps a slightly different approach is necessary. First try to boot the OS. If that doesn't work, we'll run an fsck on the partition, from the liveCD, to find out for sure what format is used. Then we can try regular /dev/<whatever> or partition labels to get the proper partition to boot.

You could also use blkid to check the files system...

Code: [Select]

[jpaglia@core2pclinuxos ~]$ blkid /dev/sda1
/dev/sda1: UUID="fe0c2dc2-6e26-4d91-a0e4-03a4148f18c5" TYPE="ext3"
[jpaglia@core2pclinuxos ~]$
...just a thought.

[Old-Polack]

I'm sorry. My bad. Remember earlier I installed mepis, then reistalled pclos? I must have chosen Reiser instead of ext3. Here is what the fstab now looks like: ( I didn't change anything - this is how it is currently installed ):

# Entry for /dev/hda2 :
UUID=84573e86-4a30-40a1-afb3-c4c0772d8950 / reiserfs defaults 1 1
none /proc proc defaults 0 0
# Entry for /dev/hda3 :
UUID=86de8aae-7a36-4c62-9a37-f0bfac2ed848 swap swap defaults 0 0
none /dev/pts devpts mode=0620 0 0

Do I need to update you again with more info??
Sorry,
 Jaybee

The first question is whether it boots now? The UUID numbers are totally different from what the original posting of the fstab entries were, so it's rather hard to determine what exactly is going on, on your end. Where did you get the first fstab output from?

Perhaps a slightly different approach is necessary. First try to boot the OS. If that doesn't work, we'll run an fsck on the partition, from the liveCD, to find out for sure what format is used. Then we can try regular /dev/<whatever> or partition labels to get the proper partition to boot.

You could also use blkid to check the files system...

Code: [Select]

[jpaglia@core2pclinuxos ~]$ blkid /dev/sda1
/dev/sda1: UUID="fe0c2dc2-6e26-4d91-a0e4-03a4148f18c5" TYPE="ext3"
[jpaglia@core2pclinuxos ~]$
...just a thought.

And a good one, at that. 

[jaybee]

 Again, sorry for throwing a wrench in the works. I thought I had a good idea trying Mepis but I guess not. The original fstab entry came from typing the command you gave me at that time. Anyway, I must admit, the last two posts are a bit over my head. I tried to figure out what to type in console and here is what I got:


[root@localhost root]# /dev/sda1
bash: /dev/sda1: Permission denied

[root@localhost root]# fsck
fsck 1.41.6 (30-May-2009)

[root@localhost root]# blkid /dev/hda1
/dev/hda1: UUID="546C67DB6C67B700" LABEL="XP PRO" TYPE="ntfs"

[root@localhost root]# blkid /dev/hda2
/dev/hda2: UUID="84573e86-4a30-40a1-afb3-c4c0772d8950" TYPE="reiserfs"

[root@localhost root]# blkid /dev/hda3
/dev/hda3: UUID="86de8aae-7a36-4c62-9a37-f0bfac2ed848" TYPE="swap"

Does this help?

[Old-Polack]

Again, sorry for throwing a wrench in the works. I thought I had a good idea trying Mepis but I guess not. The original fstab entry came from typing the command you gave me at that time. Anyway, I must admit, the last two posts are a bit over my head. I tried to figure out what to type in console and here is what I got:


[root@localhost root]# /dev/sda1
bash: /dev/sda1: Permission denied

[root@localhost root]# fsck
fsck 1.41.6 (30-May-2009)

[root@localhost root]# blkid /dev/hda1
/dev/hda1: UUID="546C67DB6C67B700" LABEL="XP PRO" TYPE="ntfs"

[root@localhost root]# blkid /dev/hda2
/dev/hda2: UUID="84573e86-4a30-40a1-afb3-c4c0772d8950" TYPE="reiserfs"

[root@localhost root]# blkid /dev/hda3
/dev/hda3: UUID="86de8aae-7a36-4c62-9a37-f0bfac2ed848" TYPE="swap"

Does this help?

The lines above, in blue, confirms both the correct UUID number and the reiserfs filesystem for the / partition, and the correct UUID number for the swap partition, so the last fstab reported seems correct. Now, if those UUID numbers are the ones in your /boot/grub/menu.lst stanzas, the OS should boot.

[jaybee]

They seem to be in there, but I don't know if they are in the right place.
here is the file:

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,1)/boot/gfxmenu
default 0

title linux
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=84573e86-4a30-40a1-afb3-c4c0772d8950  acpi=on resume=UUID=86de8aae-7a36-4c62-9a37-f0bfac2ed848 splash=silent vga=788
initrd (hd0,1)/boot/initrd.img

title linux-nonfb
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=84573e86-4a30-40a1-afb3-c4c0772d8950  acpi=on resume=UUID=86de8aae-7a36-4c62-9a37-f0bfac2ed848
initrd (hd0,1)/boot/initrd.img

title failsafe
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=84573e86-4a30-40a1-afb3-c4c0772d8950  failsafe acpi=on
initrd (hd0,1)/boot/initrd.img

title windows
root (hd0,0)
makeactive
chainloader +1

[Old-Polack]

They seem to be in there, but I don't know if they are in the right place.
here is the file:

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,1)/boot/gfxmenu
default 0

title linux
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=84573e86-4a30-40a1-afb3-c4c0772d8950  acpi=on resume=UUID=86de8aae-7a36-4c62-9a37-f0bfac2ed848 splash=silent vga=788
initrd (hd0,1)/boot/initrd.img

title linux-nonfb
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=84573e86-4a30-40a1-afb3-c4c0772d8950  acpi=on resume=UUID=86de8aae-7a36-4c62-9a37-f0bfac2ed848
initrd (hd0,1)/boot/initrd.img

title failsafe
kernel (hd0,1)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=84573e86-4a30-40a1-afb3-c4c0772d8950  failsafe acpi=on
initrd (hd0,1)/boot/initrd.img

title windows
root (hd0,0)
makeactive
chainloader +1

One resumes from the swap partition, if one has suspended, rather than shut down. The resume UUID matches the swap UUID, so is correct. The root UUID is also the same as that of hda2, so it too is correct. We already know that reiserfs is the module being loaded, so the filesystem is correct, and the pata_sis module is also loading so the hard drive controller should be properly seen, as well as the hard drive connected to it. All the pieces seem to be in place now, so boot up.

[jaybee]

  I got this same message again:

loading uhci-hcd module
USB Universal Host Controller Interface driver u3.0
usb 1-6.3: new low speed USB device using ehci_hcd and address 3
loading reiserfs module
usb 1-6.3: configuration #1 chosen from 1 choice
Loading scsi_mod module
SCSI subsystem initialized
Loading sd_mod module
Drivere 'sd' needs updating - please use bus_type methods
Loading libata module
Loading pata_sis module
Loading pata_acpi module
Loading ata_generic module
usb 1-6.4: new high speed USB device using ihci_hcd and address 4
waiting for driver initialization
usb 1-6.4: configuration #1 chosen from 1 choice
Could not resolve resume device (UUID=86de8aae-7a36-4c62-9a37-f0bfac2ed848)
Creating root device
Mounting root filesystem
mount: could not find filesystem '/dev/root'
Setting up other filesystems
setuproot: moving /dev failed: No such file or directory
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init
switchroot: /dev does not exist in new root
Booting has failed

Same UUID - Same everything. Booooooo. I was hoping you uttered the magic words or something!
So, is that it? Do I need to dban and start over - or are there more tricks up the sleeve?
 Jaybee

[Old-Polack]

jaybee:

Got to say this is weird. In the initrd image, there is a mini file system with directories and such, containing temporary init files which is supposed to allow the system to run until the / partition gets mounted, including the code that controls that mount, and the rest of the system loads from what's on the / partition. Your error is saying there is no /dev/root and later;

switchroot: /dev does not exist in new root

I'm wondering if there's a problem with the actual liveCD, in that either the installation, or the initrd image, seems a bit short on copied files, at least according to the error messages. It could be file corruption during the installation, or a problem with the disk itself, possibly from burning at too high a speed.

Put the liveCD disk in the tray, reboot, and when the menu appears, use the down arrow key on the keyboard to move down, select the Media Check, and press the Enter key. We need to know if there's any corruption to the disk, first, before trying any reinstallation attempts.

Post your results.

[ThirdOfSix]

jaybee,

Do you have an old hard drive around that is too small to do much with these days?

If so, I think it is time to find out if a clean install of PCLOS on a different drive using the livecd defaults will boot on your machine with no Windows partition etc.

You may very well have a hardware problem of some sort other than your drive. So, It would be nice to know if PCLOS will install and run on your basic machine.

Yes, I know, other operating systems work. It is quite irrelevant.

Back in the days when large memory chips were first coming out...unheard of sizes like 1024 bits... memory failures were common and could introduce the oddest array of errors.

Just changing the order that you loaded two programs would make one that ran perfectly on the machine before quit working.

Have you run a memory check?

Besides that,just because you install to other machines from your CD, that does not mean that the CD is not partially corrupted.

The reason that the CDs are so large is because they contain bits of code that work on each configuration that comes along. If you have a corrupt section of code on your disk that is not needed by your other machines, it means nothing that the others run ok.

The first thing that I do when I have trouble installing on a problem machine is to download and burn a totally different CD just so that I know that errors in it are unlikely.

Also, try burning the new disk on  different drives. Your current problem child may not always read your disk properly.

I have a 60 GB IBM/Hitachi drive here on one of my machines that was a total basket case on the original machine it came from.

Windows would run OK but when data was added to a data partition you would start getting really odd errors.

Some of the partitioning/repair programs would refuse to work with it and others would work fine.

Finally, after my brother bought a new drive for the machine and told me to throw that one in the trash, I found the disk utility that IBM put out and did a total wipe of the drive and started over.

After that, it worked fine. I have had it on one of my test machines for over a year and it is still going.

The point is that once you have used multiple different tools on a drive, you can have it end up in a state that none of them can truly repair.

A low level wipe using the manufactures tools can be the only way to make it reliable again.

I forget the name of the IBM/Hitachi disk utility but I probably can find it and therefore its name if you get to the point where you contemplate doing that.

There is no point in wiping out your current Windows install until you have found out that the problem is truly in that drive.

I know, not everyone has spare drives laying around for test purposes. Some of us find that hard to believe. But, to each his own.

A cheap source of test drives is to find an old TIVO digital video recorder that someone is throwing away. They have drives in them from about 30 GB up to 250 GB. I usually pay $5 for them and then salvage the drive and the high quality hardware.

They are usually extremely high running hour drives but they usually still work and are fine for test machines that don't deal with critical data.

One last thing, if you have any USB external drives etc connected to that machine. Don't do this test with them connected.

[Old-Polack]

ThirdOfSix:

We're thinking along the same lines here... that this is not your everyday common type problem. If it gets to the point of disk wiping, the Hitachi disk utility from the included CD, or as a d/l from their site, did not work (kept crashing) on my drive. DBAN, from the Ultimate Boot CD, however, did a marvelous job of wiping it, and mine is now going on three years since needing to do that procedure, and is my current /dev/hdb on this computer. Just a heads up on that.

[jaybee]

 I do enjoy listening to logical minds.
Okay, I think I will download another image. First of all, there is no media check option - odd, I remember using that before. Why would this copy not have it? The only change I made to the boot options was to remove the external drive boot option.
* Then, I do have a few IDE drives. I have not used them in a while so I don't remember their condition. I'll check.
* The CD working on one pc and not another makes total sense to me. Thanks
* I do have the UBCD with dban. It also has the Hitachi drive utility (which I ran twice). It gave absolutely no results so I took that as an ok. I also have the original Hitachi cd but I don't know what's on it. I'll check.
* And the external usb drive - I keep using it and forgetting to remove it at crucial times. Thanks - A few years ago I actually did a complete windows image for a new hire at work and forgot to remove my personal external. Sure enough, all my music, docs and apps were gone and I had a friggin' 160gb bootable usb drive! It's unplugged now.
Alright, I'll start my download now and report back later. Thank You my friends!
 Jaybee

[jaybee]

 Hold the bus! What the hell??
Okay, I was looking for that "check media" option on the menu. It was not there so I left the system sitting at the boot screen and returned to my laptop to type my last message. I went back to the desktop in question and hit F2 for more options, It just showed the UUID number on the bottom of the screen. I hit F1 which took me to the language option screen. Big deal. I got out and hit F1 for help and read what it had to say about DMA and ACPI and others. I hit escape to get back to the boot screen. Just as I was hitting ctl/alt/del, I saw the progress bar inch forward like I have not seen yet. Before the screen went blank, I saw items successfully loading!!!
So, I restarted and just hit the default boot choice and got the same error messages as before.

Just for kicks and giggles, I restarted and went through all those info Help and Option screens again, escaped out, AND THE DAMNED THING BOOTED UP! I entered a root password and created a user. It's sitting at the desktop right now and I don't want to turn it off again until I hear from you. Is there something I should check while it is booted up? I'm downloading another image anyway, but I'm guessing you'll have me check some stuff before shutting down. Could it simply have to do with delaying the boot for enough time for something to start? Or did I just get lucky?
   Jaybee

[Old-Polack]

jaybee:

That's about as weird as I've heard lately.

I do have one thing I'd like you to do, before anything else. Open a terminal in the running system, su to root, and enter;

[root@localhost ~]# kwrite /boot/grub/menu.lst           <Enter>

Kwrite should open the menu.lst file. I want you to change each instance of splash=silent to splash=verbose, then save the file.

Until we have this completely straightened out, each time you boot, you will see all of the boot messages, rather than the splash screen with progress bar, so you will know exactly what is happening when it is happening. If it hangs for a while, you'll know at what stage it is hanging, and if it restarts and continues the boot process, you'll be able to tell us how long the delay was and what the next stage was.

If you need to redo the F1 options, write down which ones you do choose, so we can edit the menu.lst stanzas to include them.

We're having fun now!

[jaybee]

 I tried a little experiment. I did as you said and forced it to boot in verbose mode. When I started it up, the words just flew by, way too fast to read, and it stopped - at the exact same point with the exact same error messages.
So, I rebooted again. At the boot menu, I just hit the arrow key and walked away for about 10 minutes or so. I came back and selected the default boot choice and it just booted right up! So what the heck? I'll do it a few more times but is there something that could be loading too slowly (perhaps because of some failing hardware) and all is well once I wait for it to catch up?