F5F Stay Refreshed Software Operating Systems Log file of the Linux kernel

Log file of the Linux kernel

Log file of the Linux kernel

W
Whovian_Jedi
Junior Member
5
04-28-2016, 07:49 AM
#1
I just saw a big portion of my SSD filled up. Check the kern.log here: 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 extra sense info 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 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 info 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 hard from wd. Any assistance would be appreciated
W
Whovian_Jedi
04-28-2016, 07:49 AM #1

I just saw a big portion of my SSD filled up. Check the kern.log here: 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 extra sense info 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 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 info 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 hard from wd. Any assistance would be appreciated

9
999GOT666
Member
174
05-16-2016, 05:27 PM
#2
This seems to be a problem with your setup.
9
999GOT666
05-16-2016, 05:27 PM #2

This seems to be a problem with your setup.

S
scize
Member
59
05-16-2016, 09:48 PM
#3
The latest update no longer impacts Linux, yet it's affecting you personally. Consider posting your concern in that discussion thread.
S
scize
05-16-2016, 09:48 PM #3

The latest update no longer impacts Linux, yet it's affecting you personally. Consider posting your concern in that discussion thread.

S
StyleTrick
Senior Member
744
05-16-2016, 10:26 PM
#4
It no longer impacts Linux in the way it once did, and Udisk appears to be the main cause. This interpretation is based on what I understand from the discussion. The problem has already been logged to udisks: https://bugs.freedesktop.org/show_bug.cgi?id=98991. Since it's already reported, there isn't much you can do. Try not to stress too much—it's just some unnecessary spam from the kernel, which may hide real issues. Reading the bug report further suggests a potential link to an Ubuntu kernel patch. Switching to a newer kernel or a non-stock version might help if you're concerned.
S
StyleTrick
05-16-2016, 10:26 PM #4

It no longer impacts Linux in the way it once did, and Udisk appears to be the main cause. This interpretation is based on what I understand from the discussion. The problem has already been logged to udisks: https://bugs.freedesktop.org/show_bug.cgi?id=98991. Since it's already reported, there isn't much you can do. Try not to stress too much—it's just some unnecessary spam from the kernel, which may hide real issues. Reading the bug report further suggests a potential link to an Ubuntu kernel patch. Switching to a newer kernel or a non-stock version might help if you're concerned.

V
Velizar06
Posting Freak
865
05-16-2016, 11:22 PM
#5
The main concern is SSD durability. You can create a system link and transfer /var/log to your ZFS pool.
V
Velizar06
05-16-2016, 11:22 PM #5

The main concern is SSD durability. You can create a system link and transfer /var/log to your ZFS pool.

M
Mieste
Junior Member
14
05-24-2016, 03:15 AM
#6
It wouldn't be a big concern about the writes on the SSD. Compared to what Windows does, it's almost nothing. Linux will handle links just fine or even better, adding an entry in /etc/fstab would likely be the better choice. If you're really keen, you could halt the logging service if you don't mind skipping logs. It would be nice to see your system act strangely and then stop it—like stopping rsyslog with sudo systemctl stop rsyslog.service and disabling it with sudo systemctl disable rsyslog.service.
M
Mieste
05-24-2016, 03:15 AM #6

It wouldn't be a big concern about the writes on the SSD. Compared to what Windows does, it's almost nothing. Linux will handle links just fine or even better, adding an entry in /etc/fstab would likely be the better choice. If you're really keen, you could halt the logging service if you don't mind skipping logs. It would be nice to see your system act strangely and then stop it—like stopping rsyslog with sudo systemctl stop rsyslog.service and disabling it with sudo systemctl disable rsyslog.service.

P
178
05-24-2016, 04:01 AM
#7
It's reassuring you're aware of the write process, but I'm concerned about the unexpected appearance of a 60GB log file.
P
ProSkillsNinja
05-24-2016, 04:01 AM #7

It's reassuring you're aware of the write process, but I'm concerned about the unexpected appearance of a 60GB log file.

N
Nero12321
Posting Freak
858
06-03-2016, 01:37 PM
#8
60GB seems a bit too much. Consider using a log rotator to trim the storage and let it automatically remove old files, keeping only the latest 100MB or so. Checking the HDD activity light on Windows versus Linux will give you a clear idea of what’s going on.
N
Nero12321
06-03-2016, 01:37 PM #8

60GB seems a bit too much. Consider using a log rotator to trim the storage and let it automatically remove old files, keeping only the latest 100MB or so. Checking the HDD activity light on Windows versus Linux will give you a clear idea of what’s going on.

2
2ciniseb2
Junior Member
42
06-03-2016, 05:18 PM
#9
The issue involves the program generating new lines every five minutes, which may indicate a performance slowdown.
2
2ciniseb2
06-03-2016, 05:18 PM #9

The issue involves the program generating new lines every five minutes, which may indicate a performance slowdown.

_
_pawol_
Member
102
06-03-2016, 07:40 PM
#10
Logs indicate performance drop. Reading rate at 390 ch/5min slows to 4.6 KB/h. Storage usage rising steadily. No further data available. System may be experiencing hardware issues.
_
_pawol_
06-03-2016, 07:40 PM #10

Logs indicate performance drop. Reading rate at 390 ch/5min slows to 4.6 KB/h. Storage usage rising steadily. No further data available. System may be experiencing hardware issues.