NeoID 6 Posted September 10, 2015 Share Posted September 10, 2015 I use a LSI LOGIC SAS9201 in pass-through mode and it works great. However, when stressing XPEnology by initiating a data scrub or similar i often get a notification like the one below. Anyone else has experienced this? I know that the disk are good. It seems like the cable might be bad, but changing them hasn't helped either. Dear user, The hard disk 8 on server had an I/O error, but it is working properly now after several retries. It might have been caused by bad sectors. If this error occurs again, please back up your data and run the S.M.A.R.T. test on your hard drive to examine the hard drive status. Sincerely, Synology DiskStation Link to post Share on other sites
snoopy78 1 Posted September 10, 2015 Share Posted September 10, 2015 which FW Version do you use on the LSI? Link to post Share on other sites
NeoID 6 Posted September 10, 2015 Author Share Posted September 10, 2015 which FW Version do you use on the LSI? The latest... P20 I think it is... Link to post Share on other sites
snoopy78 1 Posted September 10, 2015 Share Posted September 10, 2015 big mistake!!!! hurry and downgrade..otherwise you might get really trouble... viewtopic.php?f=2&t=4985&p=29300 next time, maybe try searching the forum first... Link to post Share on other sites
NeoID 6 Posted September 11, 2015 Author Share Posted September 11, 2015 I can confirm that this is not related to the firmware version as I'm now running P19 and still have the same issue. Best way of reproducing the issue is to do a data scrub. DSM sends a notification almost instantly. Link to post Share on other sites
dilemmaprison 0 Posted September 27, 2015 Share Posted September 27, 2015 I ran into this issue with my HBA as well; though on FreeNAS. The initial releases of firmware P20 ( Version 20.00.00.00 ) Used on the LSI 2008 / IBM M1015 etc had some bug that caused io errors or media errors. Lots of freenas community chatter on this issue too. LSI released later updates ( Versions 20.00.02.00 and 20.00.04.00 ) that are supposed to fix this bug. Link to post Share on other sites
Recommended Posts