SolidSonicTH
Occasional Visitor
Basically I've been experiencing some issues where the process log when running file operations reports “The request could not be performed because of an I/O device error," as a result of interacting with my JBOD array. I've experienced this both when writing to the array with FastCopy and reading from it when trying to make backups via Kopia. In either case it seems to affect what happens to the data (either FastCopy just gives up writing that file or Kopia won't put that file into the snapshot).
The server itself is running Windows 11 and as I peruse the Event Viewer I notice many warnings under the "System" category that say access to a location was retried on various disks. However all the data that lives on the array is seemingly fine. If I write to the storage pool with Windows Explorer it sends the files over without stopping and when I read them back they aren't corrupted (and this includes checking on files that Kopia claims it couldn't read during the backup process). To me this suggests I should be able to perform tasks in either direction without it crapping itself.
The array is being aggregated using StableBIt DrivePool with file redundancy enabled and the physical media comprises eight 6TB 12 Gb/s SAS drives from HGST connected 4x2 to a Dell PERC H310 HBA running in IT passthrough mode that I got from a garage sale. The drives all read as perfectly healthy in HD Sentinel (with all of them reporting around 2500 days of uptime - this is not a 24/7 application I'm running them in as I shut down the server when not using it to preserve the HDDs' longevity and save power as I consider the server a "tier 2" cold storage data host, with the Kopia backup acting as "tier 3" in case the array were to fail and need to be reconstructed). I've ordered a new HBA (since I was planning on doing some work inside the thing anyway since I'm finally using it the way I intended and the HBA I'm currently using only operates at half the data rate the drives are capable of) but am I barking up the wrong tree here? I have noticed the array will go through cycles during long read/write processes where the activity will drop to nothing then resume again so I thought maybe that was causing the problem but I'm also not sure if this is just regular behavior when dealing with JBODs across a discrete HBA.
The server itself is running Windows 11 and as I peruse the Event Viewer I notice many warnings under the "System" category that say access to a location was retried on various disks. However all the data that lives on the array is seemingly fine. If I write to the storage pool with Windows Explorer it sends the files over without stopping and when I read them back they aren't corrupted (and this includes checking on files that Kopia claims it couldn't read during the backup process). To me this suggests I should be able to perform tasks in either direction without it crapping itself.
The array is being aggregated using StableBIt DrivePool with file redundancy enabled and the physical media comprises eight 6TB 12 Gb/s SAS drives from HGST connected 4x2 to a Dell PERC H310 HBA running in IT passthrough mode that I got from a garage sale. The drives all read as perfectly healthy in HD Sentinel (with all of them reporting around 2500 days of uptime - this is not a 24/7 application I'm running them in as I shut down the server when not using it to preserve the HDDs' longevity and save power as I consider the server a "tier 2" cold storage data host, with the Kopia backup acting as "tier 3" in case the array were to fail and need to be reconstructed). I've ordered a new HBA (since I was planning on doing some work inside the thing anyway since I'm finally using it the way I intended and the HBA I'm currently using only operates at half the data rate the drives are capable of) but am I barking up the wrong tree here? I have noticed the array will go through cycles during long read/write processes where the activity will drop to nothing then resume again so I thought maybe that was causing the problem but I'm also not sure if this is just regular behavior when dealing with JBODs across a discrete HBA.
Last edited:
