wickedathletes
-
Posts
435 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by wickedathletes
-
-
I had no problem updating to v1.0.0 all I did was restart the plex docker
from my logs
*** Running /etc/my_init.d/10_dbus.sh...
*** Running /etc/my_init.d/20_apt_update.sh...
*** Running /etc/my_init.d/30_update_plex.sh...
Target version: 1.0.0.2261-xxxxxxx set by: latest\plexpass
Upgrading from version: 0.9.17.3.2239-fe07491 to version: 1.0.0.2261-xxxxxxx
--2016-06-24 08:55:22-- https://downloads.plex.tv/plex-media-server/1.0.0.2261-xxxxxxxxxxx/plexmediaserver_1.0.0.2261-xxxxxxxxx_amd64.deb
Resolving downloads.plex.tv (downloads.plex.tv)... 104.20.7.9, 104.20.6.9, 2400:cb00:2048:1::6814:709, ...
Connecting to downloads.plex.tv (downloads.plex.tv)|104.20.7.9|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 99524576 (95M) [application/octet-stream]
Works perfectly for me too. Just restarted the docker as usual, no special action required.
started working now for me, maybe something was down this AM.
-
Am I to assume that since plex redid there site today and released version 1.0.0 we probably need an updated docker?
Warning: wildcards not supported in HTTP. The name is too long, 506 chars total. Trying to shorten... New name is plexmediaserver_<!DOCTYPE html>%0A<html>%0A<head>%0A%0A>%0A%0A var _gaq = _gaq || [];%0A _gaq.push(['_setAccount', 'UA-6111912-23']);%0A _gaq.push(['_setDomainName', 'plex.tv']);%0A%0A (function() {%0A%0Awww') + '.google-ana. The name is too long, 506 chars total. Trying to shorten... New name is plexmediaserver_<!DOCTYPE html>%0A<html>%0A<head>%0A%0A>%0A%0A var _gaq = _gaq || [];%0A _gaq.push(['_setAccount', 'UA-6111912-23']);%0A _gaq.push(['_setDomainName', 'plex.tv']);%0A%0A (function() {%0A%0Awww') + '.google-ana. --2016-06-24 11:30:21-- https://downloads.plex.tv/plex-media-server/%3C!DOCTYPE%20html%3E%0A%3Chtml%3E%0A%3Chead%3E%0A%0A%3E%0A%0A%20%20%20%20var%20_gaq%20=%20_gaq%20%7C%7C%20[];%0A%20%20%20%20_gaq.push(['_setAccount',%20'UA-6111912-23']);%0A%20%20%20%20_gaq.push(['_setDomainName',%20'plex.tv']);%0A%0A%20%20%20%20(function()%20%7B%0A%0Awww')%20+%20'.google-analytics.com%0A%20%20%20%20%20%20var%20s%20=%20document.getElementsByTagName('script')[0];%20s.parentNode.insertBefore(ga,%20s);%0A%20%20%20%20%7D)();%0A%0A%0A%0A%3Cbody%3E%0A%20%20%3Cdiv%20class=%22block%22%3E%0A%20%20%20%20%3Cdiv%20class=%22dialog%22%3E%0A%0A%0A%0A%0A%0Aa%3E%20for%20current%20information.%20Thank%20you%20for%20your%20patience.%3C/plexmediaserver_%3C!DOCTYPE%20html%3E%0A%3Chtml%3E%0A%3Chead%3E%0A%0A%3E%0A%0A%20%20%20%20var%20_gaq%20=%20_gaq%20%7C%7C%20[];%0A%20%20%20%20_gaq.push(['_setAccount',%20'UA-6111912-23']);%0A%20%20%20%20_gaq.push(['_setDomainName',%20'plex.tv']);%0A%0A%20%20%20%20(function()%20%7B%0A%0Awww')%20+%20'.google-analytics.com%0A%20%20%20%20%20%20var%20s%20=%20document.getElementsByTagName('script')[0];%20s.parentNode.insertBefore(ga,%20s);%0A%20%20%20%20%7D)();%0A%0A%0A%0A%3Cbody%3E%0A%20%20%3Cdiv%20class=%22block%22%3E%0A%20%20%20%20%3Cdiv%20class=%22dialog%22%3E%0A%0A%0A%0A%0A%0Aa%3E%20for%20current%20information.%20Thank%20you%20for%20your%20patience.%3C_amd64.deb Resolving downloads.plex.tv (downloads.plex.tv)... 104.20.6.9, 104.20.7.9, 2400:cb00:2048:1::6814:709, ... Connecting to downloads.plex.tv (downloads.plex.tv)|104.20.6.9|:443... connected. HTTP request sent, awaiting response... 403 Forbidden 2016-06-24 11:30:21 ERROR 403: Forbidden. Warning: wildcards not supported in HTTP.just hoping I didn't break something
-
i think i am missing a step, but for some reason all my mounted usb drives mount without any permissions, so dolphin (docker) or windows explorer can not write to the drives. This worked for for me a few weeks ago and not its not, not really sure what could be causing it.
SMB is set to NO. I tried YES as well. I also tried having unassigned create the NFTS partition as well.
We need more information. What version of unRAID? What does it mean to mount with no permissions? I assume you are mounting the drives NTFS? So Windows can browse to the drive, but not write to it?
Check the UD log. It sounds like the drives are mounting read only. The log will give more information about the drives mounting.
Sometimes NTFS drives can't be mounted read/write and UD will go ahead and mount them read only so they can at lease be read. The log will give more information.
oddly enough its working now. Not sure why but its working. Could this have been the read/write issue you mentioned? Where some times it connects and sometimes it doesnt? I just switched to b23 of 6.2. I was on on b21 the last time it was working, if that matters at all. But again, its working now.
Weirdly enough I would have said it was just Dolphin acting up, because reinstalling dolphin is the only thing I did to "fix" it, however windows couldn't write to it either.
-
i think i am missing a step, but for some reason all my mounted usb drives mount without any permissions, so dolphin (docker) or windows explorer can not write to the drives. This worked for for me a few weeks ago and not its not, not really sure what could be causing it.
SMB is set to NO. I tried YES as well. I also tried having unassigned create the NFTS partition as well.
-
IMO that indicates a disk problem, error was recent, I would replace it.
do you think the first errors could also be because of this as well? I started an RMA on the drive.
-
the following was also on my smart scan of the ATA1 disk:
Error 74 occurred at disk power-on lifetime: 23799 hours (991 days + 15 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 a0 50 c0 67 04 Error: ICRC, ABRT 160 sectors at LBA = 0x0467c050 = 73908304 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 35 00 40 b0 be 67 e0 00 5d+13:05:34.474 WRITE DMA EXT 25 00 b8 c0 72 67 e0 00 5d+13:05:34.474 READ DMA EXT 35 00 d8 70 ae dc e0 00 5d+13:05:34.473 WRITE DMA EXT 35 00 40 30 a9 dc e0 00 5d+13:05:34.472 WRITE DMA EXT 35 00 40 f0 a3 dc e0 00 5d+13:05:34.471 WRITE DMA EXT Error 73 occurred at disk power-on lifetime: 23799 hours (991 days + 15 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 b0 b0 6f 3c 0c Error: ICRC, ABRT 176 sectors at LBA = 0x0c3c6fb0 = 205287344 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 35 00 40 20 6c 3c e0 00 5d+12:59:44.567 WRITE DMA EXT 25 00 38 e8 83 3c e0 00 5d+12:59:44.567 READ DMA EXT 25 00 40 a8 7e 3c e0 00 5d+12:59:44.559 READ DMA EXT 25 00 40 68 79 3c e0 00 5d+12:59:44.553 READ DMA EXT 25 00 40 28 74 3c e0 00 5d+12:59:44.546 READ DMA EXT Error 72 occurred at disk power-on lifetime: 23799 hours (991 days + 15 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 f0 30 ea b0 04 Error: ICRC, ABRT 240 sectors at LBA = 0x04b0ea30 = 78703152 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 35 00 40 e0 e7 b0 e0 00 5d+12:52:15.417 WRITE DMA EXT 35 00 40 a0 e2 b0 e0 00 5d+12:52:15.416 WRITE DMA EXT 25 00 c0 98 84 b3 e0 00 5d+12:52:15.413 READ DMA EXT 25 00 40 58 7f b3 e0 00 5d+12:52:15.395 READ DMA EXT 25 00 a8 80 95 b0 e0 00 5d+12:52:15.391 READ DMA EXT Error 71 occurred at disk power-on lifetime: 23751 hours (989 days + 15 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 0f 38 2f 0a Error: ICRC, ABRT 33 sectors at LBA = 0x0a2f380f = 170866703 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 f0 36 2f e0 00 3d+13:18:27.976 READ DMA EXT 25 00 40 b0 31 2f e0 00 3d+13:18:27.967 READ DMA EXT 25 00 80 30 2e 2f e0 00 3d+13:18:27.963 READ DMA EXT 25 00 40 f0 28 2f e0 00 3d+13:18:27.954 READ DMA EXT 25 00 40 b0 25 2f e0 00 3d+13:18:27.950 READ DMA EXT Error 70 occurred at disk power-on lifetime: 23751 hours (989 days + 15 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 c1 4f bb 5b 0f Error: ICRC, ABRT 193 sectors at LBA = 0x0f5bbb4f = 257669967 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 d0 b6 5b e0 00 3d+12:36:00.990 READ DMA EXT 25 00 c0 10 b6 5b e0 00 3d+12:36:00.989 READ DMA EXT 25 00 40 d0 b0 5b e0 00 3d+12:36:00.982 READ DMA EXT 25 00 c0 10 b0 5b e0 00 3d+12:36:00.981 READ DMA EXT 25 00 40 d0 aa 5b e0 00 3d+12:36:00.973 READ DMA EXT SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Interrupted (host reset) 90% 23217 - # 2 Short offline Completed without error 00% 23216 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 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.
-
If you want a UI like windows explorer get the Dolphin docker.
-
based on my own debugging its having trouble with 2 drives (ATA7 and ATA1)... although I am unsure at the moment if its a parity drive ATA1 or not (I have two drives with the same name), not sure of the drive location of my parity though and my ui is locked up.
is there a way I can tell if its parity or not? - Not my parity drive, found it in the var log.
Also, do you think this is more bad cable? bad port on mobo? not enough power? or just a drive slowly dying?
I recently swapped out my mobo for a new one, including an i7 and more ram. Honestly, didn't really pay attention enough prior to know if this was happening before or not (I definitely would have sporadic freezes though). These issues seem to ONLY happen when I try doing something via my windows PC to the machine though. Ive gone 30+ days without issue if I am not messing around with writing to it from a desktop app. CP/Sonarr run without issue for weeks.
Since I have a total of 12 SATA ports (4 SATA II and 8 SATA III) I can play around with the ports to check that. Not really sure how to check a possible power issue. I did not swap out my power supply, its a 520w, and I assumed it was enough for 9 drives (1 being SSD).
-
my logs are attached, I was running a program on my windows box called Ember Media Manager (it was placing jpg files on my server automatically) and my system locked up. Saw this in the log and now I can't connect. Any thoughts?
Jun 7 12:41:15 Hades kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jun 7 12:41:15 Hades kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jun 7 12:41:15 Hades kernel: ata1.00: configured for UDMA/133 Jun 7 12:41:15 Hades kernel: ata1: EH complete Jun 7 12:47:06 Hades kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen Jun 7 12:47:06 Hades kernel: ata1.00: irq_stat 0x08000000, interface fatal error Jun 7 12:47:06 Hades kernel: ata1: SError: { UnrecovData Handshk } Jun 7 12:47:06 Hades kernel: ata1.00: failed command: WRITE DMA EXT Jun 7 12:47:06 Hades kernel: ata1.00: cmd 35/00:40:b0:be:67/00:05:34:00:00/e0 tag 24 dma 688128 out Jun 7 12:47:06 Hades kernel: res 50/00:00:77:73:67/00:00:34:00:00/e4 Emask 0x10 (ATA bus error) Jun 7 12:47:06 Hades kernel: ata1.00: status: { DRDY } Jun 7 12:47:06 Hades kernel: ata1: hard resetting link Jun 7 12:47:06 Hades kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jun 7 12:47:06 Hades kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jun 7 12:47:06 Hades kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jun 7 12:47:06 Hades kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jun 7 12:47:06 Hades kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jun 7 12:47:06 Hades kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jun 7 12:47:06 Hades kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jun 7 12:47:06 Hades kernel: ata1.00: configured for UDMA/133 Jun 7 12:47:06 Hades kernel: ata1: EH complete Jun 7 12:52:49 Hades kernel: ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen Jun 7 12:52:49 Hades kernel: ata1.00: irq_stat 0x08000000, interface fatal error Jun 7 12:52:49 Hades kernel: ata1: SError: { UnrecovData Handshk } Jun 7 12:52:49 Hades kernel: ata1.00: failed command: WRITE DMA EXT Jun 7 12:52:49 Hades kernel: ata1.00: cmd 35/00:40:b8:f3:31/00:05:92:00:00/e0 tag 24 dma 688128 out Jun 7 12:52:49 Hades kernel: res 50/00:00:d7:79:e3/00:00:48:01:00/e8 Emask 0x10 (ATA bus error) Jun 7 12:52:49 Hades kernel: ata1.00: status: { DRDY } Jun 7 12:52:49 Hades kernel: ata1: hard resetting link Jun 7 12:52:49 Hades kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jun 7 12:52:49 Hades kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jun 7 12:52:49 Hades kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jun 7 12:52:49 Hades kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jun 7 12:52:49 Hades kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded Jun 7 12:52:49 Hades kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out Jun 7 12:52:49 Hades kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out Jun 7 12:52:49 Hades kernel: ata1.00: configured for UDMA/133 Jun 7 12:52:49 Hades kernel: ata1: EH complete -
I use a rsync gui on Windows (delta copy) to backup my data, mostly user folders and photos to unRaid. From there I back everything up to crash plan.
Works very well for me. Except that initial backup to the cloud takes forever, still 3 months!! to go. I am contemplating to also back up to a USB disk as I am only talking about 4TB of data.
Hope this helps
Roland
You haven't hit a RAM issue yet? I have 16GB in my server but CrashPlan kept hitting a RAM crash issue on me when I was trying to backup to the cloud 10TB. At the time I only had 8GB but still.
-
Reasons for lack of SMART -
* Really really really old drive (very unlikely, you would have to have a very old bus to connect it to)
* Unusual controller that doesn't pass SMART info (a firmware update for controller will sometimes fix it)
* Corrupted firmware on drive (perhaps corrupted by huge electrical spike (e.g. nearby lightning strike))
Note: normally the drive would have other serious problems too, but I've seen a drive that lost SMART and clicks more but otherwise is fine
* System has disabled the drive (usually requires a reboot for kernel to pick the drive back up)
Can't think of any others, might be though ...
thanks, good to know. Its definitely an old drive (at least 10 years), but its still SATA. Its never been a problem or had issues but has never in my recollection of v4, 5 or 6 been able to scan. Good to know though.
-
Do some drives just not support SMART statuses? My Drive 1 has never worked ever, it always just shows as unscanned (yellow). Its been working without an issue for 4 years though, so figured I would just check to see if there could be a specific reason some drives can't be scanned?
-
unraid_notify sounds like a very old script, highly unlikely to be something you want in v6.
based on my searches it seems to be some 4.x unmenu stuff for notification scripts.
-
Unfortunately, over the years people have posted these 2 ways to count the split level. The first way is the official LimeTech way.
Start numbering at the share = split level equals the last directory that can exist on multiple disks.
Start numbering at the first directory into the share = split level equals the first directory that can ONLY exist on a single disk.
The pictures are correct. Take level 3 for example. What the picture is saying is that the share (1), top level (2) and second level (3) can exist on multiple disks. However, the movie folder is only created on one disk which means all the movie files must exist on one disk.
I'm not a big fan of the text descriptions in the newest unRAID versions. The first top level directory is the share, which isn't the clearest for some people. The levels in the new unRAID settings do not match those Simple Features drawings.
Your splits look OK.
So to confirm (since now I just got confused (never open a thread that doesn't affect you)), if I want the below:
Movies (Share name)
--Antman (2015)
----Antman (2015).mkv
------Extras (3)
--------actor.jpg
and I want all my individual movie folders to be on a specific disk I would want Split Level 2 or Split Level 1. I assume Split Level 1.
-
Thank you for the feedback
~Spritz
I would recommend not splitting your music on more than one disk. It gets annoying with pauses when it has to spin up a new disk to get to the next track of a playlist, just my 2 cents.
-
The first line was used to auto install things from the unMenu PKG manager. Wasn't sure about the unraid_notify but it has a lot of matches when searching. See search tips in my sig.I was wondering, after comparing to a new 6.2b21 go file is any of the following old stuff I can remove?
cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c unraid_notify start
I notice during bootup is complains about unraid_notify. I searched the forums but didn't see to much about if this was truncated or not.
Unless you depend on something from unMenu you don't need either of these lines.
thanks, good to know about the first one, I had no idea what the heck it was. I don't think I ever used unMenu at all, but I did originally install it back when 5.0 was in early beta (when I joined unRAID). I Will search more about unraid_notify.
-
Since you haven't posted diagnostics not much we can add. The "3rd reboot was the charm" sounds similar to voodoo programming though.Logged into the console, can you write to it as the root user? Can you read from it,
ls
or
df
it? Have you tried formatting it again (since you can't write to it you have no data on it to lose) or running a filesystem check? Does it actually write any data to the disk or, as I suspect, is the 200 MB only going as far as the RAM cache? What does your syslog say? Any SMART errors? SMART extended test? Post diagnostics.
so oddly enough 3rd reboot was the charm... haha. I can now write to it. The syslogs showed nothing that I noticed.
the voodoo got it running though. My guess is something was left undone prior to rebooting (after format). By me trying to copy to it it left data corrupted or in a fuzzy state. After the reboot it might have stated the same. Honestly not sure, the machine cleanly rebooted all 3 times, and on the third time it worked fine.
-
I was wondering, after comparing to a new 6.2b21 go file is any of the following old stuff I can remove?
cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c unraid_notify start
I notice during bootup is complains about unraid_notify. I searched the forums but didn't see to much about if this was truncated or not.
-
Logged into the console, can you write to it as the root user? Can you read from it,
ls
or
df
it? Have you tried formatting it again (since you can't write to it you have no data on it to lose) or running a filesystem check? Does it actually write any data to the disk or, as I suspect, is the 200 MB only going as far as the RAM cache? What does your syslog say? Any SMART errors? SMART extended test? Post diagnostics.
so oddly enough 3rd reboot was the charm... haha. I can now write to it. The syslogs showed nothing that I noticed.
-
So I just moved 4TB off of a reiserFS formatted drive so I could finally switch all my drives to xfs. However, after formatting it to xfs nothing can write to it. Windows just hangs after moving about 200mb and dolphin hangs or eventually says Disk is Full.
Any thoughts? I dont see anything in my dolphin or system logs. I ran a SMART short test and it passed fine.
-
My server got hung up when trying to use dolphin to push 2TB (basically I did not have enough free on the drive I was moving it too). I had to reboot the server. Dolphin wont connect now and I get this error:
Fatal server error: Server is already active for display 1 If this server is no longer running, remove /tmp/.X1-lock and start again. Openbox-Message: Failed to open the display from the DISPLAY environment variable.
-
figured I would check to see if this was normal or I have something on I shouldn't or something, I get these warning every boot up:
avahi-daemon 0.6.31 starting up. 6 3000 /config/Library/Application Support d dbus[52]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted No service file found in /etc/avahi/services. *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** socket() failed: Address family not supported by protocol Failed to create IPv6 socket, proceeding in IPv4 only mode socket() failed: Address family not supported by protocol Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. New relevant i
-
On unRaid Main screen, there's a very tiny little picture of a hard drive immediately to the left of the drive model # / serial #. Clicking it will bring up all the ata messages for that particular drive. Keep clicking til you find the appropriate drivecan this be coorelated back to a specific drive or is this completely unrelated. Nothing is having an issue on my system but I just saw that pop up and I am wondering if my disk 2 is just cooked.
617 May 6 23:15:49 Hades kernel: ata1.00: exception Emask 0x50 SAct 0x0 SErr 0x280900 action 0x6 frozen
May 6 23:15:49 Hades kernel: ata1.00: irq_stat 0x08000000, interface fatal error
May 6 23:15:49 Hades kernel: ata1: SError: { UnrecovData HostInt 10B8B BadCRC }
May 6 23:15:49 Hades kernel: ata1.00: failed command: READ DMA EXT
May 6 23:15:49 Hades kernel: ata1.00: cmd 25/00:40:e0:be:5c/00:05:8c:01:00/e0 tag 10 dma 688128 in
May 6 23:15:49 Hades kernel: res 50/00:00:df:be:5c/00:00:8c:01:00/ec Emask 0x50 (ATA bus error)
May 6 23:15:49 Hades kernel: ata1.00: status: { DRDY }
May 6 23:15:49 Hades kernel: ata1: hard resetting link
May 6 23:15:49 Hades kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 6 23:15:49 Hades kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
May 6 23:15:49 Hades kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
May 6 23:15:49 Hades kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
May 6 23:15:49 Hades kernel: ata1.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
May 6 23:15:49 Hades kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
May 6 23:15:49 Hades kernel: ata1.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
May 6 23:15:49 Hades kernel: ata1.00: configured for UDMA/133
May 6 23:15:49 Hades kernel: ata1: EH complete
thanks! Oddly enough its not the failed drive I had but the drive I am doing the Dolphin copy from right now. Its also my only reiserfs drive left (if that matters). I didn't have the storage until recently to convert that drive over to xfs like everything else. Could this be a serious issue or just something that went funky when I tried to do a copy? Originally in dolphin I tried browsing through samba share and copying that way but it failed for me (I didn't see the root icon at first). Maybe that was the corresponding error?
-
just don't close the transfer window. The transfer will still continue, but you won't be able to get the transfer window back open until it finishes
Why not install either the dolphin or krusader docker app, which gives you an interface similar to windows, but avoids the extra time involved via windows in moving everything back and forth over the networkI know using straight windows explorer is a poor choice as its using the network to transfer a file from one spot to another (adding a TON of time). Normally I would just use command line but I need a graphical way to get my drives in a better space. I have 2 drives that are 99% full and a bunch of drives that are only 10-20% full. I want to move say 200GB-1000GB at a time but based on hundreds of specific folders in a share so it needs to be gui based.
HAHAHA, I was just about to ask this lol. oh well... this is gonna be interesting... Like an idiot I kicked off 120GB transfer which should finish without an issue but my server does maintenance every night at 2am (2.5 hrs) and it reboots dockers. I assume if the docker is restarted the transfer stops?
trying out dolphin now, this is definitely ideal over a windows app if it looks and works good
Hard Drive Issue/Question
in General Support
Posted
I had a drive failing, drive 3 (if its showing missing in the logs). It was since shipped to get replaced. I have a hard drive coming in Friday so of course I made the terrible decision of leaving myself out of parity until my hard drive arrives. Now my disk 6 is freaking out. Could this be a dying drive or could it just be a poor connection? It was a drive I removed and put back in while looking for my drive 3. It is also in my only questionable bay (I had issues long ago with it). So my question is, since I am parity broken at the moment and will need to pre-clear a 4TB drive (2-3 days) to get back up and running is it ok for me to move bays around without causing an issue? aka, can I move my disk 6 into my currently missing disk 3 without it wiping my parity or does unRAID store what ports and whatnot the drives are on?
my log is to big to post (400k)... not sure best way to post it. here it is on google drive:
https://drive.google.com/open?id=0B7baFOqwwO97QVpRbl9XYlNrQVU
EDIT: One other tidbit, my attach usb drives plugin/docker also starts showing it as "mountable" once it starts erroring out (which is leading me to the bad connection).