One drive started reporting SMART Errors so I replaced the drive, and copied all files to the new replacement drive.
I ran a diff, everything checked out, then ran a sync and all was well.
A few days later I deleted & moved some files around in the array, just performing some routine cleanup. I ran a sync from my normal schedule tasks and it appeared to never finish, the log shows that the throughput went to 0 MB/s and then I couldn't even login to the PC anymore. I had to restart the PC.
All my subsequent syncs have the same result. Diff says nothing has changed, but if I run sync it still tries to perform a sync. Each run has less of an ETA to finish, but it gets to a point where it has hardly any throughput and just hangs.
Any help would be appreciated.
--------- UPDATE -----------
I ran it again and the same thing happened. The sync doesn't finish and I can no longer login, or even connect to the PC (via something like Plex). I do see about 5 warnings (for different disks) in the Event log with the following:
Disk 11 has the same disk identifiers as one or more disks connected to the system
Thanks,
Ken
Last edit: pofo14 2019-10-19
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
How do i resolve that ? Reading some articles it looks like i can just assign a new id using diskpart, but i am not sure how i create the id
I have just done a fresh install of windows, so at this point I wpuld just do a reinstall if that will resolve the issue.
One additional question is that the drives are not offline which from what i am reading i thought windows 10 would keep it offline indid confirm that the two parity drives are ones listed with a collision issue
Last edit: pofo14 2019-10-19
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Diff only shows what has changed since the current sync was started.
How are the disks connected? Any external disks?
Are you using mount points or drive letters? Any changes to these before issue started?
Any changes done in snapraid.conf before issue started?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the response. I finally did get a sync to complete. It looks like Acronis Active Protection was flagging the snapraid.exe as a suspicious process. Not sure why it would slow the snapraid process down, but it also did start to consume all the memory on the PC. Once I added this exe to a trusted process it went fine.
Also after going into diskpart and verifying each disk ID - I have not seen the disk collision error anymore. Not sure why this made a difference.
So I think everything is working as expected now.
Diff only shows what has changed since the current sync was started.
Thanks for that clarification.
How are the disks connected? Any external disks?
All the disks are internals. There are 8 attached to an LSI Raid card, and the rest are attached directly to the motherboard SATA ports.
Are you using mount points or drive letters? Any changes to these before issue started?
I am using drive letters, but there was some changes to this, as I changed a drive letter for the failed drived.
Any changes done in snapraid.conf before issue started?
Only change here was replacing the failed disk with the new disk.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have 8 data drives, and 2 parity drives.
One drive started reporting SMART Errors so I replaced the drive, and copied all files to the new replacement drive.
I ran a diff, everything checked out, then ran a sync and all was well.
A few days later I deleted & moved some files around in the array, just performing some routine cleanup. I ran a sync from my normal schedule tasks and it appeared to never finish, the log shows that the throughput went to 0 MB/s and then I couldn't even login to the PC anymore. I had to restart the PC.
All my subsequent syncs have the same result. Diff says nothing has changed, but if I run sync it still tries to perform a sync. Each run has less of an ETA to finish, but it gets to a point where it has hardly any throughput and just hangs.
Any help would be appreciated.
--------- UPDATE -----------
I ran it again and the same thing happened. The sync doesn't finish and I can no longer login, or even connect to the PC (via something like Plex). I do see about 5 warnings (for different disks) in the Event log with the following:
Disk 11 has the same disk identifiers as one or more disks connected to the system
Thanks,
Ken
Last edit: pofo14 2019-10-19
disc identifiers should/mustbe unique. they are used by many programs to identify the disc. Problems can arrive from identical identifiers...
How do i resolve that ? Reading some articles it looks like i can just assign a new id using diskpart, but i am not sure how i create the id
I have just done a fresh install of windows, so at this point I wpuld just do a reinstall if that will resolve the issue.
One additional question is that the drives are not offline which from what i am reading i thought windows 10 would keep it offline indid confirm that the two parity drives are ones listed with a collision issue
Last edit: pofo14 2019-10-19
Additional update - I checked the uniqueid of every disk using diskpart - and there are no duplicate id's. Not sure why this is being reported.
I am still stuck in the same place where my sync's never complete.
Diff only shows what has changed since the current sync was started.
How are the disks connected? Any external disks?
Are you using mount points or drive letters? Any changes to these before issue started?
Any changes done in snapraid.conf before issue started?
Thanks for the response. I finally did get a sync to complete. It looks like Acronis Active Protection was flagging the snapraid.exe as a suspicious process. Not sure why it would slow the snapraid process down, but it also did start to consume all the memory on the PC. Once I added this exe to a trusted process it went fine.
Also after going into diskpart and verifying each disk ID - I have not seen the disk collision error anymore. Not sure why this made a difference.
So I think everything is working as expected now.
Thanks for that clarification.
All the disks are internals. There are 8 attached to an LSI Raid card, and the rest are attached directly to the motherboard SATA ports.
I am using drive letters, but there was some changes to this, as I changed a drive letter for the failed drived.
Only change here was replacing the failed disk with the new disk.