Error could not insert floppy

Tried many different ways to accomplish this task but no success. Tried changing BIOS (Legacy and UEFI).

miketh1234

Posts: 4
Joined: 2018/06/29 08:48:31

Attemping to install CentOS7 from usb but cannot

Tried many different ways to accomplish this task but no success. Tried changing BIOS (Legacy and UEFI).

1) Starting Dracut Emergency Shell…

Warning: /dev/root/ does not exist

2) ERROR: could not insert ‘floppy’: No device found
ERROR: could not insert ‘edd’ : No device found

3) vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=CENTOSx20x20x86_64 rd.live.check quiet

4) Gotten as far in the setup process but not able to choose a hard disk


User avatar

TrevorH

Site Admin
Posts: 32527
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Attemping to install CentOS7 from usb but cannot

Post

by TrevorH » 2018/06/29 09:14:53

How did you create your USB stick? A lot of the utilities that claim to do that actually break our iso images as they attempt to rewrite them while «copying» them. The best utility is plain old ‘dd’ as that doesn’t attempt to be clever.

Information on USB key based installs can be found at http://wiki.centos.org/HowTos/InstallFromUSBkey


miketh1234

Posts: 4
Joined: 2018/06/29 08:48:31

Re: Attemping to install CentOS7 from usb but cannot

Post

by miketh1234 » 2018/06/29 10:52:14

Trevor,

I will try ‘dd’ and follow up with you afterwards.

Thank you.



lightman47

Posts: 1444
Joined: 2014/05/21 20:16:00
Location: Central New York, USA

Re: Attemping to install CentOS7 from usb but cannot

Post

by lightman47 » 2018/06/29 20:27:38

After an hour trying to get a working USB key, I surmised that the of= must be the /dev/{device} and NOT the path to the mounted point!!! In my case it was sdb1 — so my command was dd if=CentOS-7-x86_64-DVD-1804.iso of=/dev/sdb (just drop the «1» and commit the whole stick).

I found that out by running the ‘disks’ utility, then selecting the stick when it showed up after I plugged it in. In the right pane was it’s /dev spec.

Hope this helps someone — I kept trying to «of=/run/media/user/directory». I now understand WHY some many people have the trouble I did getting a bootable stick.

;)

Last edited by lightman47 on 2018/10/14 16:26:47, edited 1 time in total.


miketh1234

Posts: 4
Joined: 2018/06/29 08:48:31

Re: Attemping to install CentOS7 from usb but cannot

Post

by miketh1234 » 2018/10/14 14:47:55

After taking the whole Summer off from installing (a full install) CentOS on a brand new Lenovo Windows 10 machine wondering if I could get some guidance from start to finish?
Question: Is it possible, and/or desirable, to use the Windows command line to «dd» a CentOS 7 iso image to my USB 3.1?



miketh1234

Posts: 4
Joined: 2018/06/29 08:48:31

Re: Attemping to install CentOS7 from usb but cannot

Post

by miketh1234 » 2018/10/14 22:47:41

Thank you for your timely reply but unfortunately I’m starting to wonder if I need step-by-step help because I am running into so many roadblocks. I do not have much experience with Windows. The reason I bought this computer was to use the Lenovo hardware and only use Linux-CentOS. Do you have any recommendations to get more specific help because I am not so sure that I will be able to accomplish this in this forum. Thank you very much.
Sincerely,
Michael Thomas


User avatar

TrevorH

Site Admin
Posts: 32527
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Attemping to install CentOS7 from usb but cannot

Post

by TrevorH » 2018/10/14 23:28:04

Start by downloading the iso image file then run a utility to get teh sha256sum of the file that you have. Compare that to the list of sha256sums that we publish in our wiki in the Release Notes for each release. Currently the wiki is broken so I ran sha256sum here against my copy and got 506e4e06abf778c3435b4e5745df13e79ebfc86565d7ea1e128067ef6b5a6345. If your downloaded iso image file sha256sum does not match that then download it again until it does.

