File system not responsive for short time after boot

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








up vote
0
down vote

favorite












my question concerns Ubuntu 16.04.



After every boot I can view my folders and files on my HDD as intended.
After 1 min of proper usage the file system becomes unresponsive for around 25 seconds. Then it works fine again infinitely.



How can I reach to the source of this issue? Any suggestions?



Just tell me if I should add any more information regarding my setup.










share|improve this question





















  • Sounds like an @reboot cronjob to me. Have you tried System Monitor? The Processes tab has various disk columns (r/w). Perhaps you can see there which process does the disk I/O.
    – PerlDuck
    Mar 18 at 11:19











  • What is the output of dmesg command
    – Debian_yadav
    Mar 18 at 11:20










  • Welcome to Ask Ubuntu! :-) What is the output of sudo smartctl --all /dev/sda If sudo: smartctl: command not found type sudo apt install smartmontools and try again.
    – Fabby
    Mar 18 at 12:11










  • Thank you all for your quick answers! With the help of @PerlDuck I saw that megasync required a lot of disk space. And this is already the cause for the unresponsiveness: It seems like my cloud sync program has to initialize (check) all corresponding directories. Guess I cannot solve it, I just have to be patient after a boot :)
    – Chris
    Mar 18 at 12:21











  • You may have a look at ionice. It can throttle a program's I/O greediness so that other processes aren't affected too much.
    – PerlDuck
    Mar 18 at 13:02














up vote
0
down vote

favorite












my question concerns Ubuntu 16.04.



After every boot I can view my folders and files on my HDD as intended.
After 1 min of proper usage the file system becomes unresponsive for around 25 seconds. Then it works fine again infinitely.



How can I reach to the source of this issue? Any suggestions?



Just tell me if I should add any more information regarding my setup.










share|improve this question





















  • Sounds like an @reboot cronjob to me. Have you tried System Monitor? The Processes tab has various disk columns (r/w). Perhaps you can see there which process does the disk I/O.
    – PerlDuck
    Mar 18 at 11:19











  • What is the output of dmesg command
    – Debian_yadav
    Mar 18 at 11:20










  • Welcome to Ask Ubuntu! :-) What is the output of sudo smartctl --all /dev/sda If sudo: smartctl: command not found type sudo apt install smartmontools and try again.
    – Fabby
    Mar 18 at 12:11










  • Thank you all for your quick answers! With the help of @PerlDuck I saw that megasync required a lot of disk space. And this is already the cause for the unresponsiveness: It seems like my cloud sync program has to initialize (check) all corresponding directories. Guess I cannot solve it, I just have to be patient after a boot :)
    – Chris
    Mar 18 at 12:21











  • You may have a look at ionice. It can throttle a program's I/O greediness so that other processes aren't affected too much.
    – PerlDuck
    Mar 18 at 13:02












up vote
0
down vote

favorite









up vote
0
down vote

favorite











my question concerns Ubuntu 16.04.



After every boot I can view my folders and files on my HDD as intended.
After 1 min of proper usage the file system becomes unresponsive for around 25 seconds. Then it works fine again infinitely.



How can I reach to the source of this issue? Any suggestions?



Just tell me if I should add any more information regarding my setup.










share|improve this question













my question concerns Ubuntu 16.04.



After every boot I can view my folders and files on my HDD as intended.
After 1 min of proper usage the file system becomes unresponsive for around 25 seconds. Then it works fine again infinitely.



How can I reach to the source of this issue? Any suggestions?



Just tell me if I should add any more information regarding my setup.







16.04 boot hard-drive filesystem






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 18 at 11:11









Chris

1




