Hi Everybody,
[cut]
> Unsolved problem: some distributions want to boot from disk or cdrom before
> upgrading a whole system (e.g. SuSE does that). The problem is that they don' t
> have a RAID kernel on their floppy/cdrom boot system, so you won' t be able to
> access your installation on /dev/md0.
>
> Workarounds:
> - use a non-RAID device: copy all your stuff on it, upgrade and copy all back
> to your raid device
> - make your own boot/install disk with a RAID kernel
> - don' t do this kind of update but update single packages
here's what I tried while upgrading from SuSE 6.1 to SuSE 6.2.
- raid 0.90
- raid 0 /dev/hda2 /dev/hdb2 /dev/md0 for /
- raid 5 /home
- /dev/hda1 is /boot non-raid
I 1st tried to create a SuSE-Bootdisk with a patched kernel, but I did not
suceed. It was booting fine, and started yast, but after chosing "Start
Installation", the system mentioned "Loading Data into RAMDISK" (and
certainly did), but was not able to start yast after loading it. Therefore
I was forced to use the original SuSE-bootdisk.
I used raidsetfaulty /dev/md0 /dev/hda2
and raidhotremove /dev/md0 /dev/hda2.
so the raid keeps on running on /dev/hdb2.
I used fdisk to set the /dev/hda2 partition to an normal Linux-Part. and
mke2fs /dev/hda2. Copied the entire system from to /md0 to /dev/hda2. Then
I booted from the SuSE-Bootdisk and updated that system. After booting it,
I copied the filesys back to /dev/md0.
Using fdisk, I set the partition-id of /dev/hda2 back to fd and used
raidhotadd /dev/md0 /dev/md0. After resyncing, I runs fine.
HTH,
Daniel
____________________________________________________
DANIEL WIRTH |
<[EMAIL PROTECTED]> |
http://www.wirthuell.de |
____________________________________________________
Linux: resistance is useless, you will be emulated |
____________________________________________________
