sureguy

Members
  • Posts

    914
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by sureguy

  1. It probably needs the same symlink that unmenu needed. I'm mobile so I can't look it up right now
  2. People are using pfsense on unraid I believe, I can't imagine why this wouldn't work. Unraid would need a static IP address though.
  3. This is normal behavior as long as the media share uses the cache drive. When mover runs the files should move to the share.
  4. Helpers will need to know what steps you took to replace parity Did you stop the array, unassign parity, start the array, then stop it again and assign the new disk? AFAIK you can't increase the size of your parity and maintain the contents of it
  5. Yes, preclearing new drives is a good idea. Hard drive failures follow the bathtub curve. Lots of failures early in their life (if exercised properly), much lower during the expected useful life of the drive after the initial tests, and then after the expected life the failure rate goes up.
  6. Have there been any reported issues with xfs? I haven't seen any. I know for sure some people moved away from btrfs due to problems they encountered.
  7. I'd wager that the majority of users are running non-ecc memory. ECC is nice to have, but I wouldn't say it's necessary.
  8. The problem with integrating something like this into unRAID is that if the Filesystem driver used destroys the Filesystem on the unassigned device novice users will blame unRAID. Perhaps read only would work with these devices and an option (unsupported, use at your own risk) for write would work?
  9. An update just appeared for this plugin that works with 6.1 - I've mounted and unmounted a drive a couple times, seems to be working properly for me (it's my boot drive - vmdk - for unRAID under ESXi). I'm remote so I can't check anything physical at the moment. Posting this as some people rarely visit their unRAID webui, and may be getting notifications from this thread. Thanks a lot gfjardim!
  10. Can you ping IP of the server?
  11. Given that someone posted source code for a cryptolocker to github a few weeks ago I suspect this problem is going to get much worse.
  12. I'm running 6.1 and was still having issues (I know the plugin doesn't support 6.1 properly), but others seemed to have it running. I was able to fix it by uninstalling the plugin, and then deleting the folder /boot/config/plugins/unassigned.devices - I then rebooted (probably unnecessary), and reinstalled the plugin. The UI for the plugin now works. Hope this helps someone else.
  13. This should not be necessary. Are you running in a VM? If so, we do not test unRAID OS running in a VM so there may be issues. I can confirm running on ESXi (6 - using VMDK and usb passthrough) this problem exists, and enabling/disabling notifications fixed it, and the fix persisted across reboots of the unRAID guest (80 minutes, no issues). Unsupported, I know.
  14. How are you seeing the errors / changing your parity size without the webGui loading? Can you eject the flash, plug it into a Windows PC, and run checkdisk on it and try again? Watching the boot up process on a monitor. I've ran check disk with no failures. Reverting back to 6.0.1 fixed whatever issue I was running into. Please reboot in 6.1 and if you get to a command prompt, type 'diagnostics', then upload the file it generates to the flash device here for review. I tried doing that but it's no use since it doesn't mount the usb drive to /. It gives a successful save but it saves it to the ram disk. That sounds like your drive is being mounted as read only. I know 6.1 was supposed to include a file system check on the USB but I don't know how well it works. You may want to try checking it on a Windows if it fails again.
  15. So if I leave the monitor OFF will I see the PLEASE REBOOT in the webgui? If so I will just wait until I see that before switching it on. No, there's no way that the OS knows that the monitor is disconnected and then to redirect the output to the webgui. Once the update is done (via the console popup), I'd wait a minute and then stop the array, and then reboot it.
  16. I don't think they have updated to 6.1 Verified http://lime-technology.com/forum/index.php?topic=42446.0 EDIT: Yea.. it hasn't been updated for 6.1 - http://lime-technology.com/forum/index.php?board=77.0 Since I have nobody to piss off, rebooting can't hurt. I'm guessing the problem will persist. At least there's a work around. I've rebooted after disabling and re-enabling notifications and the problem seems to be gone. I don't know what was triggering it, but after 30 minutes of uptime it hasn't returned (and I've been viewing media via plex, browsing the file system).
  17. I don't think they have updated to 6.1 Verified http://lime-technology.com/forum/index.php?topic=42446.0 EDIT: Yea.. it hasn't been updated for 6.1 - http://lime-technology.com/forum/index.php?board=77.0 Since I have nobody to piss off, rebooting can't hurt. I'm guessing the problem will persist. At least there's a work around.
  18. There was a change made in the notification system that I think is causing those messages. Disable notifications and then re-enable notifications and they should go away. I'm running ESXi and was getting the notifications. Disabling and re-enabling the notifications seemed to work. Aug 31 21:29:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:30:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:31:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:32:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:33:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:34:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:35:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:35:10 Phatstore php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'start' 'DUC' Aug 31 21:35:10 Phatstore kernel: device vethd4861c3 entered promiscuous mode Aug 31 21:35:10 Phatstore kernel: docker0: port 2(vethd4861c3) entered forwarding state Aug 31 21:35:10 Phatstore kernel: docker0: port 2(vethd4861c3) entered forwarding state Aug 31 21:35:10 Phatstore avahi-daemon[8877]: Withdrawing workstation service for veth03cfb8e. Aug 31 21:35:10 Phatstore kernel: eth0: renamed from veth03cfb8e Aug 31 21:35:25 Phatstore kernel: docker0: port 2(vethd4861c3) entered forwarding state Aug 31 21:36:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:37:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:38:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:39:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:40:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:41:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:42:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:43:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:44:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:45:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:46:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:47:16 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:48:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:49:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:50:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:50:40 Phatstore emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Aug 31 21:51:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:52:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:53:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:54:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:54:47 Phatstore php: /usr/local/emhttp/plugins/dynamix/scripts/notify 'cron-init' Aug 31 21:55:00 Phatstore php: /usr/local/emhttp/plugins/dynamix/scripts/notify 'cron-init' Aug 31 21:55:07 Phatstore emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Aug 31 21:55:15 Phatstore emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Aug 31 21:55:30 Phatstore emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Aug 31 21:56:05 Phatstore emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Aug 31 21:57:37 Phatstore emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Aug 31 21:59:38 Phatstore emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog I'm going to reboot to see if the fix is "sticky" - I've rebooted several times after upgrading as it seems the unassigned devices plugin is broken.
  19. I have this plugin installed on v6.01, but I get no UI for it, even when clicking on the plugin. I've rebooted a couple times, and tried installing RCs, moving back to stable, and removing and reinstalling the plugin. Any thoughts? I've also tested multiple browsers, cleared cache, etc.
  20. This seems to be a kernel issue, rather than an unRAID issue. So it may take some time. Using a $30 card reader (fcr-hs3) fixed it for me, and a second USB device (passed through) fixed it for someone else. If you want the advanced features of unRAID 6 I'd try one of those things, but I can only vouch for the card reader solution.