Kandinsky
-
Posts
31 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Kandinsky
-
-
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 -
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!
-
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
-
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
-
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.
-
/config /mnt/cache/Transmission/
/downloads/ /mnt/cache/
-
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.
-
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!
-
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!
-
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
-
I get the following errors: I even chmod 777 the /boot/lms directory and all things under it but seems to not make any difference. Where am I going wrong please?
I don't find a .pid file and LMS is not running. I assume there is some reason a difference in permissions for /boot/lms and /usr/local ?
chown: changing ownership of `/boot/lms/slimserver/Cache/library.db-wal': Operation not permitted chown: changing ownership of `/boot/lms/slimserver/Cache/library.db-shm': Operation not permitted chown: changing ownership of `/boot/lms/slimserver/Cache/persist.db-wal': Operation not permitted chown: changing ownership of `/boot/lms/slimserver/Cache/persist.db-shm': Operation not permitted chown: changing ownership of `/boot/lms/slimserver/Cache': Operation not permitted chown: changing ownership of `/boot/lms/slimserver': Operation not permitted chown: changing ownership of `/boot/lms': Operation not permitted ... OK Starting LMS... lms.pid not created for some reason... OK
-
Dear Experts,
I'm still having the issue that I get when I try to install LMS to anything either than "usr/local/slimserver" on the main flash drive or an extra mounted flash USB stick. The same error crops up each time "lms.pid cannot be started".
The problem is of course that 'local' is in memory and each time I reboot I lose all my settings. Any advice please as to how I can get LMS to install (ideally on a separate mounted flash USB stick rather than the unraid one to save on writes to the drive).
Any insight gratefully received.
-
Good advice. Would it be within my rights to send it back for a replacement to Seagate?
-
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
-
The errors indicate a SATA problem. Two of the drives, hda and hdb, are not configured as AHCI in BIOS. All of the drive designations should begin with sd. This may be causing the issue and should be fixed in any case. It is difficult to match ata numbers with device names or sd letter assignment. The device model is indicated here:
May 21 08:40:59 GOOGOLPLEX kernel: ata4.00: ATA-8: SAMSUNG HD204UI, 1AQ10001, max UDMA/133
See here if the AHCI setting doesn't work: http://lime-technology.com/forum/index.php?topic=27414.msg241280#msg241280
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?
-
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!
-
Dear Experts,
I am getting the errors below which seem to be repeating themselves over a short period of time. Should I be worried, if so how can I identify which drive is looking dodgy please? I am using the latest 12a release.
Now with full syslog attached. Not sure which drive I need to give any smart report on since I don't know which one it is.
May 19 12:20:10 GOOGOLPLEX kernel: ata1.00: exception Emask 0x50 SAct 0x0 SErr 0x800 action 0x6 frozen (Errors)
May 19 12:20:10 GOOGOLPLEX kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors)
May 19 12:20:10 GOOGOLPLEX kernel: ata1: SError: { HostInt } (Errors)
May 19 12:20:10 GOOGOLPLEX kernel: ata1.00: failed command: IDENTIFY DEVICE (Minor Issues)
May 19 12:20:10 GOOGOLPLEX kernel: ata1.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in (Drive related)
May 19 12:20:10 GOOGOLPLEX kernel: res 50/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x50 (ATA bus error) (Errors)
May 19 12:20:10 GOOGOLPLEX kernel: ata1.00: status: { DRDY } (Drive related)
May 19 12:20:10 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues)
May 19 12:20:20 GOOGOLPLEX kernel: ata1: softreset failed (1st FIS failed) (Minor Issues)
May 19 12:20:20 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues)
May 19 12:20:30 GOOGOLPLEX kernel: ata1: softreset failed (1st FIS failed) (Minor Issues)
May 19 12:20:30 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues)
May 19 12:20:31 GOOGOLPLEX kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related)
May 19 12:20:31 GOOGOLPLEX kernel: ata1.00: link online but device misclassified (Drive related)
May 19 12:20:36 GOOGOLPLEX kernel: ata1.00: qc timeout (cmd 0xec) (Drive related)
May 19 12:20:36 GOOGOLPLEX kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) (Errors)
May 19 12:20:36 GOOGOLPLEX kernel: ata1.00: revalidation failed (errno=-5) (Minor Issues)
May 19 12:20:36 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues)
May 19 12:20:46 GOOGOLPLEX kernel: ata1: softreset failed (1st FIS failed) (Minor Issues)
May 19 12:20:46 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues)
May 19 12:20:56 GOOGOLPLEX kernel: ata1: softreset failed (1st FIS failed) (Minor Issues)
May 19 12:20:56 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues)
May 19 12:20:56 GOOGOLPLEX kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related)
May 19 12:20:56 GOOGOLPLEX kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x100) (Errors)
May 19 12:20:56 GOOGOLPLEX kernel: ata1.00: revalidation failed (errno=-5) (Minor Issues)
May 19 12:20:56 GOOGOLPLEX kernel: ata1: limiting SATA link speed to 1.5 Gbps (Drive related)
May 19 12:21:01 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues)
May 19 12:21:02 GOOGOLPLEX kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) (Drive related)
May 19 12:21:02 GOOGOLPLEX kernel: ata1.00: configured for UDMA/133 (Drive related)
May 19 12:21:02 GOOGOLPLEX kernel: ata1: EH complete (Drive related)
May 19 12:21:44 GOOGOLPLEX kernel: mdcmd (51): check CORRECT (unRAID engine)
May 19 12:21:44 GOOGOLPLEX kernel: md: recovery thread woken up ... (unRAID engine)
May 19 12:21:44 GOOGOLPLEX kernel: md: recovery thread checking parity... (unRAID engine)
May 19 12:21:44 GOOGOLPLEX kernel: md: using 1536k window, over a total of 2930266532 blocks. (unRAID engine)
May 19 12:22:32 GOOGOLPLEX kernel: ata1.00: exception Emask 0x50 SAct 0x0 SErr 0x400801 action 0x6 frozen (Errors)
May 19 12:22:32 GOOGOLPLEX kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors)
May 19 12:22:32 GOOGOLPLEX kernel: ata1: SError: { RecovData HostInt Handshk } (Errors)
May 19 12:22:32 GOOGOLPLEX kernel: ata1.00: failed command: READ DMA EXT (Minor Issues)
May 19 12:22:32 GOOGOLPLEX kernel: ata1.00: cmd 25/00:00:40:20:14/00:04:00:00:00/e0 tag 0 dma 524288 in (Drive related)
May 19 12:22:32 GOOGOLPLEX kernel: res 50/00:00:3f:20:14/00:00:00:00:00/e0 Emask 0x50 (ATA bus error) (Errors)
May 19 12:22:32 GOOGOLPLEX kernel: ata1.00: status: { DRDY } (Drive related)
May 19 12:22:32 GOOGOLPLEX kernel: ata1: hard resetting link (Minor Issues)
May 19 12:22:32 GOOGOLPLEX kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) (Drive related)
May 19 12:22:32 GOOGOLPLEX kernel: ata1.00: configured for UDMA/133 (Drive related)
May 19 12:22:32 GOOGOLPLEX kernel: ata1: EH complete (Drive related)
May 19 12:22:33 GOOGOLPLEX kernel: ata1.00: exception Emask 0x50 SAct 0x0 SErr 0x800 action 0x6 frozen (Errors)
May 19 12:22:33 GOOGOLPLEX kernel: ata1.00: irq_stat 0x08000000, interface fatal error (Errors)
May 19 12:22:33 GOOGOLPLEX kernel: ata1: SError: { HostInt } (Errors)
May 19 12:22:33 GOOGOLPLEX kernel: ata1.00: failed command: READ DMA EXT (Minor Issues)
May 19 12:22:33 GOOGOLPLEX kernel: ata1.00: cmd 25/00:00:40:80:14/00:04:00:00:00/e0 tag 0 dma 524288 in (Drive related)
May 19 12:22:33 GOOGOLPLEX kernel: res 50/00:00:3f:80:14/00:00:00:00:00/e0 Emask 0x50 (ATA bus error) (Errors)
May 19 12:22:33 GOOGOLPLEX kernel: ata1.00: status: { DRDY } (Drive related)
-
Dear Experts,
I seem to be having problems getting LMS to install anywhere except into RAM on 'local'.
If I try to install into /mnt/user/xxx or even on the USB stick via /boot/LMS/ I always get the error when trying to start LMS which is shown below "lms.pid not created".
Any advice as to how to get it to run on my USB stick (best case) or even a HDD would be great as I can't work it out at the moment and each time I reboot the box I lose all my settings for it.
Oh and I am using logitechmediaserver-v1.4.plg if that helps.
/etc/rc.d/rc.lms enable 9000 /mnt/user/_slimserver yes /mnt/user/.slimserver
Applying Settings (enable) ...
Installing LMS...
Extracting LMS application to /tmp...
Cleaning unnecessary files...
Moving LMS application to /mnt/user/_slimserver...
Creating default playlist directory (/mnt/user/_slimserver/playlists)
Changing ownership (nobody) & permissions (0770 rwxrwx---)
... OK
Installing LMS...
Extracting LMS application to /tmp...
Cleaning unnecessary files...
Moving LMS application to /mnt/user/_slimserver...
Creating default playlist directory (/mnt/user/_slimserver/playlists)
Changing ownership (nobody) & permissions (0770 rwxrwx---)
... OK
Starting LMS...
lms.pid not created for some reason... OK
Many thanks in advance!
-
Run checkdisk on the flash in a PC or Mac.
Run reiserfsck check on all of the data drives. See Check File Systems in my sig.
Thanks to everyone for their input.
The final reason why the system was dropping off the network and file transfers timing out was due to file system problems. Once I ran the reiserfsck --check and subsequent fix commands on 2 drives. No the problem has gone away and back to writing files no problems so it wasn't anything to do with the NIC (realtec).
There is no indication in the log files that there was a file system problem so I assume there is no way to actually know you need to run the fix on them? I assume it would be good practice to perform a periodic reiserfsck on all drives. Are there any plugins for this to automate the process or report on it at all?
-
Dear Experts,
Should I be worried with the SMART report below please? I did have to run a reiserfsck --fix-fixable on this drive as well which is a concern. Do you think Samsung would accept it as an RMA or does it have to fail completely or not pass the SMART test in order to qualify for a replacement?
smartctl -a -d ata /dev/sdd
smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)
Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Device Model: SAMSUNG HD204UI
Serial Number: S2H7J1BB228759
Firmware Version: 1AQ10001
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: Mon Dec 3 23:38:13 2012 GMT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 25) The self-test routine was aborted by
the host.
Total time to complete Offline
data collection: (20880) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 255) minutes.
SCT capabilities: (0x003f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 0
2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0
3 Spin_Up_Time 0x0023 071 064 025 Pre-fail Always - 8902
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 388
5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0
8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 811
10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 69
181 Program_Fail_Cnt_Total 0x0022 100 100 000 Old_age Always - 25027
191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 179
192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0
194 Temperature_Celsius 0x0002 064 062 000 Old_age Always - 15 (Min/Max 7/40)
195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0
196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0036 097 097 000 Old_age Always - 1654
200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 1
223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0
225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 397
SMART Error Log Version: 1
ATA Error Count: 49 (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 49 occurred at disk power-on lifetime: 531 hours (22 days + 3 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:25.206 IDENTIFY DEVICE
00 00 01 01 00 00 00 08 00:01:25.206 NOP [Abort queued commands]
00 00 01 01 00 00 00 00 00:01:25.206 NOP [Abort queued commands]
00 00 01 01 00 00 00 00 00:01:25.206 NOP [Abort queued commands]
ef 10 02 00 00 00 a0 08 00:01:25.201 SET FEATURES [Reserved for Serial ATA]
Error 48 occurred at disk power-on lifetime: 531 hours (22 days + 3 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:25.185 IDENTIFY DEVICE
ec 00 00 00 00 00 a0 08 00:01:25.185 IDENTIFY DEVICE
ef 03 42 00 00 00 a0 08 00:01:25.185 SET FEATURES [set transfer mode]
ef 10 02 00 00 00 a0 08 00:01:25.185 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 08 00:01:25.185 READ NATIVE MAX ADDRESS EXT
Error 47 occurred at disk power-on lifetime: 531 hours (22 days + 3 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 d0 01 00 4f c2 00 08 00:01:25.182 SMART READ DATA
ef 10 02 00 00 00 a0 08 00:01:25.182 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 08 00:01:25.182 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 08 00:01:25.182 IDENTIFY DEVICE
ef 03 42 00 00 00 a0 08 00:01:25.182 SET FEATURES [set transfer mode]
Error 46 occurred at disk power-on lifetime: 531 hours (22 days + 3 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:25.168 IDENTIFY DEVICE
ef 03 42 00 00 00 a0 08 00:01:25.168 SET FEATURES [set transfer mode]
ef 10 02 00 00 00 a0 08 00:01:25.168 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 08 00:01:25.168 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 08 00:01:25.168 IDENTIFY DEVICE
Error 45 occurred at disk power-on lifetime: 521 hours (21 days + 17 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 20 00 00 00 e0 Error: ICRC, ABRT 32 sectors at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 20 00 00 00 e0 08 00:19:51.839 READ DMA
ef 10 02 00 00 00 a0 08 00:19:51.839 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 08 00:19:51.839 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 08 00:19:51.839 IDENTIFY DEVICE
ef 03 42 00 00 00 a0 08 00:19:51.839 SET FEATURES [set transfer mode]
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Aborted by host 90% 515 -
# 2 Extended offline Aborted by host 80% 512 -
# 3 Extended offline Aborted by host 90% 511 -
# 4 Short offline Aborted by host 70% 341 -
# 5 Short offline Completed without error 00% 338 -
# 6 Short offline Completed without error 00% 338 -
# 7 Short offline Completed without error 00% 336 -
# 8 Short offline Completed without error 00% 335 -
# 9 Short offline Completed without error 00% 333 -
#10 Short offline Completed without error 00% 332 -
#11 Short offline Completed without error 00% 330 -
#12 Short offline Completed without error 00% 329 -
#13 Extended offline Aborted by host 80% 325 -
#14 Short offline Completed without error 00% 260 -
#15 Short offline Completed without error 00% 151 -
Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run
SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Aborted_by_host [90% left] (0-65535)
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
-
Run checkdisk on the flash in a PC or Mac.
Run reiserfsck check on all of the data drives. See Check File Systems in my sig.
Thanks, that looks like it was a good idea. I get this error below. I understand from the Wiki that I need to be careful about using the --rebuild-tree. Any advice on this please?
Checking internal tree.. \/ 18 (of 18//165 (of 167\/ 1 (of 161|bad_path: The l eft delimiting key [11512 11513 0x1448b001 IND (1)] of the node (401319054) must be equal to the first element's key [11510 11511 0xbf89d001 IND (1)] within the node. /166 (of 167/block 4307355 15: The level of the node (0) is not correct, (2) expected
the problem in the internal node occured (430735515)finished
Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs.
Bad nodes were found, Semantic pass skipped
2 found corruptions can be fixed only when running with --rebuild-tree
-
Try this:
http://lime-technology.com/forum/index.php?topic=24271.msg211992#msg211992
It is a bit of a long shot as you had problems prior to rc8 but several people have had Samba problems in rc8 that were fixed by upgrading from 3.6.7 to 3.6.8
Thanks for the advice. I did upgrade to Samba 3.6.8 but the problem still seems to be happening. I did manage to capture the log file from the server whilst the network connection and webgui stopped working using the tail -f --lines=100 /var/log/syslog >/boot/syslogtail.txt command.
The file doesn't look easy to read but if anyone has ANY ideas of how I can fix this I would be so grateful as it can't be good for the system to have to hard reboot the box all the time.
Thanks in advance...
-
I had a similar issue some time ago, turned out it was due to the onboard nic sharing an IRQ with the secondary SATA controller.
Few questions - have you made any hardware changes recently?
Are you using the onboard nic? If so, what chipset is it? (mine was Realtek)
Are you using the onboard SATA connectors?
What size are the files you're attempting to copy?
Some tests:
1) Can you successfully copy 1+ GB of data from disk to disk using Midnight Commander (taking the network out of the equation)?
2) Can you successfully copy small (2-5 MB files) across the network?
3) Can you successfully copy 1+ GB file across the network?
If test 1 works and you are using the onboard nic, try adding a dedicated nic (most recommend Intel) and see if that makes any differenct.
OK I have tried all the network tests you suggested.
1. Yes no problem but was only running at less than 9Mb/s which seems slow (copied a 8Gb file between disks)
2. Yes they seem to copy including ones that were 50-60Mb
3. As soon as I tried to copy large video files it seems to crash the system
Streaming from unRAID is faultless and has never crashed when watching movies etc, its ONLY when writing files to the array. Do people think it's still a network problem please?
Is there a way to capture the log files onto the USB stick so that after the reboot I can see what errors are occuring as they get wiped when I reboot the box?
Thanks!
-
I had a similar issue some time ago, turned out it was due to the onboard nic sharing an IRQ with the secondary SATA controller.
Few questions - have you made any hardware changes recently?
Are you using the onboard nic? If so, what chipset is it? (mine was Realtek)
Are you using the onboard SATA connectors?
What size are the files you're attempting to copy?
Some tests:
1) Can you successfully copy 1+ GB of data from disk to disk using Midnight Commander (taking the network out of the equation)?
2) Can you successfully copy small (2-5 MB files) across the network?
3) Can you successfully copy 1+ GB file across the network?
If test 1 works and you are using the onboard nic, try adding a dedicated nic (most recommend Intel) and see if that makes any differenct.
No hardware changes recently other than replacing a 2Tb Parity drive with a 3Tb one but was writing file to the system for a couple of weeks.
The log file shows the network card to be:
Tower kernel: eth0: Identified chip type is 'RTL8168E/8111E'. (Network)
I am using a Foxconn A88GMV AMD 880G (Socket AM3) Motherboard and no extra SATA cards at the moment just the 6 onboard SATA connectors. I have also tried fitting some new SATA cables as well but to no avail.
I have also just tried a fresh vanilla install of unRAID 8a with only the unmenu plugin and just this morning tried to copy a 1Gb file which again ended up with the network drive no longer being visible and the webgui cannot be accessed anymore, so I assumed crashed again.
The motherboard BIOS is 2010 but not sure if upgrading it would make any difference. I will perform the tests you mentioned and report back.
Parity Check Disk Errors - Expert ideas please?
in General Support
Posted
Thanks. How can I map the ATA2 error to the SDX drive that needs a new cable please?