draft howto on making raids for surviving a disk crash
This is intended for the linux raid howto. Please give comments. It is not fully ready /keld
Howto prepare for a failing disk
The following will describe how to prepare a system to survive if one disk fails. This can be important for a server which is intended to always run. The description is mostly aimed at small servers, but it can also be used for
work stations to protect it for not losing data, and be running even if a disk fails. Some recommendations on larger server setup is given at the end of the howto.
This requires some extra hardware, especially disks, and the description will also touch how to mak the most out of the disks, be it in terms of available disk space, or input/output speed.
1. Creating of partitions
We recommend creating partitions for /boot, root, swap and other file systems. This can be done by fdisk, parted or maybe a graphical interface like the Mandriva/PClinuxos harddrake2. It is recommended to use drives with equal sizes and performance characteristics.
If we are using the 2 drives sda and sdb, then sfdisk may be used to make all the partitions into raid partitions:
sfdisk -c /dev/sda 1 fd
sfdisk -c /dev/sda 2 fd
sfdisk -c /dev/sda 3 fd
sfdisk -c /dev/sda 5 fd
sfdisk -c /dev/sdb 1 fd
sfdisk -c /dev/sdb 2 fd
sfdisk -c /dev/sdb 3 fd
sfdisk -c /dev/sdb 5 fd
Using:
fdisk -l /dev/sda /dev/sdb
The partition layout could then look like this:
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System /dev/sda1 1 37 297171 fd Linux raid autodetect /dev/sda2 38 1132 8795587+ fd Linux raid autodetect /dev/sda3 1133 1619 3911827+ fd Linux raid autodetect /dev/sda4 1620 121601 963755415 5 Extended /dev/sda5 1620 121601 963755383+ fd Linux raid autodetect
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System /dev/sdb1 1 37 297171 fd Linux raid autodetect /dev/sdb2 38 1132 8795587+ fd Linux raid autodetect /dev/sdb3 1133 1619 3911827+ fd Linux raid autodetect /dev/sdb4 1620 121601 963755415 5 Extended /dev/sdb5 1620 121601 963755383+ fd Linux raid autodetect
2. Prepare for boot
The system should be set up to boot from multiple devices, so that if one disk fails, the system can boot from another disk.
On Intel hardware, there are two common boot loaders, grub and lilo. Both grub and lilo can only boot off a raid1. they cannot boot off any other software raid device type. The reason they can boot off the raid1 is that hey see the raid1 as a normal disk, they only then use one of the dishs when booting. The boot stage only involves loading the kernel with a initrd image, so not much data is needed for this. The kernel, the initrd and other boot files can be put in a small /boot partition. We recommend something like 200 MB on an ext3 raid1.
Make the raid1 and ext3 filesystem:
mdadm --create /dev/md0 --chunk=256 -R -l 1 -n 2 /dev/sda1 /dev/sdb1 mkfs -t ext3 -f /dev/md0
Make each of the disks bootable by lilo:
lilo -b /dev/sda /etc/lilo.conf1
lilo -b /dev/sdb /etc/lilo.conf2
Make each of the disks bootable by grub
(to be described)
3. The root file system
The root file system can be on another raid tah the /boot partition. We recommend an raid10,f2, as the root file system will mostly be reads, and the raid10,f2 raid type is the fastest for reads, while also sufficient fast for writes. Other relevant raid types would be raid10,o2 or raid1.
It is recommended to use the udev file system, as this runs in RAM, and you thus can avoid a number of read and writes to disk.
It is recommended that all file systems are mounted with the noatime option, this avoids writing to the filesystem inodes every time a file has been read or written.
Make the raid10,f2 and ext3 filesystem:
mdadm --create /dev/md1 --chunk=256 -R -l 10 -n 2 -p f2 /dev/sda2 /dev/sdb2 mkfs -t ext3 -f /dev/md1
4. The swap file system
If a disk fails, where processes are swapped to, then all these processes fail. This may be vital processes for the system, or vital jobs on the system. You can prevent the failing of the processes by having the swap partitions on a raid. The swap area needed is normally relatively small compared to the overall disk space available, so we recommend the faster raid types over the more space economic. The raid10,f2 type seems to be the fastest here, other relevant raid types could be raid10,o2 or raid1.
Given that you have created a raid array, you can just make the swap partition directly on it:
mdadm --create /dev/md2 --chunk=256 -R -l 10 -n 2 -p f2 /dev/sda3 /dev/sdb3 sfdisk -c /dev/md 2 82 mkswap /dev/md2
Maybe something on /var and /tmp could go here.
5. The rest of the file systems.
Other file systems can also be protected against one failing disk. Which technique to recommend depends on your purpose with the disk space. You may mix the different raid types if you have different types of use on the same server, eg a data base and servicing of large files from the same server. (This is one of the advantages of software raid over hardware raid: you may have different types of raids on
a disk with a software raid, where a hardware raid only may take one type for the whole disk.)
Is disk capacity the main priority, and you have more than 2 drives, then raid5 is recommended. Raid5 only uses 1 drive for securing the data, while raid1 and raid10 use at least half the capacity.
For example with 4 drives, raid5 provides 75 % of the total disk space as usable, while raid1 and raid10 at most (dependent on the number of copies) give a 50 % usability of the disk space. This becomes even better for raid5 with more disks, with 10 disks you only use 10 % for security.
Is speed your main priority, then raid10,f2 raid10,o2 or raid1 would give you
most speed during normal operation. This even works if you only have 2 drives.
Is speed with a failed disk a concern, then raid10,o2 could be the choice, as raid10,f2 is somewhat slower in operation, when a disk has failed.
Examples:
mdadm --create /dev/md3 --chunk=256 -R -l 10 -n 2 -p f2 /dev/sda5 /dev/sdb5 mdadm --create /dev/md3 --chunk=256 -R -l 10 -n 2 -p o2 /dev/sd[ab]5 mdadm --create /dev/md3 --chunk=256 -R -l 5 -n 4 /dev/sd[abcd]5
6. /etc/mdadm.conf
Something here on /etc/mdadm.conf. What would be safe, allowing a system to boot even if a disk has crashed?
7. Recommendation for the setup of larger servers.
Given a larger server setup, with more disks, it is possible to survive more than one disk crash. The raid6 array type can be used
to be able to survive 2 disk crashes, at the expense of the space of 2 disks. The /boot, root and swap partitions can be set up with more disks, eg a /boot partition made up from a raid1 of 3 disks, and root and swap partitons made up from raid10,f3 arrays. Given that raid6 cannot survive more than the chashes of 2 disks, the system disks need not be prepared for more than 2 craches either, and you can use the rest of the disk IO capacity to speed up the system.
Keld Jørn Simonsen said: (by the date of Sat, 2 Feb 2008 20:41:31 +0100)
Quoted 2 lines
This is intended for the linux raid howto. Please give comments. It is not fully ready /keld
very nice. do you intend to put it on http://linux-raid.osdl.org/
As wiki, it will be much easier for our community to fix errors and add updates.
Signature · 5 lines
Janek Kozicki | - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 6 lines · Janek Kozicki
Keld Jørn Simonsen said: (by the date of Sat, 2 Feb 2008 20:41:31 +0100)
Quoted 2 lines
This is intended for the linux raid howto. Please give comments. It is not fully ready /keld
very nice. do you intend to put it on http://linux-raid.osdl.org/
Yes, that is the intention.
Quoted 2 lines
As wiki, it will be much easier for our community to fix errors and add updates.
Agreed. But I will not put it up before I am sure it is reasonably flawless, ie. it will at least work. I found myself a few errors already.
best regards
keld
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 64 lines · Keld Jørn Simonsen
This is intended for the linux raid howto. Please give comments. It is not fully ready /keld
Howto prepare for a failing disk
The following will describe how to prepare a system to survive
if one disk fails. This can be important for a server which is
intended to always run. The description is mostly aimed at
small servers, but it can also be used for
work stations to protect it for not losing data, and be running even if a disk fails. Some recommendations on larger server setup is given at the end of the howto.This requires some extra hardware, especially disks, and the description will also touch how to mak the most out of the disks, be it in terms of available disk space, or input/output speed.
1. Creating of partitions
We recommend creating partitions for /boot, root, swap and other file systems. This can be done by fdisk, parted or maybe a graphical interface like the Mandriva/PClinuxos harddrake2. It is recommended to use drives with equal sizes and performance characteristics.
If we are using the 2 drives sda and sdb, then sfdisk may be used to make all the partitions into raid partitions:
sfdisk -c
/dev/sda1 fd
sfdisk -c/dev/sda2 fd
sfdisk -c/dev/sda3 fd
sfdisk -c/dev/sda5 fd
sfdisk -c/dev/sdb1 fd
sfdisk -c/dev/sdb2 fd
sfdisk -c/dev/sdb3 fd
sfdisk -c/dev/sdb5 fdUsing:
fdisk -l
/dev/sda/dev/sdbThe partition layout could then look like this:
Disk
/dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytesDevice Boot Start End Blocks Id System /dev/sda1 1 37 297171 fd Linux raid autodetect /dev/sda2 38 1132 8795587+ fd Linux raid autodetect /dev/sda3 1133 1619 3911827+ fd Linux raid autodetect /dev/sda4 1620 121601 963755415 5 Extended /dev/sda5 1620 121601 963755383+ fd Linux raid autodetectDisk
/dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytesDevice Boot Start End Blocks Id System /dev/sdb1 1 37 297171 fd Linux raid autodetect /dev/sdb2 38 1132 8795587+ fd Linux raid autodetect /dev/sdb3 1133 1619 3911827+ fd Linux raid autodetect /dev/sdb4 1620 121601 963755415 5 Extended /dev/sdb5 1620 121601 963755383+ fd Linux raid autodetect
Quoted 6 lines
2. Prepare for boot
The system should be set up to boot from multiple devices, so that if one disk fails, the system can boot from another disk.
NOTE: if the first hd fails some BIOS will consider the 2nd as hdc, while other will use the physical location. SATA drives may also be "moved," and udev may apply interesting and unintuitive names for the devices in these cases. Use of the "UID" notation to identify raid array members is therefore desirable.
Quoted 19 lines
On Intel hardware, there are two common boot loaders, grub and lilo. Both grub and lilo can only boot off a raid1. they cannot boot off any other software raid device type. The reason they can boot off the raid1 is that hey see the raid1 as a normal disk, they only then use one of the dishs when booting. The boot stage only involves loading the kernel with a initrd image, so not much data is needed for this. The kernel, the initrd and other boot files can be put in a small /boot partition. We recommend something like 200 MB on an ext3 raid1.
Make the raid1 and ext3 filesystem:
mdadm --create /dev/md0 --chunk=256 -R -l 1 -n 2 /dev/sda1 /dev/sdb1 mkfs -t ext3 -f /dev/md0Make each of the disks bootable by lilo:
lilo -b
/dev/sda/etc/lilo.conf1
lilo -b/dev/sdb/etc/lilo.conf2
Quoted 8 lines
Make each of the disks bootable by grub
(to be described)
3. The root file system
The root file system can be on another raid tah the /boot partition.
TYPO: -------------------------------------------------------------------------^^^
Quoted 3 lines
We recommend an raid10,f2, as the root file system will mostly be reads, and the raid10,f2 raid type is the fastest for reads, while also sufficient
TYPO: s/sufficient/sufficiently/
Quoted 21 lines
fast for writes. Other relevant raid types would be raid10,o2 or raid1.
It is recommended to use the udev file system, as this runs in RAM, and you thus can avoid a number of read and writes to disk.
It is recommended that all file systems are mounted with the noatime option, this avoids writing to the filesystem inodes every time a file has been read or written.
Make the raid10,f2 and ext3 filesystem:
mdadm --create /dev/md1 --chunk=256 -R -l 10 -n 2 -p f2 /dev/sda2 /dev/sdb2 mkfs -t ext3 -f /dev/md14. The swap file system
If a disk fails, where processes are swapped to, then all these processes fail.
This may be vital processes for the system, or vital jobs on the system. You can prevent the failing of the processes by having the swap partitions on a raid. The swap area needed is normally relatively small compared to the overall disk space available,
so we recommend the faster raid types over the more space economic. The raid10,f2
type seems to be the fastest here, other relevant raid types could be raid10,o2 or raid1.
Quoted 8 lines
Given that you have created a raid array, you can just make the swap partition directly on it:
mdadm --create /dev/md2 --chunk=256 -R -l 10 -n 2 -p f2 /dev/sda3 /dev/sdb3 sfdisk -c /dev/md 2 82 mkswap /dev/md2
WARNING: some "recovery" CDs will not use raid10 as swap. This may be a problem on small memory systems, and the swap may need to be started and enabled manually.
Quoted 30 lines
Maybe something on /var and /tmp could go here.
5. The rest of the file systems.
Other file systems can also be protected against one failing disk. Which technique to recommend depends on your purpose with the disk space. You may mix the different raid types if you have different types of use on the same server, eg a data base and servicing of large files from the same server. (This is one of the advantages of software raid over hardware raid: you may have different types of raids on
a disk with a software raid, where a hardware raid only may take one type for the whole disk.)Is disk capacity the main priority, and you have more than 2 drives, then raid5 is recommended. Raid5 only uses 1 drive for securing the data, while raid1 and raid10 use at least half the capacity.
For example with 4 drives, raid5 provides 75 % of the total disk space as usable, while raid1 and raid10 at most (dependent on the number of copies) give a 50 % usability of the disk space. This becomes even better for raid5 with more disks, with 10 disks you only use 10 % for security.Is speed your main priority, then raid10,f2 raid10,o2 or raid1 would give you
most speed during normal operation. This even works if you only have 2 drives.Is speed with a failed disk a concern, then raid10,o2 could be the choice, as raid10,f2 is somewhat slower in operation, when a disk has failed.
Examples:
Quoted 9 lines
mdadm --create /dev/md3 --chunk=256 -R -l 10 -n 2 -p f2 /dev/sda5 /dev/sdb5 mdadm --create /dev/md3 --chunk=256 -R -l 10 -n 2 -p o2 /dev/sd[ab]5 mdadm --create /dev/md3 --chunk=256 -R -l 5 -n 4 /dev/sd[abcd]56.
/etc/mdadm.confSomething here on
/etc/mdadm.conf. What would be safe, allowing a system to boot even if a disk has crashed?
Recommend PARTITIONS by used
Quoted 7 lines
7. Recommendation for the setup of larger servers.
Given a larger server setup, with more disks, it is possible to
survive more than one disk crash. The raid6 array type can be used
to be able to survive 2 disk crashes, at the expense of the space of 2 disks.
The /boot, root and swap partitions can be set up with more disks, eg a /boot partition made up from a raid1 of 3 disks, and root and swap partitons made up from raid10,f3 arrays. Given that raid6 cannot survive more than the chashes
TYPO: s/chashes/crashes/ and "failure" would be better
Quoted 2 lines
of 2 disks, the system disks need not be prepared for more than 2 craches
TYPO: s/craches/crashes/ or "disk failures"
Quoted 2 lines
either, and you can use the rest of the disk IO capacity to speed up the system.
Signature · 10 lines
Bill Davidsen <[email protected]> "Woe unto the statesman who makes war without a reason that will still be valid when the war is over..." Otto von Bismark - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 6 lines · Bill Davidsen
Quoted 5 lines · Keld Jørn Simonsen
This is intended for the linux raid howto. Please give comments. It is not fully ready /keld
Howto prepare for a failing disk
Quoted 7 lines
Quoted 5 lines
6.
/etc/mdadm.confSomething here on
/etc/mdadm.conf. What would be safe, allowing a system to boot even if a disk has crashed?Recommend PARTITIONS by used
Thanks Bill for your suggestions, which I have incorporated in the text.
However, I do not understand what to do with the remark above. Please explain.
Best regards
keld
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 15 lines · Keld Jørn Simonsen
Quoted 13 lines · Bill Davidsen
Quoted 11 lines · Keld Jørn Simonsen
This is intended for the linux raid howto. Please give comments. It is not fully ready /keld
Howto prepare for a failing disk
6.
/etc/mdadm.confSomething here on
/etc/mdadm.conf. What would be safe, allowing a system to boot even if a disk has crashed?
Quoted 8 lines
Quoted 2 lines
Recommend PARTITIONS by used
Thanks Bill for your suggestions, which I have incorporated in the text.
However, I do not understand what to do with the remark above. Please explain.
The mdadm.conf file should contain the "DEVICE partitions" statement to identify all possible partitions regardless of name changes. See "man mdadm.conf" for more discussion. This protects against udev doing something innovative in device naming.
Signature · 10 lines
Bill Davidsen <[email protected]> "Woe unto the statesman who makes war without a reason that will still be valid when the war is over..." Otto von Bismark - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 8 lines · Keld Jørn Simonsen
Quoted 6 lines · Janek Kozicki
Keld Jørn Simonsen said: (by the date of Sat, 2 Feb 2008 20:41:31 +0100)
Quoted 2 lines
This is intended for the linux raid howto. Please give comments. It is not fully ready /keld
very nice. do you intend to put it on http://linux-raid.osdl.org/
Quoted 7 lines
Yes, that is the intention.
Quoted 2 lines
As wiki, it will be much easier for our community to fix errors and add updates.
Agreed. But I will not put it up before I am sure it is reasonably flawless, ie. it will at least work. I found myself a few errors already.
I have now put up the draft, at
http://linux-raid.osdl.org/index.php/Preventing_against_a_failing_disk
I made a number of corrections to the initial draft. Thanks to all who helped.
Please review and make corections.
Best regards
keld
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 4 lines · Keld Jørn Simonsen
Make each of the disks bootable by lilo:
lilo -b
/dev/sda/etc/lilo.conf1
lilo -b/dev/sdb/etc/lilo.conf2
There should be no need for that.
to achieve the above effect with lilo you use
raid-extra-boot=mbr-only
in lilo.conf
Quoted 1 line
Make each of the disks bootable by grub
install grub with the command
grub-install /dev/md0
L.
Signature · 10 lines
Luca Berra -- [email protected] Communication Media & Services S.r.l. /"\ \ / ASCII RIBBON CAMPAIGN X AGAINST HTML MAIL / \ - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 5 lines · Keld Jørn Simonsen
Make each of the disks bootable by grub
(to be described)
It would probably be good to show how to use grub shell's install command. It's the most flexible way and give the most (or rather total) control. I could write some examples.
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Purpose of Document? (was Re: draft howto on making raids for surviving a disk crash)
In reply to Luca BerraI read through the document, and I've signed up for a Wiki account so I can edit it.
One of the things I wanted to do was correct the title. I see that there are *three* different Wiki pages about how to build a system that boots from RAID. None of them are complete yet.
So, what is the purpose of this page? I think the purpose is "a complete description of how to use RAID to build a system that not only boots from RAID but is robust against other hazards such as file system corruption."
Signature · 3 lines
Moshe Yudkowsky * [email protected] * www.pobox.com/~moshe "If you pay peanuts, you get monkeys." Edward Yourdon, _The Decline and Fall of the American Progammer_
Re: Purpose of Document? (was Re: draft howto on making raids for surviving a disk crash)
Quoted 11 lines · Moshe Yudkowsky
I read through the document, and I've signed up for a Wiki account so I can edit it.
One of the things I wanted to do was correct the title. I see that there are *three* different Wiki pages about how to build a system that boots from RAID. None of them are complete yet.
So, what is the purpose of this page? I think the purpose is "a complete description of how to use RAID to build a system that not only boots from RAID but is robust against other hazards such as file system corruption."
You are right about that there are more than one wiki page addressing very related issues. I also considered whether there was a need for the new page, and discussed it with David.
And yes, my idea was to make a howto on building a system that can survive a disk crash. A simple system that can also work for a workstation. In fact the main audience is possibly here.
so my focus is: survive a failing disk, and keep it simple.
Best regards
Keld
Quoted 5 lines · Luca Berra
Quoted 4 lines · Keld Jørn Simonsen
Make each of the disks bootable by lilo:
lilo -b
/dev/sda/etc/lilo.conf1
lilo -b/dev/sdb/etc/lilo.conf2
Quoted 8 lines
There should be no need for that.
to achieve the above effect with lilo you use
raid-extra-boot=mbr-only
in lilo.confQuoted 1 line
Make each of the disks bootable by grub
install grub with the command
grub-install/dev/md0
I have already changed the text on the wiki. Still I am not convinced it is the best advice that is described.
best regards
keld
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 11 lines · Keld Jørn Simonsen
Quoted 10 lines · Luca Berra
Quoted 4 lines · Keld Jørn Simonsen
Make each of the disks bootable by lilo:
lilo -b
/dev/sda/etc/lilo.conf1
lilo -b/dev/sdb/etc/lilo.conf2There should be no need for that.
to achieve the above effect with lilo you use
raid-extra-boot=mbr-only
in lilo.conf
Quoted 6 lines
Quoted 3 lines
Quoted 1 line
Make each of the disks bootable by grub
install grub with the command
grub-install/dev/md0I have already changed the text on the wiki. Still I am not convinced it is the best advice that is described.
lilo -b /dev/md0 (without a raid-extra-boot line in lilo.conf) will install lilo on the boot sector of the partitions containing /dev/md0 (and it will break with 1.1 sb)
for grub, do you have any doubt about the grub-install script not working correctly?
L.
Signature · 10 lines
Luca Berra -- [email protected] Communication Media & Services S.r.l. /"\ \ / ASCII RIBBON CAMPAIGN X AGAINST HTML MAIL / \ - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 16 lines · Luca Berra
Quoted 15 lines · Keld Jørn Simonsen
Quoted 13 lines · Luca Berra
Quoted 4 lines · Keld Jørn Simonsen
Make each of the disks bootable by lilo:
lilo -b
/dev/sda/etc/lilo.conf1
lilo -b/dev/sdb/etc/lilo.conf2There should be no need for that.
to achieve the above effect with lilo you use
raid-extra-boot=mbr-only
in lilo.confQuoted 1 line
Make each of the disks bootable by grub
install grub with the command
grub-install/dev/md0
Quoted 6 lines
Quoted 3 lines
I have already changed the text on the wiki. Still I am not convinced it is the best advice that is described.
lilo -b
/dev/md0(without a raid-extra-boot line in lilo.conf) will install lilo on the boot sector of the partitions containing/dev/md0(and it will break with 1.1 sb)
I think 1.1 Superblocks will break all boots with lilo and grub, but 1.1 superblocks are not standard in current distributions.
When would 1.1 superblocks be a problem, for new users of raid?
Quoted 2 lines
for grub, do you have any doubt about the grub-install script not working correctly?
No, I think the grub description is OK. I only meant the lilo description.
Best regards
keld
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html