Read error on swap device

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
5
down vote

favorite
3












After a long suspended session my system gives me this message Read-error on swap-device (8:0:441040) (this is the last one received). It reboots in some way, because there are not more programs opened by me before the suspension, it's pratically a new user session. I searched bad sectors in swap partition with badblocks command but everything seems fine, recently i've incremented my swap but seems that the two things are not related because i got the error messagge even before the size incrementation process. I've already: changed the UUID in the fstab file after the incrementation (just to be sure), reformatted the swap partition, looked for bad sectors, i don't know what to do now. Another thing, in this moment my system mounts arch, but this is a problem that i didn't have before with other distros.







share|improve this question



















  • Is the swap partition large enough to hold all available RAM?
    – Kusalananda
    Apr 28 at 7:49










  • Yes. I did the incrementation because of the previous size, porting the amount of space from 1GB to 8GB (my ram is 4GB)
    – Bit'o
    Apr 28 at 8:13






  • 1




    I noticed that the passed time between the activation of suspend session and reactivation of the system affects in some way this issue. After 2-3 hours of suspended session i can resume correctly the user session, but after 10 hours circa i get the error message. I think that even the number of programs opened can be a variable.
    – Bit'o
    Apr 28 at 9:54














up vote
5
down vote

favorite
3












After a long suspended session my system gives me this message Read-error on swap-device (8:0:441040) (this is the last one received). It reboots in some way, because there are not more programs opened by me before the suspension, it's pratically a new user session. I searched bad sectors in swap partition with badblocks command but everything seems fine, recently i've incremented my swap but seems that the two things are not related because i got the error messagge even before the size incrementation process. I've already: changed the UUID in the fstab file after the incrementation (just to be sure), reformatted the swap partition, looked for bad sectors, i don't know what to do now. Another thing, in this moment my system mounts arch, but this is a problem that i didn't have before with other distros.







share|improve this question



















  • Is the swap partition large enough to hold all available RAM?
    – Kusalananda
    Apr 28 at 7:49










  • Yes. I did the incrementation because of the previous size, porting the amount of space from 1GB to 8GB (my ram is 4GB)
    – Bit'o
    Apr 28 at 8:13






  • 1




    I noticed that the passed time between the activation of suspend session and reactivation of the system affects in some way this issue. After 2-3 hours of suspended session i can resume correctly the user session, but after 10 hours circa i get the error message. I think that even the number of programs opened can be a variable.
    – Bit'o
    Apr 28 at 9:54












up vote
5
down vote

favorite
3









up vote
5
down vote

favorite
3






3





After a long suspended session my system gives me this message Read-error on swap-device (8:0:441040) (this is the last one received). It reboots in some way, because there are not more programs opened by me before the suspension, it's pratically a new user session. I searched bad sectors in swap partition with badblocks command but everything seems fine, recently i've incremented my swap but seems that the two things are not related because i got the error messagge even before the size incrementation process. I've already: changed the UUID in the fstab file after the incrementation (just to be sure), reformatted the swap partition, looked for bad sectors, i don't know what to do now. Another thing, in this moment my system mounts arch, but this is a problem that i didn't have before with other distros.







share|improve this question











After a long suspended session my system gives me this message Read-error on swap-device (8:0:441040) (this is the last one received). It reboots in some way, because there are not more programs opened by me before the suspension, it's pratically a new user session. I searched bad sectors in swap partition with badblocks command but everything seems fine, recently i've incremented my swap but seems that the two things are not related because i got the error messagge even before the size incrementation process. I've already: changed the UUID in the fstab file after the incrementation (just to be sure), reformatted the swap partition, looked for bad sectors, i don't know what to do now. Another thing, in this moment my system mounts arch, but this is a problem that i didn't have before with other distros.









share|improve this question










share|improve this question




share|improve this question









asked Apr 28 at 6:25









Bit'o

334




