Jump to content

Linux kern.log

I just noticed a large chunk of my ssd was filled up turned out to the kern.log here is the tail

 

tail -f /var/log/kern.log
Sep 13 18:39:53 Mothership kernel: [267075.823671] sd 9:0:0:0: [sdd] tag#0 Add. Sense: No additional sense information
Sep 13 18:39:53 Mothership kernel: [267075.823674] sd 9:0:0:0: [sdd] tag#0 CDB: ATA command pass through(12)/Blank a1 06 20 da 00 00 4f c2 00 b0 00 00
Sep 13 18:49:47 Mothership kernel: [267669.294048] sd 9:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
Sep 13 18:49:47 Mothership kernel: [267669.294054] sd 9:0:0:0: [sdd] tag#0 Sense Key : Hardware Error [current] [descriptor] 
Sep 13 18:49:47 Mothership kernel: [267669.294057] sd 9:0:0:0: [sdd] tag#0 Add. Sense: No additional sense information
Sep 13 18:49:47 Mothership kernel: [267669.294063] sd 9:0:0:0: [sdd] tag#0 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
Sep 13 18:49:47 Mothership kernel: [267669.842253] sd 9:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
Sep 13 18:49:47 Mothership kernel: [267669.842258] sd 9:0:0:0: [sdd] tag#0 Sense Key : Hardware Error [current] [descriptor] 
Sep 13 18:49:47 Mothership kernel: [267669.842261] sd 9:0:0:0: [sdd] tag#0 Add. Sense: No additional sense information
Sep 13 18:49:47 Mothership kernel: [267669.842265] sd 9:0:0:0: [sdd] tag#0 CDB: ATA command pass through(12)/Blank a1 06 20 da 00 00 4f c2 00 b0 00 00

ubuntu 17

amd 8350

gb 990fx mb

8gb ram

7770

 

from what I can see [sdd] is an external hd from wd. any help would be good 

                     ¸„»°'´¸„»°'´ Vorticalbox `'°«„¸`'°«„¸
`'°«„¸¸„»°'´¸„»°'´`'°«„¸Scientia Potentia est  ¸„»°'´`'°«„¸`'°«„¸¸„»°'´

Link to comment
Share on other sites

Link to post
Share on other sites

2 hours ago, AustinJ said:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618678

 

That is probably your issue there.

the last post says it no longer effect Linux but it is effecting me. Should I report it on that thread?

                     ¸„»°'´¸„»°'´ Vorticalbox `'°«„¸`'°«„¸
`'°«„¸¸„»°'´¸„»°'´`'°«„¸Scientia Potentia est  ¸„»°'´`'°«„¸`'°«„¸¸„»°'´

Link to comment
Share on other sites

Link to post
Share on other sites

4 hours ago, vorticalbox said:

the last post says it no longer effect Linux but it is effecting me. Should I report it on that thread?

No longer effects Linux in a sense that it is not the cause of it. Udisk seems to be the culprit. At least that is how I interpret what is said. The issue seems to have got reported to udisks instead here: https://bugs.freedesktop.org/show_bug.cgi?id=98991. It is already reported so there isn't too much you can do. Don't worry about it too much. It is just some kernel spam as far as you care but it will mask real errors with its spam. Reading the bug report for udisks some more it does appear to be an issue with one of Ubuntu's kernel patches so switching kernels to a more modern one or a non-stock kernel may resolve the issue if you are too worried about it.

 

Link to comment
Share on other sites

Link to post
Share on other sites

11 hours ago, AustinJ said:

No longer effects Linux in a sense that it is not the cause of it. Udisk seems to be the culprit. At least that is how I interpret what is said. The issue seems to have got reported to udisks instead here: https://bugs.freedesktop.org/show_bug.cgi?id=98991. It is already reported so there isn't too much you can do. Don't worry about it too much. It is just some kernel spam as far as you care but it will mask real errors with its spam. Reading the bug report for udisks some more it does appear to be an issue with one of Ubuntu's kernel patches so switching kernels to a more modern one or a non-stock kernel may resolve the issue if you are too worried about it.

 

the only part I'm worried about is SSD health, can I make an sys link and move /var/log to my zfs pool?

                     ¸„»°'´¸„»°'´ Vorticalbox `'°«„¸`'°«„¸
`'°«„¸¸„»°'´¸„»°'´`'°«„¸Scientia Potentia est  ¸„»°'´`'°«„¸`'°«„¸¸„»°'´

Link to comment
Share on other sites

Link to post
Share on other sites

3 hours ago, vorticalbox said:

the only part I'm worried about is SSD health, can I make an sys link and move /var/log to my zfs pool?

Wouldn't be too worried about the writes on the ssd. Compared to what Windows does it is nothing. Linux will follow links just fine or better yet adding a line in /etc/fstab would probably be the better option. If you really wanted to you could stop the logging daemon if you really don't care for logs. Now it would be nice to have if your system decides to start do funny things.

sudo systemctl stop rsyslog.service
sudo systemctl disable rsyslog.service

 

Link to comment
Share on other sites

Link to post
Share on other sites

1 minute ago, AustinJ said:

Wouldn't be too worried about the writes on the ssd. Compared to what Windows does it is nothing. Linux will follow links just fine or better yet adding a line in /etc/fstab would probably be the better option. If you really wanted to you could stop the logging daemon if you really don't care for logs. Now it would be nice to have if your system decides to start do funny things.


sudo systemctl stop rsyslog.service
sudo systemctl disable rsyslog.service

 

That's good to know about the writes, just worried me that there was suddenly a 60GB log file :/

                     ¸„»°'´¸„»°'´ Vorticalbox `'°«„¸`'°«„¸
`'°«„¸¸„»°'´¸„»°'´`'°«„¸Scientia Potentia est  ¸„»°'´`'°«„¸`'°«„¸¸„»°'´

Link to comment
Share on other sites

Link to post
Share on other sites

9 hours ago, vorticalbox said:

That's good to know about the writes, just worried me that there was suddenly a 60GB log file :/

60GB is a bit excessive... You could look into a log rotator to keep the log slimmed down and just have it delete the old parts, so you would only have the newest 100mb or something. The windows thing, just look at the hdd activity light of a windows machine vs a linux machine that'll tell you enough...

Link to comment
Share on other sites

Link to post
Share on other sites

7 hours ago, AustinJ said:

60GB is a bit excessive... You could look into a log rotator to keep the log slimmed down and just have it delete the old parts, so you would only have the newest 100mb or something. The windows thing, just look at the hdd activity light of a windows machine vs a linux machine that'll tell you enough...

problem is that bug is adding new lines every 5 mins :/ I seem to have slowed down now.

                     ¸„»°'´¸„»°'´ Vorticalbox `'°«„¸`'°«„¸
`'°«„¸¸„»°'´¸„»°'´`'°«„¸Scientia Potentia est  ¸„»°'´`'°«„¸`'°«„¸¸„»°'´

Link to comment
Share on other sites

Link to post
Share on other sites

6 hours ago, vorticalbox said:

problem is that bug is adding new lines every 5 mins :/ I seem to have slowed down now.

At 390 characters every 5 minutes, 4.6 KB/h, 109 KB/d, 2.2 MB/m, 26.4MB/y

I think something else filled your logs or it has really slowed because this is only 390 characters:

Sep 13 18:49:47 Mothership kernel: [267669.842258] sd 9:0:0:0: [sdd] tag#0 Sense Key : Hardware Error [current] [descriptor] 
Sep 13 18:49:47 Mothership kernel: [267669.842261] sd 9:0:0:0: [sdd] tag#0 Add. Sense: No additional sense information
Sep 13 18:49:47 Mothership kernel: [267669.842265] sd 9:0:0:0: [sdd] tag#0 CDB: ATA command pass through(12)/Blank a1 06 20 da 00 00 4f c2 00 b0 00 00

 

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×