Critical Dapper bug: RAID1, reconnect secondary drive, no attempt made to resolve drives
Bug #58892 reported by
Timothy Miller
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I have two identical drives that I have configured as RAID1. I set up software RAID1 on them and installed Dapper.
After installing, I shut down and disconnected power from the seconday disk. Everything booted just fine.
I shut down again and reconnected the secondary drive. When I booted up, absolutely nothing was done to resolve the two drives. Clearly, they would be in an inconsistent state. Moreover, if the new disk connected were blank, that would be an even bigger problem. This is a critical bug, because this makes it impossible to restore a RAID1 array after a drive failure.
To post a comment you must log in.
I would suggest that, after logging in, the user should see a dialog that reports that it thinks a new drive has been added that looks like one they'd like to add to the array and ask them if they want to hot-add it.