334











  • Is the swap partition large enough to hold all available RAM?
    – Kusalananda
    Apr 28 at 7:49










  • Yes. I did the incrementation because of the previous size, porting the amount of space from 1GB to 8GB (my ram is 4GB)
    – Bit'o
    Apr 28 at 8:13






  • 1




    I noticed that the passed time between the activation of suspend session and reactivation of the system affects in some way this issue. After 2-3 hours of suspended session i can resume correctly the user session, but after 10 hours circa i get the error message. I think that even the number of programs opened can be a variable.
    – Bit'o
    Apr 28 at 9:54
















  • Is the swap partition large enough to hold all available RAM?
    – Kusalananda
    Apr 28 at 7:49










  • Yes. I did the incrementation because of the previous size, porting the amount of space from 1GB to 8GB (my ram is 4GB)
    – Bit'o
    Apr 28 at 8:13






  • 1




    I noticed that the passed time between the activation of suspend session and reactivation of the system affects in some way this issue. After 2-3 hours of suspended session i can resume correctly the user session, but after 10 hours circa i get the error message. I think that even the number of programs opened can be a variable.
    – Bit'o
    Apr 28 at 9:54















Is the swap partition large enough to hold all available RAM?
– Kusalananda
Apr 28 at 7:49




Is the swap partition large enough to hold all available RAM?
– Kusalananda
Apr 28 at 7:49












Yes. I did the incrementation because of the previous size, porting the amount of space from 1GB to 8GB (my ram is 4GB)
– Bit'o
Apr 28 at 8:13




Yes. I did the incrementation because of the previous size, porting the amount of space from 1GB to 8GB (my ram is 4GB)
– Bit'o
Apr 28 at 8:13




1




1




I noticed that the passed time between the activation of suspend session and reactivation of the system affects in some way this issue. After 2-3 hours of suspended session i can resume correctly the user session, but after 10 hours circa i get the error message. I think that even the number of programs opened can be a variable.
– Bit'o
Apr 28 at 9:54




I noticed that the passed time between the activation of suspend session and reactivation of the system affects in some way this issue. After 2-3 hours of suspended session i can resume correctly the user session, but after 10 hours circa i get the error message. I think that even the number of programs opened can be a variable.
– Bit'o
Apr 28 at 9:54










1 Answer
1






active

oldest

votes

















up vote
1
down vote



accepted










There is a bug which matches everything you describe (including the separate comments when I wrote this answer). The bug was introduced in upstream kernel v4.14, which was fixed in v4.17 and v4.16.8.



https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.16.y&id=7859056bc73dea2c3714b00c83b253d4c22bf7b6



If you still do not have a new enough kernel, and you don't want to install an older kernel (switch to the linux-lts package mentioned in the Arch thread below?), there is a workaround. You can add the option "scsi_mod.scan=sync" to the end of your kernel command line, e.g. in GRUB.



The original Arch forum thread on it is here:



https://bbs.archlinux.org/viewtopic.php?id=235027



"Read-error on swap-device" during resume is a possible signature for this error (but this error message could be caused by other things, and most of the time this crash was quite silent, at least for me). For examples where this message happened, see:



https://askubuntu.com/questions/1035208/ubuntu-18-04-error-on-waking-up-from-sleep-read-error-on-swap-device/



https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c29






share|improve this answer























  • I really appreciate your help, a lot of usefull informations, but right now i don't have the chance to recreate the environment for test your solution (that solve what was my problem). Again, thanks for your time
    – Bit'o
    Jul 21 at 18:13










Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f440540%2fread-error-on-swap-device%23new-answer', 'question_page');

);

Post as a guest






























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
1
down vote



accepted










There is a bug which matches everything you describe (including the separate comments when I wrote this answer). The bug was introduced in upstream kernel v4.14, which was fixed in v4.17 and v4.16.8.



https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.16.y&id=7859056bc73dea2c3714b00c83b253d4c22bf7b6



If you still do not have a new enough kernel, and you don't want to install an older kernel (switch to the linux-lts package mentioned in the Arch thread below?), there is a workaround. You can add the option "scsi_mod.scan=sync" to the end of your kernel command line, e.g. in GRUB.



The original Arch forum thread on it is here:



https://bbs.archlinux.org/viewtopic.php?id=235027



"Read-error on swap-device" during resume is a possible signature for this error (but this error message could be caused by other things, and most of the time this crash was quite silent, at least for me). For examples where this message happened, see:



https://askubuntu.com/questions/1035208/ubuntu-18-04-error-on-waking-up-from-sleep-read-error-on-swap-device/



https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c29






share|improve this answer























  • I really appreciate your help, a lot of usefull informations, but right now i don't have the chance to recreate the environment for test your solution (that solve what was my problem). Again, thanks for your time
    – Bit'o
    Jul 21 at 18:13














up vote
1
down vote



accepted










