Troubleshooting Diskette drive (FDD) issues

Resolving The Problem

1. To begin troubleshooting, check the following top issues. If your issue is listed, select the link, otherwise proceed to step 2.
   
   

   errors

   
   

   	"Diskette Drive 0 Failure" (or 1)
   	"Error selecting drive"
   	"Invalid drive specification"
   	"Invalid media type"
   	"Not a valid block device", seen as /dev/sdx under Linux (Blade)
   	"Not ready reading drive A" (or B)
   	"Non-system disk or disk error"

   
   

   hangs

   
   

   	Hang at checkpoint 'ad' while rebooting with USB FDD
   	BladeCenter FDD activity LED stays on, or system bypasses FDD
   	Diskette drive LED stays on continuously

   
   

   not detected / unable to access

   
   

   	Diskette drive is not correctly identified in the F1 setup
   	Non-IBM USB FDD not recognized during Windows XP install
   	Unable to access USB FDD under SUSE LINUX
   	Preventive maintenance

   
   

2. Check to see if the diskette you are trying to use works in another system's diskette drive. If the diskette does not work properly in either computer, replace the diskette. However, if the diskette works OK in one drive, but not the other, then cleaning the drive may be required. Follow the cleaning kit manufacturer's directions (See preventive maintenance, above). If the system is down, a bootable diskette is another quick way to see if the system can read any diskettes. A PC Doctor diagnostics diskette can be used for this purpose.
   
   Note: The diskette media may be faulty or damaged. Reused diskettes may degrade with excessive usage, so use good quality high density diskettes.
   
   
3. Try formatting or writing to a diskette in the drive, to test if the drive recognizes the disk, and can write to the drive correctly.
   
   
4. Check settings in the system's F1 CMOS setup utility to verify the drive is recognized in the Devices section, and is shown in the Startup Sequence section. If the diskette drive is identified incorrectly in the setup utility, you will probably be unable to boot to or format a diskette.
   
   
   1. Power down the system, and press F1 at bootup to enter the Setup/Configuration utility program.
   2. Once in the setup screens, check to make sure that the diskette drive is recognized correctly. Check that the drive settings are correct and correspond with the correct drive type, for example, 3.5 inch, 1.44MB is the current standard for diskette drive 0 (or diskette drive A).
   3. Check the security section of setup and remove the supervisor password if one has been set. A password may have been enabled on an Intel Pentium or PCI system.
      
      
5. Check the cables. If the F1 CMOS setup utility settings have been checked and the settings are correct, the problem may be a poor connection between the diskette drive and the system board. The cable that goes from the back of the diskette drive to the system board or controller card may be bad, be cut, or the connection may be loose.
   
   

   View FDD installation and removal movies for your system

   
   
   1. Power down the system.
   2. On the back of the diskette drive there is a power cable connection and the data cable connection. The flat, gray ribbon cable is the data cable, this needs to be reseated first. Firmly pull the cable straight off the back of the diskette drive, and press it firmly back in place the same way it was removed. Make sure to pull the connectors, not the cable.
   3. Reseat the power cable to the back of the drive (pull the connector, not the cable) to make sure it is seated firmly and correctly.
   4. Next, follow the data cable down to where it connects to the system board, and firmly pull the cable straight off and push it back on the same way that it was removed.
   5. Power up the system and try to boot to a diskette, and format a diskette as directed in the tests above. If you are still unable to do these things, run hardware diagnostics on the diskette drive. The diskette drive may be defective and need to be replaced.
      
      
6. Check for hardware conflicts. There may be a conflict within the system with some newly added hardware or software. If any hardware has recently been added to the system, try removing these items from the system one at a time. If you are experiencing diskette drive problems after adding a tape backup unit or CD-ROM or CD-RW drive, try using the additional diskette drive cable that came with the device. Instructions should be included with the option.
   1. Each time an item is removed, try to boot to a diskette and format a diskette.
   2. If the diskette drive works, it is possible the hardware that was added may be causing a conflict with the diskette drive.
   3. Reconfigure the new hardware, and try replacing it to see if the problem persists.
      
      
7. Run hardware diagnostics. The diskette drive may be faulty or damaged.
   
   

   Download the latest diagnostics for your system

   
   
8. If these steps have not solved your problem:
   Refer to your system's Hardware Maintenance Manual, or refer to "Need more help?"

Back to top

To gain the best long-term reliability from a diskette drive, you should utilize only high quality media, keep the system in a clean environment, and keep any foreign objects out of the diskette drive. The following is a checklist of processes to implement to prevent premature diskette drive failure.

