View previous topic :: View next topic |
Author |
Message |
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54236 Location: 56N 3W
|
Posted: Fri Jul 06, 2007 12:41 pm Post subject: |
|
|
paresthesias,
Welcome to Gentoo.
/dev/hdf sound like a secondary drive on a PCI plug in hard drive conroler.
With /dev/sda and /dev/sdb in BIOS (fakeraid) your system should sgow grub either two or four drives, it varies with the BIOS.
If the BIOS can see /dev/hdf (the controller card needs to have a BIOS of its own), then that will be one dribe.
If the card is non bootable, then grub will not see it.
Your raid will appear as either one or three devices to grub. Some BIOSes will only show the raid logical device, others show the underlying hard drives too.
(hd1,0) is the first partition on one of the drives. As your fakeraid is raid0, only one SATA drive will have a partition table.
Boot the livecd by typing at the liveCD boot: prompt. Run fdisk -l and post the output.
Do not be alarmed at the apparent missing partition table on one of the SATA drives, thats normal. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
paresthesias n00b
Joined: 05 Jul 2007 Posts: 3
|
Posted: Fri Jul 06, 2007 9:58 pm Post subject: |
|
|
Thanks for the reply, I'm about ready to give up and stick with windows :-/.
Code: | gentoo dodmraid
. . .
fdisk -l |
Code: | Disk /dev/hdf": 100.2 GB, 100256292864 bytes
255 heads, 63 sectors/track, 12188 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hdf1 * 1 3264 26218048+ 7 HPFS/NTFS
/dev/hdf2 3265 6377 25005172+ 5 Extended
/dev/hdf3 6378 9641 26218080 83 Linux
/dev/hdf5 * 3265 3269 40131 83 Linux
/dev/hdf6 3270 3394 1004031 82 Linux swap/Solaris
/dev/hdf7 3395 6377 23960916 83 Linux
Disk /dev/sda": 100.2 GB, 100256292864 bytes
255 heads, 63 sectors/track, 12188 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13054 104856223+ 7 HPFS/NTFS
Disk /dev/sdb": 100.2 GB, 100256292864 bytes
255 heads, 63 sectors/track, 12188 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/sdb doesn't contain a valid partition table |
|
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54236 Location: 56N 3W
|
Posted: Fri Jul 06, 2007 11:01 pm Post subject: |
|
|
paresthesias,
You have a partition table on /dev/sda but not /dev/sdb, as expected for a raid0 set.
Code: | Device Boot Start End Blocks Id System
/dev/sda1 * 1 13054 104856223+ 7 HPFS/NTFS |
The + after the number of blocks shows its bem made to fill the drive.
How is /dev/hdf connected ?
It looks like it could be SATA, as its the same size as your raid drives. I still need to understand where and how /dev/hdf is connected - its a strange drive identifier.
I guess that you boot windows nomally from the raid ?
What does grub report if you press 'e' at the splash screen then go to the statement, erase it until it reads and press the tab key. Grub will list your drives as reported by the BIOS.
Choose one and fill in (for e.g. 0) press tab again and grub will list the partition on the selected drive.
You will have either four or two drives, depending on how the BIOS handles the raid.
If you have 4, hd0..3, two will have one partition (dev/sda and the raid) one will have 6 partitions /dev/hdf and one will have none.
Some BIOSes insist on exactly one partition being tagged as bootable on the boot drive. Linux doesn't care but windows does. Remove the bootable flag from /dev/hdf5, using fdisk. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
paresthesias n00b
Joined: 05 Jul 2007 Posts: 3
|
Posted: Sun Jul 08, 2007 1:22 am Post subject: |
|
|
Quote: | The + after the number of blocks shows its bem made to fill the drive. |
That's a 100gb partition (made under windows) on the 180gb raid0... Not sure why it displays the plus,....
I think it's plain ATA. /dev/hde is my cdrom,... Windows used to boot from the raid, but currently boots from /dev/hdf1 with no problems using its bootloader. I removed the bootable flag on /dev/hdf5, that didn't help, and pressing tab in normal Grub after "(hd" says something like "possible drives: hd1" and doesn't recognize any others, including hd0, and "(hd1," + [tab] shows only partition (hd1,0). It might be interesting to note that Fedora recognizes my drive as /dev/sda.
Right now, I'm using the windows bootloader to boot Grub4Dos,. Tab completion in the command-line lists all my drives, etc., and I've been able to boot both Gentoo and Fedora. I've spent too much time on this already, so I'll just stick with this solution. Thank-you, NeddySeagoon, for your time and support. |
|
Back to top |
|
|
tony11235 Apprentice
Joined: 15 May 2006 Posts: 198
|
Posted: Wed Jul 18, 2007 5:10 am Post subject: error 22 |
|
|
I freed some space from my /dev/sda3, to try out some other distros. I installed ubuntu on a /dev/sda4 and used my swap from /dev/sda2. I had ubuntu's grub load the grub menu at boot. This morning I deleted the /dev/sda4 partition and merged it back with sda3. Using Ubuntu's live cd, I ran grub, root (hd0,0), setup (hd0,0), quit. Yet I still get error 22 when grub tries to load. What else can I do?
Code: |
Device Boot Start End Blocks Id System
/dev/sda1 * 1 5 40131 83 Linux
/dev/sda2 6 397 3148740 82 Linux swap / Solaris
/dev/sda3 398 14593 114029370 83 Linux |
|
|
Back to top |
|
|
tony11235 Apprentice
Joined: 15 May 2006 Posts: 198
|
Posted: Wed Jul 18, 2007 1:32 pm Post subject: Now error 15 |
|
|
Ok so I accidentally deleted /dev/sda1. Good thing there wasn't anything important on that. I reformatted it, made it bootable, mounted it to /boot, installed grub again, copied my kernel image over to /boot, wrote the grub.conf. This is my fstab table
Code: |
/dev/sda1 /boot ext2 defaults,noatime 1 2
/dev/sda2 none swap sw 0 0
/dev/sda3 / ext3 noatime 0 1
/dev/cdrom /mnt/cdrom auto noauto,user 0 0
#/dev/fd0 /mnt/floppy auto noauto 0 0
# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
# use almost no memory if not populated with files)
shm /dev/shm tmpfs nodev,nosuid,noexec 0 0
proc /proc proc nodev,nosuid,noexec 0 0
|
Yet now I am getting grub error 15. My kernel image IS in /dev/sda1. Also I don't get this error when I run grub-install --no-floppy /dev/sda.
I ran fsck -y /dev/sda1, and I get:
Code: | fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
/dev/sda1: clean, 30/10040 files, 5586/40128 blocks
|
My grub.conf looks like this:
Code: |
default 0
timeout 30
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
title=Gentoo Linux
root (hd0,0)
kernel /boot/kernel root=/dev/sda3 vga=0x318
|
I hope this doesn't lead to a reinstallation. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54236 Location: 56N 3W
|
Posted: Wed Jul 18, 2007 7:26 pm Post subject: |
|
|
tony11235,
Error 15 means that grub cannot find a file you are asking for. Its easily fixed when we determine which file and why.
Code: | splashimage=(hd0,0)/boot/grub/splash.xpm.gz | tells grub to look for the file (hd0,0)/boot/grub/splash.xpm.gz. If you get the splash screen behind the grub menu (not just a black screen) its not that one.
Code: | root (hd0,0)
kernel /boot/kernel | tells grub to find a file called (hd0,0)/boot/kernel Does that file exist ?
Since you have a real /boot partition, you will beed the self referencing symbolic link in /boot, so ls -l /boot should show in cyan (pale blue). That may be missing as you remade you /boot by hand.
The alternative is to remove the /boot fragment from both the above pathnames in your grub.conf. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
tony11235 Apprentice
Joined: 15 May 2006 Posts: 198
|
Posted: Wed Jul 18, 2007 11:48 pm Post subject: |
|
|
Actually it doesn't even display the splash screen or OS selection menu.
ls -l /boot:
Code: |
total 3519
drwxr-xr-x 2 root root 1024 2007-07-18 23:17 grub
-rw-r--r-- 1 root root 3574744 2007-07-18 18:06 kernel
drwx------ 2 root root 12288 2007-07-18 17:59 lost+found
|
Ok I re-ran grub-install --root-directory=/boot /dev/sda and that went fine.
Edit:
now "ls -l /boot" gives me:
Code: |
total 3520
drwxr-xr-x 3 root root 1024 2007-07-19 09:38 boot
drwxr-xr-x 2 root root 1024 2007-07-19 09:15 grub
-rw-r--r-- 1 root root 3574744 2007-07-18 18:06 kernel
drwx------ 2 root root 12288 2007-07-18 17:59 lost+found
|
but inside of /boot/boot, "kernel" does not exist, and there is no grub.conf inside of /boot/boot/grub. Should I try to make some links? |
|
Back to top |
|
|
tony11235 Apprentice
Joined: 15 May 2006 Posts: 198
|
Posted: Thu Jul 19, 2007 2:06 am Post subject: |
|
|
So with /boot/kernel , /boot/grub/grub.conf and /boot/grub/menu.lst existing without the /boot/boot, I get error 15. But with the previous existing, plus /boot/boot existing without /boot/boot/kernel , /boot/boot/grub/grub.conf, /boot/boot/grub/menu.lst, I just get the grub prompt.
Edit:
Ok I copied the kernel image from /boot/kernel over to /boot/boot/kernel, copied /boot/grub/grub.conf over to /boot/boot/grub/grub.conf, and ln -snf grub.conf menu.list inside of /boot/boot/grub, and now it finally boots. Though I still don't see why it wouldn't have booted without /boot/boot existing.
Maybe I should delete my posts since I've basically just been talking/responding/updating to myself.
Last edited by tony11235 on Thu Jul 19, 2007 2:22 am; edited 1 time in total |
|
Back to top |
|
|
desultory Bodhisattva
Joined: 04 Nov 2005 Posts: 9410
|
Posted: Thu Jul 19, 2007 2:19 am Post subject: |
|
|
Code: | su -
mount /boot
cd /boot/
rmdir ./boot
ln -s . boot |
|
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54236 Location: 56N 3W
|
Posted: Thu Jul 19, 2007 6:20 pm Post subject: |
|
|
tony11235,
Your boot symlink is missing.
Code: | mount /boot
cd /boot
ln -s . boot | will recreate it.
Heres why you need it. You have /dev/sda1 as your /boot and Code: | splashimage=(hd0,0)/boot/grub/splash.xpm.gz |
Now, (hd0,0) is /boot, so that line translates as splashimage=/boot/boot/grub/splash.xpm.gz
Thats fine with the symlink, as it takes care of the extra /boot
The reason for the symlink is it allows the same grub.conf to work regardless if /boot is a directory on the root filesystem or its own partition.
I suspect you also have the menu.lst -> /boot/grub/grub.conf missing too. That will explain the blank screen.
Don't attempt to replicate /boot in /boot/boot ... that way lies insanity. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
tony11235 Apprentice
Joined: 15 May 2006 Posts: 198
|
Posted: Thu Jul 19, 2007 6:56 pm Post subject: |
|
|
NeddySeagoon wrote: | tony11235,
Your boot symlink is missing.
Code: | mount /boot
cd /boot
ln -s . boot | will recreate it.
Heres why you need it. You have /dev/sda1 as your /boot and Code: | splashimage=(hd0,0)/boot/grub/splash.xpm.gz |
Now, (hd0,0) is /boot, so that line translates as splashimage=/boot/boot/grub/splash.xpm.gz
Thats fine with the symlink, as it takes care of the extra /boot
The reason for the symlink is it allows the same grub.conf to work regardless if /boot is a directory on the root filesystem or its own partition.
I suspect you also have the menu.lst -> /boot/grub/grub.conf missing too. That will explain the blank screen.
Don't attempt to replicate /boot in /boot/boot ... that way lies insanity. |
Understood. |
|
Back to top |
|
|
ale.0 n00b
Joined: 21 Jul 2007 Posts: 4
|
Posted: Mon Jul 23, 2007 3:15 am Post subject: missing symlink to . in /boot |
|
|
Hi,
I was finishing an installation off of the livecd and now I have a problem similar to tony11235. I am missing the symlink to . in boot. I have tried Code: |
mount /boot
cd /boot
ln -s . boot
|
but I get Code: | ln: creating symbolic link 'boot': Operation not permitted |
I also don't see any link for menu.lst.
I tried to boot anyway, but of course it didn't work and I was greeted by the grub prompt.
My partititions ( I had a pre-existing Win XP on sda1):
Quote: |
/dev/sda1 HPFS/NTFS
/dev/sda2 W95 Ext'd (LBA)
/dev/sda3 W95 FAT32 (LBA)
/dev/sda4 Linux swap / Solaris
/dev/sda5 Linux
|
grub.conf:
Quote: |
default 0
timeout 30
splashimage=(hd0,2)/grub/splash.xmp.gz
title=Gentoo Linux 2.6.20-r8
root (hd0,2)
kernel /linux-2.6.20-gentoo-r8 root=/dev/sda5
title=Windows XP
rootnoverify (hd0,0)
makeactive
chainloader +1
|
Any help would be really appreciated. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54236 Location: 56N 3W
|
Posted: Mon Jul 23, 2007 6:40 pm Post subject: |
|
|
ale.0,
Welcome to Gentoo.
Where is your /boot partition ?
suggests its /dev/sda3, which you say is FAT 32.
If thats right, it leads to some interesting complications because FAT cannot support symbolic links, so you have to get all the names right, with no references.
If your boot is not a real partition but a subdirectory on /dev/sda5, then your statement is not correct and you need to have full pathnames for all the files mentioned in grub.conf. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
ale.0 n00b
Joined: 21 Jul 2007 Posts: 4
|
Posted: Tue Jul 24, 2007 12:13 am Post subject: boot partition as fat rather than ext2 |
|
|
[slap on forehead]
I can't remember why or how I thought that the boot partition had to be fat or fat32. Now I see why I had problems.
Yes, boot is a separate partition on /dev/sda3, and I am now back to the handbook, chapter 4. I just have
Code: |
mke2fs /dev/sda3
mkdir /mnt/gentoo/boot
mount /dev/sda3 /mnt/gentoo/boot
|
and will now recompile the kernel, copy it to /boot, update /etc/ftab, re-install grub... Did I forget something?
---
On a separate note, from the grub prompt, yesterday I did manage to boot the kernel I had compiled previously, but only to get a General protection fault really early in the boot, a little bit after detecting the Intel 965 Chipset. I suppose I'll have to rebuild the kernel with a different profile and configuration... but maybe this should go to another thread or forum. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54236 Location: 56N 3W
|
Posted: Tue Jul 24, 2007 6:36 pm Post subject: |
|
|
ale.0,
A General Protection Fault is a windows thing. Are you sure you booted Linux ?
FAT32 on /boot can be made to work, you just have to manage without symlinks.
Its no problem to change the filesystem in /boot. Copy the contents somewhere with cp -a
make the new filesystem
restore the contents (cp -a again)
reinstall grub the the MBR, so it can cope with the new fs.
make your missing symlinks.
fix grub.conf, if needed _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
ale.0 n00b
Joined: 21 Jul 2007 Posts: 4
|
Posted: Wed Jul 25, 2007 2:06 am Post subject: |
|
|
Yes, I did that, made the filesystem anew in my boot partition, reinstalled grub in the MBR and it worked, I was able to see the splash image, boot into Windows, but I got a different problem when booting Linux (not a general protection fault this time ). I'll post it to another thread, now grub works for me.
Thanks NeddySeagoon. |
|
Back to top |
|
|
amarodeeps n00b
Joined: 28 May 2002 Posts: 50
|
Posted: Wed Jul 25, 2007 2:08 pm Post subject: New Grub issue |
|
|
Hi, it seems like this is the place to post Grub problems, so I'm posting a new one in the hope that someone might have a clue what is going on.
I moved a server yesterday, turned it off for the first time in a very long time (probably last september, since that is the last time I re-compiled kernel). Now, it will not boot, and this is what I see every time I try:
Code: |
Attempting Boot From CD-ROM
Attempting Boot From Hard Drive
GRUB Loading stage1.5
GRUB loading, please wait...
_
|
(the underscore at the end represents the flashing cursor that sits there, and sits there, and sits there...)
I can boot just fine into the system with my handy gentoo install / boot disk, and I can chroot in, and run commands, and etc. The system itself seems normal.
Here's what I've tried: removing floppy boot from BIOS ordering, per Gentoo Grub Error Collection, re-compiling Grub with no CFLAGS (CFLAGS="" emerge -v grub), re-running grub-install, replacing the grub.conf file with a new freshly formatted one, and nothing works. Nada, zip, zilch, nothing. Every time I boot from hard drive I get the above. I even left the thing on all last night, we're talking 14 hours or so, and nothing happened.
At this point I think I might try installing an older version of grub just to see what happens, but who knows if that will help.
I am completely stumped at this point. If there was some sort of error, perhaps I could look for a solution there, but I feel like I'm taking punches in the dark. Does anyone have any suggestions?
Thank you!
Dave |
|
Back to top |
|
|
AriciU n00b
Joined: 03 Aug 2007 Posts: 4
|
Posted: Fri Aug 03, 2007 9:25 am Post subject: |
|
|
Ok, this is the dumbest thing i ever encountered.
I installed a new SATA HDD. Everytime i start the PC i get either an Error 15 or and Error 17 from Grub. I'm not talking about a "GRUB Error 15: xxxxx", i'm talking about a "please wait... Error 15". So no grub menu gets loaded to give me my OS'es to boot!
Anyway, i used to solve that by doing a CTRL+ALT+DEL and it would work fine the second time. That is stupid and illogical!
Anyway, i started up the PC today and i couldn't make that damn Error 15 dissapear no mather how many restarts i tried. I booted a live-cd and re-installed grub but i got the same error over and over.
So i though of doing something illogical. I disconnected the new HDD and grub menu loaded fine. I shut down the PC, reconnected the HDD and the grub menu loaded perfectly again. WTF? That is stupid and doesn't make any sence.
Any ideas about this? I'm soo close to removing grub and re-using vista's boot loader. Now i'll have a headache all day long because of this crap |
|
Back to top |
|
|
AriciU n00b
Joined: 03 Aug 2007 Posts: 4
|
Posted: Fri Aug 03, 2007 12:41 pm Post subject: |
|
|
Fixed.
I made a grub bootable cd thru stage2_eltorrito, booted that, did find /grub/menu.lst and found it as (hd2,3) instead of (hd3,3). My BIOS apparently sees it as hd2,3 while slack sees is as hd3,3. Ran root (hd2,3), setup (hd0) (MBR) and everything works fine now. |
|
Back to top |
|
|
lyallp Veteran
Joined: 15 Jul 2004 Posts: 1557 Location: Adelaide/Australia
|
Posted: Fri Aug 03, 2007 1:15 pm Post subject: Trying to boot a cloned system on a new disk. |
|
|
Trying to boot a cloned system on a new disk.
As a part of the exercise I carried out, described here https://forums.gentoo.org/viewtopic-p-4170747.html#4170747
I now have my old, trusty, failing IDE disk booting fine from GRUB using the following GRUB entry
Code: |
title Gentoo Linux - IDE Disk
root (hd0,0)
kernel /vmlinuz root=/dev/hda5 vga=306
|
Where an excerpt of my fstab on the IDE contains
Code: |
/dev/hda1 /boot xfs defaults,noatime 1 1
/dev/hda5 / xfs defaults,noatime 1 2
/dev/hda7 /usr xfs defaults,noatime 1 3
/dev/hda8 /var xfs defaults,noatime 1 4
/dev/hda9 /home xfs defaults,noatime 1 5
/dev/hda10 /tmp xfs defaults,noatime 1 6
/dev/hda11 /usr/local xfs defaults,noatime 1 7
/dev/hda12 /opt xfs defaults,noatime 1 8
/dev/hda14 /portage xfs defaults,noatime 1 9
|
I have now partitioned, formatted and duplicated my entire system onto a new SATA disk, using LVM for all but the boot and root partition. Excerpt from the fstab on the SATA as follows :-
Code: |
/dev/vg/swap none swap sw
/dev/sda2 / xfs auto,defaults,noatime 1 10
/dev/sda1 /boot xfs auto,defaults,noatime 1 11
/dev/vg/home /home xfs auto,defaults,noatime 1 12
/dev/vg/opt /opt xfs auto,defaults,noatime 1 13
/dev/vg/portage /portage xfs auto,defaults,noatime 1 14
/dev/vg/tmp /tmp xfs auto,defaults,noatime 1 15
/dev/vg/usr /usr xfs auto,defaults,noatime 1 16
/dev/vg/usr_local /usr/local xfs auto,defaults,noatime 1 17
/dev/vg/var /var xfs auto,defaults,noatime 1 18
|
but, do you think I can convince GRUB to boot using the following entry when I boot the IDE disk?
Code: |
title Gentoo Linux - SATA Disk
root (hd1,0)
kernel (hd1,0)/vmlinuz vroot=/dev/sda2 vga=306
|
Basically, I am still booting my old IDE drive, executing the GRUB on the old IDE drive but I want to make sure my new SATA drive can actually boot before I switch the BIOS to boot from that disk instead. Instead of booting the system on the SATA disk, I keep ending up booting the old IDE system.
My fstab on the SATA drive is different from the IDE Drive, basically, the old IDE system mounts the new SATA partitions under /mnt/new and the new SATA mounts the old IDE partitions under /mnt/old.
The GRUB config on the SATA drive, I am ignoring, at this stage as I figure I am using the IDE version at this point.
Of course, I am doing something really silly, anyone like to enlighten me? _________________ ...Lyall |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54236 Location: 56N 3W
|
Posted: Fri Aug 03, 2007 1:31 pm Post subject: |
|
|
lyallp,
Your BIOS may refer to the boot drive as (hd0) regardless of which drive you point it to to boot from.
What does vroot=/dev/sda2 do ?
I've seen root=/dev/sda2 and real_root=/dev/sda2
What error message do you get and at what stage of the boot process ? _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
lyallp Veteran
Joined: 15 Jul 2004 Posts: 1557 Location: Adelaide/Australia
|
Posted: Fri Aug 03, 2007 2:02 pm Post subject: |
|
|
Firstly, vroot - a typo. It was supposed to be root
So, my GRUB entry is now...
Code: |
title Gentoo Linux - SATA Disk
root (hd1,0)
kernel (hd1,0)/vmlinuz root=/dev/sda2 vga=306
|
This results in a kernel starting and then a panic as it tries to mount the root filesystem.
Code: | vfs: Cannot open root device "sda2" or unknown-block(0,0) |
I know that /dev/sda2 is valid and mounts, I have it mounted under /mnt/new when I boot the IDE disk. In fact, I have the entire SATA disk mount heirarchy mounted under /mnt/new, as per this extract from my fstab on the IDE disk...
Code: |
/dev/sda2 /mnt/new xfs auto,defaults,noatime 1 10
/dev/sda1 /mnt/new/boot xfs auto,defaults,noatime 1 11
/dev/vg/swap none swap sw
/dev/vg/home /mnt/new/home xfs auto,defaults,noatime 1 12
/dev/vg/opt /mnt/new/opt xfs auto,defaults,noatime 1 13
/dev/vg/portage /mnt/new/portage xfs auto,defaults,noatime 1 14
/dev/vg/tmp /mnt/new/tmp xfs auto,defaults,noatime 1 15
/dev/vg/usr /mnt/new/usr xfs auto,defaults,noatime 1 16
/dev/vg/usr_local /mnt/new/usr/local xfs auto,defaults,noatime 1 17
/dev/vg/var /mnt/new/var xfs auto,defaults,noatime 1 18
|
The vmlinux in IDE /boot and SATA /boot are the same - I did a diff, so it's not that I don't have XFS compiled in. (actually, the /boot directories of both disks only differ in their grub.conf content as I am not maintaining the grub.conf on the SATA drive at this stage)
I tried (by editing the grub config during boot)
Code: |
title Gentoo Linux - SATA Disk
root (hd1,0)
kernel /vmlinuz root=/dev/sda2 vga=306
|
ie, removing the device specifier off the beginning of the /vmlinuz
At this stage, I am not changing the BIOS boot order, I figure I simply want to 'select' the new OS from my existing GRUB boot up - once I know it actually boots, then I will cross the bridge of changing the BIOS boot order and probably having the device ids change. _________________ ...Lyall |
|
Back to top |
|
|
lyallp Veteran
Joined: 15 Jul 2004 Posts: 1557 Location: Adelaide/Australia
|
Posted: Fri Aug 03, 2007 2:24 pm Post subject: |
|
|
Oops, think I may have found it, I had scsi generic as a module...
Duh.
Will update this post if this was the problem, which I suspect it is. _________________ ...Lyall |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54236 Location: 56N 3W
|
Posted: Fri Aug 03, 2007 2:47 pm Post subject: |
|
|
lyallp,
Its not SCSI Generic. Its either SCSI Disk Support, because SATA drives appear as SCSI or the hardware driver for your SATA chip set.
Both must be built in, not modules. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|