[RAS] Nebka disk

Christian Zimmermann christian.zimmermann at uconn.edu
Fri Mar 14 07:24:37 EDT 2008


Don't you want me to put the 80GB disk in place of the new one, i.e., just 
switch places? It looks like you want only the 140GB, and keep the current 
placement only if BIOS does not boot off 140GB.

Christian Zimmermann                                     FIGUGEGL!
Department of Economics
University of Connecticut
341 Mansfield Road, Unit 1063
Storrs, CT 06269-1063
http://ideas.repec.org/zimm/   christian.zimmermann at uconn.edu
http://ideas.repec.org/e/pzi1.html

On Fri, 14 Mar 2008, Thomas Krichel wrote:

>
>
>  Christian Zimmermann writes
>> rsync finished, tried the grub-install, it failed:
>>
>> end_request: I/O error, dev fd0, sector 0
>> end_request: I/O error, dev fd0, sector 0
>> end_request: I/O error, dev fd0, sector 0
>> end_request: I/O error, dev fd0, sector 0
>> end_request: I/O error, dev fd0, sector 0
>> end_request: I/O error, dev fd0, sector 0
>> The file /vol/boot/grub/boot/grub/stage1 not read correctly
>>
>> I have not touched /etc/fstab/. I have not rebooted. Note that it will
>> reboot into kernel 2.4 by default. I have not restarted rid.
>>
>> I am out of here. I can get back to the machine room Friday 7:30am EDT.
>
>  You could have woken me up.
>
>  Anyway, having woken up, I did
>
> nebka:~# grub-install --root-directory=/vol /dev/sdb
> /dev/sdb does not have any corresponding BIOS drive.
>
>  Googling for this I did
>
> nebka:~# grub-install --recheck --root-directory=/vol /dev/sdb1
> Probing devices to guess BIOS drives. This may take a long time.
> Installation finished. No error reported.
> This is the contents of the device map /vol/boot/grub/device.map.
> Check if this is correct or not. If any of the lines is incorrect,
> fix it and re-run the script `grub-install'.
>
> (fd0)   /dev/fd0
> (hd0)   /dev/sda
> (hd1)   /dev/sdb
>
>  We should be ready now to exchange the disks. Take
>  the 80G out. Put the 140 into the physical
>  place where the 80G was. Go into the bios to check that the
>  bios sees only the 140G disk. You may have to do
>  this a couple of times, the bios is sometimes
>  "slow". Then reboot to Linux, everything should
>  start as normal.
>
>  If this fails, put the 80G back and check that
>  the bios boots off it. Then you can change the
>  root parameter in the
>
> /boot/grub/menu.lst
>
>  The default entry is set on line 12 of this file.
>  The numbering starts at 0. It used to be set to
>  2, to prevent firing up the 2.6 kernel. I have
>  set it to 0. Thus
>
> kernel          /boot/vmlinuz-2.6.18-6-686 root=/dev/sda1 ro noacpi noapic
>
>  can be changed to
>
> kernel          /boot/vmlinuz-2.6.18-6-686 root=/dev/sdb1 ro noacpi noapic
>
>  Then we have the 80G disk in there. In /boot/grub/menu.lst
>  change
>
>
> kernel          /boot/vmlinuz-2.6.18-6-686 root=/dev/sda1 ro single
> kernel          /boot/vmlinuz-2.4.27-2-686 root=/dev/sda1 ro noacpi noapic
> kernel          /boot/vmlinuz-2.4.27-2-686 root=/dev/sda1 ro single
>
>  to
>
> kernel          /boot/vmlinuz-2.6.18-6-686 root=/dev/sdb1 ro single
> kernel          /boot/vmlinuz-2.4.27-2-686 root=/dev/sdb1 ro noacpi noapic
> kernel          /boot/vmlinuz-2.4.27-2-686 root=/dev/sdb1 ro single
>
>  and reboot. It then should see the 80G as a boot disk, and
>  use the 140G as the root.
>
>
>  Cheers,
>
>  Thomas Krichel                    http://openlib.org/home/krichel
>                                RePEc:per:1965-06-05:thomas_krichel
>  phone: +7 383 330 6813                       skype: thomaskrichel
>



More information about the RAS-run mailing list