[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: grub 2 problems ??



Tom H schreef:
On Sat, Feb 12, 2011 at 6:46 PM, steef<debian.linux@home.nl>  wrote:
Tom H schreef:
On Sat, Feb 12, 2011 at 10:26 AM, steef<debian.linux@home.nl>   wrote:
for years (from potato/woody on) i have mounted 3 hd' s in my machine
(independently installed from each other with debian, somtimes slackware
and/or gentoo) from one specific hd with/after the command #mkdir
/mnt/sdx,
mnt/sdy etc.  and in fstab  /dev/sdx  /mnt/sdx ext3 user  0  0&&   (to
keep
it simple). on each hd i had a bootloader (lilo and later grub)
installed.

with grub2 as bootloader under squeeze i cannot mount other hd's anymore
when independently on the *other* hd' s a bootloader (grub2) in the mbr
is
installed. without installing grub2 in the mbr of a sata-hd the hd on
which
i am mounting *does* recognize the other hd *with the exception of (old)
ata
hd's.

my question: what do i miss if anything? or is this normal for the new
grub?
is there anything to do about this? has this got to do with UUID-numbers?
I assume that by "mount" you mean "boot from".

What's the output of "os-prober"?
steef@squeeze:~$ sudo os-prober
[sudo] password for steef:
Sorry, try again.
[sudo] password for steef:
/dev/sdb1:Debian GNU/Linux (6.0):Debian:linux
/dev/sdc1:Debian GNU/Linux (6.0):Debian1:linux
steef@squeeze:~$

please read my answer to camaleón in this thread. thank you for your
response,

that is exactly my problem. what i do know is the difference (after
some work) with the early days of grub. i install in one machine on
separate hd's p.e. debian, gentoo and slackware, with on each hd grub
installed in the mbr. at each install i loosened the cables of the
other two hd's. each installation is so completely independent of each
other. in the old days i could with simple modifications in /etc/fstab
and /mnt make the installation on /dev/hdax *see*  the file systems on
the other hd's : /dev/hdy and /dev/hdz.

with sata ide' s this was possible too on my (two) machines (included
windows xp that i somatimes *must* use) up till now.

my newest machine only has sata connections. when i install on the
three sata hd's in this machine completely independent of each other
with loosened cables of the *other* two disks; including grub2 placing
the bootloader in the mbr of each disk independently of each other;
and i start up with again fastened cables; my /dev/sda1 does *not*
recognize /dev/sdb1 etc.

when i install on the same way on the three disks (a lot of work last
two nights) the same os' s on these disks; the debian (squeeze) os
*can* see the filesystems on the other two hd's *with* grub2 installed
but *without* putting the bootloader in the mbr of these two disks.
older ata-hd's are not recognized/seen at all anymore.
I can't say that I really understand what you're trying to accomplish.

Given the output of "os-prober", grub2 on your sda squeeze install is
recognizing your squeeze installs on sdb and sdc when sda, sdb, sdc
are connected and grub2'll populate grub.cfg with entries for all
three installs to allow you to boot from any one of them when all
disks are connected.
agreed
If you want to be able to boot with sda disconnected, you'll have to
install grub2 into the MBRs of the other two disks and populate
grub.cfg in both those installs.

of course
If you want to add another (or other) disk(s) to fstab, run "blkid"
and add lines for the relevant partition(s) with the corresponding
UUID(s).
i did, so it is a mystery for me. and, because of this mystery i seem not to be able to formulate a question clear enough to be answered.i apologize for that and go on on this quest again tonight. thank you for your answer(s) up till noe.

kind regards,

steef

 see below: all is in /etc/fstab


# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc            /proc           proc    defaults        0       0
# / was on /dev/sda1 during installation
UUID=882ffd4e-8147-42a2-9690-9b111cdaf5cc / ext3 errors=remount-ro 0$
# swap was on /dev/sda5 during installation
UUID=d6b6bb4e-d764-4955-919f-f2985a597225 none swap sw 0 $
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0
/dev/sdb1       /mnt/sdb1       ext3    user    0       0
#is in older days /dev/sdc1
UUID=4d4caecf-1035-4296-b5c6-3a86f74f8858 /mnt/sdc1 ext3 user 0 0






Reply to: