
kricker
Members-
Posts
761 -
Joined
-
Last visited
Converted
-
Gender
Undisclosed
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
kricker's Achievements
Enthusiast (6/14)
4
Reputation
-
Awesome to know how to do this!
-
Thanks. I haven't had an issue where I need to recover anything. It's just something I was wondering if is possible in any way. Thanks for all the extra information though!
-
Is there any way to recover files that are deleted by a ftp user connected via the ProFTP server?
-
I think I had a similar issue in the past. If I recall properly... I manually removed the plugin and it's configuration file from my flash drive. I made sure to get everything related to the plugin and old copies in the plugins-old-versions folder and the plugins-removed folder. Then I rebooted unRaid and reinstalled the plugin from community applications .
-
I have and HFSplus formatted drive that I can mount using Unassigned Devices. I can't seem to copy all the files from the Macintosh_HD/Users folder to another drive or share without having permissions issues. I tried using rsyn and docker file manager such as Double Commander and Krusader. I also can't browse the Users folder in the Macintosh_HD over the SMB share. I can browse the folders and files using the Unraid webGUI. A friend had his Mac die on him, so I am trying to pull all his files off for him.
-
I can't seem to get this to work at all. I am think it has more to do with my Google Nest router, but I am not sure. Is this using port 7 to send the magic packet? I am sniffing for the packet to reach my PC on port7 and port 9 but it never receives the packet.
-
@Observe I tried out doublecommander docker and the search feature works in it.
-
I am trying the Dolphin docker. When I use the "Find" feature it just replies "Invalid Protocol". Is there a way to enable the searching feature?
-
I was having issues getting ProFTP running again after upgrading Unraid to version 6.9.1 using ProFTP 1.3.7a. ProFTP just would not start and I could not get anything in the log. I tried enabling debug logging, but still nothing. I removed the plugin and did a clean install multiple times and still nothing. Then I stumbled upon running this command in terminal sudo -u root /usr/local/SlrG-Common/usr/local/sbin/proftpd -c /etc/proftpd.conf which resulted in this error: 2021-03-30 20:12:19,459 TOWER proftpd[24730]: fatal: unknown configuration directive 'IdentLookups' on line 24 of '/etc/proftpd.conf' So looking at the config file I removed this section at lines 22-24: # Speedup Login UseReverseDNS off IdentLookups off Tehn ProFTP started without any issues.
-
Yeah, should be easy enough. Thanks for letting me know what loop2 was!
-
Ahh okay. The entire image...so all my dockers?
-
I just saw this on boot up after a random system crash. The tower just became inaccessible vis web or SAMBA. I attached a monitor and after reboot I saw some strange errors after it got to the login prompt. I am currently in the middle of a parity rebuild (replacing a possible failing drive) so I don't want to re-power down just yet, but here is a snippet of the log and I'll attach the full diagnostic as well. Doing an intial search I saw some threads somewhat similar where new RAM seemed to fix the issue. I've had this system running perfect for years...I guess there is a chance the RAM has gone bad. I can run memtest after the parity rebuild finishes. ErrorWarningSystemArrayLogin Feb 25 13:22:00 TOWER kernel: IPv6: ADDRCONF(NETDEV_UP): vethfc4d4e5: link is not ready Feb 25 13:22:07 TOWER kernel: eth0: renamed from veth6b68a4d Feb 25 13:22:07 TOWER kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethfc4d4e5: link becomes ready Feb 25 13:22:07 TOWER kernel: docker0: port 6(vethfc4d4e5) entered blocking state Feb 25 13:22:07 TOWER kernel: docker0: port 6(vethfc4d4e5) entered forwarding state Feb 25 13:22:09 TOWER avahi-daemon[4648]: Joining mDNS multicast group on interface vethfc4d4e5.IPv6 with address fe80::344b:bfff:fe2a:aafa. Feb 25 13:22:09 TOWER avahi-daemon[4648]: New relevant interface vethfc4d4e5.IPv6 for mDNS. Feb 25 13:22:09 TOWER avahi-daemon[4648]: Registering new address record for fe80::344b:bfff:fe2a:aafa on vethfc4d4e5.*. Feb 25 13:22:10 TOWER rc.docker: sonarr: started succesfully! Feb 25 13:22:14 TOWER ntpd[1519]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Feb 25 13:22:57 TOWER kernel: BUG: Bad page state in process loop2 pfn:181eaa Feb 25 13:22:57 TOWER kernel: page:ffffea000607aa80 count:0 mapcount:0 mapping:0000000000400000 index:0x1 Feb 25 13:22:57 TOWER kernel: flags: 0x2ffff0000000000() Feb 25 13:22:57 TOWER kernel: raw: 02ffff0000000000 dead000000000100 dead000000000200 0000000000400000 Feb 25 13:22:57 TOWER kernel: raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000 Feb 25 13:22:57 TOWER kernel: page dumped because: non-NULL mapping Feb 25 13:22:57 TOWER kernel: Modules linked in: md_mod veth xt_nat ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs reiserfs e1000e mpt3sas coretemp i2c_i801 i2c_core ahci raid_class libahci scsi_transport_sas intel_agp ipmi_si intel_gtt agpgart button [last unloaded: md_mod] Feb 25 13:22:57 TOWER kernel: CPU: 0 PID: 11885 Comm: loop2 Not tainted 4.19.107-Unraid #1 Feb 25 13:22:57 TOWER kernel: Hardware name: Supermicro X7SPA-HF/X7SPA-HF, BIOS 1.2a 02/21/12 Feb 25 13:22:57 TOWER kernel: Call Trace: Feb 25 13:22:57 TOWER kernel: dump_stack+0x67/0x83 Feb 25 13:22:57 TOWER kernel: bad_page+0xec/0x106 Feb 25 13:22:57 TOWER kernel: get_page_from_freelist+0x9f4/0xd0b Feb 25 13:22:57 TOWER kernel: __alloc_pages_nodemask+0x150/0xae1 Feb 25 13:22:57 TOWER kernel: __do_page_cache_readahead+0x106/0x183 Feb 25 13:22:57 TOWER kernel: ondemand_readahead+0x21d/0x22f Feb 25 13:22:57 TOWER kernel: generic_file_read_iter+0x243/0x6d0 Feb 25 13:22:57 TOWER kernel: xfs_file_buffered_aio_read+0x4b/0x66 [xfs] Feb 25 13:22:57 TOWER kernel: xfs_file_read_iter+0x6f/0xb6 [xfs] Feb 25 13:22:57 TOWER kernel: do_iter_readv_writev+0x110/0x146 Feb 25 13:22:57 TOWER kernel: do_iter_read+0x87/0x15c Feb 25 13:22:57 TOWER kernel: loop_queue_work+0x6f7/0x83a Feb 25 13:22:57 TOWER kernel: ? dequeue_task_fair+0x40/0x58d Feb 25 13:22:57 TOWER kernel: kthread_worker_fn+0xdf/0x168 Feb 25 13:22:57 TOWER kernel: ? loop_info64_to_compat+0x134/0x134 Feb 25 13:22:57 TOWER kernel: kthread+0x10c/0x114 Feb 25 13:22:57 TOWER kernel: ? kthread_park+0x89/0x89 Feb 25 13:22:57 TOWER kernel: ret_from_fork+0x1f/0x40 Feb 25 13:22:57 TOWER kernel: Disabling lock debugging due to kernel taint Feb 25 13:27:00 TOWER root: Fix Common Problems Version 2021.02.18 Feb 25 13:27:02 TOWER root: Fix Common Problems: Warning: unRaid's built in FTP server is currently disabled, but users are defined ** Ignored Feb 25 13:27:18 TOWER root: Fix Common Problems: Other Warning: CPU possibly will not throttle down frequency at idle ** Ignored Feb 25 13:30:01 TOWER root: Fix Common Problems Version 2021.02.18 Feb 25 13:30:02 TOWER root: Fix Common Problems: Warning: unRaid's built in FTP server is currently disabled, but users are defined ** Ignored Feb 25 13:30:17 TOWER root: Fix Common Problems: Other Warning: CPU possibly will not throttle down frequency at idle ** Ignored Feb 25 13:31:31 TOWER kernel: vethdea0a21: renamed from eth0 Feb 25 13:31:32 TOWER kernel: docker0: port 2(veth56a37cc) entered disabled state Feb 25 13:31:32 TOWER kernel: docker0: port 2(veth56a37cc) entered disabled state Feb 25 13:31:32 TOWER avahi-daemon[4648]: Interface veth56a37cc.IPv6 no longer relevant for mDNS. Feb 25 13:31:32 TOWER avahi-daemon[4648]: Leaving mDNS multicast group on interface veth56a37cc.IPv6 with address fe80::e056:27ff:fe97:e93c. Feb 25 13:31:32 TOWER kernel: device veth56a37cc left promiscuous mode Feb 25 13:31:32 TOWER kernel: docker0: port 2(veth56a37cc) entered disabled state Feb 25 13:31:32 TOWER avahi-daemon[4648]: Withdrawing address record for fe80::e056:27ff:fe97:e93c on veth56a37cc. Feb 25 13:32:37 TOWER kernel: kvm: no hardware support Feb 25 13:32:37 TOWER kernel: has_svm: not amd Feb 25 13:32:37 TOWER kernel: kvm: no hardware support tower-diagnostics-20210225-1326.zip
-
I tried setting the users directory to that disk mount point such as ftpuser /mnt/disks/test, but that didn't seem to work. The users account still went to /mnt/usr and saw all the shares as normal. I'll try those two options you mentioned. Thanks! I think I must have something in my config file keeping everyone jailed to /mn/usr, because setting anyone to just ftpuser has the same result. I'll do some diggining.
-
I am trying to add access to a disk outside of the array that is mounted using Unassigned devices. Is that possible?