MisterWolfe

Members
  • Posts

    88
  • Joined

Everything posted by MisterWolfe

  1. Switching to onboard SATA controller resolved the issue. Thanks for replying.
  2. Good morning, I have just installed an ssd on an existing unraid server (Version: 6.12.4). I'm attempting to copy the docker.img and appdata files from the array to the cache drive. After a short period of time into the copy process I get an error message saying that the drive is read only and can't be written to. I have tried copying using MC and a simply copy command from an ssh window and I get the same behaviour. I want to be clear that the cache drive is initially readable and writable before I start the copy process. It becomes read only after I start the copy process and about 10GB of data has been copied. I did notice that the SSD temperature went up to 55 degrees during the last copy. The ssd is a Samsung 870 EVO. I initially formatted the drive as BTRFS when I first got the error. I reformatted as XFS and I still get the error. The drive is formatted XFS currently. The drive is connected via a PCIE expansion card. (Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)). I've attached the diagnostics file. Thanks for looking! luna-diagnostics-20230927-0857.zip
  3. Thank you for replying. It was indeed the seek error rate that was concerning me. I appreciate your time.
  4. Got myself two 12TB ironwolf drives before prices rose. Precleared the first, no smart error changes. Precleared the second and I see some errors of concern. It could possibly be cable related. I'd appreciate any thoughts experienced 'smart' folks have on this. Thanks
  5. I'm on 6.9.1 and have an LSI 9200-8i controller. No issues at all with my ironwolf drives, thankfully. I wonder if the issue is card version specific.
  6. Good morning, I was following a video tutorial on enabling ssl on the web gui, and had completed setting up my router to allow dns rebinding for unraid.net. After I did that I refreshed the web gui and saw that certificate showed provisioned (I did not manually provision). I wasn't being redirected to the unraid.net web url. After trying to navigate to the dashboard I was kicked out of the web gui and am now no longer able to log in using my admin creds via the server's ip address on the gui or via ssh. Is there any way I can reset these changes? I've pulled the flash drive, and have a tower diagnostic file that seems to have been auto created around the same time things topped working. I'd appreciate any help you may have to offer. Thanks! edit: If I set ssl to yes or no in the ident.cfg file and I can access the gui. If I change to auto, I cannot. I've set it to yes while I test. edit2: d'oh. So YES works in ssl settings because I'm already using a letsencrypt certificate that I pull from the letsencrypt docker. I use a script to import that into unraid so I can use the cert for plex. The fact that I cannot access unraid on the LAN using a subdomain of my primary domain means that I should figure out the port and dnsmasq settings in my router. ident.cfg tower-diagnostics-20200717-0735.zip
  7. Have you thought of using a VPN between the two servers? Then you could potentially mount shares via unassigned devices and make cron jobs that you could use with rsync. The main downside I can see here might be transfer speed with a VPN, which partially depends on the cpu's in both your machines.
  8. I've been using unraid for 9 years. I like how responsive the devs are for adding new features. I also really like how use friendly it is.
  9. I had this issue some time ago. I bypassed the problem by writing a script that checks for the existence of a file on the unassigned disk path before allowing the copy to take place. Not the most elegant solution, but it works.
  10. I have never replaced a disk solely based on age either in my home or business environment. They either start to get errors that are uncorrectable and I replace them, or I replace smaller drives with larger ones when my array gets full. I've had drives in the array for 7 or 8 years before being cycled out. Some of those 8 year old drives were repurposed for other projects and are still going strong.
  11. I use the NUT plugin and I get the dashboard display for my UPS. Works great.
  12. I had the same issue using the NUT plugin. I fixed it by uninstalling and reinstalling the NUT plugin. I now have the UPS watt usage display on the dashboard.
  13. At idle my server draws 27 watts, or .65 kWh per day. When spun up I've seen it drawing a maximum of 65watts, or 1.65kWh per day.
  14. This started happening in 6.6.3. It still happens after an upgrade to 6.6.4. This has happened 4 or 5 times in the last week. Issues first seems to appear on my docker containers. I'll try to access one of my docker's web gui and I can't get to it. I then go into the UNRAID web management and try to access the docker tab. The docker tab is unresponsive. I then ssh into the server and attempt to stop docker from the cli. I can log into ssh, but when I try to run any command it hangs. I opened another putty session to try to see if there were any open files that could be locked, and also attempted to run ps to see what processes were running. That also hung. I have space on my cache drive and on the ssd I use for my docker app storage. I was able to grab a diagnostics file from the server. I also was able to run htop, which showed high load over 100 just prior to grabbing the capture and a docker process monopolizing the server. Since I grabbed the screen capture, load has gone back to normal, but most of my dockers are still unresponsive. Thanks, tower-diagnostics-20181108-0833.zip
  15. Edit: Upgrading from 6.6.1 to 6.6.2 and the plugin works properly again. Having some issues with the NerdPack plugin. When I go into settings and choose nerdpack, none of the packages show up. I've tried removing the plugin, deleting the nerdpack directory, rebooting, & reinstalling the plugin with no change. Is this a just my server issue or have others also experienced this? I'm on v6.6.1. I'm including a screenshot and diagnostics. tower-diagnostics-20181012-1254.zip Thanks
  16. Thank you for the information. It's greatly appreciated.
  17. Sorry to resurrect an old thread. I have been using the above method for cron jobs for a number of years successfully. On Feb 23, cron jobs stopped running that I've set up in the /boot/config/plugins/mycron folder. The cron jobs are inside a file called bkp.cron. The cron jobs in the file are all rsyncs that I use to back up primary data to a secondary location. The cron jobs stopped working around the time I moved from 6.4 to 6.5. I haven't downgraded to test if an earlier version works yet. It's a production environment and I don't want to take it offline unless I have to. Upgrading to the latest version of Unraid, 6.5.1-rc1, hasn't resolved the issue. Has anyone else experienced this? I've attached diags. luna-diagnostics-20180323-0854.zip
  18. I notice that the docker has been updated Ubooquity version 2.1. It looks like the update made some internal changes that made the existing databases inaccessible. The databases are repopulating from the path set in the docker setup, rather than from the path set in the ubooquity admin area. The admin page is also no longer accessible via the normal url method. Is there a new method I should be using to access the admin page, and if not, how can I revert back to v 1.10? Thanks!
  19. Repairing the file system on the cache drive was the solution. Thanks again!
  20. Thanks, Squid! I appreciate the assistance. I'll start a file system check and go from there.
  21. I've gotten a warning about Call traces in my syslog from the Fix Common problems plugin. It looks like a kernel issue, but I'm not sure what, if anything, I can do to solve it. Any input would be appreciated. I've attached the diagnostics file, and included the call trace inside the post. Thank you! Mar 13 10:04:11 Tower kernel: ------------[ cut here ]------------ Mar 13 10:04:11 Tower kernel: WARNING: CPU: 2 PID: 13689 at fs/btrfs/extent-tree.c:134 btrfs_put_block_group+0x42/0x59 Mar 13 10:04:11 Tower kernel: Modules linked in: xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod hwmon_vid pata_marvell coretemp kvm_intel kvm r8169 mii ahci libahci sata_mv i2c_i801 intel_agp i2c_smbus intel_gtt i2c_core ata_piix agpgart asus_atk0110 acpi_cpufreq [last unloaded: md_mod] Mar 13 10:04:11 Tower kernel: CPU: 2 PID: 13689 Comm: umount Not tainted 4.9.10-unRAID #1 Mar 13 10:04:11 Tower kernel: Hardware name: System manufacturer System Product Name/P5Q-PRO, BIOS 2102 02/23/2009 Mar 13 10:04:11 Tower kernel: ffffc900053ebd20 ffffffff813a353e 0000000000000000 ffffffff81968f2d Mar 13 10:04:11 Tower kernel: ffffc900053ebd60 ffffffff8104d00c 00000086053ebd00 ffff880222bb3c00 Mar 13 10:04:11 Tower kernel: ffff880222bb3ce8 ffff880222476090 ffff880222bb3c00 ffff8802224760a0 Mar 13 10:04:11 Tower kernel: Call Trace: Mar 13 10:04:11 Tower kernel: [<ffffffff813a353e>] dump_stack+0x61/0x7e Mar 13 10:04:11 Tower kernel: [<ffffffff8104d00c>] __warn+0xb8/0xd3 Mar 13 10:04:11 Tower kernel: [<ffffffff8104d0d4>] warn_slowpath_null+0x18/0x1a Mar 13 10:04:11 Tower kernel: [<ffffffff812d591a>] btrfs_put_block_group+0x42/0x59 Mar 13 10:04:11 Tower kernel: [<ffffffff812dbc2b>] btrfs_free_block_groups+0x19d/0x39b Mar 13 10:04:11 Tower kernel: [<ffffffff812eadf9>] close_ctree+0x1d4/0x2e8 Mar 13 10:04:11 Tower kernel: [<ffffffff81137d51>] ? evict_inodes+0x128/0x137 Mar 13 10:04:11 Tower kernel: [<ffffffff812c5c50>] btrfs_put_super+0x14/0x16 Mar 13 10:04:11 Tower kernel: [<ffffffff8112305b>] generic_shutdown_super+0x6a/0xeb Mar 13 10:04:11 Tower kernel: [<ffffffff811232be>] kill_anon_super+0xd/0x17 Mar 13 10:04:11 Tower kernel: [<ffffffff812c5b97>] btrfs_kill_super+0x11/0x94 Mar 13 10:04:11 Tower kernel: [<ffffffff811234b0>] deactivate_locked_super+0x3b/0x68 Mar 13 10:04:11 Tower kernel: [<ffffffff81123e34>] deactivate_super+0x39/0x3c Mar 13 10:04:11 Tower kernel: [<ffffffff8113acd2>] cleanup_mnt+0x53/0x71 Mar 13 10:04:11 Tower kernel: [<ffffffff8113ad24>] __cleanup_mnt+0xd/0xf Mar 13 10:04:11 Tower kernel: [<ffffffff81062530>] task_work_run+0x6a/0x7d Mar 13 10:04:11 Tower kernel: [<ffffffff81002b24>] exit_to_usermode_loop+0x55/0x81 Mar 13 10:04:11 Tower kernel: [<ffffffff81002c61>] syscall_return_slowpath+0x44/0x47 Mar 13 10:04:11 Tower kernel: [<ffffffff8167d344>] entry_SYSCALL_64_fastpath+0xa7/0xa9 Mar 13 10:04:11 Tower kernel: ---[ end trace 8e45affbece91bb7 ]--- Mar 13 10:04:11 Tower kernel: ------------[ cut here ]------------ Mar 13 10:04:11 Tower kernel: WARNING: CPU: 2 PID: 13689 at fs/btrfs/extent-tree.c:10045 btrfs_free_block_groups+0x37a/0x39b Mar 13 10:04:11 Tower kernel: Modules linked in: xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod hwmon_vid pata_marvell coretemp kvm_intel kvm r8169 mii ahci libahci sata_mv i2c_i801 intel_agp i2c_smbus intel_gtt i2c_core ata_piix agpgart asus_atk0110 acpi_cpufreq [last unloaded: md_mod] Mar 13 10:04:11 Tower kernel: CPU: 2 PID: 13689 Comm: umount Tainted: G W 4.9.10-unRAID #1 Mar 13 10:04:11 Tower kernel: Hardware name: System manufacturer System Product Name/P5Q-PRO, BIOS 2102 02/23/2009 Mar 13 10:04:11 Tower kernel: ffffc900053ebd38 ffffffff813a353e 0000000000000000 ffffffff81968f2d Mar 13 10:04:11 Tower kernel: ffffc900053ebd78 ffffffff8104d00c 0000273d053ebd40 ffff880222476000 Mar 13 10:04:11 Tower kernel: ffff880221e1bc88 ffff880221e1bc00 ffff880222476b30 0000000000000000 Mar 13 10:04:11 Tower kernel: Call Trace: Mar 13 10:04:11 Tower kernel: [<ffffffff813a353e>] dump_stack+0x61/0x7e Mar 13 10:04:11 Tower kernel: [<ffffffff8104d00c>] __warn+0xb8/0xd3 Mar 13 10:04:11 Tower kernel: [<ffffffff8104d0d4>] warn_slowpath_null+0x18/0x1a Mar 13 10:04:11 Tower kernel: [<ffffffff812dbe08>] btrfs_free_block_groups+0x37a/0x39b Mar 13 10:04:11 Tower kernel: [<ffffffff812eadf9>] close_ctree+0x1d4/0x2e8 Mar 13 10:04:11 Tower kernel: [<ffffffff81137d51>] ? evict_inodes+0x128/0x137 Mar 13 10:04:11 Tower kernel: [<ffffffff812c5c50>] btrfs_put_super+0x14/0x16 Mar 13 10:04:11 Tower kernel: [<ffffffff8112305b>] generic_shutdown_super+0x6a/0xeb Mar 13 10:04:11 Tower kernel: [<ffffffff811232be>] kill_anon_super+0xd/0x17 Mar 13 10:04:11 Tower kernel: [<ffffffff812c5b97>] btrfs_kill_super+0x11/0x94 Mar 13 10:04:11 Tower kernel: [<ffffffff811234b0>] deactivate_locked_super+0x3b/0x68 Mar 13 10:04:11 Tower kernel: [<ffffffff81123e34>] deactivate_super+0x39/0x3c Mar 13 10:04:11 Tower kernel: [<ffffffff8113acd2>] cleanup_mnt+0x53/0x71 Mar 13 10:04:11 Tower kernel: [<ffffffff8113ad24>] __cleanup_mnt+0xd/0xf Mar 13 10:04:11 Tower kernel: [<ffffffff81062530>] task_work_run+0x6a/0x7d Mar 13 10:04:11 Tower kernel: [<ffffffff81002b24>] exit_to_usermode_loop+0x55/0x81 Mar 13 10:04:11 Tower kernel: [<ffffffff81002c61>] syscall_return_slowpath+0x44/0x47 Mar 13 10:04:11 Tower kernel: [<ffffffff8167d344>] entry_SYSCALL_64_fastpath+0xa7/0xa9 Mar 13 10:04:11 Tower kernel: ---[ end trace 8e45affbece91bb8 ]--- Mar 13 10:04:11 Tower kernel: BTRFS info (device loop0): space_info 4 has 993476608 free, is not full Mar 13 10:04:11 Tower kernel: BTRFS info (device loop0): space_info total=1342177280, used=348618752, pinned=0, reserved=16384, may_use=0, readonly=65536 Mar 13 10:04:11 Tower kernel: BTRFS warning (device loop0): page private not zero on page 4524769280 Mar 13 10:04:11 Tower kernel: BTRFS warning (device loop0): page private not zero on page 4524773376 Mar 13 10:04:11 Tower kernel: BTRFS warning (device loop0): page private not zero on page 4524777472 Mar 13 10:04:11 Tower kernel: BTRFS warning (device loop0): page private not zero on page 4524781568 tower-diagnostics-20170313-1030.zip
  22. I've had some trouble updating mylar to update. The web gui tells me there is a newer version available with 33 new commits. I hit the update option, the web gui goes to an updating page, and then shows me that none of the updates have been applied. Log file gives me this error: 2016-09-22 11:04:37 WARNING Could not get the latest commit from github 2016-09-22 11:04:36 INFO Retrieving latest version information from github I've got it set yp pull from the development branch. I've tried deleting the docker and re-adding it. I've tried creating a new appadata directory with no change. Suggestions?
  23. Try running make_bootable in Windows7. Windows 10 didn't allow the make_bootable to run for me, but I was able to run it on a Win 7 OS.