Jump to content

fersal

Members
  • Content Count

    74
  • Joined

  • Last visited

Community Reputation

0 Neutral

About fersal

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. fersal

    (SOLVED) Crashing Server

    Maybe you could explain what you did to solve the problem in case some of us here have a similar issue?
  2. As I understand it, even if we preserve the path mappings exactly the same in a new container we may lose a bunch of metadata? So it may be better to keep the same container and just replace the Repository entry? How about the Docker Hub URL? And also the entries in Template Repositories field? Has anyone migrated from Needo Plex docker to a more current one like linuxserver's can you please chime in? Thanks!
  3. Thanks Squid but what is the process to install the new repository? Stop the current PlexMediaServer container, then create a new container with the binhex Plexpass? Is there step-by-step documentation somewhere? So theoretically I could keep the old Plex container (stopped) just in case something doesn't work with the new one?
  4. I'm still getting the same warning but now I'm getting notices on the Plex UI itself that the application is not up to date and may be missing some features. I have 2 Questions if you'd be so kind: What is the process for changing my Plex docker to a new repository? I'm attaching my current settings and mappings. Would my appdata files sitting on my cache need to be updated or can they be used as they are? Thanks!
  5. fersal

    Rootfs file is getting full

    One thing that I did notice was that in the Docker volume mappings for Plex I have everything under /mnt/user/ except one entry that says: /transcode <--> /tmp Could this be causing this issue?
  6. fersal

    Rootfs file is getting full

    Actually no major hardware or software changes in the past year other than upgrade to 6.5.3. However maybe it's happened before because I don't look at the log file very often. The only docker is a Plex Media Server. And yes, all files are in user shares under /mnt/user/; I'll keep monitoring the log file to see of this happens again. If anyone else has any ideas please let me know, thanks!
  7. fersal

    Rootfs file is getting full

    Thanks, as far as I know I have all my data files under /mnt. I tried looking at the Diagnostics file but I don't know where to look... has someone else had this issue before?
  8. While checking the log to determine what was causing some drives to spin up, I saw an entry that mentioned "Warning: Rootfs file is getting full (currently 81 % used)". What causes this usually, and how can I prevent it? I'm attaching diagnostics file, thanks for your help! tower-diagnostics-20180916-0538.zip
  9. fersal

    Error in Unassigned Devices on 6.5.2

    Yes I did set the Share switch from the beginning thanks, if not I don't think it would've showed up in MC? But still not visible from Win 10.
  10. fersal

    Error in Unassigned Devices on 6.5.2

    Thanks, that helped, after upgrading to 6.5.3 I had no problems resuming the copy to the USB drive using MC... actually it's now copying twice as fast as before! However, the share still did not show up in WIndows 10, only in MC.
  11. fersal

    Error in Unassigned Devices on 6.5.2

    Thanks, I'll upgrade and check. As I understand it, exFAT has very large file size limits. The USB drive was originally NTFS-formatted, but it didn't show up as a SMB share on WIndows 10, so I repartitioned and reformatted using exFAT it to see if that would fix the problem. It didn't, so I tried Midnight Commander and the share did appear there, so I started copying. It's weird that the error occurred after copying 3TB of data without issues. Let's see if an upgrade takes care of it, thanks!
  12. fersal

    Error in Unassigned Devices on 6.5.2

    Is it possible that this is caused by a bug in the Unassigned Devices plugin? If so, hopefully the developer sees this topic. Any opinions please?
  13. I'm using the Unassigned Devices plugin to copy a large number of files to a 6TB Seagate USB external drive. After mounting and sharing it, I used MC to copy almost 3TB over 18 hours with no apparent problems. However, after it finished copying a large folder the drive somehow got unmounted and will not mount again, even after rebooting the server. However, it still works fine when plugged into a Windows 10 machine. Below are the contents of the log file and attached Diagnostics zip file. Any ideas? Thanks! tower-diagnostics-20180825-2133.zip Aug 25 21:21:55 Tower kernel: sd 8:0:0:0: [sdg] Very big device. Trying to use READ CAPACITY(16). Aug 25 21:21:55 Tower kernel: sd 8:0:0:0: [sdg] 11721045167 512-byte logical blocks: (6.00 TB/5.46 TiB) Aug 25 21:21:55 Tower kernel: sd 8:0:0:0: [sdg] 4096-byte physical blocks Aug 25 21:21:55 Tower kernel: sd 8:0:0:0: [sdg] Write Protect is off Aug 25 21:21:55 Tower kernel: sd 8:0:0:0: [sdg] Mode Sense: 4f 00 00 00 Aug 25 21:21:55 Tower kernel: sd 8:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Aug 25 21:21:55 Tower kernel: sd 8:0:0:0: [sdg] Very big device. Trying to use READ CAPACITY(16). Aug 25 21:21:55 Tower kernel: sdg: sdg1 sdg2 Aug 25 21:21:55 Tower kernel: sd 8:0:0:0: [sdg] Very big device. Trying to use READ CAPACITY(16). Aug 25 21:21:55 Tower kernel: sd 8:0:0:0: [sdg] Attached SCSI disk Aug 25 21:21:55 Tower rc.diskinfo[8536]: SIGHUP received, forcing refresh of disks info. Aug 25 21:21:55 Tower rc.diskinfo[8536]: PHP Warning: Use of undefined constant ID_MODEL - assumed 'ID_MODEL' (this will throw an Error in a future version of PHP) in /etc/rc.d/rc.diskinfo on line 470 Aug 25 21:21:55 Tower rc.diskinfo[8536]: PHP Warning: Use of undefined constant SERIAL_SHORT - assumed 'SERIAL_SHORT' (this will throw an Error in a future version of PHP) in /etc/rc.d/rc.diskinfo on line 470 Aug 25 21:21:55 Tower unassigned.devices: Disk with serial 'ST6000DM003-2CY186_WF2089AM', mountpoint 'Seagate' is not set to auto mount and will not be mounted... Aug 25 21:21:55 Tower rc.diskinfo[8536]: PHP Warning: Use of undefined constant byte11h - assumed 'byte11h' (this will throw an Error in a future version of PHP) in /etc/rc.d/rc.diskinfo on line 662 Aug 25 21:21:55 Tower rc.diskinfo[8536]: PHP Warning: Use of undefined constant byte10h - assumed 'byte10h' (this will throw an Error in a future version of PHP) in /etc/rc.d/rc.diskinfo on line 662 Aug 25 21:21:55 Tower rc.diskinfo[8536]: PHP Warning: Use of undefined constant byte9h - assumed 'byte9h' (this will throw an Error in a future version of PHP) in /etc/rc.d/rc.diskinfo on line 662 Aug 25 21:21:55 Tower rc.diskinfo[8536]: PHP Warning: Use of undefined constant byte8h - assumed 'byte8h' (this will throw an Error in a future version of PHP) in /etc/rc.d/rc.diskinfo on line 662 Aug 25 21:21:55 Tower rc.diskinfo[8536]: PHP Warning: Use of undefined constant byte15h - assumed 'byte15h' (this will throw an Error in a future version of PHP) in /etc/rc.d/rc.diskinfo on line 663 Aug 25 21:21:55 Tower rc.diskinfo[8536]: PHP Warning: Use of undefined constant byte14h - assumed 'byte14h' (this will throw an Error in a future version of PHP) in /etc/rc.d/rc.diskinfo on line 663 Aug 25 21:21:55 Tower rc.diskinfo[8536]: PHP Warning: Use of undefined constant byte13h - assumed 'byte13h' (this will throw an Error in a future version of PHP) in /etc/rc.d/rc.diskinfo on line 663 Aug 25 21:21:55 Tower rc.diskinfo[8536]: PHP Warning: Use of undefined constant byte12h - assumed 'byte12h' (this will throw an Error in a future version of PHP) in /etc/rc.d/rc.diskinfo on line 663 Aug 25 21:21:55 Tower unassigned.devices: Disk with serial 'ST6000DM003-2CY186_WF2089AM', mountpoint 'ST6000DM003-2CY186_WF2089AM-part1' is not set to auto mount and will not be mounted... Aug 25 21:22:08 Tower unassigned.devices: Adding disk '/dev/sdg1'... Aug 25 21:22:08 Tower unassigned.devices: No filesystem detected on '/dev/sdg1'. Aug 25 21:22:08 Tower unassigned.devices: Partition 'ST6000DM003-2CY186_WF2089AM-part1' could not be mounted... Aug 25 21:22:08 Tower unassigned.devices: Adding disk '/dev/sdg2'... Aug 25 21:22:08 Tower unassigned.devices: Mount drive command: /sbin/mount -t exfat -o auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdg2' '/mnt/disks/Seagate' Aug 25 21:22:08 Tower kernel: usb 2-1: reset SuperSpeed USB device number 10 using xhci_hcd Aug 25 21:22:09 Tower unassigned.devices: Mount of '/dev/sdg2' failed. Error message: fuse: mountpoint is not empty fuse: if you are sure this is safe, use the 'nonempty' mount option FUSE exfat 1.2.7 Aug 25 21:22:09 Tower unassigned.devices: Partition 'Seagate' could not be mounted... Aug 25 21:22:41 Tower unassigned.devices: Adding disk '/dev/sdg1'... Aug 25 21:22:41 Tower unassigned.devices: No filesystem detected on '/dev/sdg1'. Aug 25 21:22:41 Tower unassigned.devices: Partition 'ST6000DM003-2CY186_WF2089AM-part1' could not be mounted... Aug 25 21:22:41 Tower unassigned.devices: Adding disk '/dev/sdg2'... Aug 25 21:22:41 Tower unassigned.devices: Mount drive command: /sbin/mount -t exfat -o auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdg2' '/mnt/disks/Seagate' Aug 25 21:22:41 Tower unassigned.devices: Mount of '/dev/sdg2' failed. Error message: fuse: mountpoint is not empty fuse: if you are sure this is safe, use the 'nonempty' mount option FUSE exfat 1.2.7 Aug 25 21:22:41 Tower unassigned.devices: Partition 'Seagate' could not be mounted...
  14. fersal

    unRAID OS version 6.5.2 available

    6.3.5 -> 6.5.2 looks good, so far no issues.
  15. Thanks dlandon, that worked! I've had this problem for a few months, having to use the IP address on Windows Explorer was getting old...