Master or Slave for an disk bearing os

Started by mylo, 2013/09/28, 18:15:37

Previous topic - Next topic
Print
Go Down Pages1
User actions

mylo

2013/09/28, 18:15:37
A new install of firestarter was placed on my second hd as I want to give rest to my first disk (that bears the siduction install up to now).

I have just this os. My question:
The os is now installed on the ide slave disk. Does this matter or shall i connect the os bearing hd to a master ide port?

ReinerS

#1
2013/09/28, 18:59:44
As far as I am aware this shouldn't matter. The only thing that must be assured is that grub finds it by the UID or the label as some times the order of disks seems to change.

regards

Reiner
slackware => SuSE => kanotix => sidux => aptosid  => siduction

michaa7

#2
2013/09/28, 19:45:30
Quote from: "mylo"...
The os is now installed on the ide slave disk. Does this matter or shall i connect the os bearing hd to a master ide port?

No. The only real requirement is: On one IDE cable you must have one master - and if a second hd is attached - a slave. As a best practice, the master should be at the end of the cable, the slave in the middle. Although the latter is *not* part of the IDE specification I stubled over old BIOSes which got confused when the master was in the middle.

BTW: my boot- and system hd is on sdbx, the slave hd.
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

ralul

#3
2013/09/28, 20:12:14
@michaa7, If you install grub2 then directly into the mbr of /dev/sda, can it then find the SLAVE /dev/sdbX/boot ?
(Or: is it required to have an extra /boot partition on the MASTER disk /dev/sda? )
experiencing siduction runs better than my gentoo makes me know I know nothing

michaa7

#4
2013/09/29, 04:00:07
Quote from: "ralul"@michaa7, If you install grub2 then directly into the mbr of /dev/sda, can it then find the SLAVE /dev/sdbX/boot ?
(Or: is it required to have an extra /boot partition on the MASTER disk /dev/sda? )
I'm a bit confused by your question. As I understand it the master/slave relationship of harddisks concerns only the hardware. Like connecting a cable to the right pins. I don't understand in which way grub could be affected?

I just recently had a IDE-hd jumpered as slave with an unused system and grub installed in mbr. I attached the disk as the only disk (still accidently in slave mode) Grub found a system, started it but stopped with file system errors. Then I realized my error, and after changing the disk to master mode it booted without problems.

This is not really an answer to you question. It's only an example on how grub and master/slave are acting on different levels.
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

Gabriel_M

#5
2013/09/30, 02:23:24
The first portion of the Grub is always installed into the mbr of /dev/sda
This is the Grub that starts the systems, using the rest of the various Grubs installed into /boot of each system.
Print
Go Up Pages1
User actions