• Check all diskettes for physical damage and ensure the diskette shutter moves freely prior to inserting into the diskette drive.
  
  
• Use the diskette drive on a regular basis. Frequent use cleans the recording head surfaces of dust or fiber particles that may adhere to the heads via minute static electrical charges. Frequent use also minimizes the risk of contaminants damaging the diskette, which could result in read/write errors.
  
  
• If the drive has not been used for an extended period, test the drive first with an expendable diskette, and verify that it can be read from, and written to prior to inserting a critical data diskette.

Warning: When using a FDD cleaning kit, be sure to follow the manufacturer's directions carefully. When using kits with isopropyl alcohol, be careful not to use excess amounts of the solution. Excess solution may accumulate on the drive's heads, resulting in the degradation of the diskette's magnetic recording surface, and possibly transfer to the next diskette inserted in the drive. This can cause residue to be left on the heads of the drive which can further compound problems.

Back to top

Both Red Hat Linux and SUSE LINUX see the diskette drive as /dev/sdx (where x is the last SCSI device in the line) instead of /dev/fd0. When you try to mount the drive as fd0, the Linux operating system does not recognize the device, and gives the error "not a valid block device".

Note: When running Linux, you must unmount the diskette drive before changing ownership of the media tray.

For SUSE LINUX version 8.0:

1. Modify the /etc/fstab file to include the following line:
   /dev/sdx /media/floppy auto noauto,user,sync 0 0
   (where x in sdx is the letter assigned to the FDD).

For Red Hat Linux version 7.3:

1. Modify the /etc/fstab file to include the following line:
   /dev/fdx /mnt/floppy auto noauto,user 0 0
   (where x in fdx is the letter assigned to the FDD).
   
   
2. Create a directory for the diskette drive under /mnt by running:
   mkdir /mnt/floppy
   
   
3. Mount the diskette drive by typing:
   mount /mnt/floppy and press Enter.
   

Back to top

Verify the following:

1. The diskette is inserted correctly in the drive.
   
2. The diskette is good and not damaged and the drive light comes on (one-second flash) when the diskette is inserted (try another diskette if you have one).
   
3. The diskette contains the necessary files to start the computer.
   
4. The diskette drive is enabled in the F1 Configuration/Setup utility program.
5. The software program is working correctly.
6. The cable is installed correctly (in the proper orientation).
7. To prevent diskette drive read/write errors, be sure the distance between monitors and diskette drives is at least 76 mm (3 inches).
8. Run diskette drive diagnostics.
9. Replace cable.
10. If still fails, replace diskette drive.
11. If still fails, replace Media tray card.

Back to top

If the diskette drive is identified incorrectly in F1 CMOS setup utility, you will probably be unable to boot to or format a diskette.

1. Power down the system, and press F1 at bootup to enter the Setup/Configuration utility program.
   
   
2. Once in the setup screens, check to make sure that the diskette drive is recognized correctly. Check that the drive settings are correct and correspond with the correct drive type, for example, 3.5 inch, 1.44MB is the current standard for diskette drive 0 (or diskette drive A).
   
   
3. Check the security section of setup and remove the supervisor password if one has been set. A password may have been enabled on an Intel Pentium or PCI system.

Back to top

If the light on the diskette drive stays on constantly from the time the system is powered up, the data cable on the system board or controller card may be connected backwards.

1. Power down the system and locate where the data cable is attached to the system board.
   
   
2. Once it is located, pull the cable off gently (pull the connector, not the cable).
   
   
3. Turn the cable around 180 degrees and put it back onto the system board.
   
   
4. Power up the system to see if the lights stay on continuously.
   

Back to top

This error is usually seen as the system boots up. Check the F1 CMOS setup utility to make sure that the drive(s) are identified correctly. If that does not correct the error, open the system and reseat the diskette drive cable. If that still does not correct the error, try another diskette drive cable.

Back to top

This error may be caused by incorrect drive identification in the F1 CMOS setup utility. Check to make sure that the drive(s) are identified correctly. This error can be caused by not having a diskette in the diskette drive(s) when trying to access it. If the diskette drive cable is poorly seated, this error often occurs. This error may also occur if the supervisor password is enabled in the F1 CMOS setup utility.

Back to top

This error can be caused by incorrect F1 CMOS setup utility settings, including the diskette drive not being identified at all.

Back to top

This error may occur if trying to format a diskette that is defective or if accessing a media type that is incompatible with the diskette drive.

Back to top

This error occurs primarily in Microsoft Windows when attempting to access the diskette drive without a diskette inserted. This error can occur with some operating systems, such as Norton Desktop or PC Tools; often these programs have updates to correct the problem.

Back to top

This error occurs if you are booting the system using a diskette other than a bootable diskette. If a bootable diskette is in the drive and this error is still received, the cable to the diskette drive cable is loose or defective.

Back to top

Support forums

Submit a technical question

Before you call IBM Service