Well, not really solved, but avoided.
Even with Xpressrecovery2, the mobo's manual says that PATA drives will
always be used first, no matter what the BIOS says. In addition, I had
to reinstall Windows for other reasons, and a lot of things refused to
I took the PATA disk out of the computer and put it back in the remote
USB case. That makes it /dev/sdb and the SATA drive /dev/sda every
time. The Windows issues disappeared immediately, and the mountlist is
as it should be.
On Fri, 4 Jun 2010 20:01:19 +1000
Doug Laidlaw <laidlaws@...> wrote:
> On Fri, 4 Jun 2010 09:54:17 +0200
> Bruno Cornec <Bruno.Cornec@...> wrote:
> > Doug Laidlaw said on Fri, Jun 04, 2010 at 10:30:48AM +1000:
> > > To be fair, the problem seems to be bigger than Mondo. The
> > > installers for Suse 11.1 and now Ubuntu Lucid both put the PATA
> > > drive first. The simplest solution would probably be to put the
> > > PATA drive
> > Anything you could modify in the BIOS to make drive seen in the
> > order you want ?
> > Bruno.
> Yes, I have the BIOS set to make the SATA drive No. 1. I
> recently upgraded my BIOS, and I have just checked that it was
> kept that way. PATA is Channel 0, SATA is Channel 2, and Channel 3 is
> empty. (It may be the spare SATA socket.) Windows (XP) honours that;
> and Mandriva seems to, as well. But otherwise, it seems to be
> ignored. I seem to recall reading somewhere that Mondo disregards the
> BIOS; that may be completely wrong.
> To me, intuitively, it seems absolutely strange that SATA is the newer
> technology, yet my SATA is Channel 2 in the BIOS. In other words, it
> seems to be in second priority by design. As supplied, the BIOS did
> not support booting from USB, so I suspect that the mobo was then
> "new" in the technological sense, although RAID setup is described in
> its manual. The release of Mandriva back then did not support its
> onboard NIC, and I used a card.
> The other option is to put the OS on the PATA, but by now it is rather
> long in the tooth. It used to be possible to swap drives in GRUB.
> With GRUB 2 on the horizon, I would rather not fiddle there. And it
> would probably not suit Windows.
> Because I am a home user, I have the time to re-type the mountlist if
> I have to, but I would have expected the industry to find this
> problem as well. I am inclined to experiment, then put back what I
> had, rather than disaster recovery.