-
Posts
10,398 -
Joined
-
Last visited
-
Days Won
20
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by dlandon
-
I didn't take it as a demand. This docker has gotten to where it takes more time than I care to invest for virtually zero donations. I am a little frazzled.
-
I don't compile in ES. I include the released version once it is ready. pliablepixels did make some last minute changes that I wasn't expecting when he asked me to give 5.7 a try. It was just released 16 hours ago! Give me a break! I do this part time and I have to do some testing before I release it. I'll get it done when I can.
-
Add this to the 'FFMPEG_OUTPUT_OPTIONS': -hwaccel auto
-
Yes. It was never intended for UD to support VM disk images. VM images should be on the cache or an array disk. UD happens to handle mounting and supporting a VM image disk to a point. Spin down control is fixed and disk monitoring is non-existent. I know the arguments about how the cache and array don't do what you want right now. Eventually Unraid will have multiple cache device capability that will let you do what you are doing with UD. Yes, and I don't intend to change it. Post a feature request for LT to add the multiple cache device capability.
-
Not necessary. Removing and recreating SMB shares was needed when UD was updated to encrypt passwords. Yes. If the password changes, you'll have to recreate the share. If you entered the credentials correctly, then clicked the 'Load Shares' and they show up, then the credentials are correct. For further help, post diagnostics.
-
[support] Zoneminder - 1.35 (in development)
dlandon replied to dlandon's topic in Docker Containers
Use the Zoneminder 1.34 release version and not this version. -
Looks like it started here: Feb 4 20:44:21 ramiii unassigned.devices: Mount of '/dev/sda2' failed. Error message: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Failed to read NTFS : Input/output error NTFS is either inconsistent, or there is a hardware fault, or it's a SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows then reboot into Windows twice. The usage of the /f parameter is very important! If the device is a SoftRAID/FakeRAID then first activate it and mount a different device under the /dev/mapper/ directory, (e.g. /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation for more details. Failed to sync device /dev/sda2: Input/output error Failed to close volume /dev/sda2: Input/output error Looks to be a hardware error came up before you converted from ntfs. It also appears you removed the disk while it was mounted: Feb 6 00:21:53 ramiii unassigned.devices: Partition 'Home' could not be mounted. Feb 6 00:21:53 ramiii unassigned.devices: Running device script: 'Home.sh' with action 'ERROR_MOUNT'. Feb 6 00:21:54 ramiii mount.exfat: failed to read cluster 0x12 Feb 6 00:21:54 ramiii mount.exfat: failed to open directory '/TV Shows' Feb 6 00:21:54 ramiii kernel: Buffer I/O error on dev sdp1, logical block 2816, async page read Feb 6 00:21:56 ramiii mount.exfat: failed to read cluster 0x13 Feb 6 00:21:56 ramiii mount.exfat: failed to open directory '/Movies' Feb 6 00:21:56 ramiii kernel: Buffer I/O error on dev sdp1, logical block 2848, async page read Feb 6 00:21:57 ramiii mount.exfat: failed to read cluster 0x4419a Feb 6 00:21:57 ramiii mount.exfat: failed to open directory '/ebooks' Feb 6 00:21:57 ramiii kernel: Buffer I/O error on dev sdp1, logical block 8928256, async page read Feb 6 00:23:12 ramiii webGUI: Successful login user root from 192.168.11.95 Feb 6 00:23:39 ramiii kernel: usb 16-1.1: USB disconnect, device number 24 Reboot your server to clear the improper mount and then figure out what is wrong with the USB disk.
-
It was a problem in UD. I've released a fix.
-
Normally these are: - PUID=99 - PGID=100 Which is user:nobody. Use CA to install the docker.
-
I would disable the recycle bin on UD devices: Feb 5 19:20:02 BasementNAS unassigned.devices: Enabling the Recycle Bin on share 'TempDrive' You are also getting some errors on the ntfs disk: Feb 5 19:10:54 BasementNAS ntfs-3g[6388]: ntfs_mst_post_read_fixup_warn: magic: 0x48fc9c1b size: 4096 usa_ofs: 28023 usa_count: 55516: Invalid argument Feb 5 19:10:54 BasementNAS ntfs-3g[6388]: Actual VCN (0x5de9b5dd95e655e7) of index buffer is different from expected VCN (0x0). Feb 5 19:10:54 BasementNAS ntfs-3g[6388]: ntfs_mst_post_read_fixup_warn: magic: 0x48fc9c1b size: 4096 usa_ofs: 28023 usa_count: 55516: Invalid argument Feb 5 19:10:54 BasementNAS ntfs-3g[6388]: Actual VCN (0x5de9b5dd95e655e7) of index buffer is different from expected VCN (0x0). Feb 5 19:10:54 BasementNAS ntfs-3g[6388]: ntfs_mst_post_read_fixup_warn: magic: 0x48fc9c1b size: 4096 usa_ofs: 28023 usa_count: 55516: Invalid argument Feb 5 19:10:54 BasementNAS ntfs-3g[6388]: Actual VCN (0x5de9b5dd95e655e7) of index buffer is different from expected VCN (0x0) in inode 0x2c25. Feb 5 19:10:54 BasementNAS ntfs-3g[6388]: ntfs_mst_post_read_fixup_warn: magic: 0x48fc9c1b size: 4096 usa_ofs: 28023 usa_count: 55516: Invalid argument Feb 5 19:10:54 BasementNAS ntfs-3g[6388]: Actual VCN (0x5de9b5dd95e655e7) of index buffer is different from expected VCN (0x0). Feb 5 19:10:54 BasementNAS ntfs-3g[6388]: ntfs_mst_post_read_fixup_warn: magic: 0x48fc9c1b size: 4096 usa_ofs: 28023 usa_count: 55516: Invalid argument Feb 5 19:10:54 BasementNAS ntfs-3g[6388]: Corrupt index block signature: vcn 0 inode 11301 Feb 5 19:10:54 BasementNAS ntfs-3g[6388]: Failed to find place for new entry: Input/output error Feb 5 19:10:54 BasementNAS ntfs-3g[6388]: Failed to add entry to the index: Input/output error I am not familiar with these errors. Maybe @johnnie.black can offer some help. If it were me, I would use an xfs or btrfs disk format and not ntfs.
-
No changes to es.
-
There is a Docker update that adjusts the ownership of the event, images, cache, and temp folders. When the docker is run it will adjust the ownership. If you have a lot of events it will take a while. Just be patient and let it finish it's work. The ownership of these folders has been changed from root:www-data to www-data:www-data. Let me know if anyone has problems with events being saved.
-
Try the Zoneminder forum for help.