Full install on second HD makes XP unhappy
Full install on second HD makes XP unhappy
First, of all this is my first post here so hello all. I've only just started using Puppy about a week and a half ago, but so far I'm enjoying myself. The journey with Linux reminds me of my days and nights editing config files with MS-DOS 5.0.
Ok, on to my problem, but first the setup. I have a computer running XP pro with service pack 2 with 512 MB of RAM. XP lives on the first hard drive (a 100 gig affair, NTFS), and my second disk drive is 150 gigs partioned in three nearly equal parts (excepting the swap). Hdb1 is an ext2 partition (48 gigs), hdb2 is a 550 meg linux swap partition, hdb3 is another 48 gig ext2 partition, and hdb4 is a 53 gig fat32 partition.
I've been trying to full install to hdb1 and I kept having issues with grub not seeing the partition correctly. Grub kept telling me that the only place it was seeing /dev/vmlinuz was on (hd0,0). Now, I never ran an install of any kind on my first HD because I didn't want it being messed up somehow. Grub kept giving me an error saying "File system type unknown, partition type 0x7" when it hit the "root (hd1,0)" line.
Many scratchings of my head later I said what the heck and edited my grub file to something like
root (hd0,0)
kernel /boot/vmlinuz root=/dev/hdb1 ro vga=normal
boot
Well, lo and behold that worked. Which says to me that grub is using (hd0,0) for hdb1 when it should be using (hd1,0) for hdb1 (as far as I understand what I've read). The problem is (hd0,0) is supposed to be my Windows NTFS partition, and I don't know what to call it in grub to get it to load.
The other issue is now I can't mount hda right, which is making me a feared for my Windows partition. When I click to mount it in MUT a Rox window pops up for /mnt/hda1 but the window is totally empty.
So, what should I do now oh gurus of all things canine and Linux?
Oh, also, I thought grub loaded off of a specific HDD, my BIOS is set to load HHD 1 first (Windows) and HDD 2 second (Linux, the other white meat), but grub keeps popping up first.
Ok, on to my problem, but first the setup. I have a computer running XP pro with service pack 2 with 512 MB of RAM. XP lives on the first hard drive (a 100 gig affair, NTFS), and my second disk drive is 150 gigs partioned in three nearly equal parts (excepting the swap). Hdb1 is an ext2 partition (48 gigs), hdb2 is a 550 meg linux swap partition, hdb3 is another 48 gig ext2 partition, and hdb4 is a 53 gig fat32 partition.
I've been trying to full install to hdb1 and I kept having issues with grub not seeing the partition correctly. Grub kept telling me that the only place it was seeing /dev/vmlinuz was on (hd0,0). Now, I never ran an install of any kind on my first HD because I didn't want it being messed up somehow. Grub kept giving me an error saying "File system type unknown, partition type 0x7" when it hit the "root (hd1,0)" line.
Many scratchings of my head later I said what the heck and edited my grub file to something like
root (hd0,0)
kernel /boot/vmlinuz root=/dev/hdb1 ro vga=normal
boot
Well, lo and behold that worked. Which says to me that grub is using (hd0,0) for hdb1 when it should be using (hd1,0) for hdb1 (as far as I understand what I've read). The problem is (hd0,0) is supposed to be my Windows NTFS partition, and I don't know what to call it in grub to get it to load.
The other issue is now I can't mount hda right, which is making me a feared for my Windows partition. When I click to mount it in MUT a Rox window pops up for /mnt/hda1 but the window is totally empty.
So, what should I do now oh gurus of all things canine and Linux?
Oh, also, I thought grub loaded off of a specific HDD, my BIOS is set to load HHD 1 first (Windows) and HDD 2 second (Linux, the other white meat), but grub keeps popping up first.
Re: Full install on second HD makes XP unhappy
Welcome to Puppy! It is a fine distro!quyzbuk wrote:First, of all this is my first post here so hello all. I've only just started using Puppy about a week and a half ago, but so far I'm enjoying myself. The journey with Linux reminds me of my days and nights editing config files with MS-DOS 5.0.
I wish I understood the machinations of Linux well enough to assist you with
your Grub-XP challenge but I am still learning myself.
I look forward to reading this thread as I may be faced with a similar challenge
very soon!
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
Re: Full install on second HD makes XP unhappy
Try hitting the refresh button in the Rox File Explorer Window (it's the two green arrows going round).quyzbuk wrote:When I click to mount it in MUT a Rox window pops up for /mnt/hda1 but the window is totally empty.
Could this be drive jumpers not set correctly? Check that you have master and slave set the right way round.
Will
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]
I should have also said, when I click to mount it a blank window pops up and the drive doesn't change to mounted. It's still unmounted.
The drives have been working perfectly for about a year now, so I don't think it's the jumpers, but I'll check.
I did have the wrong HDD selected in BIOS. My BIOS seems to start with HDD-0, but when I selected HDD-0 the screen hung at a single line saying 'GRUB' with a cursor blinking at me mockingly for I couldn't get any more response out of the system. Switch back to HDD-1 at bootup and Linux runs fine. I'm enjoying the Linux install =).
The drives have been working perfectly for about a year now, so I don't think it's the jumpers, but I'll check.
I did have the wrong HDD selected in BIOS. My BIOS seems to start with HDD-0, but when I selected HDD-0 the screen hung at a single line saying 'GRUB' with a cursor blinking at me mockingly for I couldn't get any more response out of the system. Switch back to HDD-1 at bootup and Linux runs fine. I'm enjoying the Linux install =).
My experience with a frugal install made me understand that the boot partition x always shows up as hd(0,x).
Also wrt your grub file:
root (hd0,0)
kernel /boot/vmlinuz root=/dev/hdb1 ro vga=normal
the root ( hd0,0) is for grub to know where to look for the kernel etc, whereas the root=/dev/hdb1 is where the Linux filesystem / will be mounted from...
I am having some issues with multiple drives of my own, but they have to do with trying to boot off a drive connected to an PCI IDE controller. In your case are the 2 drives, connected to the mobo?
Also wrt your grub file:
root (hd0,0)
kernel /boot/vmlinuz root=/dev/hdb1 ro vga=normal
the root ( hd0,0) is for grub to know where to look for the kernel etc, whereas the root=/dev/hdb1 is where the Linux filesystem / will be mounted from...
I am having some issues with multiple drives of my own, but they have to do with trying to boot off a drive connected to an PCI IDE controller. In your case are the 2 drives, connected to the mobo?
Everything is true, if this works, as apparently it does.
If you think something is false, please explain what and why you think it is false.
Code: Select all
root (hd0,0)
kernel /boot/vmlinuz root=/dev/hdb1 ro vga=normal
boot
Have you tried making a kickstart boot floppy for XP?
Get access to a PC running windows XP on the same drive and partitiiion as your install was on.
Format a floppy in XP.
Copy NTLDR and NTDETECT and BOOT.INI to it
Boot that floppy.
It should start windows normally.
That is at least using the floppy.
You could also try booting a live CD of puppy PFIX=RAM and trying to mount the drives and see if any files appear.
Get access to a PC running windows XP on the same drive and partitiiion as your install was on.
Format a floppy in XP.
Copy NTLDR and NTDETECT and BOOT.INI to it
Boot that floppy.
It should start windows normally.
That is at least using the floppy.
You could also try booting a live CD of puppy PFIX=RAM and trying to mount the drives and see if any files appear.
Last edited by 8-bit on Wed 11 Jul 2007, 22:53, edited 1 time in total.
you could try this (and tell us what it says if anything):quyzbuk wrote:Okay, misunderstandings of grub designations aside....
Where the heck has all my data on hda1 gone?!
NTFS (read/write)
ntfsmount /dev/hda1 /mnt/hda1 -o force
NTFS Unmount (read/write)
fusermount -u /mnt/hda1
NTFS (readonly)
mount /dev/hda1 /mnt/hda1 -t ntfs -r
more shell tips here:
http://www.puppylinux.org/wikka/ShellScriptsExamples
sh-3.00# ntfsmount /dev/hda1 /mnt/hda1 -o force
Failed to startup volume : Invalid argument
Couldn't mount device '/dev/hda1' : Invalid argument
Mount failed.
sh-3.00# fusermount -u /mnt/hda1
fusermount: failed to unmount /mnt/hda1: Invalid argument
sh-3.00# mount /dev/hda1 /mnt/hda1 -t ntfs -r
Unexpected clusters per mft record (-128).
Failed to startup volume: Invalid argument
Failed to mount '/dev/hda1': Invalid argument
The device '/dev/hda1' doesn't have a valid NTFS.
Maybe you selected the wrong device? Or the whole disk instead of a
partition (e.g. /dev/hda, not /dev/hda1)? Or the other way around?
mount: Mounting /dev/hda1 on /mnt/hda1 failed: Invalid argument
Unexpected clusters per mft record (-128).
Failed to startup volume: Invalid argument
Failed to mount '/dev/hda1': Invalid argument
The device '/dev/hda1' doesn't have a valid NTFS.
Maybe you selected the wrong device? Or the whole disk instead of a
partition (e.g. /dev/hda, not /dev/hda1)? Or the other way around?
sh-3.00#
Gonna try my live-CD next
Failed to startup volume : Invalid argument
Couldn't mount device '/dev/hda1' : Invalid argument
Mount failed.
sh-3.00# fusermount -u /mnt/hda1
fusermount: failed to unmount /mnt/hda1: Invalid argument
sh-3.00# mount /dev/hda1 /mnt/hda1 -t ntfs -r
Unexpected clusters per mft record (-128).
Failed to startup volume: Invalid argument
Failed to mount '/dev/hda1': Invalid argument
The device '/dev/hda1' doesn't have a valid NTFS.
Maybe you selected the wrong device? Or the whole disk instead of a
partition (e.g. /dev/hda, not /dev/hda1)? Or the other way around?
mount: Mounting /dev/hda1 on /mnt/hda1 failed: Invalid argument
Unexpected clusters per mft record (-128).
Failed to startup volume: Invalid argument
Failed to mount '/dev/hda1': Invalid argument
The device '/dev/hda1' doesn't have a valid NTFS.
Maybe you selected the wrong device? Or the whole disk instead of a
partition (e.g. /dev/hda, not /dev/hda1)? Or the other way around?
sh-3.00#
Gonna try my live-CD next
Booted from my live CD
sh-3.00# ntfsmount /dev/hda1 /mnt/hda1 -o force
Failed to startup volume : Invalid argument
Couldn't mount device '/dev/hda1' : Invalid argument
Mount failed.
sh-3.00# fusermount -u /mnt/hda1
fusermount: failed to unmount /mnt/hda1: Invalid argument
sh-3.00# mount /dev/hda1 /mnt/hda1 -t ntfs -r
Unexpected clusters per mft record (-128).
Failed to startup volume: Invalid argument
Failed to mount '/dev/hda1': Invalid argument
The device '/dev/hda1' doesn't have a valid NTFS.
Maybe you selected the wrong device? Or the whole disk instead of a
partition (e.g. /dev/hda, not /dev/hda1)? Or the other way around?
mount: Mounting /dev/hda1 on /mnt/hda1 failed: Invalid argument
Unexpected clusters per mft record (-128).
Failed to startup volume: Invalid argument
Failed to mount '/dev/hda1': Invalid argument
The device '/dev/hda1' doesn't have a valid NTFS.
Maybe you selected the wrong device? Or the whole disk instead of a
partition (e.g. /dev/hda, not /dev/hda1)? Or the other way around?
sh-3.00#
I'm a feared
sh-3.00# ntfsmount /dev/hda1 /mnt/hda1 -o force
Failed to startup volume : Invalid argument
Couldn't mount device '/dev/hda1' : Invalid argument
Mount failed.
sh-3.00# fusermount -u /mnt/hda1
fusermount: failed to unmount /mnt/hda1: Invalid argument
sh-3.00# mount /dev/hda1 /mnt/hda1 -t ntfs -r
Unexpected clusters per mft record (-128).
Failed to startup volume: Invalid argument
Failed to mount '/dev/hda1': Invalid argument
The device '/dev/hda1' doesn't have a valid NTFS.
Maybe you selected the wrong device? Or the whole disk instead of a
partition (e.g. /dev/hda, not /dev/hda1)? Or the other way around?
mount: Mounting /dev/hda1 on /mnt/hda1 failed: Invalid argument
Unexpected clusters per mft record (-128).
Failed to startup volume: Invalid argument
Failed to mount '/dev/hda1': Invalid argument
The device '/dev/hda1' doesn't have a valid NTFS.
Maybe you selected the wrong device? Or the whole disk instead of a
partition (e.g. /dev/hda, not /dev/hda1)? Or the other way around?
sh-3.00#
I'm a feared
Given the RAM capacity of your machine, I wonder if the partitions you're using are much too large. Maybe the simplest solution might be to reformat the second hard drive with a few much smaller partitions such as a 1gig primary and a 2gig extended within which the swap partition is created. Reworking the MBR may also be necessary.
A very good procedure for full install to hard drive is here:
http://puppylinux.org/wikka/HardDiskInstall
That wiki page contains a few alternate installations and the description of the stages of the install at which a reboot is in order were very helpful to me.
I'm using HD installs of Puppy on three machines and all have rather small Puppy partitions. For my purposes, the smaller partitions enable my older computers to achieve much better operating speeds since less of the hard drive has to be searched while running the Puppy OS. Puppy's simple GRUB installation procedure has made booting a breeze.
A very good procedure for full install to hard drive is here:
http://puppylinux.org/wikka/HardDiskInstall
That wiki page contains a few alternate installations and the description of the stages of the install at which a reboot is in order were very helpful to me.
I'm using HD installs of Puppy on three machines and all have rather small Puppy partitions. For my purposes, the smaller partitions enable my older computers to achieve much better operating speeds since less of the hard drive has to be searched while running the Puppy OS. Puppy's simple GRUB installation procedure has made booting a breeze.
... except that the procedure is for Puppy versions 1.03-1.05, circa mid-year 2005.twodees wrote:A very good procedure for full install to hard drive is here:
http://puppylinux.org/wikka/HardDiskInstall
-aj
[size=84][i]hangout:[/i] ##b0rked on irc.freenode.net
[i]diversion:[/i] [url]http://alienjeff.net[/url] - visit The Fringe
[i]quote:[/i] "The foundation of authority is based upon the consent of the people." - Thomas Hooker[/size]
[i]diversion:[/i] [url]http://alienjeff.net[/url] - visit The Fringe
[i]quote:[/i] "The foundation of authority is based upon the consent of the people." - Thomas Hooker[/size]
sh-3.00# probedisk
/dev/hdc|cdrom|LITE-ON LTR-52327S
/dev/hdb|disk|WDC WD1600JB-22GVC0
/dev/hda|disk|WDC WD1000BB-00CAA1
sh-3.00# probepart
/dev/hdc|iso9660|0|LITE-ON LTR-52327S
/dev/hdb1|ext2|100357992|Linux Ext2Fs
/dev/hdb2|swap|1124550|Linux Swap
/dev/hdb3|ext2|100358055|Linux Ext2Fs
/dev/hdb4|vfat|110736045|Win95 FAT32
/dev/hda1|ntfs|195350337|OS/2 HPFS or NTFS
sh-3.00#
Looks like it's there.
/dev/hdc|cdrom|LITE-ON LTR-52327S
/dev/hdb|disk|WDC WD1600JB-22GVC0
/dev/hda|disk|WDC WD1000BB-00CAA1
sh-3.00# probepart
/dev/hdc|iso9660|0|LITE-ON LTR-52327S
/dev/hdb1|ext2|100357992|Linux Ext2Fs
/dev/hdb2|swap|1124550|Linux Swap
/dev/hdb3|ext2|100358055|Linux Ext2Fs
/dev/hdb4|vfat|110736045|Win95 FAT32
/dev/hda1|ntfs|195350337|OS/2 HPFS or NTFS
sh-3.00#
Looks like it's there.