severity 495909 normal reassign 495909 grub forcemerge 495909 496035 thanks
On Thu, Aug 21, 2008 at 11:57:06AM +0200, martin f krafft wrote: > piper:/boot% sudo update-grub > Searching for GRUB installation directory ... found: /boot/grub > error: Unsupported RAID level: 10 > error: Unsupported RAID level: 10 > error: Unsupported RAID level: 10 > error: Unsupported RAID level: 10 > Searching for default file ... found: /boot/grub/default > Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst > Searching for splash image ... none found, skipping ... > Found kernel: /vmlinuz-2.6.26-1-amd64 > Found kernel: /vmlinuz-2.6.25-2-amd64 > Found kernel: /memtest86+.bin > Updating /boot/grub/menu.lst ... done > > > Well, it never supported RAID, so why should it suddenly report an > error? And if it now supports RAID, why not RAID 10? Argueably, GRUB Legacy shouldn't report any of this. They're real errors, but only make sense for GRUB 2. This stems from grub-probe being a bit biased towards GRUB 2. I think we could just fix it by sending its output to /dev/null. (anyway, expect raid10 support to be included soon) -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
