air_marshall

ddrescue completed without error, took a while as everytime the console closed it seemed to stop. anyway, handy that it can resume..... I mounted the destination drive and the data is present and readable. How can I check the data on disc 6 is identical to the ddresuce copy to destination? Some sort of checksum comparison process/tool? I didn't see your message so the extended SMART check was run on disc 6, it passed without error. Following the new config the array is now back up and parity is being created. Diagnostics attached. tower-diagnostics-20241010-2028.zip

Thank you for the reply @JorgeB I will let ddrescue complete then reboot and do a new config and report back after an extended SMART test.

I recently had my parity drive go bad. So set about replacing it. When I re-powered the server I started getting CRC errors of Drive 5 and Drive 6, which obviously led to a parity sync fail. I powered down and replaced the sata cables on those drives. By this point Drive 6 had gone disabled and I can't get it back. It passes a short SMART test. Researching on the forum I see this situation has been encountered before so I wanted to do a xfs file system check, however it instantly results in a "superblock read failed" I'm currently using ddrescue to clone Drive 6 to another drive that is outside the array (that has been pre-cleared). Can someone advise me of the next steps once ddrescue has finished its process? Is there a chance I can repair Disk 6 in situ without having to copy back data from ddrescue destination disc? Diagnostics attached. Thanks in advance to this great community! tower-diagnostics-20241009-1148.zip

sde extended SMART attached GUI reports completed without error tower-smart-20240326-2039.zip

Ok, extended sde SMART test is running. Will post results. Same for sdj, the disc I replaced in the array. Any ideas why there is such a gap in my logs? syslog-previous ends Mar 21 12:30:57. Any place else I can go looking for them? Log seems to be flooded with an nvidia error that I've not seen before!

Started 22 Mar 1051 Finished 22 Mar 2254 No reboot or power cycle since! Data-Rebuild 2024-03-22, 22:53:15 (Friday) 4 TB 12 hr, 2 min, 49 sec 92,2 MB/s OK 41

Hi Guys, Long story short, had some 'thermal management' issues in my 'comms room' that may have started to push some of my older drives closer to EOL. Drive sdj threw a couple of SMART errors so set about replacing that one first with a pre-cleared 4TB drive sdi that was pre-cleared. During rebuild of data drive sde threw 41 read errors which translated to 41 data errors with the rebuild. Last Parity check without errors was 07 Mar 24. See attached diagnostics. sdj still attached to machine and hasn't been touched since removing from the array. Data on that drive is largely expendable. Non-expendable is backed up elsewhere. I have another 4TB waiting to be pre-cleared that is available for either replacement of another drive or adding to the array. What are my next steps before I make this situation worse..... TIA tower-diagnostics-20240326-0923.zip

Good thinking. Done. First reboot from freshly prepared and restored stick has given the same result. Server GUI not accessible. Shares not mounted. SSH available. Looks like USB is read-only again. root@Tower:~# diagnostics mkdir: cannot create directory ‘/boot/logs’: Input/output error Starting diagnostics collection... tail: cannot open '/boot/bz*.sha256' for reading: No such file or directory sed: can't read /tower-diagnostics-20230829-0942/config/go.txt: No such file or directory done. ZIP file '/boot/logs/tower-diagnostics-20230829-0942.zip' created. Last lines of syslog using: Aug 29 09:42:42 Tower kernel: FAT-fs (sda1): Directory bread(block 30620) failed Aug 29 09:42:42 Tower kernel: FAT-fs (sda1): Directory bread(block 30621) failed Aug 29 09:42:42 Tower kernel: FAT-fs (sda1): Directory bread(block 30622) failed Aug 29 09:42:42 Tower kernel: FAT-fs (sda1): Directory bread(block 30623) failed Aug 29 09:42:42 Tower kernel: FAT-fs (sda1): Directory bread(block 30624) failed Aug 29 09:42:42 Tower kernel: FAT-fs (sda1): Directory bread(block 30625) failed Aug 29 09:42:42 Tower kernel: FAT-fs (sda1): Directory bread(block 30626) failed Aug 29 09:42:42 Tower kernel: FAT-fs (sda1): Directory bread(block 30627) failed Does this mean the USB is bad OR files in the USB config folder are corrupted? Diagnostics file attached from last shutdown before erasing and reinstalling usb. USB 2 port is in use. Best path forward at this point? tower-diagnostics-20230829-0914-shutdown.zip

Almost everytime I reboot/shutdown my server comes back-up with no GUI, no shares mounted. SSH is available and 'diagnostics' command results is a 'directory' doesn't exist error. USB drive chkdisk repair results in a successful boot. Diagnostics file is attached - I believe this one was captured automatically during post Tip and Tweaks install. TL;DR Server was off for c12 months during our house renovation. Upon reboot I've had multiple issues. First seemed to be related to docker not being terminated on array stop/reboot/shutdown. I found the forum post, used the commands to stop and then was able to clean reboot/shutdown. Server upgraded to latest stable. I set-about reformatting my cache to ZFS using spaceinvader video. Created a pool, but on copying back to the cache pool 1 of the drives had significant ATA issues, that drive eventually disappeared (I suspect went bad, but I've now pulled the SATA cable on it). So back to a single drive cache. Current situation is as above. I've carried out most suggestions from the 'Unclean Shutdown Thread", docker is disabled, no VMs, Tips & Tweaks plugin is installed to capture diagnostics on shutdown and time-outs set at 7 mins. There isn't a delay in unmounting drives however I feel like something is hanging on reboot/shutdown that results in the usb drive being mounted "read-only" on almost every reboot. Fixed by pulling the usb and doing a repair in windows but obviously not sustainable. Any/All help is much appreciated. I'm a long time unraid user and these are the first stability issues i've experienced. TIA tower-diagnostics-20230827-1032.zip

does docker-compose persist after reboot if you install it this way?

I'm wondering this too. Looking at the master docker info you'd have to specify some more variable. I'm getting InnoDB and subsequent mysql errors on install so can't yet get it up. Everything stock as per the video apart from eth0 set to a static IP. root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='shinobi_pro' --net='eth0' --ip='192.168.50.200' -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'TCP_PORT_8080'='8080' -e 'ADMIN_USER'='admin' -e 'ADMIN_PASSWORD'='password' -v '/mnt/disks/cctv/':'/opt/shinobi/videos':'rw,slave' -v '/mnt/user/appdata/shinobi_pro':'/config':'rw' -v '/mnt/user/appdata/shinobipro/database':'/var/lib/mysql':'rw' -v '/mnt/user/appdata/shinobipro/customautoload':'/opt/shinobi/libs/customAutoLoad':'rw' 'spaceinvaderone/shinobi_pro_unraid:latest' a8aa5c000266e29966658067e0cdc657becf86d88cac66537f73f209a2e4b39f The command finished successfully! Log result after install: Copy custom configuration files ... cp: cannot stat '/config/*': No such file or directory No custom config files found. Create default config file /opt/shinobi/conf.json ... Create default config file /opt/shinobi/super.json ... Create default config file /opt/shinobi/plugins/motion/conf.json ... Hash admin password ... MariaDB Directory ... Installing MariaDB ... Installing MariaDB/MySQL system tables in '/var/lib/mysql' ... 2019-12-28 12:46:49 0 [ERROR] InnoDB: preallocating 12582912 bytes for file ./ibdata1 failed with error 95 2019-12-28 12:46:49 0 [ERROR] InnoDB: Could not set the file size of './ibdata1'. Probably out of disk space 2019-12-28 12:46:49 0 [ERROR] InnoDB: Database creation was aborted with error Generic error. You may need to delete the ibdata1 file before trying to start up again. 2019-12-28 12:46:49 0 [ERROR] Plugin 'InnoDB' init function returned error. 2019-12-28 12:46:49 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2019-12-28 12:46:50 0 [ERROR] Unknown/unsupported storage engine: InnoDB 2019-12-28 12:46:50 0 [ERROR] Aborting Installation of system tables failed! Examine the logs in /var/lib/mysql for more information. The problem could be conflicting information in an external my.cnf files. You can ignore these by doing: shell> /usr/bin/mysql_install_db --defaults-file=~/.my.cnf You can also try to start the mysqld daemon with: shell> /usr/bin/mysqld --skip-grant-tables --general-log & and use the command line tool /usr/bin/mysql to connect to the mysql database and look at the grant tables: shell> /usr/bin/mysql -u root mysql mysql> show tables; Try 'mysqld --help' if you have problems with paths. Using --general-log gives you a log in /var/lib/mysql that may be helpful. The latest information about mysql_install_db is available at https://mariadb.com/kb/en/installing-system-tables-mysql_install_db You can find the latest source at https://downloads.mariadb.org and the maria-discuss email list at https://launchpad.net/~maria-discuss Please check all of the above before submitting a bug report at http://mariadb.org/jira

I believe they've moved it in the latest betas but that should also have been incorporated into the latest stable, which isn't available as part of this container yet (still!). I copied the dzvents from the windows install and fixed the permissions, seems to work fine for most things BUT I if I try to update a virtual temp sensor with a script I get reboots every minute - this can't be replicated by others on the domoticz forum, so can only assume it's something weird with the container... I'm debating moving it to a dedicated pi as my house gets more dependant on it and I need to ensure the WAF!

Forgive my ignorance, but can I just use the branch on github you created anyway, without the tag? If so, how?

Any news on the ETA for the stable-3.8153 tag? Many thanks!

Can we get a tag for the latest stable? 3.8153 Currently using the 'latest' tag but experiencing some of the bleeding edge bugs which is ruining the WAF, but I need functionality that was added between the stable tag on the repo and the latest stable release.