sdiama

As I wrote at the title, both of my SSD (WD Green) died in 24 hours (bought also at the same day!) after 2 years and 5 months of usage. The first one died at midnight (bad disk - not discovered by Unraid), while the second on after 8 hours (Too many bad sectors). Thank god they were still under warranty. At the cache I am only storing my dockers, VMs and ISOs, but for some "strange?" reason I also lost my shares. Ok, it's easy to recreate the shares but... tomorrow I'll installed the replacement SSDs and I plan to restore from CA Backup. Is it a straight forward procedure? Are my Dockers and VMs recreated automatically? Is it something I must be extra careful? I'm counting at your previous experience to help me for a "bloodless" restore procedure. Thank in advance

The banner I'm using this period:

I just installed it from Community Applications

Here's the log file after the docker restart: *** Running /etc/my_init.d/10_syslog-ng.init... Oct 25 09:48:25 b4110ea3034a syslog-ng[13]: syslog-ng starting up; version='3.13.2' *** Running /etc/my_init.d/firstrun.sh... Using existing PHP database config file. warning: commands will be executed using /bin/sh job 3 at Thu Oct 25 09:49:00 2018 ln: failed to create symbolic link '/opt/observium/config.php': File exists *** Booting runit daemon... *** Runit started as PID 29 Oct 25 09:48:26 b4110ea3034a cron[34]: (CRON) INFO (pidfile fd = 3) Oct 25 09:48:26 b4110ea3034a cron[34]: (CRON) INFO (Skipping @reboot jobs -- not system startup) Database exists. Starting MariaDB... 181025 09:48:26 mysqld_safe Logging to '/config/databases/b4110ea3034a.err'. 181025 09:48:26 mysqld_safe Starting mysqld daemon with databases from /config/databases Oct 25 09:50:01 b4110ea3034a CRON[324]: (root) CMD ( /opt/observium/discovery.php -h new >> /dev/null 2>&1) Oct 25 09:50:01 b4110ea3034a CRON[325]: (root) CMD ( /opt/observium/poller-wrapper.py 2 >> /dev/null 2>&1)

After installation, I'm entering the default username and password 'observium' and is not working Please advice

Currently I run a Freenas 9.10 with a 6x3Tb WD Red in a RAIDZ2 pool filled with 9+Tb of data on it. I'm planning to upgrade my box, to unRAID, mainly because of the VM/Docker features. So I plan to use the following procedure in order to migrate it: Currently I run a Freenas 9.10 with a 6x3Tb WD Red in a RAIDZ2 pool filled with 9+Tb of data on it. I'm planning to upgrade my box, to unRAID, mainly because of the VM/Docker features. So I plan to use the following procedure in order to migrate it: 1. Build a new temporary box, with some spare parts and add 2x6Tb new WD Red HDDs. 2. Configure unRAID to my "temp box", keeping the 1out of 2 disks as parity. 3. Copy as many files the "temp box" can hold, from my existing FreeNAS box. 4. The remaining files I'll copy them on a Synology NAS, I already have, that has about 5Tb free space. 5. Move the 2x6Tb HDDs at the existing "FreeNAS" case and boot with the unRAID USB stick I created at the "temp box". 6. Now my "old Freenas" case runs unRAID with 2x6Tb already configured and all the data I previously copied on them . Correct?? 7. Add the "old Freenas" 6x3Tb (already in the case) at the unRAID array devices expanding the box. Now the old case has unRAID installed with 1x6Tb & 6x3Tb plus 1x6Tb as parity. Correct?? 8. Move the remaining files from my Synology NAS. 9. Add one 64Gb "slow" (spare) SSD disk as cache. Is there any problem with the procedure? Please note that the existing case, hosting FreeNAS, it will have 2 SATA controllers (1x6 SATA + 1x5 SATA) T.I.A. PS: I don't have many simultaneous writes on my NAS. Only a couple of users at the local network and a couple of sporadic remote users. So, I don't have great speed needs (initially). Do you believe I have to add the SSD cache?