There is a bug which matches everything you describe (including the separate comments when I wrote this answer). The bug was introduced in upstream kernel v4.14, which was fixed in v4.17 and v4.16.8.



https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.16.y&id=7859056bc73dea2c3714b00c83b253d4c22bf7b6



If you still do not have a new enough kernel, and you don't want to install an older kernel (switch to the linux-lts package mentioned in the Arch thread below?), there is a workaround. You can add the option "scsi_mod.scan=sync" to the end of your kernel command line, e.g. in GRUB.



The original Arch forum thread on it is here:



https://bbs.archlinux.org/viewtopic.php?id=235027



"Read-error on swap-device" during resume is a possible signature for this error (but this error message could be caused by other things, and most of the time this crash was quite silent, at least for me). For examples where this message happened, see:



https://askubuntu.com/questions/1035208/ubuntu-18-04-error-on-waking-up-from-sleep-read-error-on-swap-device/



https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c29






share|improve this answer























  • I really appreciate your help, a lot of usefull informations, but right now i don't have the chance to recreate the environment for test your solution (that solve what was my problem). Again, thanks for your time
    – Bit'o
    Jul 21 at 18:13












up vote
1
down vote



accepted







up vote
1
down vote



accepted






There is a bug which matches everything you describe (including the separate comments when I wrote this answer). The bug was introduced in upstream kernel v4.14, which was fixed in v4.17 and v4.16.8.



https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.16.y&id=7859056bc73dea2c3714b00c83b253d4c22bf7b6



If you still do not have a new enough kernel, and you don't want to install an older kernel (switch to the linux-lts package mentioned in the Arch thread below?), there is a workaround. You can add the option "scsi_mod.scan=sync" to the end of your kernel command line, e.g. in GRUB.



The original Arch forum thread on it is here:



https://bbs.archlinux.org/viewtopic.php?id=235027



"Read-error on swap-device" during resume is a possible signature for this error (but this error message could be caused by other things, and most of the time this crash was quite silent, at least for me). For examples where this message happened, see:



https://askubuntu.com/questions/1035208/ubuntu-18-04-error-on-waking-up-from-sleep-read-error-on-swap-device/



https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c29






share|improve this answer















There is a bug which matches everything you describe (including the separate comments when I wrote this answer). The bug was introduced in upstream kernel v4.14, which was fixed in v4.17 and v4.16.8.



https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.16.y&id=7859056bc73dea2c3714b00c83b253d4c22bf7b6



If you still do not have a new enough kernel, and you don't want to install an older kernel (switch to the linux-lts package mentioned in the Arch thread below?), there is a workaround. You can add the option "scsi_mod.scan=sync" to the end of your kernel command line, e.g. in GRUB.



The original Arch forum thread on it is here:



https://bbs.archlinux.org/viewtopic.php?id=235027



"Read-error on swap-device" during resume is a possible signature for this error (but this error message could be caused by other things, and most of the time this crash was quite silent, at least for me). For examples where this message happened, see:



https://askubuntu.com/questions/1035208/ubuntu-18-04-error-on-waking-up-from-sleep-read-error-on-swap-device/



https://bugzilla.redhat.com/show_bug.cgi?id=1553979#c29







share|improve this answer















share|improve this answer



share|improve this answer








edited Jul 20 at 14:54


























answered Jul 20 at 14:48









sourcejedi

18.3k32475




18.3k32475











  • I really appreciate your help, a lot of usefull informations, but right now i don't have the chance to recreate the environment for test your solution (that solve what was my problem). Again, thanks for your time
    – Bit'o
    Jul 21 at 18:13
















  • I really appreciate your help, a lot of usefull informations, but right now i don't have the chance to recreate the environment for test your solution (that solve what was my problem). Again, thanks for your time
    – Bit'o
    Jul 21 at 18:13















I really appreciate your help, a lot of usefull informations, but right now i don't have the chance to recreate the environment for test your solution (that solve what was my problem). Again, thanks for your time
– Bit'o
Jul 21 at 18:13




I really appreciate your help, a lot of usefull informations, but right now i don't have the chance to recreate the environment for test your solution (that solve what was my problem). Again, thanks for your time
– Bit'o
Jul 21 at 18:13












 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f440540%2fread-error-on-swap-device%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

How to check contact read email or not when send email to Individual?

Bahrain

Postfix configuration issue with fips on centos 7; mailgun relay