11:19 p.m.
Greetings all;
I started an install of f12 on what is /dev/sdb here, after using gparted
to set it up, and figured out a way to get around the disk config in anaconda.
I answered a few questions, and it looked as if it was headed off to do it
all by itself, so I toddled off to do a bit of walnut machining for several
hours.
On return, I had a hell of a time getting my monitor to unblank, so I guess
this BS with the ATI driver, radeon, has finally gotten to the ccfl lamp in
my monitor, and its just about 18 months old.
However, when I tried to use the exit button in that cd's simple gui, there
was no response until I right clicked on the screen, but since it was running
from the cd, it would not eject at any point during the reboot, and I finally
killed the power for the 2nd time and managed to grab it in the 2 seconds
between getting it to eject, and the bios sucking it back in. I expected it
to boot F12, but there was no sign of F12 in the grub menu. Just my
regular menu.
So I booted normally to F10 & kernel 2.6.34-rc2, and I have now tried to add
a chainloader stanza to my grub.conf here on /dev/sda1 that will cause it to
reload grub from /dev/sdb1.
However, all I can get are 'file not found' errors. Looking at /dev/sdb1
after mounting it shows:
root@coyote boot]# ls -l
total 16769
-rw-r--r-- 1 root root 98051 2009-11-07 21:24 config-2.6.31.5-127.fc12.x86_64
drwxr-xr-x 3 root root 1024 2009-11-08 23:40 efi
-rw-r--r-- 1 root root 161956 2009-10-13 15:13 elf-memtest86+-4.00
drwxr-xr-x 2 root root 1024 2010-03-21 23:56 grub
-rw-r--r-- 1 root root 11356301 2010-03-21 16:29 initramfs-2.6.31.5-127.fc12.x86_64.img
drwx------ 2 root root 12288 2010-03-21 16:15 lost+found
-rw-r--r-- 1 root root 160280 2009-10-13 15:13 memtest86+-4.00
-rw-r--r-- 1 root root 1869961 2009-11-07 21:24 System.map-2.6.31.5-127.fc12.x86_64
-rwxr-xr-x 1 root root 3423296 2009-11-07 21:24 vmlinuz-2.6.31.5-127.fc12.x86_64
Is anything missing?
Thanks.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
I do desire we may be better strangers.
-- William Shakespeare, "As You Like It"
3:10 a.m.
On Wed, 24 Mar 2010 02:40:08 -0400, Gene wrote:
On Wednesday 24 March 2010, Michael Schwendt wrote:
>On Tue, 23 Mar 2010 13:13:57 -0400, Gene wrote:
>> [...] how then do I install grub in /dev/sdb1? Easier to
>> reinstall, I want /root and /usr both on their own partitions anyway.
>
>You can tell the Fedora installer where to store GRUB.
>
Well, in this case I did, told it to put it in the mbr of /dev/sdb.
Then chainloading the boot sector of sdb1 doesn't make any sense.
Have you tried chainloading the MBR on sdb, at least?
title Fedora 12
rootnoverify (hd1)
chainloader +1
But apparently there is no way to verify that?
Even if you found the word "GRUB" in the MBR, it would need further
checks to verify whether that really is from your F12 install and not
an older one.
1:40 a.m.
On Wednesday 24 March 2010, Michael Schwendt wrote:
On Tue, 23 Mar 2010 13:13:57 -0400, Gene wrote:
> [...] how then do I install grub in /dev/sdb1? Easier to
> reinstall, I want /root and /usr both on their own partitions anyway.
You can tell the Fedora installer where to store GRUB.
Well, in this case I did, told it to put it in the mbr of /dev/sdb.
But apparently there is no way to verify that?
Thanks Michael.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
When the weight of the paperwork equals the weight of the plane, the
plane will fly.
-- Donald Douglas
6:07 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/23/2010 06:08 PM, Michael Schwendt wrote:
On Mon, 22 Mar 2010 17:10:49 -0400, Gene wrote:
> On Monday 22 March 2010, Will Walthall wrote:
>> So I made the assumption that your part layout was /dev/sdb1 f10
>> system, /dev/sdb2 f12 system.
>>
>> Option #1 Install grub to the MBR of /dev/sdb
>> Option #2 Install grub to the partition of /dev/sdb1
>>
>> Lots of things you need to consider, one you dont want to break
>>
>> Do you Chainload into mandriva aswell? is the Mandriva boot installed
>> to MBR /dev/sdd or in the partition /dev/sdd1?
>>
>> Steps I would take:
>> :Reinstall grub to the MBR of /dev/sda and make sure that it has these 3
>> : devices
>>
>> -grub prompt in f10-
>> device (hd0) /dev/sda //f10
>> device (hd1) /dev/sdb //f12
>> device (hd2) /dev/sdd //mandriva
>> root (hd0,0)
>> setup (hd0)
>
> This did not return any errors, so I am off to try it.
>
> And, and hour later, it failed, error 13. Invalid file format or some such
> drivel.
>
> The hour was because it decided to do an e2fsck on /usr, which is something
> over half a Tb.
>
>> Option #1
>>
>> :Reinstall grub to the MBR of /dev/sdb
>>
>> device (hd0) /dev/sdb // This grub is isolated from the MBR one on
>> /dev/sda so I believe this is correct, I've never done something like
>> this personally, though I've messed around with grub alot
>> root (hd0,0)
>> setup (hd0)
>>
>> : Make sure all your entries in menu.lst for f10 are correct
>>
>> # Again I think this is correct, though I haven't done anything like
>> this, I have chainloaded into grub installed to a partition, but not
>> into one installed to another MBR on a seperate drive
>> title Fedora 12
>> root (hd1,1)
>> chainloader (hd1)+1
>
> Now I have done this, and will try it. And this reverts to the grub screen
> from /dev/sda in about 4 seconds, silently.
Why did you try that? root (hd1,1) expands to /dev/sdb2 which is not
what you had referred to earlier.
# load boot sector of first partition (sdb1)
title Fedora 12
rootnoverify (hd1,0)
chainloader +1
Assuming that F12's GRUB _really_ is installed in /dev/sdb1 and NOT the MBR.
And if it's installed in the MBR, you could boot F12 by changing the boot
order in your BIOS, then use "grub-install" to (re-)install the boot loader.
Make sure that you don't mix /dev/sda1 and /dev/sdb1 when running grub-install.
you may also need to edit /boot/grub/device.map to make sure that the device
mapping is correct. (Note: this is USUALLY not necessary)
- -Greg
- --
+---------------------------------------------------------------------+
Please also check the log file at "/dev/null" for additional information.
(from /var/log/Xorg.setup.log)
| Greg Hosler ghosler(a)redhat.com |
+---------------------------------------------------------------------+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAkuooPAACgkQ404fl/0CV/TsogCg2KQKE4CRV8iSCn1s5rMtPcLd
D2UAnRgWtqHCss3XC0icIC8Jzv8aFE9O
=5hu+
-----END PGP SIGNATURE-----
5:08 a.m.
On Mon, 22 Mar 2010 17:10:49 -0400, Gene wrote:
On Monday 22 March 2010, Will Walthall wrote:
>So I made the assumption that your part layout was /dev/sdb1 f10
>system, /dev/sdb2 f12 system.
>
>Option #1 Install grub to the MBR of /dev/sdb
>Option #2 Install grub to the partition of /dev/sdb1
>
>Lots of things you need to consider, one you dont want to break
>
>Do you Chainload into mandriva aswell? is the Mandriva boot installed
>to MBR /dev/sdd or in the partition /dev/sdd1?
>
>Steps I would take:
>:Reinstall grub to the MBR of /dev/sda and make sure that it has these 3
>: devices
>
>-grub prompt in f10-
>device (hd0) /dev/sda //f10
>device (hd1) /dev/sdb //f12
>device (hd2) /dev/sdd //mandriva
>root (hd0,0)
>setup (hd0)
This did not return any errors, so I am off to try it.
And, and hour later, it failed, error 13. Invalid file format or some such
drivel.
The hour was because it decided to do an e2fsck on /usr, which is something
over half a Tb.
>Option #1
>
>:Reinstall grub to the MBR of /dev/sdb
>
>device (hd0) /dev/sdb // This grub is isolated from the MBR one on
>/dev/sda so I believe this is correct, I've never done something like
>this personally, though I've messed around with grub alot
>root (hd0,0)
>setup (hd0)
>
>: Make sure all your entries in menu.lst for f10 are correct
>
># Again I think this is correct, though I haven't done anything like
>this, I have chainloaded into grub installed to a partition, but not
>into one installed to another MBR on a seperate drive
>title Fedora 12
>root (hd1,1)
>chainloader (hd1)+1
Now I have done this, and will try it. And this reverts to the grub screen
from /dev/sda in about 4 seconds, silently.
Why did you try that? root (hd1,1) expands to /dev/sdb2 which is not
what you had referred to earlier.
# load boot sector of first partition (sdb1)
title Fedora 12
rootnoverify (hd1,0)
chainloader +1
Assuming that F12's GRUB _really_ is installed in /dev/sdb1 and NOT the MBR.
And if it's installed in the MBR, you could boot F12 by changing the boot
order in your BIOS, then use "grub-install" to (re-)install the boot loader.
Make sure that you don't mix /dev/sda1 and /dev/sdb1 when running grub-install.
4:48 p.m.
On Monday 22 March 2010, Michael Schwendt wrote:
On Mon, 22 Mar 2010 11:28:46 -0400, Gene wrote:
> >> So I booted normally to F10 & kernel 2.6.34-rc2, and I have now tried
> >> to add a chainloader stanza to my grub.conf here on /dev/sda1 that
> >> will cause it to reload grub from /dev/sdb1.
> >>
> >> Is anything missing?
> >
> >Two things. Confirmation that there really is a GRUB in /dev/sdb1's boot
> >sector and not in /dev/sdb's MBR. And you forgot to show what you added
> >to your F10's grub.conf.
>
> 1. I told it to put it in the MBR.
That would be /dev/sdb = (hd1) and not /dev/sdb1 = (hd1,0).
> The string 'GRUB' exists in the MBR, but
> there was a grub 2 install there prior from a mint8 install.
>
> 2.:
> #26
> title Fedora 12 64 bit from sdb by chainloading
> rootnoverify (hd1,0)
> makeactive
> chainloader +1
The comment is wrong. It tries to chainload /dev/sdb1 not the MBR.
The "makeactive" or "makeactive 1" typically is not necessary.
Do you see (hd1) in your F10's /boot/grub/device.map?
And what does /boot/grub/device.map on /dev/sdb1 contain?
I played with that some on the f12 disk, and yes, f10's device map is in
order, all bootable disks are listed in sata jack order, skipping the
Terrabyte drive I use for amanda.
Thanks Michael.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
"Anyone who is capable of getting themselves made President
should on no account be allowed to do the job."
- Some wisdom from The Book.
4:10 p.m.
On Monday 22 March 2010, Will Walthall wrote:
So I made the assumption that your part layout was /dev/sdb1 f10
system, /dev/sdb2 f12 system.
Option #1 Install grub to the MBR of /dev/sdb
Option #2 Install grub to the partition of /dev/sdb1
Lots of things you need to consider, one you dont want to break
Do you Chainload into mandriva aswell? is the Mandriva boot installed
to MBR /dev/sdd or in the partition /dev/sdd1?
Steps I would take:
:Reinstall grub to the MBR of /dev/sda and make sure that it has these 3
: devices
-grub prompt in f10-
device (hd0) /dev/sda //f10
device (hd1) /dev/sdb //f12
device (hd2) /dev/sdd //mandriva
root (hd0,0)
setup (hd0)
This did not return any errors, so I am off to try it.
And, and hour later, it failed, error 13. Invalid file format or some such
drivel.
The hour was because it decided to do an e2fsck on /usr, which is something
over half a Tb.
Option #1
:Reinstall grub to the MBR of /dev/sdb
device (hd0) /dev/sdb // This grub is isolated from the MBR one on
/dev/sda so I believe this is correct, I've never done something like
this personally, though I've messed around with grub alot
root (hd0,0)
setup (hd0)
: Make sure all your entries in menu.lst for f10 are correct
# Again I think this is correct, though I haven't done anything like
this, I have chainloaded into grub installed to a partition, but not
into one installed to another MBR on a seperate drive
title Fedora 12
root (hd1,1)
chainloader (hd1)+1
Now I have done this, and will try it. And this reverts to the grub screen
from /dev/sda in about 4 seconds, silently.
Don't do anything till we have another exchange of dialog, my
previous
message didn't take into account your non simple partition layout.
Humm, I didn't read this far, so I did it anyway. Sorry.
-Will
Thanks Will.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Are the STEWED PRUNES still in the HAIR DRYER?
2:06 p.m.
On Mon, 22 Mar 2010 11:28:46 -0400, Gene wrote:
>> So I booted normally to F10 & kernel 2.6.34-rc2, and I
have now tried to
>> add a chainloader stanza to my grub.conf here on /dev/sda1 that will
>> cause it to reload grub from /dev/sdb1.
>>
>> Is anything missing?
>
>Two things. Confirmation that there really is a GRUB in /dev/sdb1's boot
>sector and not in /dev/sdb's MBR. And you forgot to show what you added
>to your F10's grub.conf.
1. I told it to put it in the MBR.
That would be /dev/sdb = (hd1) and not /dev/sdb1 = (hd1,0).
The string 'GRUB' exists in the MBR, but
there was a grub 2 install there prior from a mint8 install.
2.:
#26
title Fedora 12 64 bit from sdb by chainloading
rootnoverify (hd1,0)
makeactive
chainloader +1
The comment is wrong. It tries to chainload /dev/sdb1 not the MBR.
The "makeactive" or "makeactive 1" typically is not necessary.
Do you see (hd1) in your F10's /boot/grub/device.map?
And what does /boot/grub/device.map on /dev/sdb1 contain?
1:26 p.m.
So I made the assumption that your part layout was /dev/sdb1 f10
system, /dev/sdb2 f12 system.
Option #1 Install grub to the MBR of /dev/sdb
Option #2 Install grub to the partition of /dev/sdb1
Lots of things you need to consider, one you dont want to break
Do you Chainload into mandriva aswell? is the Mandriva boot installed
to MBR /dev/sdd or in the partition /dev/sdd1?
Steps I would take:
:Reinstall grub to the MBR of /dev/sda and make sure that it has these 3 devices
-grub prompt in f10-
device (hd0) /dev/sda //f10
device (hd1) /dev/sdb //f12
device (hd2) /dev/sdd //mandriva
root (hd0,0)
setup (hd0)
Option #1
:Reinstall grub to the MBR of /dev/sdb
device (hd0) /dev/sdb // This grub is isolated from the MBR one on
/dev/sda so I believe this is correct, I've never done something like
this personally, though I've messed around with grub alot
root (hd0,0)
setup (hd0)
: Make sure all your entries in menu.lst for f10 are correct
# Again I think this is correct, though I haven't done anything like
this, I have chainloaded into grub installed to a partition, but not
into one installed to another MBR on a seperate drive
title Fedora 12
root (hd1,1)
chainloader (hd1)+1
Don't do anything till we have another exchange of dialog, my previous
message didn't take into account your non simple partition layout.
-Will
10:28 a.m.
On Monday 22 March 2010, Michael Schwendt wrote:
On Mon, 22 Mar 2010 00:19:58 -0400, Gene wrote:
> So I booted normally to F10 & kernel 2.6.34-rc2, and I have now tried to
> add a chainloader stanza to my grub.conf here on /dev/sda1 that will
> cause it to reload grub from /dev/sdb1.
>
> Is anything missing?
Two things. Confirmation that there really is a GRUB in /dev/sdb1's boot
sector and not in /dev/sdb's MBR. And you forgot to show what you added
to your F10's grub.conf.
1. I told it to put it in the MBR. The string 'GRUB' exists in the MBR, but
there was a grub 2 install there prior from a mint8 install.
2.:
#26
title Fedora 12 64 bit from sdb by chainloading
rootnoverify (hd1,0)
makeactive
chainloader +1
Thanks Michael.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Everything in this book may be wrong.
-- Messiah's Handbook : Reminders for the Advanced Soul
3:36 a.m.
You may need to just reinstall grub to the f12 partition
I'd backup your menu.lst on /dev/sdb2
Also make sure you /boot/grub directory has these files
-rw-r--r-- 1 root root 63 2010-03-11 12:33 device.map
-rw-r--r-- 1 root root 14872 2010-03-11 12:33 e2fs_stage1_5
-rw-r--r-- 1 root root 14036 2010-03-11 12:33 fat_stage1_5
-rw-r--r-- 1 root root 13344 2010-03-11 12:33 ffs_stage1_5
-rw------- 1 root root 1021 2010-03-11 13:54 grub.conf
-rw-r--r-- 1 root root 13356 2010-03-11 12:33 iso9660_stage1_5
-rw-r--r-- 1 root root 14928 2010-03-11 12:33 jfs_stage1_5
lrwxrwxrwx 1 root root 11 2010-03-11 12:33 menu.lst -> ./grub.conf
-rw-r--r-- 1 root root 13480 2010-03-11 12:33 minix_stage1_5
-rw-r--r-- 1 root root 16128 2010-03-11 12:33 reiserfs_stage1_5
-rw-r--r-- 1 root root 17488 2009-10-01 12:08 splash.xpm.gz
-rw-r--r-- 1 root root 512 2010-03-11 12:33 stage1
-rw-r--r-- 1 root root 125432 2010-03-14 14:54 stage2
-rw-r--r-- 1 root root 13628 2010-03-11 12:33 ufs2_stage1_5
-rw-r--r-- 1 root root 12932 2010-03-11 12:33 vstafs_stage1_5
-rw-r--r-- 1 root root 15664 2010-03-11 12:33 xfs_stage1_5
Amusing, I didn't realize that menu.lst was a symlink, neat!
Boot into fedora 10 on /dev/sdb1
su -c "grub"
at the grub prompt
device (hd0) /dev/sdb
root (hd0,1)
setup(hd0,1)
If this doesn't work then I dunno what's going on. If these aren't the
right settings for your Drive layout, send back a full overview of that and
I'll try edit the command sequence for you.
How this Helps
-Will
3:34 a.m.
On Mon, 22 Mar 2010 00:19:58 -0400, Gene wrote:
So I booted normally to F10 & kernel 2.6.34-rc2, and I have now
tried to add
a chainloader stanza to my grub.conf here on /dev/sda1 that will cause it to
reload grub from /dev/sdb1.
Is anything missing?
Two things. Confirmation that there really is a GRUB in /dev/sdb1's boot
sector and not in /dev/sdb's MBR. And you forgot to show what you added
to your F10's grub.conf.
1:48 a.m.
Do what thou wilt
shall be the whole of the Law.
On 3/21/10, Gene Heskett <gene.heskett(a)verizon.net> wrote:
Greetings all;
I started an install of f12 on what is /dev/sdb here, after using gparted
to set it up, and figured out a way to get around the disk config in
anaconda.
I answered a few questions, and it looked as if it was headed off to do it
all by itself, so I toddled off to do a bit of walnut machining for several
hours.
On return, I had a hell of a time getting my monitor to unblank,
darn power-saving technique scares me when it happens. :)
<space bar> , mouse moving didn't work?
so I guess
this BS with the ATI driver, radeon, has finally gotten to the ccfl
lamp in
my monitor, and its just about 18 months old.
However, when I tried to use the exit button in that cd's simple gui, there
was no response until I right clicked on the screen, but since it was
running
from the cd, it would not eject at any point during the reboot, and I
finally
killed the power for the 2nd time and managed to grab it in the 2 seconds
between getting it to eject, and the bios sucking it back in. I expected it
to boot F12, but there was no sign of F12 in the grub menu. Just my
regular menu.
and no first-boot screen? you might have an incomplete install...
however...
So I booted normally to F10 & kernel 2.6.34-rc2, and I have now tried to add
a chainloader stanza to my grub.conf here on /dev/sda1 that will cause it to
reload grub from /dev/sdb1.
instead of chaining, you could try:
making a copy of your F10 stanza,
and editing its fields to point to the paths/files on sdb.
Is anything missing?
Thanks.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
I do desire we may be better strangers.
-- William Shakespeare, "As You Like It"
--
Love is the law, love under will.
charles zeitler
10:25 a.m.
On Monday 22 March 2010, charles zeitler wrote:
Do what thou wilt
shall be the whole of the Law.
On 3/21/10, Gene Heskett <gene.heskett(a)verizon.net> wrote:
> Greetings all;
>
> I started an install of f12 on what is /dev/sdb here, after using
> gparted to set it up, and figured out a way to get around the disk config
> in anaconda.
>
> I answered a few questions, and it looked as if it was headed off to do
> it all by itself, so I toddled off to do a bit of walnut machining for
> several hours.
>
> On return, I had a hell of a time getting my monitor to unblank,
darn power-saving technique scares me when it happens. :)
<space bar> , mouse moving didn't work?
Nah, it will eventually start, and from some googling, it appears I need to
haul it up to the tv station & make use of the capacitor wizard I bought
before I retired. Bad caps in the PSU, they have to warm up before they work
somewhere near right. Which also explains the occasional odor of something
hot in this little man cave that I haven't been able to run down. That
little $175 gizmo is the slickest thing for finding bad caps I've ever seen.
In a busy shop, it will pay for itself the first week in troubleshooting time
saved.
so I guess
> this BS with the ATI driver, radeon, has finally gotten to the ccfl lamp
> in my monitor, and its just about 18 months old.
>
> However, when I tried to use the exit button in that cd's simple gui,
> there was no response until I right clicked on the screen, but since it
> was running
> from the cd, it would not eject at any point during the reboot, and I
> finally
> killed the power for the 2nd time and managed to grab it in the 2 seconds
> between getting it to eject, and the bios sucking it back in. I expected
> it to boot F12, but there was no sign of F12 in the grub menu. Just my
> regular menu.
and no first-boot screen? you might have an incomplete install...
There is a grub installed on the first drive and the 4th drive, and I have
been booting the 4th drive by copying its vmlinuz etc to the first drives
boot partition but naming the 4th drives partitions as I can't get a
chainload to work there either. I did have it working to the 2nd drive for a
while, booting Mint8-x64, but I did something to mint and it won't boot
anymore, so I overwrote it with F12. If it installed grub in /dev/sdb's MBR,
I should be able to do this. Unforch, I have not found a tool which can read
the MBR and tell if it is. dd of course can pull it, but I have NDI how to
interpret that output. The string 'GRUB' does exist in it, sstartiong at
offset 0179, but that could be leftovers from the old mint install FAIK.
however...
> So I booted normally to F10 & kernel 2.6.34-rc2, and I have now tried to
> add a chainloader stanza to my grub.conf here on /dev/sda1 that will
> cause it to reload grub from /dev/sdb1.
instead of chaining, you could try:
making a copy of your F10 stanza,
and editing its fields to point to the paths/files on sdb.
Which of course limits me to a verse of grub.conf for each kernel installed,
and easy thing to do with mandriva since they default the boot names to
softlinks from vmlinuz to whatever the latest kernel installed is, same for
the initrd.
But Fedora doesn't, which will be the case if I ever get it booted and let
the update run, and then of course it won't be able to find the old, been
removed kernel. Mint8's grub 2 screen looks cool FWTW.
> Is anything missing?
Slash would appear to be there, but I haven't wandered around and found where
I put /home yet, shoulda wrote it down I guess, and I'd like to make /root a
separate partition too, I have it separate here on F10 after I copied the F10
from a failing drive to a fresh 1Tb drive, which sped this box up by about
4x, so I may just re-install again. But that is only a 370GB drive. With
the monitor problem being foremost, it will be a day or so before I get back
to this. I have another Samsung digital tv I can use for a monitor and have
for troubleshooting another box, its tuner failed but its awfully close to be
too darned big for the space it has to fit into. Tape measure time I guess.
;-)
Many Thanks Charles.
> Thanks.
>
> --
> Cheers, Gene
> "There are four boxes to be used in defense of liberty:
> soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
>
> I do desire we may be better strangers.
> -- William Shakespeare, "As You Like It"
> --
Love is the law, love under will.
charles zeitler
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Somewhere in suburban Honolulu, an unemployed bellhop is whipping up a
batch of illegal psilocybin chop suey!!
12:15 p.m.
On Tuesday 23 March 2010, Gregory Hosler wrote:
On 03/23/2010 06:08 PM, Michael Schwendt wrote:
> On Mon, 22 Mar 2010 17:10:49 -0400, Gene wrote:
>> On Monday 22 March 2010, Will Walthall wrote:
>>> So I made the assumption that your part layout was /dev/sdb1 f10
>>> system, /dev/sdb2 f12 system.
>>>
>>> Option #1 Install grub to the MBR of /dev/sdb
>>> Option #2 Install grub to the partition of /dev/sdb1
>>>
>>> Lots of things you need to consider, one you dont want to break
>>>
>>> Do you Chainload into mandriva aswell? is the Mandriva boot installed
>>> to MBR /dev/sdd or in the partition /dev/sdd1?
>>>
>>> Steps I would take:
>>> :Reinstall grub to the MBR of /dev/sda and make sure that it has these
>>> : 3 devices
>>>
>>> -grub prompt in f10-
>>> device (hd0) /dev/sda //f10
>>> device (hd1) /dev/sdb //f12
>>> device (hd2) /dev/sdd //mandriva
>>> root (hd0,0)
>>> setup (hd0)
>>
>> This did not return any errors, so I am off to try it.
>>
>> And, and hour later, it failed, error 13. Invalid file format or some
>> such drivel.
>>
>> The hour was because it decided to do an e2fsck on /usr, which is
>> something over half a Tb.
>>
>>> Option #1
>>>
>>> :Reinstall grub to the MBR of /dev/sdb
>>>
>>> device (hd0) /dev/sdb // This grub is isolated from the MBR one on
>>> /dev/sda so I believe this is correct, I've never done something like
>>> this personally, though I've messed around with grub alot
>>> root (hd0,0)
>>> setup (hd0)
>>>
>>> : Make sure all your entries in menu.lst for f10 are correct
>>>
>>> # Again I think this is correct, though I haven't done anything like
>>> this, I have chainloaded into grub installed to a partition, but not
>>> into one installed to another MBR on a seperate drive
>>> title Fedora 12
>>> root (hd1,1)
>>> chainloader (hd1)+1
>>
>> Now I have done this, and will try it. And this reverts to the grub
>> screen from /dev/sda in about 4 seconds, silently.
>
> Why did you try that? root (hd1,1) expands to /dev/sdb2 which is not
> what you had referred to earlier.
>
> # load boot sector of first partition (sdb1)
> title Fedora 12
> rootnoverify (hd1,0)
> chainloader +1
>
> Assuming that F12's GRUB _really_ is installed in /dev/sdb1 and NOT the
> MBR.
>
> And if it's installed in the MBR, you could boot F12 by changing the boot
> order in your BIOS, then use "grub-install" to (re-)install the boot
> loader. Make sure that you don't mix /dev/sda1 and /dev/sdb1 when running
> grub-install.
you may also need to edit /boot/grub/device.map to make sure that the
device mapping is correct. (Note: this is USUALLY not necessary)
-Greg
If not exact, (hand edited) then I can also copy this one to the others.
Thanks Greg.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
It is exactly because a man cannot do a thing that he is a proper judge of
it.
-- Oscar Wilde
12:13 p.m.
On Tuesday 23 March 2010, Michael Schwendt wrote:
On Mon, 22 Mar 2010 17:10:49 -0400, Gene wrote:
> On Monday 22 March 2010, Will Walthall wrote:
> >So I made the assumption that your part layout was /dev/sdb1 f10
> >system, /dev/sdb2 f12 system.
> >
> >Option #1 Install grub to the MBR of /dev/sdb
> >Option #2 Install grub to the partition of /dev/sdb1
> >
> >Lots of things you need to consider, one you dont want to break
> >
> >Do you Chainload into mandriva aswell? is the Mandriva boot installed
> >to MBR /dev/sdd or in the partition /dev/sdd1?
> >
> >Steps I would take:
> >:Reinstall grub to the MBR of /dev/sda and make sure that it has these 3
> >: devices
> >
> >-grub prompt in f10-
> >device (hd0) /dev/sda //f10
> >device (hd1) /dev/sdb //f12
> >device (hd2) /dev/sdd //mandriva
> >root (hd0,0)
> >setup (hd0)
>
> This did not return any errors, so I am off to try it.
>
> And, and hour later, it failed, error 13. Invalid file format or some
> such drivel.
>
> The hour was because it decided to do an e2fsck on /usr, which is
> something over half a Tb.
>
> >Option #1
> >
> >:Reinstall grub to the MBR of /dev/sdb
> >
> >device (hd0) /dev/sdb // This grub is isolated from the MBR one on
> >/dev/sda so I believe this is correct, I've never done something like
> >this personally, though I've messed around with grub alot
> >root (hd0,0)
> >setup (hd0)
> >
> >: Make sure all your entries in menu.lst for f10 are correct
> >
> ># Again I think this is correct, though I haven't done anything like
> >this, I have chainloaded into grub installed to a partition, but not
> >into one installed to another MBR on a seperate drive
> >title Fedora 12
> >root (hd1,1)
> >chainloader (hd1)+1
>
> Now I have done this, and will try it. And this reverts to the grub
> screen from /dev/sda in about 4 seconds, silently.
Why did you try that? root (hd1,1) expands to /dev/sdb2 which is not
what you had referred to earlier.
# load boot sector of first partition (sdb1)
title Fedora 12
rootnoverify (hd1,0)
chainloader +1
Assuming that F12's GRUB _really_ is installed in /dev/sdb1 and NOT the
MBR.
And I repeat, at the initilization screen, I told it to put it in the mbr of
/dev/sdb. No idea if it did. But now I'll redo it (the whole install) and
have it put there.
And if it's installed in the MBR, you could boot F12 by changing
the boot
order in your BIOS, then use "grub-install" to (re-)install the boot
loader. Make sure that you don't mix /dev/sda1 and /dev/sdb1 when running
grub-install.
If its that complex, how then do I install grub in /dev/sdb1? Easier to
reinstall, I want /root and /usr both on their own partitions anyway.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If your bread is stale, make toast.
12:28 p.m.
On Monday 22 March 2010, Will Walthall wrote:
You may need to just reinstall grub to the f12 partition
I'd backup your menu.lst on /dev/sdb2
Also make sure you /boot/grub directory has these files
-rw-r--r-- 1 root root 63 2010-03-11 12:33 device.map
-rw-r--r-- 1 root root 14872 2010-03-11 12:33 e2fs_stage1_5
-rw-r--r-- 1 root root 14036 2010-03-11 12:33 fat_stage1_5
-rw-r--r-- 1 root root 13344 2010-03-11 12:33 ffs_stage1_5
-rw------- 1 root root 1021 2010-03-11 13:54 grub.conf
-rw-r--r-- 1 root root 13356 2010-03-11 12:33 iso9660_stage1_5
-rw-r--r-- 1 root root 14928 2010-03-11 12:33 jfs_stage1_5
lrwxrwxrwx 1 root root 11 2010-03-11 12:33 menu.lst -> ./grub.conf
-rw-r--r-- 1 root root 13480 2010-03-11 12:33 minix_stage1_5
-rw-r--r-- 1 root root 16128 2010-03-11 12:33 reiserfs_stage1_5
-rw-r--r-- 1 root root 17488 2009-10-01 12:08 splash.xpm.gz
-rw-r--r-- 1 root root 512 2010-03-11 12:33 stage1
-rw-r--r-- 1 root root 125432 2010-03-14 14:54 stage2
-rw-r--r-- 1 root root 13628 2010-03-11 12:33 ufs2_stage1_5
-rw-r--r-- 1 root root 12932 2010-03-11 12:33 vstafs_stage1_5
-rw-r--r-- 1 root root 15664 2010-03-11 12:33 xfs_stage1_5
Amusing, I didn't realize that menu.lst was a symlink, neat!
Boot into fedora 10 on /dev/sdb1
F10 /.boot is installed in /dev/sda1.
su -c "grub"
at the grub prompt
>device (hd0) /dev/sdb
>root (hd0,1)
>setup(hd0,1)
Snipped from that shell:
grub> device (hd0,0) /dev/sdb
device (hd0,0) /dev/sdb
grub> root (hd0,1)
root (hd0,1)
Filesystem type unknown, partition type 0x82
grub> setup (hd0,1)
setup (hd0,1)
Error 17��: Cannot mount selected partition
grub> quit
quit
[root@coyote f12]#
But I can mount it just fine.
I think that (hdx,x) crap is whats confusing grub. No two installs are using
the same (hd0,0) to drive correlations. And no one seems to have written
the definitive tome on how this works yet either. IMO, grubs man pages
contain about a -10ee34 torr vacuum. That is slightly better than
interstellar space 2 light years out.
And until we have a method to absolutely, carved in Forentine Marble, method
of correlating the installed drives to the (hdx,x) crap that the bios and grub
seem married to, this confusion will likely remain. I assume (there _that_
word again) that the bios _should_ be treating disks in the order of the
sata jacks they are plugged into, and my F10 install does.
If this doesn't work then I dunno what's going on. If these
aren't the
right settings for your Drive layout, send back a full overview of that and
I'll try edit the command sequence for you.
All sata drives except for a worn out floppy, but the linux floppy driver has
been broken for the use I would use it for for about 2 years now. It
cannot read or write a 256 byte sector format.
Here is the blkid output:
[root@coyote f12]# blkid
Part of F10 install
/dev/sda1: LABEL="seaboot" UUID="9848a6bb-6ecd-412d-b2f5-0fdf68102bd3"
SEC_TYPE="ext2" TYPE="ext3"
/dev/sda2: TYPE="swap" UUID="1e5d265b-0097-4699-b2f9-47e75ec2f95c"
/dev/sda3: LABEL="sea-slash"
UUID="3d923d41-fe1d-49b2-9618-c03005888c41" SEC_TYPE="ext2"
TYPE="ext3"
Amanda's virtual tapes
/dev/sdc1: LABEL="/amandatapes-1-T"
UUID="223e0988-3155-4935-8511-20e3edd77910" SEC_TYPE="ext2"
TYPE="ext3"
Mandriva 2010-x64
/dev/sdd1: UUID="9838db29-2ddd-46e5-835a-7c0f5eafae2a" TYPE="ext3"
SEC_TYPE="ext2" LABEL="mdv-boot"
/dev/sdd5: TYPE="swap" UUID="7daaed8e-b1be-48fd-b701-852f4c904eb2"
/dev/sdd6: UUID="00a85218-ca2a-4265-bd8f-f9f511586dbc" SEC_TYPE="ext2"
TYPE="ext3" LABEL="mdv-home"
/dev/sdd7: UUID="b832a03e-54ad-44d1-8f3e-e5322f359f90" SEC_TYPE="ext2"
TYPE="ext3" LABEL="mdv-opt"
/dev/sdd8: UUID="a00d2ff6-179d-431b-8b57-984f12a89e0d" SEC_TYPE="ext2"
TYPE="ext3" LABEL="mdv-usr"
/dev/sdd9: UUID="cbb6883f-04f3-4acb-b46b-032bb28dfea8" SEC_TYPE="ext2"
TYPE="ext3" LABEL="mdv-var"
/dev/sdd10: UUID="ab39ede0-9b10-40e3-9fa9-2db747347934"
SEC_TYPE="ext2" TYPE="ext3" LABEL="mdv-slash"
More of the F10 install
/dev/sda5: LABEL="sea-opt" UUID="bce6a095-6e7b-475d-b8a4-f75c1ae74a11"
SEC_TYPE="ext2" TYPE="ext3"
/dev/sda6: LABEL="sea-home"
UUID="7c9c7c96-4dcc-43db-8248-7dca7dd2abad" SEC_TYPE="ext2"
TYPE="ext3"
/dev/sda7: LABEL="sea-root"
UUID="937fecdd-d6f8-49aa-a438-4cee9789d796" SEC_TYPE="ext2"
TYPE="ext3"
/dev/sda8: LABEL="sea-var" UUID="efbd9228-89d0-428a-86c4-dfaec8c40ebd"
SEC_TYPE="ext2" TYPE="ext3"
/dev/sda9: LABEL="sea-tmp" UUID="466c0f0b-5b5e-4a8f-a83a-a8016d9c17f3"
SEC_TYPE="ext2" TYPE="ext3"
/dev/sda10: LABEL="sea-usr"
UUID="c377dbfc-caa6-464e-9d32-e75ef4b70e03" SEC_TYPE="ext2"
TYPE="ext3"
The F12 install
/dev/sdb1: UUID="021e13d4-5444-4f90-a4cd-033991a9b992" SEC_TYPE="ext2"
TYPE="ext3" LABEL="F12boot"
/dev/sdb2: TYPE="swap" UUID="1a530a26-93f0-439e-b8d0-0aa1c6fa46ae"
/dev/sdb3: UUID="018cb1db-d493-4a8e-a2eb-a642ef434851" TYPE="ext4"
<--anaconda insisted & wouldn't proceed if ext3
/dev/sdb5: LABEL="F12slash"
UUID="1c53bab9-8764-46f3-8ddd-90681f0b46b4" TYPE="ext4" <--anaconda
insisted, ditto
/dev/sdb6: UUID="0eb7f1d5-9480-4a65-9295-3b66129a256f" SEC_TYPE="ext2"
TYPE="ext3"
/dev/sdb7: UUID="25d147be-117e-4b45-a582-4001c3b8592d" SEC_TYPE="ext2"
TYPE="ext3"
/dev/sdb8: UUID="21bfa162-b42b-44da-907f-1b09d67dc378" SEC_TYPE="ext2"
TYPE="ext3"
/dev/sdb9: UUID="b5eb25cf-07a8-4b79-b702-decb2ff3bc34" SEC_TYPE="ext2"
TYPE="ext3"
How this Helps
-Will
Why that is not in sata port number order I have NDI.
Thanks Will.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Inara: "Mal, you don't have to die alone."
Mal: "Everybody dies alone."
--Episode #8, "Out of Gas"
5208
days inactive
5210
days old
17 comments
5 participants
participants (5)
-
Charles Zeitler -
Gene Heskett -
Gregory Hosler -
Michael Schwendt -
Will Walthall