When you dd that, make sure you write it to the entire USB device — in linux terms /dev/sdX — not to a partition on the device — i.e. not to /dev/sdX1. That iso image file should boot on both UEFI and legacy BIOS machines.

I believe that you can ignore errors about floppy and edd, those are just for information. The messages about missing /dev/root imply that it had trouble reading your installation media so if you haven’t already done so, try a different USB stick and/or a different USB socket.


id2concept

Posts: 1
Joined: 2019/02/08 20:21:30

Re: Attemping to install CentOS7 from usb but cannot

Post

by id2concept » 2019/02/08 21:41:06

For me sticking the USB drive in a USB 2 port instead of USB 3 did the job (Shuttle DH310).


View previous topic :: View next topic  
Author Message
ImageJPEG
n00b
n00b

Joined: 03 Feb 2013
Posts: 20
Location: North West Iowa

PostPosted: Tue Dec 10, 2013 1:34 am    Post subject: Having issues getting my USB floppy drive working Reply with quote

I bought a USB floppy drive to transfer files from my modern computer to my vintage ones. I tried compiling the floppy driver in the kernel but that messed some things up. I’ve compiled the driver as a module instead but when I try to load it, it gives me an error:

Code:
sudo modprobe floppy

Password:

modprobe: ERROR: could not insert ‘floppy’: No such device

dmesg gives me this:

Code:
…[   35.054975] end_request: I/O error, dev sdg, sector 0

[   35.054981] Buffer I/O error on device sdg, logical block 0

[   42.926894] sd 7:0:0:0: [sdg] Unhandled sense code

[   42.926898] sd 7:0:0:0: [sdg] 

[   42.926900] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE

[   42.926902] sd 7:0:0:0: [sdg] 

[   42.926903] Sense Key : Medium Error [current]

[   42.926907] sd 7:0:0:0: [sdg] 

[   42.926911] Add. Sense: Incompatible medium installed

[   42.926913] sd 7:0:0:0: [sdg] CDB:

[   42.926915] Read(10): 28 00 00 00 00 00 00 00 08 00 00 00

[   42.926925] end_request: I/O error, dev sdg, sector 0

[   42.926927] Buffer I/O error on device sdg, logical block 0

[   43.171712] EXT4-fs (sda3): re-mounted. Opts: commit=0

[   43.175109] EXT4-fs (sda1): re-mounted. Opts: commit=0

[   43.211283] EXT4-fs (sdb1): re-mounted. Opts: commit=0

[   50.766891] sd 7:0:0:0: [sdg] Unhandled sense code

[   50.766899] sd 7:0:0:0: [sdg] 

[   50.766903] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE

[   50.766907] sd 7:0:0:0: [sdg] 

[   50.766910] Sense Key : Medium Error [current]

[   50.766917] sd 7:0:0:0: [sdg] 

[   50.766924] Add. Sense: Incompatible medium installed

[   50.766929] sd 7:0:0:0: [sdg] CDB:

[   50.766931] Read(10): 28 00 00 00 00 00 00 00 08 00 00 00

[   50.766951] end_request: I/O error, dev sdg, sector 0

[   50.766955] Buffer I/O error on device sdg, logical block 0

[  246.940097] floppy0: no floppy controllers found

What lsusb -vv shows:

Code:
Bus 002 Device 002: ID 0644:0000 TEAC Corp. Floppy

