#862217 initscript does fsck on empty floppy drive and stops booting

Package:
debian-installer
Source:
debian-installer
Description:
Debian Installer documentation
Submitter:
David Lawyer
Date:
2021-02-20 14:27:03 UTC
Severity:
normal
#862217#5
Date:
2017-05-09 21:29:31 UTC
From:
To:
My PC has a floppy drive which I seldom use.  When I boot linux, it runs
/etc/init.d/checkfs.sh which runs fsck.fat on the floppy drive
/dev/fd0.  The fsck fails because there is no floppy in the drive and
booting halts.  The error message is: open: No such device or address fsck.fat 4.1 (2017-01-24).
The error message is also wrong since there is such a device, /dev/fd0,
but it has no media (disk) in it.  Following this error message are
messages that fsck failed and that I can type C-d to continue booting.

Linux should not try to run fsck on a floppy drive at boottime, unless
perhaps if it's booting from floppy and the boot fails.  I'm booting from
my harddrive.

Here's my /etc/fstab file:
# /etc/fstab: static file system information for 80GB Maxtor.
#
# <file system>     <mount point>   <type>  <options>   <dump>  <pass>
LABEL=80GB-Maxtor	/            ext4    defaults    0       1
LABEL=80GB-Maxtor-swp   none            swap    sw            0       0
/dev/cdrom		 /home/dave/cd	iso9660	rw,noauto,user   0       2
LABEL=8GB-Maxtor         /bak 	        ext4    rw,noauto,user,exec  0       2
/dev/fd0	/home/dave/fd		vfat	rw,noauto,user,noexec,  0       1

			David Lawyer
#862217#10
Date:
2017-05-09 23:16:35 UTC
From:
To:
David Lawyer writes ("Bug#862217: initscript does fsck on empty floppy drive and stops booting"):
...

The final field there, the 1, is the fs_passno field and means to
check the filesystem.  See fstab(5).  Where did that fstab entry come
from ?  That is where the bug lies.

Regards,
Ian.
#862217#15
Date:
2017-05-09 23:49:23 UTC
From:
To:
...

...

Please change that last line in /etc/fstab to:

	/dev/fd0 /home/dave/fd vfat rw,noauto,user,noexec 0 0

(i.e. that last "1" needs to be "0").

After updating /etc/fstab, please regenerate the initramfs just in case.
As root:

	update-initramfs -u

Then reboot to test the changes, without a floppy inserted.  It should
not attempt to fsck /dev/fd0.
#862217#20
Date:
2019-02-20 13:55:58 UTC
From:
To:
Anybody knows who else than the admin could be responsible for
generating or adding entries to /etc/fstab? The installer? So that the
respective maintainers could take a look at this. This is apparently not
an issue with initscripts.
#862217#25
Date:
2019-02-20 14:38:30 UTC
From:
To:
The installer puts entries in /etc/fstab. I think finish-install is in
charge of that, but I am not sure if more than one component can
actually mangle with fstab. If anything, it should run with a
menu-item number larger than 6500 (base-installer).

My2Cents

KatolaZ
#862217#30
Date:
2019-02-20 23:15:15 UTC
From:
To:
reassign 862217 debian-installer
thanks

The email address of the submitter bounces email back, so he won't be
telling us where that entry came from. Reassigning to the installer.

Dear maintainers, could you please look at this, in case you would know
about something that could cause an /etc/fstab entry for a floppy drive
with fsck enabled?

Thanks,
#862217#37
Date:
2021-02-20 14:26:03 UTC
From:
To:
لدي عمل مربح للغاية لأناقشه معك.



لمزيد من التفاصيل ، يرجى الكتابة إلي على عنوان بريدي الإلكتروني الخاص: aa1938@mtazzo.com



شكرا جزيلا لك!