print_req_error: I/O error while booting into Bunsenlabs lithium

SSD · 2022-04-07 14:13:31

After turning on my computer I see GNU GRUB from there I boot into Bunsenlabs OS. After that I see a message on black screen written in white
[ 17.157522] print_req_error: I/O error, dev fd0, sector 0
/dev/sda1: clean, 171115/1525920 files, 1162474/6103296 blocks

Can anyone kindly help how to solve this error and what shall I do, so that I do not see this error message. I installed Bunsenlabs Lithium 32 bit through bootable pendrive from official site> I made that bootable using Balena Etcher. I have checked the integrity of the file and it was perfect. Is this a problem of my hard disk?

Bearded_Blunder · 2022-04-07 14:32:46

print_req_error: I/O error, dev fd0, sector 0

Does your machine have a floppy drive?
Does your motherboard have a floppy controller?
If the first is no & the second is yes, then you could try making sure the controller is disabled in BIOS.

The kernel believes you have a floppy & then can't find it.

SSD · 2022-04-07 18:49:27

Bearded_Blunder wrote:

print_req_error: I/O error, dev fd0, sector 0
Does your machine have a floppy drive?
Does your motherboard have a floppy controller?
If the first is no & the second is yes, then you could try making sure the controller is disabled in BIOS.
The kernel believes you have a floppy & then can't find it.

I have disabled the controller in BIOS, however now something else is being shown
[ 17.157707] print_req_error: I/O error, dev fdo, sector 0
/dev/sda1: recovering journal
/dev/sda1: clean, 171118/1525920 files, 1162477/6103296 blocks

How to remove this 3 lines while booting into linux?

rbh · 2022-04-07 21:24:31

SSD wrote:

I have disabled the controller in BIOS, however now something else is being shown
[ 17.157707] print_req_error: I/O error, dev fdo, sector 0
/dev/sda1: recovering journal
/dev/sda1: clean, 171118/1525920 files, 1162477/6103296 blocks

Message "recovering journal", tells you that your journaled filesystem got damaged before last time you shut down the computer. Some information was not writen to disk before the shutdowwn.
When booting up, computer notice the damage and repairs it, writes the info in journal to disk.

If you have important data on your harddisk(s), I advice you to backup. I think I have seen In/Out (I/O) error, dev fd0 (fdzerro, not lowercase letter o), when the problem was with the harddrive.

Examine your log for errors on hd. If you have a singe hd run:

# journalctl | grep sda | less