Device Descriptor:

  bLength                18

  bDescriptorType         1

  bcdUSB               1.10

  bDeviceClass            0 (Defined at Interface level)

  bDeviceSubClass         0

  bDeviceProtocol         0

  bMaxPacketSize0         8

  idVendor           0x0644 TEAC Corp.

  idProduct          0x0000 Floppy

  bcdDevice            2.00

  iManufacturer           1 TEACV0.0

  iProduct                2 TEACV0.0

  iSerial                 0

  bNumConfigurations      1

  Configuration Descriptor:

    bLength                 9

    bDescriptorType         2

    wTotalLength           39

    bNumInterfaces          1

    bConfigurationValue     1

    iConfiguration          0

    bmAttributes         0x80

      (Bus Powered)

    MaxPower               98mA

    Interface Descriptor:

      bLength                 9

      bDescriptorType         4

      bInterfaceNumber        0

      bAlternateSetting       0

      bNumEndpoints           3

      bInterfaceClass         8 Mass Storage

      bInterfaceSubClass      4 Floppy (UFI)

      bInterfaceProtocol      0 Control/Bulk/Interrupt

      iInterface              0

      Endpoint Descriptor:

        bLength                 7

        bDescriptorType         5

        bEndpointAddress     0x82  EP 2 IN

        bmAttributes            2

          Transfer Type            Bulk

          Synch Type               None

          Usage Type               Data

        wMaxPacketSize     0x0040  1x 64 bytes

        bInterval               0

      Endpoint Descriptor:

        bLength                 7

        bDescriptorType         5

        bEndpointAddress     0x02  EP 2 OUT

        bmAttributes            2

          Transfer Type            Bulk

          Synch Type               None

          Usage Type               Data

        wMaxPacketSize     0x0040  1x 64 bytes

        bInterval               0

      Endpoint Descriptor:

        bLength                 7

        bDescriptorType         5

        bEndpointAddress     0x81  EP 1 IN

        bmAttributes            3

          Transfer Type            Interrupt

          Synch Type               None

          Usage Type               Data

        wMaxPacketSize     0x0002  1x 2 bytes

        bInterval             127

Device Status:     0x0000

  (Bus Powered)

Any ideas?

Back to top

View user's profile Send private message

eccerr0r
Watchman
Watchman

Joined: 01 Jul 2004
Posts: 9221
Location: almost Mile High in the USA

PostPosted: Tue Dec 10, 2013 2:02 am    Post subject: Reply with quote

I have a USB floppy, yes these are strange beasts.

No, you don’t need the floppy.ko driver — that’s for the 8272 clones. These drives show up as a 1.44MB /dev/sdX drive like a hard disk and just use it as a hard drive, pretty much.

I don’t know how you would format these things however. I think it’s best to format floppies in a real floppy controller than one of these things. I also do not know how it would behave with 720K disks, I’ve only tested with 1.44MB standard high density PC format disks.
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD

What am I supposed watching?

Back to top

View user's profile Send private message

Logicien
Veteran
Veteran

Joined: 16 Sep 2005
Posts: 1506
Location: Montréal

PostPosted: Tue Dec 10, 2013 3:06 am    Post subject: Reply with quote

Is the USB floppy detected by the BIOS(EFI) as a bootable drive?

If yes, have you try to use it as a bootable drive to see how it work?

Have you try to make it work with an other Linux live-cd distribution?

It is easier to compile the Linux floppy support as a module if you need to pass it some parameters. Like eccerr0r said you dont need it, this module do not support USB according to it source code. But you may miss some USB support for your floppy.

You have the Linux floppy kernel parameter that can be use to change the kernel behavior. See /usr/src/linux/Documentation/blockdev/floppy.txt.

Have you try to make it work with an other Linux live-cd distribution?
_________________
Paul

Back to top

View user's profile Send private message

ImageJPEG
n00b
n00b

Joined: 03 Feb 2013
Posts: 20
Location: North West Iowa

PostPosted: Tue Dec 10, 2013 3:25 am    Post subject: Reply with quote

Yes, it does show up as a bootable device in my BIOS.

I’ll check to see if I can boot from it.

I currently don’t have any live CDs or burnable CD/DVDs.

UPDATE:

It does not boot from the drive…however, the only bootable 3.5″ floppy I have is DOS 3.30 for a Tandy 1000 HX.

One thing I do notice thought, about every two seconds, the light on the drive flashes.

Also, when I try to mount the floppy using:

Code:
sudo mount -t msdos /dev/sdg /mnt/floppy

I get this error:

