So i am fairly new to this Truenas thing but hoping that this forum can help me.
The specs of my "server" are:
I am simply using the onboard sata ports to connect the hard drive and they are in a raid5 configurition? (2+1 so one drive can die without losing any data)
After setting up the system for the first time after about 1.5 months I got my first error stating that ada1 had an unrecoverable error. As a novice user and the hard drive still being in its warrenty I shut the system down and send the hard drive back to where it came from. The replacement arrived and i simply put it in without burning it in since i learned about that process about 15 minutes ago... after a week orso i got the same errors the previous drive spat out. This time around i tried some more troubleshooting. This included changing out the data cable, trying another power cable, trying all four sata ports. The two other drives were recognized with al the configurations the other one wasn't. After this i tried putting it into my windows system were it was detected in disk manegment as an empy volume. Since the data could be rebuild I tried initializing the disk which failed because of an io error. Is this simply a case of not catching the bad drive earlier because i did not perform a burn in? or is there another thing i haven't tried to fix this issue. The data on the nas is backup of photos and other stuff, all of this data is also stored in various other places so losing all of the data is not a big deal but will just take time to copy back onto the server. Any help is greatly appreciated.
The specs of my "server" are:
| Intel i3-10100 |
| asrock h510 |
| Kingston 500gb nvme ssd |
| Fractal design node 304 |
| Seasonic PX-550 |
| 3 X Seagate ironwolf pro 16tb |
After setting up the system for the first time after about 1.5 months I got my first error stating that ada1 had an unrecoverable error. As a novice user and the hard drive still being in its warrenty I shut the system down and send the hard drive back to where it came from. The replacement arrived and i simply put it in without burning it in since i learned about that process about 15 minutes ago... after a week orso i got the same errors the previous drive spat out. This time around i tried some more troubleshooting. This included changing out the data cable, trying another power cable, trying all four sata ports. The two other drives were recognized with al the configurations the other one wasn't. After this i tried putting it into my windows system were it was detected in disk manegment as an empy volume. Since the data could be rebuild I tried initializing the disk which failed because of an io error. Is this simply a case of not catching the bad drive earlier because i did not perform a burn in? or is there another thing i haven't tried to fix this issue. The data on the nas is backup of photos and other stuff, all of this data is also stored in various other places so losing all of the data is not a big deal but will just take time to copy back onto the server. Any help is greatly appreciated.
