Jump to content

MrLondon

Members
  • Content Count

    272
  • Joined

  • Last visited

Community Reputation

0 Neutral

About MrLondon

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi there, I used the the wrong bootable key for the Dell H310 and it appears that I wiped the SAS address as its now only showing 000000000000 is there a way to recover from this? I checked on the card and I cannot see anywhere where it is listed, there certainly is not a sticker for it. When use option 1 it does not list the SAS address. Did I now brick the card. I was still able to install the latest firmware I just don't have the SAS address. I just used a slightly different SAS address of my 2nd Dell H310 controll and it appears that unraid is ok with that.
  2. I did put the array into sleep mode and pressed a keyboard button. The LSI raid controllers do not have power cords itself. So does this mean I should not use sleep mode? This is a new motherboard and with my old board I was not able to use sleep mode, but I do not want to run into this problem continuesly. Also how can I recover from this, will I have to redo the parity check again? Is the only way to avoid this to not use sleep mode with LSI controllers?
  3. after about 30min of me asking the server to shutdown it finally did, without me doing anything.
  4. I suddenly gotten a read error on the parity drive which disabled the parity disk. I know that there is nothing wrong with the parity disk as I only completed a parity test successfully yesterday evening and another one a week before. However now it appears that the SAS driver for the LSI controller is having issues and therefore is not able to shutdown the server. I am trying to download the diagnostic file but that was so far not possible. I have the syslog. I am currently not able to resolve this, any suggestions to fix this are highly appreciated. tower-syslog-20190731-1836.zip
  5. johnnie.black, you are 100% correct, I missed the bit to wait to assign the parity drive, I now did as you suggested and it mounted drive 18, so now I started the parity check again, let's hope it will work as expected. Thanks again for the assitance.
  6. Ok I am getting worried now. I did as suggested, did a new config, assigned the parity drive but it will still not mount disk 18, even though I have now connected a different SATA cable to the drive, but the syslog shows this Feb 20 18:19:56 Tower emhttpd: shcmd (130): mount -t btrfs,xfs,reiserfs -o noatime,nodiratime /dev/md18 /mnt/disk18 Feb 20 18:19:56 Tower kernel: Buffer I/O error on dev md18, logical block 16, async page read Feb 20 18:19:56 Tower kernel: REISERFS warning (device md18): sh-2006 read_super_block: bread failed (dev md18, block 2, size 4096) Feb 20 18:19:56 Tower kernel: REISERFS warning (device md18): sh-2006 read_super_block: bread failed (dev md18, block 16, size 4096) Feb 20 18:19:56 Tower root: mount: /mnt/disk18: wrong fs type, bad option, bad superblock on /dev/md18, missing codepage or helper program, or other error. Feb 20 18:19:56 Tower emhttpd: shcmd (130): exit status: 32 Feb 20 18:19:56 Tower emhttpd: /mnt/disk18 mount error: No file system Feb 20 18:19:56 Tower emhttpd: shcmd (131): umount /mnt/disk18 so it appears that somehow something happened last night when I used the user script for clearing disk 3. tower-diagnostics-20190220-1825.zip
  7. Hi there, I removed two drives today which I no longer use. After I removed the power and data cable I started the server again and now disk 18 is reporting invalid file system, in the syslog I can see that it tried raiserfs but I am only using XFS on my data disks, but I do not see that it tried to mount it via XFS, is there a way to resolve this without data loss? No problems were reported from this disk before it showed this problem that I am aware of. tower-diagnostics-20190220-1630.zip
  8. I have removed the drives manually and I have also changed back the Tunable (md_write_method): setting to auto, but now I have a new problem that one of my drives which worked fine without any issues suddenly cannot detect the XFS file system, which was not a problem before I did the new config. In the syslog I saw that it tried to mount it with raiserfs which it has not been for a very long time, is there a way to resolve this without losing all data on the drive? tower-diagnostics-20190220-1630.zip
  9. Hi there, I am not sure if this is the correct forum to post my question, but I used the clear array drive user script last night and suddenly this morning I saw that my parity drive was disabled because of read errors. Here is the script log output *** Clear an unRAID array data drive *** v1.4 Checking all array data drives (may need to spin them up) ... Found a marked and empty drive to clear: Disk 3 ( /mnt/disk3 ) * Disk 3 will be unmounted first. * Then zeroes will be written to the entire drive. * Parity will be preserved throughout. * Clearing while updating Parity takes a VERY long time! * The progress of the clearing will not be visible until it's done! * When complete, Disk 3 will be ready for removal from array. * Commands to be executed: ***** umount /mnt/disk3 ***** dd bs=1M if=/dev/zero of=/dev/md3 status=progress You have 60 seconds to cancel this script (click the red X, top right) Unmounting Disk 3 ... Clearing Disk 3 ... 2000108388352 bytes (2.0 TB, 1.8 TiB) copied, 13263 s, 151 MB/s dd: error writing '/dev/md3': No space left on device 1907730+0 records in 1907729+0 records out 2000398901248 bytes (2.0 TB, 1.8 TiB) copied, 13264 s, 151 MB/s A message saying "error writing ... no space left" is expected, NOT an error. Unless errors appeared, the drive is now cleared! Because the drive is now unmountable, the array should be stopped, and the drive removed (or reformatted). Script Finished Wed, 20 Feb 2019 02:24:20 +0000 Feb 19 22:36:35 Tower emhttpd: req (6): cmd=/plugins/user.scripts/backgroundScript.sh&arg1=/tmp/user.scripts/tmpScripts/clear_array_drive/script&csrf_token=**************** Feb 19 22:36:35 Tower emhttpd: cmd: /usr/local/emhttp/plugins/user.scripts/backgroundScript.sh /tmp/user.scripts/tmpScripts/clear_array_drive/script Feb 19 22:37:13 Tower emhttpd: req (7): csrf_token=****************&title=Log+Information&cmd=%2Fplugins%2Fuser.scripts%2FshowLog.php&arg1=clear_array_drive Feb 19 22:37:13 Tower emhttpd: cmd: /usr/local/emhttp/plugins/user.scripts/showLog.php clear_array_drive Feb 19 22:38:21 Tower emhttpd: req (8): cmd=/plugins/user.scripts/startScript.sh&arg1=/tmp/user.scripts/tmpScripts/viewDockerLogSize/script&arg2=&csrf_token=**************** Feb 19 22:38:21 Tower emhttpd: cmd: /usr/local/emhttp/plugins/user.scripts/startScript.sh /tmp/user.scripts/tmpScripts/viewDockerLogSize/script Feb 19 22:43:15 Tower clear_array_drive: Clear an unRAID array data drive v1.4 Feb 19 22:43:15 Tower clear_array_drive: Unmounting Disk 3 (command: umount /mnt/disk3 ) ... Feb 19 22:43:15 Tower kernel: XFS (md3): Unmounting Filesystem Feb 19 22:43:16 Tower clear_array_drive: Clearing Disk 3 (command: dd bs=1M if=/dev/zero of=/dev/md3 status=progress ) ... Feb 19 23:28:02 Tower sSMTP[4359]: Creating SSL connection to host Feb 19 23:28:02 Tower sSMTP[4359]: SSL connection using ECDHE-RSA-CHACHA20-POLY1305 Feb 19 23:28:05 Tower sSMTP[4359]: Sent mail for email@removed.com (221 2.0.0 closing connection p6sm22933209wre.63 - gsmtp) uid=0 username=xxx outbytes=722 Feb 19 23:59:01 Tower sSMTP[16970]: Creating SSL connection to host Feb 19 23:59:01 Tower sSMTP[16970]: SSL connection using ECDHE-RSA-CHACHA20-POLY1305 Feb 19 23:59:03 Tower sSMTP[16970]: Sent mail for email@removed.com (221 2.0.0 closing connection b3sm7262188wme.27 - gsmtp) uid=0 username=xxx outbytes=714 Feb 20 00:04:44 Tower kernel: sd 8:0:2:0: [sdi] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Feb 20 00:04:44 Tower kernel: sd 8:0:2:0: [sdi] tag#3 Sense Key : 0x5 [current] Feb 20 00:04:44 Tower kernel: sd 8:0:2:0: [sdi] tag#3 ASC=0x21 ASCQ=0x0 Feb 20 00:04:44 Tower kernel: sd 8:0:2:0: [sdi] tag#3 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Feb 20 00:04:44 Tower kernel: print_req_error: critical target error, dev sdi, sector 486580287 Feb 20 00:04:44 Tower kernel: BTRFS warning (device sdi1): failed to trim 1 device(s), last error -121 Feb 20 00:04:44 Tower sSMTP[19242]: Creating SSL connection to host Feb 20 00:04:44 Tower sSMTP[19242]: SSL connection using ECDHE-RSA-CHACHA20-POLY1305 Feb 20 00:04:46 Tower sSMTP[19242]: Sent mail for email@removed.com (221 2.0.0 closing connection a1sm16966553wrq.96 - gsmtp) uid=0 username=xxx outbytes=474 Feb 20 00:20:01 Tower sSMTP[25315]: Creating SSL connection to host Feb 20 00:20:01 Tower sSMTP[25315]: SSL connection using ECDHE-RSA-CHACHA20-POLY1305 Feb 20 00:20:03 Tower sSMTP[25315]: Sent mail for email@removed.com (221 2.0.0 closing connection d9sm33728287wrn.72 - gsmtp) uid=0 username=xxx outbytes=2454 Feb 20 01:30:53 Tower kernel: sas: Enter sas_scsi_recover_host busy: 20 failed: 20 Feb 20 01:30:53 Tower kernel: sas: trying to find task 0x00000000ecb91ffc Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: aborting task 0x00000000ecb91ffc Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: task 0x00000000ecb91ffc is aborted Feb 20 01:30:53 Tower kernel: sas: sas_eh_handle_sas_errors: task 0x00000000ecb91ffc is aborted Feb 20 01:30:53 Tower kernel: sas: trying to find task 0x00000000f0c82a64 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: aborting task 0x00000000f0c82a64 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: task 0x00000000f0c82a64 is aborted Feb 20 01:30:53 Tower kernel: sas: sas_eh_handle_sas_errors: task 0x00000000f0c82a64 is aborted Feb 20 01:30:53 Tower kernel: sas: trying to find task 0x0000000063078c7c Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: aborting task 0x0000000063078c7c Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: task 0x0000000063078c7c is aborted Feb 20 01:30:53 Tower kernel: sas: sas_eh_handle_sas_errors: task 0x0000000063078c7c is aborted Feb 20 01:30:53 Tower kernel: sas: trying to find task 0x000000000109a392 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: aborting task 0x000000000109a392 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: task 0x000000000109a392 is aborted Feb 20 01:30:53 Tower kernel: sas: sas_eh_handle_sas_errors: task 0x000000000109a392 is aborted Feb 20 01:30:53 Tower kernel: sas: trying to find task 0x000000002947cfff Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: aborting task 0x000000002947cfff Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: task 0x000000002947cfff is aborted Feb 20 01:30:53 Tower kernel: sas: sas_eh_handle_sas_errors: task 0x000000002947cfff is aborted Feb 20 01:30:53 Tower kernel: sas: trying to find task 0x00000000c6d0f4ad Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: aborting task 0x00000000c6d0f4ad Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: task 0x00000000c6d0f4ad is aborted Feb 20 01:30:53 Tower kernel: sas: sas_eh_handle_sas_errors: task 0x00000000c6d0f4ad is aborted Feb 20 01:30:53 Tower kernel: sas: trying to find task 0x00000000d2b185de Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: aborting task 0x00000000d2b185de Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: task 0x00000000d2b185de is aborted Feb 20 01:30:53 Tower kernel: sas: sas_eh_handle_sas_errors: task 0x00000000d2b185de is aborted Feb 20 01:30:53 Tower kernel: sas: trying to find task 0x00000000392bb1a3 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: aborting task 0x00000000392bb1a3 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: task 0x00000000392bb1a3 is aborted Feb 20 01:30:53 Tower kernel: sas: sas_eh_handle_sas_errors: task 0x00000000392bb1a3 is aborted Feb 20 01:30:53 Tower kernel: sas: trying to find task 0x00000000df4c2250 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: aborting task 0x00000000df4c2250 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: task 0x00000000df4c2250 is aborted Feb 20 01:30:53 Tower kernel: sas: sas_eh_handle_sas_errors: task 0x00000000df4c2250 is aborted Feb 20 01:30:53 Tower kernel: sas: trying to find task 0x000000009a5ae873 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: aborting task 0x000000009a5ae873 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: task 0x000000009a5ae873 is aborted Feb 20 01:30:53 Tower kernel: sas: sas_eh_handle_sas_errors: task 0x000000009a5ae873 is aborted Feb 20 01:30:53 Tower kernel: sas: trying to find task 0x00000000e01c78e5 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: aborting task 0x00000000e01c78e5 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: task 0x00000000e01c78e5 is aborted Feb 20 01:30:53 Tower kernel: sas: sas_eh_handle_sas_errors: task 0x00000000e01c78e5 is aborted Feb 20 01:30:53 Tower kernel: sas: trying to find task 0x00000000b475d310 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: aborting task 0x00000000b475d310 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: task 0x00000000b475d310 is aborted Feb 20 01:30:53 Tower kernel: sas: sas_eh_handle_sas_errors: task 0x00000000b475d310 is aborted Feb 20 01:30:53 Tower kernel: sas: trying to find task 0x0000000075f49975 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: aborting task 0x0000000075f49975 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: task 0x0000000075f49975 is aborted Feb 20 01:30:53 Tower kernel: sas: sas_eh_handle_sas_errors: task 0x0000000075f49975 is aborted Feb 20 01:30:53 Tower kernel: sas: trying to find task 0x000000002046c5d0 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: aborting task 0x000000002046c5d0 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: task 0x000000002046c5d0 is aborted Feb 20 01:30:53 Tower kernel: sas: sas_eh_handle_sas_errors: task 0x000000002046c5d0 is aborted Feb 20 01:30:53 Tower kernel: sas: trying to find task 0x00000000f6bb7c42 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: aborting task 0x00000000f6bb7c42 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: task 0x00000000f6bb7c42 is aborted Feb 20 01:30:53 Tower kernel: sas: sas_eh_handle_sas_errors: task 0x00000000f6bb7c42 is aborted Feb 20 01:30:53 Tower kernel: sas: trying to find task 0x000000009962c027 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: aborting task 0x000000009962c027 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: task 0x000000009962c027 is aborted Feb 20 01:30:53 Tower kernel: sas: sas_eh_handle_sas_errors: task 0x000000009962c027 is aborted Feb 20 01:30:53 Tower kernel: sas: trying to find task 0x00000000df4774a8 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: aborting task 0x00000000df4774a8 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: task 0x00000000df4774a8 is aborted Feb 20 01:30:53 Tower kernel: sas: sas_eh_handle_sas_errors: task 0x00000000df4774a8 is aborted Feb 20 01:30:53 Tower kernel: sas: trying to find task 0x00000000a04d4d65 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: aborting task 0x00000000a04d4d65 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: task 0x00000000a04d4d65 is aborted Feb 20 01:30:53 Tower kernel: sas: sas_eh_handle_sas_errors: task 0x00000000a04d4d65 is aborted Feb 20 01:30:53 Tower kernel: sas: trying to find task 0x00000000f7f08458 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: aborting task 0x00000000f7f08458 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: task 0x00000000f7f08458 is aborted Feb 20 01:30:53 Tower kernel: sas: sas_eh_handle_sas_errors: task 0x00000000f7f08458 is aborted Feb 20 01:30:53 Tower kernel: sas: trying to find task 0x0000000052e80978 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: aborting task 0x0000000052e80978 Feb 20 01:30:53 Tower kernel: sas: sas_scsi_find_task: task 0x0000000052e80978 is aborted Feb 20 01:30:53 Tower kernel: sas: sas_eh_handle_sas_errors: task 0x0000000052e80978 is aborted Feb 20 01:30:53 Tower kernel: sas: ata12: end_device-7:5: cmd error handler Feb 20 01:30:53 Tower kernel: sas: ata7: end_device-7:0: dev error handler Feb 20 01:30:53 Tower kernel: sas: ata8: end_device-7:1: dev error handler Feb 20 01:30:53 Tower kernel: sas: ata9: end_device-7:2: dev error handler Feb 20 01:30:53 Tower kernel: sas: ata10: end_device-7:3: dev error handler Feb 20 01:30:53 Tower kernel: sas: ata11: end_device-7:4: dev error handler Feb 20 01:30:53 Tower kernel: sas: ata12: end_device-7:5: dev error handler Feb 20 01:30:53 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x1ffffe00 SErr 0x0 action 0x6 frozen Feb 20 01:30:53 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Feb 20 01:30:53 Tower kernel: ata12.00: cmd 61/00:00:38:c8:10/02:00:43:00:00/40 tag 9 ncq dma 262144 out Feb 20 01:30:53 Tower kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 20 01:30:53 Tower kernel: ata12.00: status: { DRDY } Feb 20 01:30:53 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Feb 20 01:30:53 Tower kernel: ata12.00: cmd 61/00:00:38:ca:10/02:00:43:00:00/40 tag 10 ncq dma 262144 out Feb 20 01:30:53 Tower kernel: res 40/00:a8:38:e9:83/00:00:36:00:00/40 Emask 0x4 (timeout) Feb 20 01:30:53 Tower kernel: ata12.00: status: { DRDY } Feb 20 01:30:53 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Feb 20 01:30:53 Tower kernel: ata12.00: cmd 61/00:00:38:cc:10/02:00:43:00:00/40 tag 11 ncq dma 262144 out Feb 20 01:30:53 Tower kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 20 01:30:53 Tower kernel: ata12.00: status: { DRDY } Feb 20 01:30:53 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Feb 20 01:30:53 Tower kernel: ata12.00: cmd 61/00:00:38:ce:10/02:00:43:00:00/40 tag 12 ncq dma 262144 out Feb 20 01:30:53 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 20 01:30:53 Tower kernel: ata12.00: status: { DRDY } Feb 20 01:30:53 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Feb 20 01:30:53 Tower kernel: ata12.00: cmd 61/00:00:38:d0:10/02:00:43:00:00/40 tag 13 ncq dma 262144 out Feb 20 01:30:53 Tower kernel: res 40/00:44:08:0a:f8/00:00:42:00:00/40 Emask 0x4 (timeout) Feb 20 01:30:53 Tower kernel: ata12.00: status: { DRDY } Feb 20 01:30:53 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Feb 20 01:30:53 Tower kernel: ata12.00: cmd 61/d8:00:38:d2:10/01:00:43:00:00/40 tag 14 ncq dma 241664 out Feb 20 01:30:53 Tower kernel: res 40/00:5c:68:d4:83/00:00:36:00:00/40 Emask 0x4 (timeout) Feb 20 01:30:53 Tower kernel: ata12.00: status: { DRDY } Feb 20 01:30:53 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Feb 20 01:30:53 Tower kernel: ata12.00: cmd 61/00:00:10:d4:10/02:00:43:00:00/40 tag 15 ncq dma 262144 out Feb 20 01:30:53 Tower kernel: res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 20 01:30:53 Tower kernel: ata12.00: status: { DRDY } Feb 20 01:30:53 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Feb 20 01:30:53 Tower kernel: ata12.00: cmd 61/00:00:10:d6:10/02:00:43:00:00/40 tag 16 ncq dma 262144 out Feb 20 01:30:53 Tower kernel: res 40/00:d8:f8:e3:9a/00:00:1d:00:00/40 Emask 0x4 (timeout) Feb 20 01:30:53 Tower kernel: ata12.00: status: { DRDY } Feb 20 01:30:53 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Feb 20 01:30:53 Tower kernel: ata12.00: cmd 61/c8:00:10:d8:10/00:00:43:00:00/40 tag 17 ncq dma 102400 out Feb 20 01:30:53 Tower kernel: res 40/00:68:80:b3:09/00:00:1e:00:00/40 Emask 0x4 (timeout) Feb 20 01:30:53 Tower kernel: ata12.00: status: { DRDY } Feb 20 01:30:53 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Feb 20 01:30:53 Tower kernel: ata12.00: cmd 61/00:00:d8:d8:10/02:00:43:00:00/40 tag 18 ncq dma 262144 out Feb 20 01:30:53 Tower kernel: res 40/00:6c:a8:5a:9f/00:00:42:00:00/40 Emask 0x4 (timeout) Feb 20 01:30:53 Tower kernel: ata12.00: status: { DRDY } Feb 20 01:30:53 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Feb 20 01:30:53 Tower kernel: ata12.00: cmd 61/00:00:d8:da:10/02:00:43:00:00/40 tag 19 ncq dma 262144 out Feb 20 01:30:53 Tower kernel: res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 20 01:30:53 Tower kernel: ata12.00: status: { DRDY } Feb 20 01:30:53 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Feb 20 01:30:53 Tower kernel: ata12.00: cmd 61/00:00:d8:dc:10/02:00:43:00:00/40 tag 20 ncq dma 262144 out Feb 20 01:30:53 Tower kernel: res 40/00:e4:a8:5a:9f/00:00:42:00:00/40 Emask 0x4 (timeout) Feb 20 01:30:53 Tower kernel: ata12.00: status: { DRDY } Feb 20 01:30:53 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Feb 20 01:30:53 Tower kernel: ata12.00: cmd 61/00:00:d8:de:10/02:00:43:00:00/40 tag 21 ncq dma 262144 out Feb 20 01:30:53 Tower kernel: res 40/00:a0:d8:59:6e/00:00:36:00:00/40 Emask 0x4 (timeout) Feb 20 01:30:53 Tower kernel: ata12.00: status: { DRDY } Feb 20 01:30:53 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Feb 20 01:30:53 Tower kernel: ata12.00: cmd 61/00:00:d8:e0:10/02:00:43:00:00/40 tag 22 ncq dma 262144 out Feb 20 01:30:53 Tower kernel: res 40/00:00:a7:5e:9f/00:00:42:00:00/e2 Emask 0x4 (timeout) Feb 20 01:30:53 Tower kernel: ata12.00: status: { DRDY } Feb 20 01:30:53 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Feb 20 01:30:53 Tower kernel: ata12.00: cmd 61/00:00:d8:e2:10/02:00:43:00:00/40 tag 23 ncq dma 262144 out Feb 20 01:30:53 Tower kernel: res 40/00:18:08:10:f8/00:00:42:00:00/40 Emask 0x4 (timeout) Feb 20 01:30:53 Tower kernel: ata12.00: status: { DRDY } Feb 20 01:30:53 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Feb 20 01:30:53 Tower kernel: ata12.00: cmd 61/00:00:d8:e4:10/02:00:43:00:00/40 tag 24 ncq dma 262144 out Feb 20 01:30:53 Tower kernel: res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 20 01:30:53 Tower kernel: ata12.00: status: { DRDY } Feb 20 01:30:53 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Feb 20 01:30:53 Tower kernel: ata12.00: cmd 61/00:00:d8:e6:10/02:00:43:00:00/40 tag 25 ncq dma 262144 out Feb 20 01:30:53 Tower kernel: res 40/00:a4:d8:5d:6e/00:00:36:00:00/40 Emask 0x4 (timeout) Feb 20 01:30:53 Tower kernel: ata12.00: status: { DRDY } Feb 20 01:30:53 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Feb 20 01:30:53 Tower kernel: ata12.00: cmd 61/60:00:d8:e8:10/01:00:43:00:00/40 tag 26 ncq dma 180224 out Feb 20 01:30:53 Tower kernel: res 40/00:9c:d8:5b:6e/00:00:36:00:00/40 Emask 0x4 (timeout) Feb 20 01:30:53 Tower kernel: ata12.00: status: { DRDY } Feb 20 01:30:53 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Feb 20 01:30:53 Tower kernel: ata12.00: cmd 61/00:00:38:ea:10/02:00:43:00:00/40 tag 27 ncq dma 262144 out Feb 20 01:30:53 Tower kernel: res 40/00:cc:80:af:09/00:00:1e:00:00/40 Emask 0x4 (timeout) Feb 20 01:30:53 Tower kernel: ata12.00: status: { DRDY } Feb 20 01:30:53 Tower kernel: ata12.00: failed command: WRITE FPDMA QUEUED Feb 20 01:30:53 Tower kernel: ata12.00: cmd 61/00:00:38:ec:10/02:00:43:00:00/40 tag 28 ncq dma 262144 out Feb 20 01:30:53 Tower kernel: res 40/00:ff:ff:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 20 01:30:53 Tower kernel: ata12.00: status: { DRDY } Feb 20 01:30:53 Tower kernel: ata12: hard resetting link Feb 20 01:30:53 Tower kernel: sas: ata13: end_device-7:6: dev error handler Feb 20 01:30:53 Tower kernel: sas: ata14: end_device-7:7: dev error handler Feb 20 01:30:56 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1435:mvs_I_T_nexus_reset for device[5]:rc= 0 Feb 20 01:30:56 Tower kernel: sas: sas_ata_task_done: SAS error 8a Feb 20 01:30:56 Tower kernel: WARNING: CPU: 3 PID: 18661 at drivers/ata/libata-core.c:5180 __ata_qc_complete+0x16/0xfb Feb 20 01:30:56 Tower kernel: Modules linked in: xt_nat veth ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs md_mod it87 hwmon_vid intel_powerclamp coretemp kvm_intel kvm mpt3sas mvsas crc32c_intel libsas e1000 intel_cstate intel_uncore i2c_i801 asus_atk0110 raid_class i2c_core ahci libahci scsi_transport_sas button pcc_cpufreq acpi_cpufreq intel_agp intel_gtt agpgart Feb 20 01:30:56 Tower kernel: CPU: 3 PID: 18661 Comm: kworker/u32:2 Not tainted 4.18.20-unRAID #1 Feb 20 01:30:56 Tower kernel: Hardware name: System manufacturer System Product Name/P7H55-M LX, BIOS 0406 06/18/2012 Feb 20 01:30:56 Tower kernel: Workqueue: events_unbound async_run_entry_fn Feb 20 01:30:56 Tower kernel: RIP: 0010:__ata_qc_complete+0x16/0xfb Feb 20 01:30:56 Tower kernel: Code: 12 c7 40 58 fd fc fb fa f6 46 1b 01 74 05 e9 b1 8f 00 00 c3 48 85 ff 41 54 55 53 48 89 fb 75 02 0f 0b 48 8b 43 50 a8 01 75 02 <0f> 0b 48 8b 53 08 a8 02 48 8b 2b 4c 8b 22 74 61 48 8b b3 a0 00 00 Feb 20 01:30:56 Tower kernel: RSP: 0018:ffffc90008997b20 EFLAGS: 00010046 Feb 20 01:30:56 Tower kernel: RAX: 0000000000010010 RBX: ffff880111841f30 RCX: 0000000006e33263 Feb 20 01:30:56 Tower kernel: RDX: 0000000000000046 RSI: ffff880111841fe8 RDI: ffff880111841f30 Feb 20 01:30:56 Tower kernel: RBP: ffffc90008997be0 R08: 00000000000243a0 R09: ffffffffa00f1c47 Feb 20 01:30:56 Tower kernel: R10: ffffea00004bca80 R11: 0000000000000e6c R12: ffff8801118424c0 Feb 20 01:30:56 Tower kernel: R13: ffffc90008997c70 R14: ffff880111840000 R15: 0000000000000000 Feb 20 01:30:56 Tower kernel: FS: 0000000000000000(0000) GS:ffff8801134c0000(0000) knlGS:0000000000000000 Feb 20 01:30:56 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 20 01:30:56 Tower kernel: CR2: 000000c4205ef000 CR3: 0000000001e0a001 CR4: 00000000000206e0 Feb 20 01:30:56 Tower kernel: Call Trace: Feb 20 01:30:56 Tower kernel: ata_exec_internal_sg+0x2b1/0x4c9 Feb 20 01:30:56 Tower kernel: ata_exec_internal+0x6a/0x89 Feb 20 01:30:56 Tower kernel: ata_do_dev_read_id+0x17/0x19 Feb 20 01:30:56 Tower kernel: ata_dev_read_id+0xfc/0x457 Feb 20 01:30:56 Tower kernel: ? ata_eh_reset+0x8b9/0xa1a Feb 20 01:30:56 Tower kernel: ata_dev_reread_id+0x41/0x98 Feb 20 01:30:56 Tower kernel: ata_dev_revalidate+0x86/0x17f Feb 20 01:30:56 Tower kernel: ata_eh_recover+0x6ae/0xfe8 Feb 20 01:30:56 Tower kernel: ? vprintk_emit+0x16b/0x17d Feb 20 01:30:56 Tower kernel: ? ata_phys_link_offline+0x4f/0x4f Feb 20 01:30:56 Tower kernel: ? sas_ata_sched_eh+0x56/0x56 [libsas] Feb 20 01:30:56 Tower kernel: ? ata_phys_link_online+0x4f/0x4f Feb 20 01:30:56 Tower kernel: ata_do_eh+0x47/0x91 Feb 20 01:30:56 Tower kernel: ? ata_phys_link_online+0x4f/0x4f Feb 20 01:30:56 Tower kernel: ? sas_ata_sched_eh+0x56/0x56 [libsas] Feb 20 01:30:56 Tower kernel: ? ata_phys_link_offline+0x4f/0x4f Feb 20 01:30:56 Tower kernel: ata_scsi_port_error_handler+0x221/0x53c Feb 20 01:30:56 Tower kernel: async_sas_ata_eh+0x3f/0xba0 [libsas] Feb 20 01:30:56 Tower kernel: async_run_entry_fn+0x33/0xc5 Feb 20 01:30:56 Tower kernel: process_one_work+0x16e/0x24f Feb 20 01:30:56 Tower kernel: ? cancel_delayed_work_sync+0xa/0xa Feb 20 01:30:56 Tower kernel: worker_thread+0x1dc/0x2ac Feb 20 01:30:56 Tower kernel: kthread+0x10b/0x113 Feb 20 01:30:56 Tower kernel: ? kthread_flush_work_fn+0x9/0x9 Feb 20 01:30:56 Tower kernel: ret_from_fork+0x35/0x40 Feb 20 01:30:56 Tower kernel: ---[ end trace 1ba83a30263be2c0 ]--- Feb 20 01:30:56 Tower kernel: ata12.00: failed to IDENTIFY (I/O error, err_mask=0x11) Feb 20 01:30:56 Tower kernel: ata12.00: revalidation failed (errno=-5) Feb 20 01:30:56 Tower kernel: mvsas 0000:02:00.0: Phy5 : No sig fis Feb 20 01:31:00 Tower kernel: sas: sas_form_port: phy5 belongs to port5 already(1)! Feb 20 01:31:01 Tower kernel: ata12: hard resetting link Feb 20 01:31:16 Tower kernel: ata12.00: qc timeout (cmd 0x27) Feb 20 01:31:16 Tower kernel: ata12.00: failed to read native max address (err_mask=0x4) Feb 20 01:31:16 Tower kernel: ata12.00: HPA support seems broken, skipping HPA handling Feb 20 01:31:16 Tower kernel: ata12.00: revalidation failed (errno=-5) Feb 20 01:31:16 Tower kernel: ata12.00: limiting speed to UDMA/100:PIO3 Feb 20 01:31:16 Tower kernel: ata12: hard resetting link Feb 20 01:31:19 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1435:mvs_I_T_nexus_reset for device[5]:rc= 0 Feb 20 01:31:19 Tower kernel: mvsas 0000:02:00.0: Phy5 : No sig fis Feb 20 01:31:23 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1870:Release slot [0] tag[0], task [00000000a61ba796]: Feb 20 01:31:23 Tower kernel: sas: sas_ata_task_done: SAS error 8a Feb 20 01:31:23 Tower kernel: ata12.00: failed to IDENTIFY (I/O error, err_mask=0x11) Feb 20 01:31:23 Tower kernel: ata12.00: revalidation failed (errno=-5) Feb 20 01:31:23 Tower kernel: ata12.00: disabled Feb 20 01:31:23 Tower kernel: ata12: EH complete Feb 20 01:31:23 Tower kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 20 tries: 1 Feb 20 01:31:23 Tower kernel: sas: sas_form_port: phy5 belongs to port5 already(1)! Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] tag#7 CDB: opcode=0x8a 8a 00 00 00 00 00 43 10 ec 38 00 00 02 00 00 00 Feb 20 01:31:23 Tower kernel: print_req_error: I/O error, dev sds, sector 1125182520 Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] tag#8 CDB: opcode=0x8a 8a 00 00 00 00 00 43 10 ea 38 00 00 02 00 00 00 Feb 20 01:31:23 Tower kernel: print_req_error: I/O error, dev sds, sector 1125182008 Feb 20 01:31:23 Tower kernel: md: disk0 write error, sector=1125182456 Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] tag#9 CDB: opcode=0x8a 8a 00 00 00 00 00 43 10 e8 d8 00 00 01 60 00 00 Feb 20 01:31:23 Tower kernel: print_req_error: I/O error, dev sds, sector 1125181656 Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] tag#10 CDB: opcode=0x8a 8a 00 00 00 00 00 43 10 e6 d8 00 00 02 00 00 00 Feb 20 01:31:23 Tower kernel: print_req_error: I/O error, dev sds, sector 1125181144 Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] tag#11 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] tag#11 CDB: opcode=0x8a 8a 00 00 00 00 00 43 10 e4 d8 00 00 02 00 00 00 Feb 20 01:31:23 Tower kernel: print_req_error: I/O error, dev sds, sector 1125180632 Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] tag#12 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] tag#12 CDB: opcode=0x8a 8a 00 00 00 00 00 43 10 e2 d8 00 00 02 00 00 00 Feb 20 01:31:23 Tower kernel: print_req_error: I/O error, dev sds, sector 1125180120 Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] tag#13 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] tag#13 CDB: opcode=0x8a 8a 00 00 00 00 00 43 10 e0 d8 00 00 02 00 00 00 Feb 20 01:31:23 Tower kernel: print_req_error: I/O error, dev sds, sector 1125179608 Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] tag#14 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] tag#14 CDB: opcode=0x8a 8a 00 00 00 00 00 43 10 de d8 00 00 02 00 00 00 Feb 20 01:31:23 Tower kernel: print_req_error: I/O error, dev sds, sector 1125179096 Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] tag#15 CDB: opcode=0x8a 8a 00 00 00 00 00 43 10 dc d8 00 00 02 00 00 00 Feb 20 01:31:23 Tower kernel: print_req_error: I/O error, dev sds, sector 1125178584 Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] tag#16 CDB: opcode=0x8a 8a 00 00 00 00 00 43 10 da d8 00 00 02 00 00 00 Feb 20 01:31:23 Tower kernel: print_req_error: I/O error, dev sds, sector 1125178072 Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] Read Capacity(16) failed: Result: hostbyte=0x04 driverbyte=0x00 Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] Sense not available. Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] Read Capacity(10) failed: Result: hostbyte=0x04 driverbyte=0x00 Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] Sense not available. Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] 0 512-byte logical blocks: (0 B/0 B) Feb 20 01:31:23 Tower kernel: sd 7:0:5:0: [sds] 4096-byte physical blocks Feb 20 01:31:23 Tower kernel: sds: detected capacity change from 6001175126016 to 0 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182464 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182472 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182480 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182488 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182496 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182504 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182512 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182520 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182528 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182536 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182544 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182552 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182560 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182568 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182576 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182584 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182592 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182600 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182608 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182616 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182624 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182632 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182640 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182648 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182656 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182664 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182672 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182680 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182688 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182696 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182704 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182712 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182720 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182728 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182736 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182744 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182752 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182760 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182768 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182776 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182784 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182792 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182800 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182808 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182816 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182824 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182832 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182840 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182848 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182856 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182864 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182872 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182880 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182888 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182896 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182904 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182912 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182920 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182928 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182936 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182944 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182952 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182960 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125181944 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125181952 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125181960 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125181968 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125181976 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125181984 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125181992 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182000 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182008 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182016 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182024 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182032 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182040 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182048 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182056 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182064 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182072 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182080 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182088 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182096 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182104 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182112 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182120 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182128 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182136 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182144 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182152 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182160 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182168 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182176 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182184 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182192 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182200 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182208 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182216 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182224 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182232 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182240 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182248 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182256 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182264 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182272 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182280 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182288 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182296 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182304 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182312 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182320 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182328 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182336 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182344 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182352 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182360 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182368 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182376 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182384 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182392 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182400 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182408 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182416 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182424 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182432 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182440 Feb 20 01:31:25 Tower kernel: md: disk0 write error, sector=1125182448 So my question is what should I best do now, before I ran the user script there were no errors reported every time I did a parity check. The only change I made was to change the value for the tuneables as suggested in the Wiki.
  10. Hi there I am using sickbeard together with headless-kodi and mariadb sql docker, all these worked fine but for the past few weeks every time I select update kodi it says it sends the update to the port but when I check kodi afterwards it does not show the updated shows, in the logs from sickbeard I can see that it was sent, however how can I verify why headless kodi is not updating the database anymore unless I do a manual library update?
  11. So how will I get the 2 tb of data back to the replacement drive?
  12. Hi there, I replaced a 2 TB drive yesterday with a 4 TB drive, I powered down the server replaced the drive and once the server was up I chose the new drive in the old drives position and started the rebuild then I saw a message that it was unmountable and it gave me an option to format the drive which I did, I aborted the existing parity resync and started it again. It now finished but there is no data on the drive and it shows a utilization of 4 gb. Luckily I still have the original drive as it did not fail, but what did I do wrong here? I have attached my diagnostic file tower-diagnostics-20180129-0742.zip
  13. Hi there, can you please advise if the card is still available?
  14. I figured out the IP address of my server changed but did not realise it.