Kandinsky

Members
  • Posts

    31
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Kandinsky's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Thanks. How can I map the ATA2 error to the SDX drive that needs a new cable please?
  2. Dear Experts, I'm getting the error below repeating during a parity check. Any ideas please as to what's causing it and how to remedy it? Thanks in advance! Oct 24 19:03:58 GOOGOLPLEX kernel: ata2.00: configured for UDMA/33 Oct 24 19:03:58 GOOGOLPLEX kernel: ata2: EH complete Oct 24 19:03:59 GOOGOLPLEX kernel: ata2.00: exception Emask 0x50 SAct 0x0 SErr 0x280900 action 0x6 frozen Oct 24 19:03:59 GOOGOLPLEX kernel: ata2.00: irq_stat 0x08000000, interface fatal error Oct 24 19:03:59 GOOGOLPLEX kernel: ata2: SError: { UnrecovData HostInt 10B8B BadCRC } Oct 24 19:03:59 GOOGOLPLEX kernel: ata2.00: failed command: READ DMA EXT Oct 24 19:03:59 GOOGOLPLEX kernel: ata2.00: cmd 25/00:40:78:31:e6/00:05:06:00:00/e0 tag 27 dma 688128 in Oct 24 19:03:59 GOOGOLPLEX kernel: res 50/00:00:77:31:e6/00:00:06:00:00/e6 Emask 0x50 (ATA bus error) Oct 24 19:03:59 GOOGOLPLEX kernel: ata2.00: status: { DRDY } Oct 24 19:03:59 GOOGOLPLEX kernel: ata2: hard resetting link Oct 24 19:04:00 GOOGOLPLEX kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Oct 24 19:04:00 GOOGOLPLEX kernel: ata2.00: configured for UDMA/33
  3. Dear experts, For some reason (unknown to me) the log file access via the 'log' button on the GUI no longer appears. Reboots have no effect. This is concerning as I'm also seeing errors on one of the HDD with no easy way to check the details of the errors. I just get the spinning wheel on the browser and the "waiting for 192....." Nothing ever appears. Any advice on how I can get this to work again please? Am on the latest release as well. cheers!
  4. Dear Experts, I've been happy running transmission as a Docker app since V6 came out and it was made available within Docker. I recently stopped it and since then it just won't restart again. I've tried rebooting the server, manually selecting start, autostart is also enabled but nothing seems to work. It has served me well so far for torrents and would love to get it back up running again. This is in the log files for both unraid and the docker itself. *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/config.sh... The username is: admin The password is: password *** Killing all processes... emhttp: cmd: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker logs --tail=350 -f Transmission php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'start' 'Transmission' emhttp: cmd: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker logs --tail=350 -f Transmission Any ideas are very welcome! Cheers, Kand Modify message
  5. Dear Experts, I've been happy running transmission as s Docker app since V6 came out and it was made available within Docker. I recently stopped it and since then it just won't restart again. I've tried rebooting the server, manually selecting start, autostart is also enabled but nothing seems to work. It has served me well so far for torrents and would love to get it back up running again. This is in the log file. *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/config.sh... The username is: admin The password is: password *** Killing all processes... Any ideas are very welcome! Cheers, Kand
  6. I have never used a cache drive before upgrading to 6 hence why I seem to have come unstuck. 1. Yes my intention was to have all torrent downloads either files or folders to exist in /mnt/cache/downloads, if this is not the correct way to do it as I also want them to remain there and not be transferred to the array then the correct config would be useful. 2. I assume I should create the appdata share for cache only and then have all docker related content in there? Any advice for best use of cache drive and the transmission docker would be very useful please. I have found all of the previous downloads directories that have been moved to the array and either deleted them or moved them to a previous share.
  7. I am on 6.01 and after upgrading to 6 decided to start to use the Transmission Docker all seemed fine with the target directory being /mnt/cache/downloads both in the docker settings and in the transmission settings itself. Strange thing is that all the files only ever were written to a directory called 'incomplete' and never in downloads. Then randonly both the incomplete and the downloads directories disappear with no trace of the files as well as the config director on the cache drive. Any subsequent request to download anything now results in a "unable to resume file: no such file or directory". Here is a line from the log file... [2015-07-18 18:59:46.780 BST] Couldn't save temporary file "/config/resume/tvshow.mkv.eb483abd8b62b746.resume.tmp.qq2d4O": No such file or directory (variant.c:1227) Is this saying that it's trying to write to the USB stick rather than the file on the cache drive? It's very perspexing to say the least.
  8. Interestingly I have resolved the issue. It transpires there is a problem with the backplane on my 5 drive caddy which obviously is causing SATA errors which then seems to screw up the drives or at least unRaid things it is. Take the backplane out of the equation and link it directly to the M1015 and all is well. Very strange!
  9. Dear Experts, Please see below an extract from the log file for a specific HDD that keeps coming up with the same errors over and over. Is the drive faulty or should I investigate something else please? Sep 18 18:27:09 GOOGOLPLEX kernel: ata1.00: exception Emask 0x50 SAct 0x0 SErr 0x280900 action 0x6 frozen (Errors) Sep 18 18:27:09 GOOGOLPLEX kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors) Sep 18 18:27:09 GOOGOLPLEX kernel: ata1: SError: { UnrecovData HostInt 10B8B BadCRC } (Errors) Sep 18 18:27:09 GOOGOLPLEX kernel: ata1.00: failed command: IDENTIFY DEVICE (Minor Issues) Sep 18 18:27:09 GOOGOLPLEX kernel: ata1.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in (Drive related) Sep 18 18:27:09 GOOGOLPLEX kernel: res 50/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x50 (ATA bus error) (Errors) Sep 18 18:27:09 GOOGOLPLEX kernel: ata1.00: status: { DRDY } (Drive related) Sep 18 18:27:09 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues) Sep 18 18:27:10 GOOGOLPLEX kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) (Drive related) Sep 18 18:27:10 GOOGOLPLEX kernel: ata1.00: configured for UDMA/33 (Drive related) Sep 18 18:27:10 GOOGOLPLEX kernel: ata1: EH complete (Drive related) Sep 18 18:31:54 GOOGOLPLEX kernel: ata1.00: exception Emask 0x50 SAct 0x0 SErr 0x280900 action 0x6 frozen (Errors) Sep 18 18:31:54 GOOGOLPLEX kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors) Sep 18 18:31:54 GOOGOLPLEX kernel: ata1: SError: { UnrecovData HostInt 10B8B BadCRC } (Errors) Sep 18 18:31:54 GOOGOLPLEX kernel: ata1.00: failed command: IDENTIFY DEVICE (Minor Issues) Sep 18 18:31:54 GOOGOLPLEX kernel: ata1.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in (Drive related) Sep 18 18:31:54 GOOGOLPLEX kernel: res 50/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x50 (ATA bus error) (Errors) Sep 18 18:31:54 GOOGOLPLEX kernel: ata1.00: status: { DRDY } (Drive related) Sep 18 18:31:54 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues) Sep 18 18:31:55 GOOGOLPLEX kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) (Drive related) Sep 18 18:31:55 GOOGOLPLEX kernel: ata1.00: configured for UDMA/33 (Drive related) Sep 18 18:31:55 GOOGOLPLEX kernel: ata1: EH complete (Drive related) SMART Report: ATA Error Count: 171 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 171 occurred at disk power-on lifetime: 1859 hours (77 days + 11 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 00 00 00 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ec 00 01 00 00 00 00 08 00:04:43.993 IDENTIFY DEVICE b0 da 00 00 4f c2 00 08 00:04:43.992 SMART RETURN STATUS b0 d1 01 01 4f c2 00 08 00:04:43.992 SMART READ ATTRIBUTE THRESHOLDS [OBS-4] b0 d0 01 00 4f c2 00 08 00:04:43.992 SMART READ DATA ec 00 01 00 00 00 00 08 00:04:43.992 IDENTIFY DEVICE Error 170 occurred at disk power-on lifetime: 1859 hours (77 days + 11 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 4f c2 00 Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- b0 d1 01 01 4f c2 00 08 00:04:43.965 SMART READ ATTRIBUTE THRESHOLDS [OBS-4] b0 d0 01 00 4f c2 00 08 00:04:43.965 SMART READ DATA ec 00 01 00 00 00 00 08 00:04:43.965 IDENTIFY DEVICE e5 00 00 00 00 00 00 08 00:04:43.965 CHECK POWER MODE ec 00 01 00 00 00 00 08 00:04:43.965 IDENTIFY DEVICE Error 169 occurred at disk power-on lifetime: 1859 hours (77 days + 11 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 4f c2 00 Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- b0 d1 01 01 4f c2 00 08 00:04:43.932 SMART READ ATTRIBUTE THRESHOLDS [OBS-4] b0 d0 01 00 4f c2 00 08 00:04:43.931 SMART READ DATA ec 00 01 00 00 00 00 08 00:04:43.931 IDENTIFY DEVICE e5 00 00 00 00 00 00 08 00:04:43.931 CHECK POWER MODE ec 00 01 00 00 00 00 08 00:04:43.931 IDENTIFY DEVICE Error 168 occurred at disk power-on lifetime: 1859 hours (77 days + 11 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 4f c2 00 Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- b0 d1 01 01 4f c2 00 08 00:04:43.872 SMART READ ATTRIBUTE THRESHOLDS [OBS-4] b0 d0 01 00 4f c2 00 08 00:04:43.871 SMART READ DATA ec 00 01 00 00 00 00 08 00:04:43.871 IDENTIFY DEVICE e5 00 00 00 00 00 00 08 00:04:43.871 CHECK POWER MODE ec 00 01 00 00 00 00 08 00:04:43.871 IDENTIFY DEVICE Error 167 occurred at disk power-on lifetime: 1859 hours (77 days + 11 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 00 00 00 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ec 00 01 00 00 00 00 08 00:04:43.871 IDENTIFY DEVICE e5 00 00 00 00 00 00 08 00:04:43.871 CHECK POWER MODE ec 00 01 00 00 00 00 08 00:04:43.871 IDENTIFY DEVICE b0 d1 01 01 4f c2 00 08 00:04:43.869 SMART READ ATTRIBUTE THRESHOLDS [OBS-4] b0 d0 01 00 4f c2 00 08 00:04:43.868 SMART READ DATA Many thanks!
  10. Could someone please advise if these drive errors on a new 3Tb Tosh drive are something to be concerned about? ATA Error Count: 1633 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 1633 occurred at disk power-on lifetime: 582 hours (24 days + 6 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 21 37 a1 5b 01 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 80 00 d8 a0 5b 40 00 2d+06:06:13.068 READ FPDMA QUEUED 60 b0 00 a8 dc 5b 40 00 2d+06:06:12.971 READ FPDMA QUEUED 60 50 00 58 dc 5b 40 00 2d+06:06:12.970 READ FPDMA QUEUED 60 08 00 d0 37 4a 40 00 2d+06:06:12.970 READ FPDMA QUEUED 60 00 00 58 d8 5b 40 00 2d+06:06:12.895 READ FPDMA QUEUED Error 1632 occurred at disk power-on lifetime: 582 hours (24 days + 6 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 91 2f e1 4c 01 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 c0 e0 4c 40 00 2d+06:02:13.271 READ FPDMA QUEUED 60 70 00 50 dd 4c 40 00 2d+06:02:13.082 READ FPDMA QUEUED 60 90 00 c0 dc 4c 40 00 2d+06:02:13.081 READ FPDMA QUEUED 60 08 00 18 34 4a 40 00 2d+06:02:13.081 READ FPDMA QUEUED 60 00 00 c0 d8 4c 40 00 2d+06:02:13.002 READ FPDMA QUEUED Error 1631 occurred at disk power-on lifetime: 536 hours (22 days + 8 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 f1 ff 51 c4 0e Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 f0 4f c4 40 00 08:21:06.684 READ FPDMA QUEUED 60 00 00 f0 4b c4 40 00 08:21:06.682 READ FPDMA QUEUED 60 00 00 f0 47 c4 40 00 08:21:06.679 READ FPDMA QUEUED 60 00 00 f0 43 c4 40 00 08:21:06.676 READ FPDMA QUEUED 60 00 00 f0 3f c4 40 00 08:21:06.673 READ FPDMA QUEUED Error 1630 occurred at disk power-on lifetime: 536 hours (22 days + 8 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 01 ef 81 04 03 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 f0 7f 04 40 00 08:20:58.973 READ FPDMA QUEUED 60 00 00 f0 7b 04 40 00 08:20:58.970 READ FPDMA QUEUED 60 00 00 f0 77 04 40 00 08:20:58.966 READ FPDMA QUEUED 60 00 00 f0 73 04 40 00 08:20:58.963 READ FPDMA QUEUED 60 00 00 f0 6f 04 40 00 08:20:58.960 READ FPDMA QUEUED Error 1629 occurred at disk power-on lifetime: 536 hours (22 days + 8 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 91 d7 41 dc 03 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 68 40 dc 40 00 08:20:56.149 READ FPDMA QUEUED 60 00 00 68 3c dc 40 00 08:20:56.147 READ FPDMA QUEUED 60 00 00 68 38 dc 40 00 08:20:56.143 READ FPDMA QUEUED 60 00 00 68 34 dc 40 00 08:20:56.140 READ FPDMA QUEUED 60 00 00 68 30 dc 40 00 08:20:56.136 READ FPDMA QUEUED
  11. Good advice. Would it be within my rights to send it back for a replacement to Seagate?
  12. Dear Experts, Please see below the error log from my 2Tb Samsung drive. It has failed in the past in Unraid which I then removed and rebuilt and it seems to work again. Based on the error log below, should I be proactive and send the drive back and get a replacement or just stick with it and hope it doesn't fail again? Device Model: SAMSUNG HD203WI Serial Number: S1UYJ1BZ107154 Firmware Version: 1AN10003 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 6 Local Time is: Tue Jun 4 14:31:34 2013 BST SMART support is: Available - device has SMART capability. SMART support is: Enabled SMART overall-health : PASSED ATA Error Count: 69 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 69 occurred at disk power-on lifetime: 5125 hours (213 days + 13 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 00 00 a0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ec 00 00 00 00 00 a0 08 00:01:07.856 IDENTIFY DEVICE ec 00 00 00 00 00 a0 08 00:01:07.856 IDENTIFY DEVICE 00 00 01 01 00 00 00 08 00:01:07.856 NOP [Abort queued commands] 00 00 01 01 00 00 00 00 00:01:07.856 NOP [Abort queued commands] 00 00 01 01 00 00 00 00 00:01:07.856 NOP [Abort queued commands] Error 68 occurred at disk power-on lifetime: 5125 hours (213 days + 13 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 00 00 a0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ec 00 00 00 00 00 a0 08 00:01:07.851 IDENTIFY DEVICE ec 00 00 00 00 00 a0 08 00:01:07.851 IDENTIFY DEVICE 00 00 01 01 00 00 00 08 00:01:07.851 NOP [Abort queued commands] a1 00 00 00 00 00 a0 08 00:01:07.840 IDENTIFY PACKET DEVICE ec 00 00 00 00 00 a0 08 00:01:07.840 IDENTIFY DEVICE Error 67 occurred at disk power-on lifetime: 5125 hours (213 days + 13 hours) When the command that caused the error occurred, the device was in a reserved state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 00 00 a0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ec 00 00 00 00 00 a0 08 00:01:07.840 IDENTIFY DEVICE ec 00 00 00 00 00 a0 08 00:01:07.840 IDENTIFY DEVICE 00 00 01 01 00 00 00 08 00:01:07.839 NOP [Abort queued commands] 00 00 01 01 00 00 00 00 00:01:07.839 NOP [Abort queued commands] 00 00 01 01 00 00 00 00 00:01:07.839 NOP [Abort queued commands] Error 66 occurred at disk power-on lifetime: 5099 hours (212 days + 11 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 00 00 a0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ec 00 00 00 00 00 a0 08 00:00:18.771 IDENTIFY DEVICE ef 03 42 00 00 00 a0 08 00:00:18.771 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 00:00:18.771 IDENTIFY DEVICE 00 00 01 01 00 00 00 08 00:00:18.771 NOP [Abort queued commands] 00 00 01 01 00 00 00 00 00:00:18.771 NOP [Abort queued commands] Error 65 occurred at disk power-on lifetime: 5099 hours (212 days + 11 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 00 00 a0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ec 00 00 00 00 00 a0 08 00:00:18.766 IDENTIFY DEVICE 00 00 01 01 00 00 00 08 00:00:18.766 NOP [Abort queued commands] 00 00 01 01 00 00 00 00 00:00:18.765 NOP [Abort queued commands] 00 00 01 01 00 00 00 00 00:00:18.765 NOP [Abort queued commands] ec 00 00 00 00 00 a0 08 00:00:18.760 IDENTIFY DEVICE
  13. Since I set the BIOS originally for AHCI, how can I have some HDD's showing up as sdX and some as hdx? Could it have anything to do with the drives themselves please?
  14. Dear Experts, I both replaced the cable and the drive since I had a spare one. Please see attached the updated log. Am i getting drive problems again as now its ata4. How can I correlate the ATA errors to the relevant HDD please as I can't see the link in the logs? Cheers! syslog-2013-05-23.zip