1











  • Sounds like an @reboot cronjob to me. Have you tried System Monitor? The Processes tab has various disk columns (r/w). Perhaps you can see there which process does the disk I/O.
    – PerlDuck
    Mar 18 at 11:19











  • What is the output of dmesg command
    – Debian_yadav
    Mar 18 at 11:20










  • Welcome to Ask Ubuntu! :-) What is the output of sudo smartctl --all /dev/sda If sudo: smartctl: command not found type sudo apt install smartmontools and try again.
    – Fabby
    Mar 18 at 12:11










  • Thank you all for your quick answers! With the help of @PerlDuck I saw that megasync required a lot of disk space. And this is already the cause for the unresponsiveness: It seems like my cloud sync program has to initialize (check) all corresponding directories. Guess I cannot solve it, I just have to be patient after a boot :)
    – Chris
    Mar 18 at 12:21











  • You may have a look at ionice. It can throttle a program's I/O greediness so that other processes aren't affected too much.
    – PerlDuck
    Mar 18 at 13:02
















  • Sounds like an @reboot cronjob to me. Have you tried System Monitor? The Processes tab has various disk columns (r/w). Perhaps you can see there which process does the disk I/O.
    – PerlDuck
    Mar 18 at 11:19











  • What is the output of dmesg command
    – Debian_yadav
    Mar 18 at 11:20










  • Welcome to Ask Ubuntu! :-) What is the output of sudo smartctl --all /dev/sda If sudo: smartctl: command not found type sudo apt install smartmontools and try again.
    – Fabby
    Mar 18 at 12:11










  • Thank you all for your quick answers! With the help of @PerlDuck I saw that megasync required a lot of disk space. And this is already the cause for the unresponsiveness: It seems like my cloud sync program has to initialize (check) all corresponding directories. Guess I cannot solve it, I just have to be patient after a boot :)
    – Chris
    Mar 18 at 12:21











  • You may have a look at ionice. It can throttle a program's I/O greediness so that other processes aren't affected too much.
    – PerlDuck
    Mar 18 at 13:02















Sounds like an @reboot cronjob to me. Have you tried System Monitor? The Processes tab has various disk columns (r/w). Perhaps you can see there which process does the disk I/O.
– PerlDuck
Mar 18 at 11:19





Sounds like an @reboot cronjob to me. Have you tried System Monitor? The Processes tab has various disk columns (r/w). Perhaps you can see there which process does the disk I/O.
– PerlDuck
Mar 18 at 11:19













What is the output of dmesg command
– Debian_yadav
Mar 18 at 11:20




What is the output of dmesg command
– Debian_yadav
Mar 18 at 11:20












Welcome to Ask Ubuntu! :-) What is the output of sudo smartctl --all /dev/sda If sudo: smartctl: command not found type sudo apt install smartmontools and try again.
– Fabby
Mar 18 at 12:11




Welcome to Ask Ubuntu! :-) What is the output of sudo smartctl --all /dev/sda If sudo: smartctl: command not found type sudo apt install smartmontools and try again.
– Fabby
Mar 18 at 12:11












Thank you all for your quick answers! With the help of @PerlDuck I saw that megasync required a lot of disk space. And this is already the cause for the unresponsiveness: It seems like my cloud sync program has to initialize (check) all corresponding directories. Guess I cannot solve it, I just have to be patient after a boot :)
– Chris
Mar 18 at 12:21





Thank you all for your quick answers! With the help of @PerlDuck I saw that megasync required a lot of disk space. And this is already the cause for the unresponsiveness: It seems like my cloud sync program has to initialize (check) all corresponding directories. Guess I cannot solve it, I just have to be patient after a boot :)
– Chris
Mar 18 at 12:21













You may have a look at ionice. It can throttle a program's I/O greediness so that other processes aren't affected too much.
– PerlDuck
Mar 18 at 13:02




You may have a look at ionice. It can throttle a program's I/O greediness so that other processes aren't affected too much.
– PerlDuck
Mar 18 at 13:02















active

oldest

votes











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',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2faskubuntu.com%2fquestions%2f1016969%2ffile-system-not-responsive-for-short-time-after-boot%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1016969%2ffile-system-not-responsive-for-short-time-after-boot%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

GRUB: Fatal! inconsistent data read from (0x84) 0+xxxxxx

`kcmshell` modules relation with `/usr/share/applications`

How to enroll fingerprints to Ubuntu 17.10 with VFS491