(Command preceded by # has to be given by rot or with sudo rights)
Probabley there is other better ways to filter the log for hd errors...

Use smartmontools to examine your harddrives health. Read up on smartmontools. A begining is https://www.thomas-krenn.com/en/wiki/SM … h_smartctl, command "man smartctl" and https://www.smartmontools.org/.

Configure your harddisk to report its health status as described.

Run a short test

# smartctl --test=short /dev/sda

the computer tells how long the test will take.

When test has finished, read info with:
# smartctl
Smart logs, is difficultut, under heading: "SMART Attributes Data Structure revision number: ", you can look for:
"9 Power_On_Hours
[...]
198 Offline_Uncorrectable"

Your numbers might be different.
Total time hd has been powered on is intresting.
Offline_Uncorrectable should be 0.

You can boot the computer on the BL usb-stick and repair your partions.
Command "lsblk -f" lists all partitions. Do not touch swap. just run

# fsck -f /dev/sda1

Will force a check and filerepair, if you have ext2, ext3 and ext4 filesystem.
Go through all partitions (exept swap).
Run fsck again and add flags for checking badblocks (-c or cc for more thorough examination) on the hd. The magnetic surfaceof the hd will be examined. If to low magnetism in a block, it will be marked for not to use. If there is data in a block, it will be moved copied to new location. It will tke soime time and continous report status. If you have badblocks, do not use the hd in critical machine. It can work for some year or it can be useles in a month.

Bearded_Blunder · 2022-04-08 06:35:32

If the good advice of @rbh doesn't help with the print_req_error: I/O error, dev fd0, sector 0 part of your issue, you might need to tell Linux not to load the driver module for the floppy.

I have seen Linux ignore BIOS settings & keep using a device that's been disabled, though Linux is much better behaved than Windows in that regard.

If you do need to, here's how:
Unload the driver

sudo rmmod floppy

Set the configuration to not load it

echo "blacklist floppy" | sudo tee /etc/modprobe.d/blacklist-floppy.conf

Update the boot files to reflect the change

sudo dpkg-reconfigure initramfs-tools

SSD · 2022-04-10 15:48:01

rbh wrote:

You can boot the computer on the BL usb-stick and repair your partions.
Command "lsblk -f" lists all partitions. Do not touch swap. just run
# fsck -f /dev/sda1
Will force a check and filerepair, if you have ext2, ext3 and ext4 filesystem.
Go through all partitions (exept swap).
Run fsck again and add flags for checking badblocks (-c or cc for more thorough examination) on the hd. The magnetic surfaceof the hd will be examined. If to low magnetism in a block, it will be marked for not to use. If there is data in a block, it will be moved copied to new location. It will tke soime time and continous report status. If you have badblocks, do not use the hd in critical machine. It can work for some year or it can be useles in a month.

Thanks for the advice I have tried Everything you have said, and few bad sectors were repaired in sda1...However now only 1 line is being shown:
/dev/sda1: clean, 171133/1525920 files, 1162491/6103296 blocks
Can the bad sectors or blocks of sda1 can be repaired with any command for scanning? If not what shall I do to hide this message?

SSD · 2022-04-10 16:02:27

Bearded_Blunder wrote:

If the good advice of @rbh doesn't help with the print_req_error: I/O error, dev fd0, sector 0 part of your issue, you might need to tell Linux not to load the driver module for the floppy.
I have seen Linux ignore BIOS settings & keep using a device that's been disabled, though Linux is much better behaved than Windows in that regard.
If you do need to, here's how:
Unload the driver
sudo rmmod floppy
Set the configuration to not load it
echo "blacklist floppy" | sudo tee /etc/modprobe.d/blacklist-floppy.conf
Update the boot files to reflect the change
sudo dpkg-reconfigure initramfs-tools

Thanks a lot for the help this was really helpful as there was some problem in my BIOS s after disabling the floppy the settings were not saved in bios probably because of dead CIMOS battery but anyways those above commands helped me to remove fdo I/O error. However as mentioned Only one line is shown now i.e :
/dev/sda1: clean, 171133/1525920 files, 1162491/6103296 blocks
Can you say how to solve this and hide this?

Bearded_Blunder · 2022-04-10 16:02:56

That one just shows anyway.

SSD · 2022-04-10 16:11:24

Bearded_Blunder wrote:

That one just shows anyway.

Can any boot file be altered to skip this message?

Bearded_Blunder · 2022-04-10 16:21:17

Can the bad sectors or blocks of sda1 can be repaired with any command for scanning?

They're marked not to be used in the filesystem now, if you look at the SMART data you can tell if there are possibilities.

sudo smartctl -H /dev/sda

Should flag up any problematic attributes.

sudo smartctl --all /dev/sda

Current_Pending_Sector can sometimes be corrected back to zero (by the drive firmware) by writing to that sector. The method I'd use takes the computer offline for a long time though, & isn't guaranteed.

Reallocated_Sector_Ct needs watching.. if that increases over time your drive is on it's way out.
Some people will replace a drive if that one isn't 0, though drives typically have hundreds of spares they can map in as replacements.

As to skipping that message, I've never tried since it doesn't bother me enough, you probably could, but given it's the output from a drive check.. & yours had problems.. skipping it would probably be unwise.

#1 2022-04-07 14:13:31

print_req_error: I/O error while booting into Bunsenlabs lithium

#2 2022-04-07 14:32:46

Re: print_req_error: I/O error while booting into Bunsenlabs lithium

#3 2022-04-07 18:49:27

Re: print_req_error: I/O error while booting into Bunsenlabs lithium

#4 2022-04-07 21:24:31

Re: print_req_error: I/O error while booting into Bunsenlabs lithium

#5 2022-04-08 06:35:32

Re: print_req_error: I/O error while booting into Bunsenlabs lithium

#6 2022-04-10 15:48:01

Re: print_req_error: I/O error while booting into Bunsenlabs lithium

#7 2022-04-10 16:02:27

Re: print_req_error: I/O error while booting into Bunsenlabs lithium

#8 2022-04-10 16:02:56

Re: print_req_error: I/O error while booting into Bunsenlabs lithium

#9 2022-04-10 16:11:24

Re: print_req_error: I/O error while booting into Bunsenlabs lithium

#10 2022-04-10 16:21:17

Re: print_req_error: I/O error while booting into Bunsenlabs lithium

Board footer