Code:
mount: /dev/sdg: can’t read superblock

Back to top

View user's profile Send private message

Logicien
Veteran
Veteran

Joined: 16 Sep 2005
Posts: 1506
Location: Montréal

PostPosted: Tue Dec 10, 2013 3:54 am    Post subject: Reply with quote

It’s because your floppy disk is not formated in msdosfs. You can execute the command

Code:
blkid



to know the filesystem in which the floppy disk is formated and/or try

Code:
sudo mount -t auto /dev/sdg /mnt/floppy



You may need to format the floppy disk in a filesystem of your choice before mounting it. A dirty filesystem can be the cause of Input/output errors. Use the badblocks command to verify the integrity of the floppy disk. Change it for a new one supported by your floppy drive if the problem persist.
_________________
Paul

Back to top

View user's profile Send private message

eccerr0r
Watchman
Watchman

Joined: 01 Jul 2004
Posts: 9221
Location: almost Mile High in the USA

PostPosted: Tue Dec 10, 2013 7:26 pm    Post subject: Reply with quote

The behavior of my usb floppy when a disk is inserted is for the drive to first read it on its own — which makes sense in order to become a real SCSI mass storage device. I don’t know what the behavior is if the disk can’t actually be read however.

I’ll need to do more experiments on this drive, and I still don’t know if it’s possible to format disks…
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD

What am I supposed watching?

Back to top

View user's profile Send private message

Display posts from previous:   

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

#1 2021-04-14 16:34:29

SaturnOfTheStars6728
Member
Registered: 2021-03-25
Posts: 23

Trouble using Floppy Drive

In my computer I have installed an old Sony 3.5 Floppy Drive because more often than not it comes in handy for me. It is connected via a IDE to USB converter. I recently started using Arch Linux so I could better archive my floppy disks, but have encountered a problem. Upon start up of the system, the drive makes consistent clicking noises every second like a metronome unless a floppy disk is inserted. But when trying to mount the floppy disk I am returned with a «can’t read superblock» error. Formatting also doesn’t work. Trying to use modprobe floppy results in the error «could not insert ‘floppy’. No such device.». The floppy drive isn’t broken because it still works on my Windows 10 partition. I also noticed that my floppy drive is being recognized as a SCSI device going by the name sda. Assistance would be much appreciated.

Last edited by SaturnOfTheStars6728 (2021-04-14 16:38:40)

#2 2021-04-14 19:13:28

seth
Member
Registered: 2012-09-03
Posts: 35,309

Re: Trouble using Floppy Drive

Does it also do that if you only attach the converter to the PC after the system has booted?

Either you flipped the FD plug (that’s possible and will get you this behavior) or something™ is constantly accessing the drive (eg. some automounter) which is more reasonable if it doesn’t show the behavior on windows.
Speaking of which, also see the 3rd link in my signature.

INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

Thanks. We have received your request and will respond promptly.

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!

  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It’s Free!

*Tek-Tips’s functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

modprobe — no floppy error

modprobe — no floppy error

(OP)

25 Jun 04 12:15

I have a fedora core 2 installed on my laptop.

During boot I have an error in modprobe because it can’t insert the floppy module, in fact I have no floppy on my laptop.

How can I configure my linux to stop having the error in every boot?

Thanks in advance

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Join Tek-Tips® Today!

Join your peers on the Internet’s largest technical computer professional community.
It’s easy to join and it’s free.

Here’s Why Members Love Tek-Tips Forums:

  • Tek-Tips ForumsTalk To Other Members
  • Notification Of Responses To Questions
  • Favorite Forums One Click Access
  • Keyword Search Of All Posts, And More…

Register now while it’s still free!

Already a member? Close this window and log in.

Join Us             Close

Понравилась статья? Поделить с друзьями:
  • Error could not initialize directx 9 renderer painkiller что делать
  • Error could not handle the request как исправить
  • Error could not get the current mvc module paths
  • Error could not get primary adapter handle
  • Error could not get file size of file как исправить