[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#681681: marked as done (installation-reports: grub-install doesn't install grub to all drives in RAID5 array during install)

Your message dated Sat, 31 Aug 2013 00:24:06 +0200
with message-id <201308310024.32985.holger@layer-acht.org>
and subject line dealing with old installation-reports
has caused the Debian Bug report #681681,
regarding installation-reports: grub-install doesn't install grub to all drives in RAID5 array during install
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
681681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681681
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: installation-reports
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
I recently rebuilt my former home server as a test desktop machine using 3 x 500G SATA drives I had lying around. This required me to install a cheap PCI SATA controller to get enough SATA ports 
to handle the drives. The DVD writer is an IDE unit.
I'd heard that it was possible to boot from a RAID5 array and I wanted to try that out. After a couple of days of trying to get the system to boot after the install, I realized the problem was that GRUB wasn't installed on all the drives and the system was trying to boot from a drive without 
GRUB on it.
* What exactly did you do (or not do) that was effective (or ineffective)? Using the NetInst CD to boot into rescue mode allowed me open a shell in the /dev/md/0 
environment and grub-install to the other two drives.

   * What was the outcome of this action?
As expected, with grub installed on all three drives, I could boot into a RAID5 array. 


*** End of the template - remove these lines ***


-- Package-specific info:

Boot method: CD
Image version: current NetInst for Wheezy as of July 14
Date: <Date and time of the install>
Machine: old ASUS Athlon 64 motherboard with an add-in SATA controller to give enough SATA ports for a RAID5 array 
Partitions: <df -Tl will do; the raw partition table is preferred>


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:           [ ]
Detect network card:    [ ]
Configure network:      [ ]
Detect CD:              [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:    [ ]
Detect hard drives:     [ ]
Partition hard drives:  [ ]
Install base system:    [ ]
Install tasks:          [ ]
Install boot loader:    [X]
Overall install:        [ ]

Comments/Problems:
I note that the installer doesn't give you the option to partition a RAID array, even though this is a legal and perfectly reasonable thing to do. Without this capability I have to set up the RAID array before starting the installer if I want a partitioned 
array.
Also, I'm submitting this report from my regular workstation, so I've removed 
the non-relevant parts of the report that would normally be below.

--

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to submit@bugs.debian.org.

--- End Message ---
--- Begin Message --- 
Hi,

thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


cheers,
        Holger

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: