[SOLVED] Is it ok to edit device.map?

Tiberius · 2009-01-25 11:09:02

I've gone round in circles and i'm all googled out. :( In a nutshell I would like Arch to reflect the disk order the same as in the bios. The setup at the moment is confusing and i've one failed grub2 update already.

outcome I would like:
Disk /dev/sda: 163.9 GB, 163928604672 bytes sata
Disk /dev/sdb: 120.0 GB, 120034123776 bytes sata
Disk /dev/sdc: 61.4 GB, 61492838400 bytes ide

To match disk order in BIOS:
160G
120G
60G

but currently it looks like this <snip>

fdisk -l
Arch see's it this way (back to front?)
Disk /dev/sda: 61.4 GB, 61492838400 bytes        ide
Disk /dev/sdb: 120.0 GB, 120034123776 bytes      sata
Disk /dev/sdc: 163.9 GB, 163928604672 bytes      sata

this bits fine <snip> note (hd0,0)

menu.lst 
# (0) Arch Linux
title  Arch Linux
root   (hd0,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/3b3d47a9-ee38-46a5-870a-79161cd7d2da ro
initrd /kernel26.img

bash-3.2# cat /boot/grub/device.map
(hd0)    /dev/sda
(hd1)    /dev/sdb
(hd2)    /dev/sdc

grub> find /grub/stage1
 (hd2,0)

grub>

Would an edit to /boot/grub/device.map then reset Grub to (hd0,0) be the way to do this or does Arch have another preffered method ? Honestly i'm all grubbed out at the moment :-)

edit: menu.lst (created by grub) shows root (hd0,0) but (hd2,0) for stage1 ??

Last edited by Tiberius (2009-01-25 15:29:06)

toad · 2009-01-25 12:19:47

I can't say I've tried it but don't see why you shouldn't. If you don't like it just edit/restore it again with a live CD and no harm is done.

Anyway, I don't think you can change the way grub sees your hard disks as that comes straight from the BIOS. But by editing the device.map file you can have your system act like you wish.

Personally I would find this confusing. Congruence in devices across processes is simple, changing things around is complicated

Tiberius · 2009-01-25 13:54:19

Personally I would find this confusing. Congruence in devices across processes is simple, changing things around is complicated sad

I agree and i'm loathe to tackle this but it's confusing right now. I think my best way out is to grub-install to root=(hd2,0) ,shutdown and unhook the 60gig (no OS). Boot back in with a possible grub edit.

I figure Arch is seeing the 60gig as sda because thats where the grub root sits at the moment ??

toad · 2009-01-25 13:58:10

It sees it as sda 'cos of your hardware. If the bios sees it first it is going to be sda. What are you physical connections to the mobo?

Tiberius · 2009-01-25 14:12:28

Thanks for your help and the swift reply! cheers.

I've a 60gig IDE 1st primary device and SCSI DVD on secondary slave. the SATA drives dont show up in the first section of my AMIBIOS menu. Further in their is another screen to select BOOT options. In here its set as I laid out in the first post - disk order 1st 160gig sata 2nd 120gig sata 3rd 60gig IDE.

This is why i'm thinking by physically removing the 60gig ide (for its getting in the way) it'll pickup the 160gig as the first disk thus sda.

ide connection to mobo 60gig - primary ide1
sata connections to mobo 160gig - channel1
120gig - channel2

toad · 2009-01-25 14:17:35

With that setup the only way to get your ide drive recognised after the sata lot is to get an ide pci card I reckon...

Tiberius · 2009-01-25 14:26:35

Yeah that sounds a good fix though I might just ebay the 60gig anyhow. I'll drop an update here later with the outcome.

cheers

Tiberius · 2009-01-25 15:27:25

Ok that almost went without hiccup ,i forgot to edit /etc/fstab and comment out the disconnected drive so Arch loader complained. quick fix on that and here it is.

steps taken:
grub set root to (hd2,0)
edit /boot/grub/menu.lst to leave only Arch loader
edit /etc/fstab and comment out the disk to be disconnected (I forgot this one)
reboot

bash-3.2# fdisk -l

Disk /dev/sda: 163.9 GB, 163928604672 bytes
255 heads, 63 sectors/track, 19929 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xb95b67cd

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          64      514048+  83  Linux
/dev/sda2              65        1339    10241437+  83  Linux
/dev/sda3            1340        2614    10241437+  83  Linux
/dev/sda4            2615       19929   139082737+   5  Extended
/dev/sda5            2615        3889    10241406   83  Linux
/dev/sda6            3890       16637   102398278+  83  Linux

Disk /dev/sdb: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xb897b897

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1         773     6209091   83  Linux
/dev/sdb2   *         774        1676     7253347+  83  Linux
/dev/sdb3            2678       14593    95715270   83  Linux
/dev/sdb4            1677        2677     8040532+  83  Linux

grub> find /grub/stage1
 (hd0,0)

grub>

Arch Linux

#1 2009-01-25 11:09:02

[SOLVED] Is it ok to edit device.map?

#2 2009-01-25 12:19:47

Re: [SOLVED] Is it ok to edit device.map?

#3 2009-01-25 13:54:19

Re: [SOLVED] Is it ok to edit device.map?

#4 2009-01-25 13:58:10

Re: [SOLVED] Is it ok to edit device.map?

#5 2009-01-25 14:12:28

Re: [SOLVED] Is it ok to edit device.map?

#6 2009-01-25 14:17:35

Re: [SOLVED] Is it ok to edit device.map?

#7 2009-01-25 14:26:35

Re: [SOLVED] Is it ok to edit device.map?

#8 2009-01-25 15:27:25

Re: [SOLVED] Is it ok to edit device.map?

Board footer