print_req_error: I/0 errorsh: echo: I/O error on pm-suspend Ubuntu 14.04Crash, followed by I/0 errorSegfaults and “Read-only filesystem” after a dist-upgradePoor IO performance - PCIe NVMe Samsung 950 proFailed install of ubuntu 16.04 & 15.10 with error message “following file did not match its source copy…”
Who inspired the character Geordi La Forge?
How low is the lowest tone that a human can sing?
I don't want my ls command in my script to print results on screen
Making a pikuach nefesh phone call on Yom Kippur - mitsva or something to be avoided?
What exactly is meant by "partial function" in functional programming?
In the example of guess a specified number between 1 and 20 (both inclusive), what is the sample space?
What is the following style of typography called?
Can an Unconscious PC hear you?
Did Bobby Fischer actually write "Bobby Fischer Teaches Chess"
Why did my relationship with my wife go down by two hearts?
Visualize a large int
Which person is telling the truth?
Would a spacecraft carry arc welding supplies?
Minimum number of turns to capture all pieces in Checkers
Is sucess due to hard work sustainable in academic research?
Generate an array with custom index
A toy model in 0-d QFT
Grade changes with auto grader
What would a chair for a Human with a Tail look like?
Repair drywall and protect wires on back of electrical panel
Euclid Algorithm to Find Muliplicative Inverse
Did the US push the Kurds to lower their defences against Turkey in the months preceding the latest Turkish military operation against them?
Does using an img title attribute in addition to the alt attribute help image SEO?
Conveying the idea of "tricky"
print_req_error: I/0 error
sh: echo: I/O error on pm-suspend Ubuntu 14.04Crash, followed by I/0 errorSegfaults and “Read-only filesystem” after a dist-upgradePoor IO performance - PCIe NVMe Samsung 950 proFailed install of ubuntu 16.04 & 15.10 with error message “following file did not match its source copy…”
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
Every couple of days I get these errors that lockup the server.
[501.882940] print_req_error: I/O error, dev fd0, sector 0
[504.338961] print_req_error: I/O error, dev fd0, sector 0
[504.738984] print_req_error: I/O error, dev fd0, sector 0
[509.250929] print_req_error: I/O error, dev fd0, sector 0
[509.898921] print_req_error: I/O error, dev fd0, sector 0
[510.334916] print_req_error: I/O error, dev fd0, sector 0
[517.714867] print_req_error: I/O error, dev fd0, sector 0
[520.118801] print_req_error: I/O error, dev fd0, sector 0
[520.618864] print_req_error: I/O error, dev fd0, sector 0
[521.047029] print_req_error: I/O error, dev fd0, sector 0
I've blacklisted the floppy drive and I also disabled the floppy drive in vSphere. Any help would be appreciated! Thanks
io
edited Dec 17 '18 at 17:04
waltinator
25k7 gold badges43 silver badges74 bronze badges
asked Dec 17 '18 at 15:25
John De La MotteJohn De La Motte
161 gold badge1 silver badge2 bronze badges
add a comment
|
Every couple of days I get these errors that lockup the server.
[501.882940] print_req_error: I/O error, dev fd0, sector 0
[504.338961] print_req_error: I/O error, dev fd0, sector 0
[504.738984] print_req_error: I/O error, dev fd0, sector 0
[509.250929] print_req_error: I/O error, dev fd0, sector 0
[509.898921] print_req_error: I/O error, dev fd0, sector 0
[510.334916] print_req_error: I/O error, dev fd0, sector 0
[517.714867] print_req_error: I/O error, dev fd0, sector 0
[520.118801] print_req_error: I/O error, dev fd0, sector 0
[520.618864] print_req_error: I/O error, dev fd0, sector 0
[521.047029] print_req_error: I/O error, dev fd0, sector 0
I've blacklisted the floppy drive and I also disabled the floppy drive in vSphere. Any help would be appreciated! Thanks
io
edited Dec 17 '18 at 17:04
waltinator
25k7 gold badges43 silver badges74 bronze badges
asked Dec 17 '18 at 15:25
John De La MotteJohn De La Motte
161 gold badge1 silver badge2 bronze badges
1
Did you disable the Floppy drive in the VM's 'firmware' level? Otherwise it'll stil 'see' a floppy drive whether it exists or not in the VM. This is more or less how the BIOS reveals to the underlying system whether a device exists or not, and thisfd0problem is one I run into regularly on my VMs in VMware (I always boot to firmware and disable the floppy drive on first-run)
– Thomas Ward♦
Dec 17 '18 at 15:28
This is happening to me too, I tried to comment out/dev/fd0from /etc/fstab with no luck.
– Nicolas Hanna
Apr 26 at 10:30
add a comment
|
Every couple of days I get these errors that lockup the server.
[501.882940] print_req_error: I/O error, dev fd0, sector 0
[504.338961] print_req_error: I/O error, dev fd0, sector 0
[504.738984] print_req_error: I/O error, dev fd0, sector 0
[509.250929] print_req_error: I/O error, dev fd0, sector 0
[509.898921] print_req_error: I/O error, dev fd0, sector 0
[510.334916] print_req_error: I/O error, dev fd0, sector 0
[517.714867] print_req_error: I/O error, dev fd0, sector 0
[520.118801] print_req_error: I/O error, dev fd0, sector 0
[520.618864] print_req_error: I/O error, dev fd0, sector 0
[521.047029] print_req_error: I/O error, dev fd0, sector 0
I've blacklisted the floppy drive and I also disabled the floppy drive in vSphere. Any help would be appreciated! Thanks
io
edited Dec 17 '18 at 17:04
waltinator
25k7 gold badges43 silver badges74 bronze badges
asked Dec 17 '18 at 15:25
John De La MotteJohn De La Motte
161 gold badge1 silver badge2 bronze badges
Every couple of days I get these errors that lockup the server.
[501.882940] print_req_error: I/O error, dev fd0, sector 0
[504.338961] print_req_error: I/O error, dev fd0, sector 0
[504.738984] print_req_error: I/O error, dev fd0, sector 0
[509.250929] print_req_error: I/O error, dev fd0, sector 0
[509.898921] print_req_error: I/O error, dev fd0, sector 0
[510.334916] print_req_error: I/O error, dev fd0, sector 0
[517.714867] print_req_error: I/O error, dev fd0, sector 0
[520.118801] print_req_error: I/O error, dev fd0, sector 0
[520.618864] print_req_error: I/O error, dev fd0, sector 0
[521.047029] print_req_error: I/O error, dev fd0, sector 0
I've blacklisted the floppy drive and I also disabled the floppy drive in vSphere. Any help would be appreciated! Thanks
io
io
edited Dec 17 '18 at 17:04
waltinator
25k7 gold badges43 silver badges74 bronze badges
asked Dec 17 '18 at 15:25
John De La MotteJohn De La Motte
161 gold badge1 silver badge2 bronze badges
edited Dec 17 '18 at 17:04
waltinator
25k7 gold badges43 silver badges74 bronze badges
asked Dec 17 '18 at 15:25
John De La MotteJohn De La Motte
161 gold badge1 silver badge2 bronze badges
edited Dec 17 '18 at 17:04
waltinator
25k7 gold badges43 silver badges74 bronze badges
edited Dec 17 '18 at 17:04
waltinator
25k7 gold badges43 silver badges74 bronze badges
edited Dec 17 '18 at 17:04
waltinator
25k7 gold badges43 silver badges74 bronze badges
25k7 gold badges43 silver badges74 bronze badges
asked Dec 17 '18 at 15:25
John De La MotteJohn De La Motte
161 gold badge1 silver badge2 bronze badges
asked Dec 17 '18 at 15:25
John De La MotteJohn De La Motte
161 gold badge1 silver badge2 bronze badges
asked Dec 17 '18 at 15:25
John De La MotteJohn De La Motte
161 gold badge1 silver badge2 bronze badges
161 gold badge1 silver badge2 bronze badges
1
Did you disable the Floppy drive in the VM's 'firmware' level? Otherwise it'll stil 'see' a floppy drive whether it exists or not in the VM. This is more or less how the BIOS reveals to the underlying system whether a device exists or not, and thisfd0problem is one I run into regularly on my VMs in VMware (I always boot to firmware and disable the floppy drive on first-run)
– Thomas Ward♦
Dec 17 '18 at 15:28
This is happening to me too, I tried to comment out/dev/fd0from /etc/fstab with no luck.
– Nicolas Hanna
Apr 26 at 10:30
add a comment
|
1
Did you disable the Floppy drive in the VM's 'firmware' level? Otherwise it'll stil 'see' a floppy drive whether it exists or not in the VM. This is more or less how the BIOS reveals to the underlying system whether a device exists or not, and thisfd0problem is one I run into regularly on my VMs in VMware (I always boot to firmware and disable the floppy drive on first-run)
– Thomas Ward♦
Dec 17 '18 at 15:28
This is happening to me too, I tried to comment out/dev/fd0from /etc/fstab with no luck.
– Nicolas Hanna
Apr 26 at 10:30
1
1
Did you disable the Floppy drive in the VM's 'firmware' level? Otherwise it'll stil 'see' a floppy drive whether it exists or not in the VM. This is more or less how the BIOS reveals to the underlying system whether a device exists or not, and this
fd0 problem is one I run into regularly on my VMs in VMware (I always boot to firmware and disable the floppy drive on first-run)– Thomas Ward♦
Dec 17 '18 at 15:28
Did you disable the Floppy drive in the VM's 'firmware' level? Otherwise it'll stil 'see' a floppy drive whether it exists or not in the VM. This is more or less how the BIOS reveals to the underlying system whether a device exists or not, and this
fd0 problem is one I run into regularly on my VMs in VMware (I always boot to firmware and disable the floppy drive on first-run)– Thomas Ward♦
Dec 17 '18 at 15:28
This is happening to me too, I tried to comment out
/dev/fd0 from /etc/fstab with no luck.– Nicolas Hanna
Apr 26 at 10:30
This is happening to me too, I tried to comment out
/dev/fd0 from /etc/fstab with no luck.– Nicolas Hanna
Apr 26 at 10:30
add a comment
|
3 Answers
3
active
oldest
votes
Okay this worked for me!
If you have removed your swap file then ensure that in step 3. that you have commented out the swap file line (it will have 'swap' in the same line) and in step 4. comment out the first (and only)
Run this
dpkg-reconfigure initramfs-toolsand then restart and continuelsblk -fcommand, and note the UUID'sEnsure that the UUID's in this file is right
/etc/fstab--sudo nano /etc/fstabEnsure that the UUID's in this file is also right
/etc/initramfs-tools/conf.d/resume.--sudo nano /etc/initramfs-tools/conf.d/resume.Run
sudo update-initramfs -uand restart
Okay, I am no expert but this is how I fixed the problem and when I fixed this problem and it introduced another problem that should be fixed using these commands.
Please comment if this worked and especially if this didn't work so i know if it fixed (and answered) your problem.
Sources:
https://tinycp.com/community/show/solved-print-req-error-i-o-error-dev-fd0-sector-0,43.html#sidebar
https://lists.debian.org/debian-user/2017/09/msg00866.html
answered Apr 26 at 11:01
Nicolas HannaNicolas Hanna
1051 gold badge3 silver badges13 bronze badges
add a comment
|
I kept getting this error, which made me boot into emergency mode and did not allow SSH/remote access.
I removed all custom /etc/fstab entries except the default ones. In my case I had entries to mount hard disks that were no longer plugged in, once I removed them I stopped getting that error. For reference, my error said the problem was with sr0, but I couldn't find a reference to sr0 in any logs/fdisk.
answered Jul 10 at 13:21
Corey BordersCorey Borders
11 silver badge2 bronze badges
add a comment
|
Why are you disabling the Floppy Drive? Why not just remove it from the VM's configuration?
I completely removed the Floppy Drive from the configuration of the VM. Time will tell if the error returns.
answered Sep 4 at 15:42
PapaJimPapaJim
1
add a comment
|
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1102580%2fprint-req-error-i-0-error%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Okay this worked for me!
If you have removed your swap file then ensure that in step 3. that you have commented out the swap file line (it will have 'swap' in the same line) and in step 4. comment out the first (and only)
Run this
dpkg-reconfigure initramfs-toolsand then restart and continuelsblk -fcommand, and note the UUID'sEnsure that the UUID's in this file is right
/etc/fstab--sudo nano /etc/fstabEnsure that the UUID's in this file is also right
/etc/initramfs-tools/conf.d/resume.--sudo nano /etc/initramfs-tools/conf.d/resume.Run
sudo update-initramfs -uand restart
Okay, I am no expert but this is how I fixed the problem and when I fixed this problem and it introduced another problem that should be fixed using these commands.
Please comment if this worked and especially if this didn't work so i know if it fixed (and answered) your problem.
Sources:
https://tinycp.com/community/show/solved-print-req-error-i-o-error-dev-fd0-sector-0,43.html#sidebar
https://lists.debian.org/debian-user/2017/09/msg00866.html
answered Apr 26 at 11:01
Nicolas HannaNicolas Hanna
1051 gold badge3 silver badges13 bronze badges
add a comment
|
Okay this worked for me!
If you have removed your swap file then ensure that in step 3. that you have commented out the swap file line (it will have 'swap' in the same line) and in step 4. comment out the first (and only)
Run this
dpkg-reconfigure initramfs-toolsand then restart and continuelsblk -fcommand, and note the UUID'sEnsure that the UUID's in this file is right
/etc/fstab--sudo nano /etc/fstabEnsure that the UUID's in this file is also right
/etc/initramfs-tools/conf.d/resume.--sudo nano /etc/initramfs-tools/conf.d/resume.Run
sudo update-initramfs -uand restart
Okay, I am no expert but this is how I fixed the problem and when I fixed this problem and it introduced another problem that should be fixed using these commands.
Please comment if this worked and especially if this didn't work so i know if it fixed (and answered) your problem.
Sources:
https://tinycp.com/community/show/solved-print-req-error-i-o-error-dev-fd0-sector-0,43.html#sidebar
https://lists.debian.org/debian-user/2017/09/msg00866.html
answered Apr 26 at 11:01
Nicolas HannaNicolas Hanna
1051 gold badge3 silver badges13 bronze badges
add a comment
|
Okay this worked for me!
If you have removed your swap file then ensure that in step 3. that you have commented out the swap file line (it will have 'swap' in the same line) and in step 4. comment out the first (and only)
Run this
dpkg-reconfigure initramfs-toolsand then restart and continuelsblk -fcommand, and note the UUID'sEnsure that the UUID's in this file is right
/etc/fstab--sudo nano /etc/fstabEnsure that the UUID's in this file is also right
/etc/initramfs-tools/conf.d/resume.--sudo nano /etc/initramfs-tools/conf.d/resume.Run
sudo update-initramfs -uand restart
Okay, I am no expert but this is how I fixed the problem and when I fixed this problem and it introduced another problem that should be fixed using these commands.
Please comment if this worked and especially if this didn't work so i know if it fixed (and answered) your problem.
Sources:
https://tinycp.com/community/show/solved-print-req-error-i-o-error-dev-fd0-sector-0,43.html#sidebar
https://lists.debian.org/debian-user/2017/09/msg00866.html
answered Apr 26 at 11:01
Nicolas HannaNicolas Hanna
1051 gold badge3 silver badges13 bronze badges
Okay this worked for me!
If you have removed your swap file then ensure that in step 3. that you have commented out the swap file line (it will have 'swap' in the same line) and in step 4. comment out the first (and only)
Run this
dpkg-reconfigure initramfs-toolsand then restart and continuelsblk -fcommand, and note the UUID'sEnsure that the UUID's in this file is right
/etc/fstab--sudo nano /etc/fstabEnsure that the UUID's in this file is also right
/etc/initramfs-tools/conf.d/resume.--sudo nano /etc/initramfs-tools/conf.d/resume.Run
sudo update-initramfs -uand restart
Okay, I am no expert but this is how I fixed the problem and when I fixed this problem and it introduced another problem that should be fixed using these commands.
Please comment if this worked and especially if this didn't work so i know if it fixed (and answered) your problem.
Sources:
https://tinycp.com/community/show/solved-print-req-error-i-o-error-dev-fd0-sector-0,43.html#sidebar
https://lists.debian.org/debian-user/2017/09/msg00866.html
answered Apr 26 at 11:01
Nicolas HannaNicolas Hanna
1051 gold badge3 silver badges13 bronze badges
answered Apr 26 at 11:01
Nicolas HannaNicolas Hanna
1051 gold badge3 silver badges13 bronze badges
answered Apr 26 at 11:01
Nicolas HannaNicolas Hanna
1051 gold badge3 silver badges13 bronze badges
answered Apr 26 at 11:01
Nicolas HannaNicolas Hanna
1051 gold badge3 silver badges13 bronze badges
1051 gold badge3 silver badges13 bronze badges
add a comment
|
add a comment
|
I kept getting this error, which made me boot into emergency mode and did not allow SSH/remote access.
I removed all custom /etc/fstab entries except the default ones. In my case I had entries to mount hard disks that were no longer plugged in, once I removed them I stopped getting that error. For reference, my error said the problem was with sr0, but I couldn't find a reference to sr0 in any logs/fdisk.
answered Jul 10 at 13:21
Corey BordersCorey Borders
11 silver badge2 bronze badges
add a comment
|
I kept getting this error, which made me boot into emergency mode and did not allow SSH/remote access.
I removed all custom /etc/fstab entries except the default ones. In my case I had entries to mount hard disks that were no longer plugged in, once I removed them I stopped getting that error. For reference, my error said the problem was with sr0, but I couldn't find a reference to sr0 in any logs/fdisk.
answered Jul 10 at 13:21
Corey BordersCorey Borders
11 silver badge2 bronze badges
add a comment
|
I kept getting this error, which made me boot into emergency mode and did not allow SSH/remote access.
I removed all custom /etc/fstab entries except the default ones. In my case I had entries to mount hard disks that were no longer plugged in, once I removed them I stopped getting that error. For reference, my error said the problem was with sr0, but I couldn't find a reference to sr0 in any logs/fdisk.
answered Jul 10 at 13:21
Corey BordersCorey Borders
11 silver badge2 bronze badges
I kept getting this error, which made me boot into emergency mode and did not allow SSH/remote access.
I removed all custom /etc/fstab entries except the default ones. In my case I had entries to mount hard disks that were no longer plugged in, once I removed them I stopped getting that error. For reference, my error said the problem was with sr0, but I couldn't find a reference to sr0 in any logs/fdisk.
answered Jul 10 at 13:21
Corey BordersCorey Borders
11 silver badge2 bronze badges
answered Jul 10 at 13:21
Corey BordersCorey Borders
11 silver badge2 bronze badges
answered Jul 10 at 13:21
Corey BordersCorey Borders
11 silver badge2 bronze badges
answered Jul 10 at 13:21
Corey BordersCorey Borders
11 silver badge2 bronze badges
11 silver badge2 bronze badges
add a comment
|
add a comment
|
Why are you disabling the Floppy Drive? Why not just remove it from the VM's configuration?
I completely removed the Floppy Drive from the configuration of the VM. Time will tell if the error returns.
answered Sep 4 at 15:42
PapaJimPapaJim
1
add a comment
|
Why are you disabling the Floppy Drive? Why not just remove it from the VM's configuration?
I completely removed the Floppy Drive from the configuration of the VM. Time will tell if the error returns.
answered Sep 4 at 15:42
PapaJimPapaJim
1
add a comment
|
Why are you disabling the Floppy Drive? Why not just remove it from the VM's configuration?
I completely removed the Floppy Drive from the configuration of the VM. Time will tell if the error returns.
answered Sep 4 at 15:42
PapaJimPapaJim
1
Why are you disabling the Floppy Drive? Why not just remove it from the VM's configuration?
I completely removed the Floppy Drive from the configuration of the VM. Time will tell if the error returns.
answered Sep 4 at 15:42
PapaJimPapaJim
1
answered Sep 4 at 15:42
PapaJimPapaJim
1
answered Sep 4 at 15:42
PapaJimPapaJim
1
answered Sep 4 at 15:42
PapaJimPapaJim
1
1
add a comment
|
add a comment
|
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1102580%2fprint-req-error-i-0-error%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Did you disable the Floppy drive in the VM's 'firmware' level? Otherwise it'll stil 'see' a floppy drive whether it exists or not in the VM. This is more or less how the BIOS reveals to the underlying system whether a device exists or not, and this
fd0problem is one I run into regularly on my VMs in VMware (I always boot to firmware and disable the floppy drive on first-run)– Thomas Ward♦
Dec 17 '18 at 15:28
This is happening to me too, I tried to comment out
/dev/fd0from /etc/fstab with no luck.– Nicolas Hanna
Apr 26 at 10:30