XPost: alt.os.linux   
   From: robin_listas@es.invalid   
      
   On 19/12/2018 13.54, Anton Shepelev wrote:   
   > Carlos E.R. to Anton Shepelev:   
   >   
   >>> Have you any idea why it started access the floppy drive   
   >>> and how to restore the normal boot process?   
   >>   
   >> Do you actually have a floppy drive on the machine?   
   >   
   > The server is not mine.  After it stopped booting because of   
   > the floppy error, the administrator removed the floppy from   
   > the virtual machine, but the error persisted.  Then he added   
   > it back.   
      
   Ah, virtual machine.   
      
      
   >> If you have, does it work in Linux?   
   >   
   > How can I test it without booting the machine -- using some   
   > LiveCD?   
   >   
   >> If you don't, make sure the BIOS doesn't list it.   
   >   
   > In the Boot menu I have:   
   >   
   >    - Removable Devices   
   >       Legacy Floppy Drives   
   >   
   > I am not sure it counts as listing that specific floppy.   
      
   Yes, that's the entry I meant. If it is there, and old bug in some SUSE   
   versions make the boot process to hang. If I recall correctly, it hangs   
   if the bios says in that entry above that there is a floppy drive, but   
   there is no such drive.   
      
   In a virtual machine, unless you have a reason for having floppy drive,   
   I would disable it in the virtual hardware definition and then in the   
   bios screen.   
      
   Otherwise, I might try to tell the virtual machine to use a floppy   
   image, ie, a file in the host machine that is a "dd" copy of a real   
   floppy. The emulation makes the guest think then that there is a floppy   
   drive with a floppy inside.   
      
   But I see no reason to do that :-?   
      
      
   > After the administrator disabled the floppy controller in   
   > BIOS, the boot process hung at:   
   >   
   >    sd 30:0:0:0: [sda] Assuming drive cache: write through   
   >    sd 30:0:1:0: [sdb] Assuming drive cache: write through   
   >   
   > We are still waiting.   
      
   Oh?   
      
   Probably there is some problem with the disks, and the guest tries to   
   boot instead from the floppy it thinks is there but is not, as an   
   alternative. So this would be the real problem, not the floppy.   
      
   I will read your other posts now, see if there are more clues. [...] No,   
   no clues.   
      
   What type of hard disk is the host virtualization emulating? SCSI, SATA,   
   PATA...?  Try another type.   
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)