Install doesn't proceed because of I/O error for floppy disk drive

Bug #769704 reported by Takashi Sakamoto
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Release Notes for Ubuntu
Invalid
Undecided
Unassigned
debian-installer (Ubuntu)
Expired
Medium
Unassigned
Natty
Invalid
Medium
Unassigned
Oneiric
Invalid
Medium
Unassigned

Bug Description

Binary package hint: debian-installer

Hi,

CPU: Intel Core-i7 960
Motherboard: GA-X58-UD5 (X58 Express Chipset)

What happend:

I installed Ubuntu Studio 11.04, release candidate as of 2011-04-23.
http://iso.qa.ubuntu.com/qatracker/test/5606

And the installation process didn't proceed because of floppy disk drive
issue.

What I did:

I enabled floppy disk drive in Bios function but don't use the drive, do
not connect the drive.

I ran installer and the installer was not proceeded just after DHCP
detection.

Then I move to text console to push F4 key. The text concole report
"end_request: I/O error, dev fd0, sector 0". I guess this is an issue of
floppy disk drive.

I reboot my system and went to bios section and change the setting to
disable floppy disk drive. Then the installer proceeded.

What I expected:

I can install Ubuntu till maverick the same settings to enable floppy
disk drive and without connecting it to my system. The installer should
run as the same circumstanses.

Error messages:

end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 2
EXT3-fs (fd0): error: unable to read superblock

end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 2
EXT2-fs (fd0): error: unable to read superblock

end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
EXT4-fs (fd0): error: unable to read superblock

attempt to access beyond end of device
fd0: rw=0, want=66, limit=8
isofs_fill_super: bread failed, dev=fr0, iso_blknum=16, block=32

end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
FAT (fd0): error: unable to read superblock

end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
FAT (fd0): error: unable to read superblock

end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 2
EXT3-fs (fd0): error: unable to read superblock

end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 2
EXT2-fs (fd0): error: unable to read superblock

end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
EXT4-fs (fd0): error: unable to read superblock

attempt to access beyond end of device
fd0: rw=0, want=66, limit=8
isofs_fill_super: bread failed, dev=fr0, iso_blknum=16, block=32

end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
end_request: I/O error, dev fd0, sector 0
FAT (fd0): error: unable to read superblock
EXT3-fs (sda1): error couldn't mount because of unsupported optional features (240)
EXT2-fs (sda1): error couldn't mount because of unsupported optional features (240)
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts:
EXT3-fs (sda1): error couldn't mount because of unsupported optional features (240)
EXT2-fs (sda1): error couldn't mount because of unsupported optional features (240)
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts:

Regards

tags: added: iso-testing
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks for your report.

This looks like bug 739774. Can you go into your BIOS and see if you can disable the floppy controller? Do let us know whether or not that fixes the issue.

Thanks in advance.

Changed in debian-installer (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Takashi Sakamoto (mocchi) wrote :

I disabled the floppy controller at BIOS then the process proceeded as I described above.

The bug #739774 you mentioned said it's fixed in the beginning of this month but what I tested is a release candidate for Ubuntu Studio. I think it should be fixed but I faced it.

Regards

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks for confirming. Moving to casper and setting to triage.

Don't hesitate to submit any new bug.

affects: debian-installer (Ubuntu) → casper (Ubuntu)
Changed in casper (Ubuntu):
status: Incomplete → Triaged
tags: added: natty
Revision history for this message
Takashi Sakamoto (mocchi) wrote :

Hi,
Today I test the final test for Ubuntu Studio.

http://iso.qa.ubuntu.com/qatracker/build/ubuntustudio/all

And I faced the same problem...

Regards

Changed in casper (Ubuntu Oneiric):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Martin Pitt (pitti) wrote :

Moving back to debian-installer, as Ubuntu Stuido uses that, not a live system. I suppose there was some change in natty about partition probing, which forgot to filter out /dev/fd0? Just as we do in udev, udisks, and casper, partman/d-i/etc. should never try to do any open() on /dev/fdX because of this common problem.

Colin, do you have a rough idea which part of d-i could have changed here, or which parts do this sort of thing (partman?).

Takashi, can you please attach your log files after an installation? They are in /var/log/installer/. It would be great if you could just let the install finish, even if it takes very long (in the equivalent problem in casper it took 40 minutes to proceed).

Thanks!

affects: casper (Ubuntu Natty) → debian-installer (Ubuntu Natty)
Changed in debian-installer (Ubuntu Natty):
status: Triaged → Confirmed
Colin Watson (cjwatson)
Changed in ubuntu-release-notes:
assignee: nobody → Colin Watson (cjwatson)
Pete Graner (pgraner)
Changed in ubuntu-release-notes:
assignee: Colin Watson (cjwatson) → nobody
status: New → Invalid
Revision history for this message
dino99 (9d9) wrote :

is it still an issue ?

Changed in debian-installer (Ubuntu Oneiric):
status: Triaged → Invalid
Changed in debian-installer (Ubuntu Natty):
status: Confirmed → Invalid
Changed in debian-installer (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for debian-installer (Ubuntu) because there has been no activity for 60 days.]

Changed in debian-installer (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.