Re: strange boot behavior

["Douglas A. Tutty" <dtutty@porchlight.ca>]

On Sun, Jun 08, 2008 at 10:41:43AM -0400, Philip Bernstein wrote:
 
>   After making any kind of changes to the drives, like setting up 
> virtualbox, unmount the ata drives and remount them, add filesystems to 
> the ata drives, or even updating the kernel, etc.  On the next reboot 
> the drives are mounted and labeled incorrectly. Ex:
> Sata drive
> # /dev/sda4
> # /dev/sda1
> # /dev/sda3
> # /dev/sda2
> 
> Ata drives
> Wrong or incorrect filesystem or no spcial file /dev/xxx (this is not 
> the exact msg but you get the point)
> 
> The system boots but of course the additional drives are not there.  Now 
> in order to fix this, I have to reboot the system 2 more times and then 
> all the drives are seen and labeled correctly.  So after making any of 
> the above changes, I have to reboot my system 3 times for it to come up 
> properly.  Anyone can explain?  Need more info?
> The system is and AMD64 bit running Hardy 8.04 with all the latest updates.

What is Hardy 8.04?  

Is this a device renaming issue that has been discussed so many times on
this list (use LABEL=)?

Doug.