I have the same setup on one of the drives in my ich10 raid. Looking into it, it seems to be a bios recovery feature for gigabyte motherboards, which apparently uses the ata HPA, which suggested bug#219393, which says to add "libata.ignore_hpa=0" to the kernel command line, which fixes the problem for me.
(for reference, my motherboard is a ga-ex58-ud3r, and last 1k of the affected drive looks like this (offsets from beginning of intel raid signature): 00108400: 2447 4146 5210 4108 0000 0000 0000 0000 $GAFR.A......... 00108410: 0000 0000 0000 0000 0000 3f5b 381d 0000 ..........?[8... 00108420: 0000 0008 0000 0000 0000 0000 0000 0000 ................ ..... 00108500: 2231 322f 3330 2f32 3030 382d 5835 382d "12/30/2008-X58- 00108510: 4943 4831 302d 3741 3839 5147 3041 432d ICH10-7A89QG0AC- 00108520: 001f d000 00af a95f 4445 4347 5f03 0010 ......._DECG_... 00108530: 0000 0000 0000 0000 0000 0000 0000 0000 ................ where 3f 5b 38 1d = 0x1d385b3f is the sector 2 sectors after the isw raid metadata) -- intel isw raid metadata at odd offset https://bugs.launchpad.net/bugs/372170 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs -- universe-bugs mailing list universe-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/universe-bugs