On Sun, 13 Feb 2011 00:35:22 +0100, steef wrote: > Camaleón schreef:
>> "Mounting" is different than "booting", so, what kind of error are you >> experiencing that involves GRUB2 and mounting? Moreover, how can a >> bootloader interfere in mounting a partition? :-? >> > >> >> > hi camaleón > > 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. Wow, there is no need to remove the cables, just telling the installer where do you want to install GRUB (legacy or 2), that is, in the MBR of the selected disk. And how do you know what is the device name of each disk? By running a LiveCD before installing and taking note of the device detection "inside" GRUB :-) Better yet, I prefer to keep the MBR with "generic code" (no GRUB nor any other bootloader at all) and install GRUB inside the boot sector of the selected partition. But true is that I've only seen that option of "generic code" within the openSUSE installer, but not in Debian. In Debian installer (and IIRC) you only have 3 options with GRUB: 1/ Install GRUB into MBR 2/ Install GRUB into partition 3/ Do not install any bootloader After all, I suppose your main concern for unplugging the hard disks was only to be sure that GRUB was going to be installed in the proper MBR of the selected disk :-) > 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. Let's make a pause here. What do you exactly mean for "my /dev/sda1 does *not* recognize /dev/sdb1 etc."? I can't understand this sentence. Are you talking here about GRUB's menu, that cannot boot the other operating systems or are you saying that you cannot access the other hard disks once you booted and are inside the system? We need to know what are you trying to do and what result (error message) are you getting. > 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. You still need to clarify what do you mean by "ata-hd's are not recognized/seen at all anymore" because hard disk recognition is a complete different thing and does not involve GRUB (or any bootloader) at all. "dmesg" will tell if/how are the disks being detected. > so: without a solution i have to put lilo after years in working order > again. i do not see any progression in this; with due respect to all the > work of the developers put in grub2. > > i am sorry i was not clear enough. i hope i made myself clearer now. I'm still a bit unclear about the role that is playing GRUB 2 with your problem :-? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.02.13.12.41...@gmail.com
