Commissioning fails when BIOS reports floppy drive, but there is none installed

Bug #1584211 reported by shewless on 2016-05-20
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Critical
Blake Rouse
1.9
Critical
Blake Rouse

Bug Description

When commissioning a server it consistently "Failed commissioning"

Looking at the console logs we see a conspicous log: "blk_update_request: I/O error, dev fd0, sector 0"
http://pastebin.com/eeaMUvPs

After disabling the "floppy drive" in the BIOS (there wasn't a physical floppy drive installed) the problem goes away and commissioning is successful!

Thanks to kiko for the help debugging

ubuntu@maas:~$ dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============================-============================-============-=================================================
ii maas 2.0.0~beta3+bzr4941-0ubuntu1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.0.0~beta3+bzr4941-0ubuntu1 all MAAS client and command-line interface
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.0.0~beta3+bzr4941-0ubuntu1 all MAAS server common files
ii maas-dhcp 2.0.0~beta3+bzr4941-0ubuntu1 all MAAS DHCP server
ii maas-dns 2.0.0~beta3+bzr4941-0ubuntu1 all MAAS DNS server
ii maas-proxy 2.0.0~beta3+bzr4941-0ubuntu1 all MAAS Caching Proxy
ii maas-rack-controller 2.0.0~beta3+bzr4941-0ubuntu1 all Rack Controller for MAAS
ii maas-region-api 2.0.0~beta3+bzr4941-0ubuntu1 all Region controller API service for MAAS
ii maas-region-controller 2.0.0~beta3+bzr4941-0ubuntu1 all Region Controller for MAAS
un maas-region-controller-min <none> <none> (no description available)
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-maas-provisioningserver <none> <none> (no description available)
ii python3-django-maas 2.0.0~beta3+bzr4941-0ubuntu1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.0.0~beta3+bzr4941-0ubuntu1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.0.0~beta3+bzr4941-0ubuntu1 all MAAS server provisioning libraries (Python 3)

Related branches

Christian Reis (kiko) on 2016-05-20
summary: - commissioning fails - related to "blk_update_request: I/O error, dev
- fd0, sector 0"
+ Commissioning fails when BIOS reports floppy drive, but there is none
+ installed
Changed in maas:
milestone: none → 2.0.0
importance: Undecided → Critical
Christian Reis (kiko) wrote :

Note the related question: http://askubuntu.com/questions/213512/buffer-i-o-error-on-device-fd0-logical-block-0-error

I'm not sure why blkid returns an error if fd0 is missing; I guess the problem may be that floppies are not really probeable -- i.e. the only way to tell if they are there is to go and read from them.

At any rate, there's an easy big hammer, which is blacklisting the floppy module during the commissioning run, or we could be more subtle and not really mind blkid's return code.

Changed in maas:
status: New → In Progress
assignee: nobody → Blake Rouse (blake-rouse)
Ante Karamatić (ivoks) wrote :

As a workaround, set 'modprobe.blacklist=floppy' in Global Kernel Parameters.

Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers