Comment 13 for bug 568720

Same problem on Lucid server but I think I caused it

The boot was clean until I installed 2tb drives and messed up (I think).

I recently set up a Dell Precision 390 (no floppy) with two WD 80Gb disks with three partitions (swap root and userspace) in raid 1 under MD

Everything was fine until tried to upgrade the disks to Samsung 2TB
I cloned the a and b 80GB disks using ddrescue to the new 2TB ones and physically swapped them in (partitions are currently as per the original 80Gb i.e. only using partitions up to 80 of the 2000 Gb available)

On boot there was a serious hiccup re file system that I couldn't capture but it was prompting 'I to ignore' or 'F to fix' so I opted for F and the machine rebooted and came up.

On checking the system after reboot I noticed that mdadm was reporting the sd devices in reverse order to what they were
eg. md1 : active raid1 sdb2[0] sda2[1] when it used to be md1 : active raid1 sda2[0] sdb2[1]

I figured I had mixed up the two devices and decided to simply swap them around again and cross my fingers.

Sure enough the machine hiccuped again on reboot with the same (am assuming) hiccup and with the same options for I or F
I used F again but this time I had to reboot before several times before is sorted itself out.

Machine up again and running and reporting all but one of the MD devices as it used to.
Using mdadm -- manage fail and add I dropped the b drive paritions completely rebooted the machine and it started a rebuild on the two 'normal' partitions automatically when they finished I simply added the third one manually and all appears right now.

Somewhere in all of that the machine started giving 'error: fd0' + 'invalid environment' while booting but I wasn't too bothered because I thought it would go when I got the raids sorted out but it now appears to be a permanent feature though it only flashes up and causes minimal (if any) delay. As the machine is normally headless it wont be noticed but I would like to know if the error could turn critical at some point (before I start using it in earnest as a file server)?

Based on this post
I checked the bios diskette setting which was set to 'USB floppy drives are enabled' and changed it to 'off' but error message still appearing.
I also turned off SMART reporting and the error persists

Hope this helps - if I there are logs that would be of use let me know where I will post them or filtered versions..