tucansam
-
Posts
1107 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by tucansam
-
-
Anyone? Old version I could copy-and-paste an URL, click the button, and away it goes. Now, clicking the button adds it to the list, but I have to click the actual download arrow icon to get it to download.
-
Latest update won't auto-start the downloads?
-
Nevermind. For some inexplicable reason the "Movies" share had some things in it that the "movies" share also had, and since "movies" in my main share, I simply removed the "Movies" share and all of its contents.
-
I don't know what the problem is or how to fix it.
My share is defined in one place, and only one place, as far as I am aware. I only ever remember creating one share, with one case of the first letter. Now there are two shares. With two cases. I don't know where the second share came from.
-
Just upgraded to the latest, got this now:
Same share (movies) exists in a different caseThis will confuse SMB shares. Manual intervention required. Use the dolphin / krusader docker app to combine the shares into one unified spelling More Information
Same share (Movies) exists in a different caseThis will confuse SMB shares. Manual intervention required. Use the dolphin / krusader docker app to combine the shares into one unified spelling More Information
I have no idea what this means. Well, I know what it means, but where do I "manually intervene?" I'm not interested in downloading another docker appp, and when I looked at both of the suggestions, they simply appear to be file managers.
-
I have 250GB of queue going in sab.
I have Windows Explorer open as I peruse the filesystem cleaning up old files, fixing renaming errors sonarr or sab screw up, etc.
Within 60 minutes of conducting both of these activities at the same time, the issue surfaces.
Its now happened six or seven times today. It seems to be the consistent manipulation of the filesystem in some way (usually unpacking downloaded rar files is the instant at which it occurs).
It occurs when Explorer is closed and sab is the only thing messing with the filesystem (although in fairness Plex is doing its constantly watching thing in the background, indexing newly downloaded files)
-
I can consistently reproduce it.
Its just not throwing anything in syslog AFAIK. Anywhere else I can be looking?
-
Is there a known fix? Or just theories?
-
Have seen similar threads going back to 2020 indicating it may be the mover. Some users indicated that turning the mover off had no effect. Some believe it is an issue with NFS -- I cannot turn NFS off.
-
This is now happening all the time. It used to be a regular (once or twice a month) occurance, but today it has now happened three times, and I have some idea why.
Shares are available to Windows machines. After a particular amount of file I/O onto the array, all shares disappear, and /mnt/user becomes unavailable with errors at the shell prompt. /mnt/user: Transport endpoint is not connected
Today I am doing a lot of maintenance on my media library, and sabnzbd is downloading several terabytes of data. It gets to a certain point, successfully, and then the aforementioned issue pops up. Stopping and starting the array has no effect; only a reboot will bring /mnt/user back online. Then sab will continue about its business until the next the time issue happens. Like I said, sitting here for the last couple of hours, its now happened three time.
This has been an ongoing issue for me for at least a year, but today it is bad enough (and consistent) enough that I've had enough. Diags attached.
-
6.12.3 just froze out of nowhere. Totally froze. Couldn't even get console to work. Dead GUI. Could ping, that's it.
-
I replaced four or five drives in the last 60 days or so, and one of them is failing. I want to make sure I return it to the correct vendor. And yes, you're right, I need to set up a spreadsheet or simple list as far as what serial numbers get installed on what date, etc.
-
Yeah, this drive already had hours on it. I've replaced four or five drives in the last few months and need to know the order in which they made it into the server.
-
Is there a way to tell what date a disk was installed in an array?
-
I'm not understanding the "no space left on device" error..... This is an 8TB disk I'm trying to preclear.
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 100274+0 records out
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 210289819648 bytes (210 GB, 196 GiB) copied, 1705.49 s, 123 MB/s
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 100283+0 records in
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 100283+0 records out
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 210308694016 bytes (210 GB, 196 GiB) copied, 1721.06 s, 122 MB/s
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 100284+0 records in
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 100284+0 records out
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 210310791168 bytes (210 GB, 196 GiB) copied, 1894.07 s, 111 MB/s
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 100284+0 records in
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 100284+0 records out
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 210310791168 bytes (210 GB, 196 GiB) copied, 1894.07 s, 111 MB/s
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: dd: error writing '/dev/sdc': No space left on device
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 100285+0 records in
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 100284+0 records out
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 210310791168 bytes (210 GB, 196 GiB) copied, 1894.07 s, 111 MB/s
Jul 29 08:09:13 preclear_disk_Z840SENE_13892: Zeroing: zeroing the disk failed!
Jul 29 08:09:13 preclear_disk_Z840SENE_13892: S.M.A.R.T.: Error:
Jul 29 08:09:13 preclear_disk_Z840SENE_13892: S.M.A.R.T.:
Jul 29 08:09:13 preclear_disk_Z840SENE_13892: S.M.A.R.T.: ATTRIBUTE INITIAL NOW STATUS
Jul 29 08:09:13 preclear_disk_Z840SENE_13892: S.M.A.R.T.: Reallocated_Sector_Ct 0 -
Jul 29 08:09:13 preclear_disk_Z840SENE_13892: S.M.A.R.T.: Power_On_Hours 49905 -
Jul 29 08:09:14 preclear_disk_Z840SENE_13892: S.M.A.R.T.: Runtime_Bad_Block 0 -
Jul 29 08:09:14 preclear_disk_Z840SENE_13892: S.M.A.R.T.: End-to-End_Error 0 -
Jul 29 08:09:14 preclear_disk_Z840SENE_13892: S.M.A.R.T.: Reported_Uncorrect 0 -
Jul 29 08:09:14 preclear_disk_Z840SENE_13892: S.M.A.R.T.: Airflow_Temperature_Cel 31 -
Jul 29 08:09:14 preclear_disk_Z840SENE_13892: S.M.A.R.T.: Current_Pending_Sector 0 -
Jul 29 08:09:14 preclear_disk_Z840SENE_13892: S.M.A.R.T.: Offline_Uncorrectable 0 -
Jul 29 08:09:14 preclear_disk_Z840SENE_13892: S.M.A.R.T.: UDMA_CRC_Error_Count 76 -
Jul 29 08:09:14 preclear_disk_Z840SENE_13892: S.M.A.R.T.:
Jul 29 08:09:14 preclear_disk_Z840SENE_13892: error encountered, exiting ... -
I'm not understanding the "no space left on device" error..... This is an 8TB disk I'm trying to preclear.
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 100274+0 records out
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 210289819648 bytes (210 GB, 196 GiB) copied, 1705.49 s, 123 MB/s
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 100283+0 records in
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 100283+0 records out
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 210308694016 bytes (210 GB, 196 GiB) copied, 1721.06 s, 122 MB/s
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 100284+0 records in
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 100284+0 records out
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 210310791168 bytes (210 GB, 196 GiB) copied, 1894.07 s, 111 MB/s
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 100284+0 records in
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 100284+0 records out
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 210310791168 bytes (210 GB, 196 GiB) copied, 1894.07 s, 111 MB/s
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: dd: error writing '/dev/sdc': No space left on device
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 100285+0 records in
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 100284+0 records out
Jul 29 08:09:12 preclear_disk_Z840SENE_13892: Zeroing: dd output: 210310791168 bytes (210 GB, 196 GiB) copied, 1894.07 s, 111 MB/s
Jul 29 08:09:13 preclear_disk_Z840SENE_13892: Zeroing: zeroing the disk failed!
Jul 29 08:09:13 preclear_disk_Z840SENE_13892: S.M.A.R.T.: Error:
Jul 29 08:09:13 preclear_disk_Z840SENE_13892: S.M.A.R.T.:
Jul 29 08:09:13 preclear_disk_Z840SENE_13892: S.M.A.R.T.: ATTRIBUTE INITIAL NOW STATUS
Jul 29 08:09:13 preclear_disk_Z840SENE_13892: S.M.A.R.T.: Reallocated_Sector_Ct 0 -
Jul 29 08:09:13 preclear_disk_Z840SENE_13892: S.M.A.R.T.: Power_On_Hours 49905 -
Jul 29 08:09:14 preclear_disk_Z840SENE_13892: S.M.A.R.T.: Runtime_Bad_Block 0 -
Jul 29 08:09:14 preclear_disk_Z840SENE_13892: S.M.A.R.T.: End-to-End_Error 0 -
Jul 29 08:09:14 preclear_disk_Z840SENE_13892: S.M.A.R.T.: Reported_Uncorrect 0 -
Jul 29 08:09:14 preclear_disk_Z840SENE_13892: S.M.A.R.T.: Airflow_Temperature_Cel 31 -
Jul 29 08:09:14 preclear_disk_Z840SENE_13892: S.M.A.R.T.: Current_Pending_Sector 0 -
Jul 29 08:09:14 preclear_disk_Z840SENE_13892: S.M.A.R.T.: Offline_Uncorrectable 0 -
Jul 29 08:09:14 preclear_disk_Z840SENE_13892: S.M.A.R.T.: UDMA_CRC_Error_Count 76 -
Jul 29 08:09:14 preclear_disk_Z840SENE_13892: S.M.A.R.T.:
Jul 29 08:09:14 preclear_disk_Z840SENE_13892: error encountered, exiting ... -
"Plex AEA services" and scanning media has 16 cores at 95-100%...... I don't recall this ever happening before in previous versions of unraid.
-
I've never seen this many X.X.y releases in a row in maybe forever. Are the major releases not ready for prime-time before they're rolled out?
-
i installed tdarr not 48 hours ago after a friend of mine espoused his amazing success with using it.... but I had it disabled as I was still trying to configure it.
And I do use NFS, mostly because I can never get SMB shares to work correctly without hours of troubleshooting. In all my years using unix, I don't think I've ever had a single entry in /etc/fstab that was consistent in syntax and switches used, lol. SMB seems like such a huge pain in the ass vs NFS, that I've just used NFS wherever possible.
-
Hasn't happened for a while, but happens a lot. Shares disappear. Totally. Like samba just dies. They are visible from the command line (they show up in 'ls /mnt/user') but they cannot be entered or their contents viewed. Start/stop array doesn't fix. Reboot does.
Pre-reboot diags attached.
-
I'm getting this error too. Start/stop array has no effect. Hard reboot is required. Quite annoying indeed.
-
Sweet, thanks!!!
-
1
-
-
I have disk high temp set at 42F, critical set at 48F -- no spinner ever gets past 41, even in the summer during a parity check.
I have two m2 SSDs, and one of them alters to a high temp (44F) every single day. I'm not sure what its dong (trim?) but its happening consistently.
The google machine says an SSD can operate up to 50F happily.
How can I set SSD temp alarms separately from mechanical disk temp alarms?
-
Got it working, not sure how.
But MAN, this is WAY more complicated than it was a decade ago when I ran an old version on an old linux. I have no idea how to begin doing this. I've managed to set up the source, an can see it. The camera itself handles motion detection, and films in 30s clips, which is fine. I literally just need the camera to write videos to my unraid server instead of the SD card in it. Nothing more complicated than that.
[Support] MeTube
in Docker Containers
Posted
I see that I have stumped you all.