isopropyl
Contributor
- Joined
- Jan 29, 2022
- Messages
- 159
I'm curious about some of the messages in my console. If anything is concerning or not. Or if anything should attempted to be resolved, and if so some guidance.
Generic rundown of my setup:
- it's a TrueNAS Core (TrueNAS-13.0-U5.3) server with a Supermicro motherboard, in a Supermicro 4U chassis (I think it's a 48 drive chassis).
- AMD EPYC 7401P CPU, 64gb ECC RAM.
- All my drives are mirrors of 2. 7 vdevs. 1 storage pool.
- I have 1 ethernet link (igb1) running from the NAS to my firewall.
- I have the pool mounted to my main desktop ("DESKTOPPC") over Samba, and I also have an iSCSI share mounted on that pc for games.
Some of the lines from the console are:
Questions:
So I keep seeing the link state issues. And no ping replies. This is to my desktop pc. I assume this is related to ISCSI or SMB. However, the computer has been running this entire time. I don't notice any active issues when playing games. I mean the games are stored on the NAS. So I assume if it was dropping connections it would completely freeze or something. I could be wrong. I do notice some packet loss here or there in online games. Granted I can't really confirm if that is just because it is running over a 1gbps local link and not 10g. Or just the game's servers, or what. I don't really notice much issues in single player games. Everything seems smooth. But if it is dropping connections, I would like to resolve it if it is not normal.
Second, the smartd messages saying it's not capable of a long self-test. I have all my drives setup on a cron to do a short test, and a long test. I am curious why these would not be capable of a long self-test? Is it just the hard drives software? I am not sure if they are the exact same model as all the other hard drives. I thought so, but maybe not. I bought them used, don't have the time to pull them all out and check everyone atm.
Thirdly, those CAM SCSI status errors. Seem potentially critical?
Overall, I see no warning messages, when running zpool status -v
Generic rundown of my setup:
- it's a TrueNAS Core (TrueNAS-13.0-U5.3) server with a Supermicro motherboard, in a Supermicro 4U chassis (I think it's a 48 drive chassis).
- AMD EPYC 7401P CPU, 64gb ECC RAM.
- All my drives are mirrors of 2. 7 vdevs. 1 storage pool.
- I have 1 ethernet link (igb1) running from the NAS to my firewall.
- I have the pool mounted to my main desktop ("DESKTOPPC") over Samba, and I also have an iSCSI share mounted on that pc for games.
Some of the lines from the console are:
Code:
Jul 29 21:44:48 kernel: igb1: link state changed to UP Jul 29 21:45:04 kernel: bridge0: Ethernet address: [redacted] Jul 29 21:45:04 kernel: igb1: link state changed to DOWN Jul 29 21:45:04 kernel: bridge0: link state changed to UP Jul 29 21:45:04 kernel: igb1: promiscuous mode enabled Jul 29 21:45:04 kernel: epair0a: Ethernet address: [redacted] Jul 29 21:45:04 kernel: epair0b: Ethernet address: [redacted] Jul 29 21:45:04 kernel: epair0a: link state changed to UP Jul 29 21:45:04 kernel: epair0b: link state changed to UP Jul 29 21:45:04 kernel: epair0a: changing name to 'vnet0.1' Jul 29 21:45:05 kernel: vnet0.1: promiscuous mode enabled Jul 29 21:45:07 kernel: lo0: link state changed to UP Jul 29 21:45:08 WARNING: (DESKTOPPC): no ping reply (NOP-Out) after 5 seconds; dropping connection Jul 29 21:45:09 kernel: igb1: link state changed to UP Jul 30 00:00:00 syslog-ng[2349]: Configuration reload request received, reloading configuration; Jul 30 00:00:00 syslog-ng[2349]: Configuration reload finished; Jul 30 02:48:31 WARNING: DESKTOPPC no ping reply (NOP-Out) after 5 seconds; dropping connection Jul 30 10:56:23 (da13:mpr0:0:28:0): READ(16). CDB: 88 00 00 00 00 01 37 1c 1d 70 00 00 01 60 00 00 Jul 30 10:56:23 (da13:mpr0:0:28:0): CAM status: SCSI Status Error Jul 30 10:56:23 (da13:mpr0:0:28:0): SCSI status: Check Condition Jul 30 10:56:23 (da13:mpr0:0:28:0): SCSI sense: ABORTED COMMAND asc:4b,4 (NAK received) Jul 30 10:56:23 (da13:mpr0:0:28:0): Descriptor 0x80: f5 50 Jul 30 10:56:23 (da13:mpr0:0:28:0): Descriptor 0x81: 00 00 00 00 00 00 Jul 30 10:56:23 (da13:mpr0:0:28:0): Retrying command (per sense data) Jul 30 11:03:01 WARNING: (DESKTOPPC): no ping reply (NOP-Out) after 5 seconds; dropping connection Jul 30 11:45:00 WARNING: (DESKTOPPC): no ping reply (NOP-Out) after 5 seconds; dropping connection Jul 30 11:48:00 WARNING: (DESKTOPPC): no ping reply (NOP-Out) after 5 seconds; dropping connection Jul 30 14:52:30 (da4:mpr0:0:19:0): READ(10). CDB: 28 00 7a 2c 91 b8 00 00 10 00 Jul 30 14:52:30 (da4:mpr0:0:19:0): CAM status: SCSI Status Error Jul 30 14:52:30 (da4:mpr0:0:19:0): SCSI status: Check Condition Jul 30 14:52:30 (da4:mpr0:0:19:0): SCSI sense: ABORTED COMMAND asc:4b,4 (NAK received) Jul 30 14:52:30 (da4:mpr0:0:19:0): Command Specific Info: 0 Jul 30 14:52:30 (da4:mpr0:0:19:0): Descriptor 0x80: f5 50 Jul 30 14:52:30 (da4:mpr0:0:19:0): Descriptor 0x81: 00 00 00 00 00 00 Jul 30 14:52:30 (da4:mpr0:0:19:0): Retrying command (per sense data) Jul 31 00:00:00 syslog-ng[2349]: Configuration reload request received, reloading configuration; Jul 31 00:00:00 syslog-ng[2349]: Configuration reload finished; Jul 31 03:15:01 1 2023-07-31T03:15:01.692041-04:00 nas.lan smartd 2550 - - Device: /dev/da9, not capable of Long Self-Test Jul 31 03:15:01 1 2023-07-31T03:15:01.697325-04:00 nas.lan smartd 2550 - - Device: /dev/da13, not capable of Long Self-Test Jul 31 03:15:01 1 2023-07-31T03:15:01.702506-04:00 nas.lan smartd 2550 - - Device: /dev/da12, not capable of Long Self-Test Jul 31 03:15:01 1 2023-07-31T03:15:01.707749-04:00 nas.lan smartd 2550 - - Device: /dev/da14, not capable of Long Self-Test Jul 31 03:15:01 1 2023-07-31T03:15:01.713081-04:00 nas.lan smartd 2550 - - Device: /dev/da15, not capable of Long Self-Test Aug 1 00:00:00 syslog-ng[2349]: Configuration reload request received, reloading configuration; Aug 1 00:00:00 syslog-ng[2349]: Configuration reload finished; Aug 1 16:08:44 WARNING: (DESKTOPPC): no ping reply (NOP-Out) after 5 seconds; dropping connection Aug 1 22:02:09 WARNING: (DESKTOPPC): no ping reply (NOP-Out) after 5 seconds; dropping connection Aug 2 00:00:00 syslog-ng[2349]: Configuration reload request received, reloading configuration; Aug 2 00:00:00 syslog-ng[2349]: Configuration reload finished;
Questions:
So I keep seeing the link state issues. And no ping replies. This is to my desktop pc. I assume this is related to ISCSI or SMB. However, the computer has been running this entire time. I don't notice any active issues when playing games. I mean the games are stored on the NAS. So I assume if it was dropping connections it would completely freeze or something. I could be wrong. I do notice some packet loss here or there in online games. Granted I can't really confirm if that is just because it is running over a 1gbps local link and not 10g. Or just the game's servers, or what. I don't really notice much issues in single player games. Everything seems smooth. But if it is dropping connections, I would like to resolve it if it is not normal.
Second, the smartd messages saying it's not capable of a long self-test. I have all my drives setup on a cron to do a short test, and a long test. I am curious why these would not be capable of a long self-test? Is it just the hard drives software? I am not sure if they are the exact same model as all the other hard drives. I thought so, but maybe not. I bought them used, don't have the time to pull them all out and check everyone atm.
Thirdly, those CAM SCSI status errors. Seem potentially critical?
Overall, I see no warning messages, when running zpool status -v
Code:
zpool status -v
pool: PrimaryPool
state: ONLINE
scan: scrub repaired 0B in 14:29:29 with 0 errors on Mon Jul 24 17:29:30 2023
config:
NAME STATE READ WRITE CKSUM
PrimaryPool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
gptid/d7476d46-32ca-11ec-b815-002590f52cc2 ONLINE 0 0 0
gptid/d8d6aa36-32ca-11ec-b815-002590f52cc2 ONLINE 0 0 0
mirror-1 ONLINE 0 0 0
gptid/d9a6f5dc-32ca-11ec-b815-002590f52cc2 ONLINE 0 0 0
gptid/db71bcb5-32ca-11ec-b815-002590f52cc2 ONLINE 0 0 0
mirror-2 ONLINE 0 0 0
gptid/d8b2f42f-32ca-11ec-b815-002590f52cc2 ONLINE 0 0 0
gptid/d96847a9-32ca-11ec-b815-002590f52cc2 ONLINE 0 0 0
mirror-3 ONLINE 0 0 0
gptid/d9fb7757-32ca-11ec-b815-002590f52cc2 ONLINE 0 0 0
gptid/da1e1121-32ca-11ec-b815-002590f52cc2 ONLINE 0 0 0
mirror-4 ONLINE 0 0 0
gptid/9fd0872d-8f64-11ec-8462-002590f52cc2 ONLINE 0 0 0
gptid/9ff0f041-8f64-11ec-8462-002590f52cc2 ONLINE 0 0 0
mirror-5 ONLINE 0 0 0
gptid/14811777-1b6d-11ed-8423-ac1f6be66d76 ONLINE 0 0 0
spare-1 ONLINE 0 0 0
gptid/03daa071-505c-11ed-a9fe-ac1f6be66d76 ONLINE 0 0 0
gptid/0d56b97d-1e91-11ed-a6aa-ac1f6be66d76 ONLINE 0 0 0
mirror-6 ONLINE 0 0 0
gptid/749a1891-1b5c-11ee-941f-ac1f6be66d76 ONLINE 0 0 0
spare-1 ONLINE 0 0 0
gptid/4710dd39-1b6d-11ed-8423-ac1f6be66d76 ONLINE 0 0 0
gptid/0d48d4ab-1e91-11ed-a6aa-ac1f6be66d76 ONLINE 0 0 0
spares
gptid/0d48d4ab-1e91-11ed-a6aa-ac1f6be66d76 INUSE currently in use
gptid/0d56b97d-1e91-11ed-a6aa-ac1f6be66d76 INUSE currently in use
errors: No known data errors
pool: boot-pool
state: ONLINE
status: Some supported and requested features are not enabled on the pool.
The pool can still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
the pool may no longer be accessible by software that does not support
the features. See zpool-features(7) for details.
scan: scrub repaired 0B in 00:01:11 with 0 errors on Sat Jul 29 03:46:12 2023
errors: no known data errors
