Model: DS1019+
DSM 7.2.2-72806 Update 3
2x Samsung 970 EVO 512 GB (might actually be 2x 980's)
I used the scripts and setup an nvme storage pool, seemed to go great. I had been using the drives for read/write cache before that. After i setup the volume, I was doing some io testing using dd, and seeing quite slow iops with various tests. Set it down for a week or so while I was on vacation.
Today, I setup the nics to do link aggregation, and after getting that going (most likely coincidentally), the nvme storage pool showed as degraded. one of the drives was completely missing from DSM.
I chalked it up to a bad drive, explaining the poor iops test. But in an effort to troubleshoot, i powered down and re-seated both nvme drives. Boot back into DSM, now both drives are missing.
Not exactly sure how to troubleshoot, dmesg shows them failing to initialize:
dmesg | grep nvme
[ 5.654591] nvme nvme0: pci function 0000:02:00.0
[ 5.660408] nvme nvme1: pci function 0000:05:00.0
[ 36.220492] nvme nvme0: Device not ready; aborting initialisation
[ 36.220495] nvme nvme0: Removing after probe failure status: -19
[ 36.229496] nvme nvme1: Device not ready; aborting initialisation
[ 36.229499] nvme nvme1: Removing after probe failure status: -19
I had also setup some iscsi targets to these disks as I was going to test using this as shared storage for a proxmox cluster.
I saw another issue where the pool was degregated, and it was advised to run the syno HDD DB script. I tried that, and it indicates it found no nvme drives. Anyone else have similar issues?
Model: DS1019+
DSM 7.2.2-72806 Update 3
2x Samsung 970 EVO 512 GB (might actually be 2x 980's)
I used the scripts and setup an nvme storage pool, seemed to go great. I had been using the drives for read/write cache before that. After i setup the volume, I was doing some io testing using dd, and seeing quite slow iops with various tests. Set it down for a week or so while I was on vacation.
Today, I setup the nics to do link aggregation, and after getting that going (most likely coincidentally), the nvme storage pool showed as degraded. one of the drives was completely missing from DSM.
I chalked it up to a bad drive, explaining the poor iops test. But in an effort to troubleshoot, i powered down and re-seated both nvme drives. Boot back into DSM, now both drives are missing.
Not exactly sure how to troubleshoot, dmesg shows them failing to initialize:
I had also setup some iscsi targets to these disks as I was going to test using this as shared storage for a proxmox cluster.
I saw another issue where the pool was degregated, and it was advised to run the syno HDD DB script. I tried that, and it indicates it found no nvme drives. Anyone else have similar issues?