I am having problems with my FreeNAS 9.1.1 system. The error button is Green and says
But I do get loads of error messages along these lines:
And none of my Plugins load anymore, although I still 'see' all of my files from my Windows machine in my 'Network'.
Can anybody please tell me whether there is a systematic troubleshooting guide for things like this? So which commands I should use to diagnose what's wrong and then what can be done to solve it. Thanks!
-Stephan
OK: The volume StephanNAS (ZFS) status is HEALTHY

But I do get loads of error messages along these lines:
Code:
Nov 29 18:15:34 freenas kernel: (ada0:ahcich0:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 40 4e 56 40 ee 00 00 01 00 00 Nov 29 18:15:34 freenas kernel: (ada0:ahcich0:0:0:0): CAM status: ATA Status Error Nov 29 18:15:34 freenas kernel: (ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC ) Nov 29 18:15:34 freenas kernel: (ada0:ahcich0:0:0:0): RES: 41 40 40 4e 56 00 ee 00 00 00 01 Nov 29 18:15:34 freenas kernel: (ada0:ahcich0:0:0:0): Retrying command Nov 29 18:15:55 freenas kernel: (ada0:ahcich0:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 f8 ac 56 40 ee 00 00 01 00 00 Nov 29 18:15:55 freenas kernel: (ada0:ahcich0:0:0:0): CAM status: ATA Status Error Nov 29 18:15:55 freenas kernel: (ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC ) Nov 29 18:15:55 freenas kernel: (ada0:ahcich0:0:0:0): RES: 41 40 d0 ad 56 00 ee 00 00 00 01 Nov 29 18:15:55 freenas kernel: (ada0:ahcich0:0:0:0): Retrying command Nov 29 18:16:09 freenas kernel: (ada0:ahcich0:0:0:0): READ_FPDMA_QUEUED. ACB: 60 00 10 ce 56 40 ee 00 00 01 00 00 Nov 29 18:16:09 freenas kernel: (ada0:ahcich0:0:0:0): CAM status: ATA Status Error Nov 29 18:16:09 freenas kernel: (ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 40 (UNC ) Nov 29 18:16:09 freenas kernel: (ada0:ahcich0:0:0:0): RES: 41 40 28 ce 56 00 ee 00 00 00 01 Nov 29 18:16:09 freenas kernel: (ada0:ahcich0:0:0:0): Retrying command
And none of my Plugins load anymore, although I still 'see' all of my files from my Windows machine in my 'Network'.
Can anybody please tell me whether there is a systematic troubleshooting guide for things like this? So which commands I should use to diagnose what's wrong and then what can be done to solve it. Thanks!
-Stephan