gfjardim

Can you please send me the list of installed plugins?

What I wish with this test is to improve array disks detection, to fix that /boot/config/disk.cfg not found bug. It's very helpful, thanks!

Since many users use reverse proxy here (me included), it will remain use 8.1.4 due to this bug.

Ok, thank you very much!

login as: root root@tower's password: Linux 4.1.7-unRAID. root@Tower:~# php -r "$(curl -skL https://gist.githubusercontent.com/gfjardim/c81fba928425e7a1dfac/raw/)" Disks: + /dev/sdl => /dev/disk/by-id/scsi-SATA_ST6000DM001-1XY_Z4D23K9N + /dev/sdm => /dev/disk/by-id/scsi-SATA_WDC_WD20EZRX-00_WD-WMC4M2038014 + /dev/sdi => /dev/disk/by-id/scsi-SATA_WDC_WD60EFRX-68_WD-WX51D6402971 + /dev/sdj => /dev/disk/by-id/scsi-SATA_WDC_WD20EZRX-00_WD-WMC1T0154634 + /dev/sdh => /dev/disk/by-id/scsi-SATA_ST8000AS0002-1N_Z8406M0L + /dev/sdk => /dev/disk/by-id/scsi-SATA_WDC_WD20EZRX-00_WD-WCC300673196 + /dev/sdn => /dev/disk/by-id/scsi-SATA_Samsung_SSD_840S1DBNEAD812507A + /dev/sdg => /dev/disk/by-id/scsi-MD04ACA500_24R6K00RFS9A + /dev/sdf => /dev/disk/by-id/scsi-ST2000DM001-1CH1_Z1F5DKBF + /dev/sde => /dev/disk/by-id/scsi-ST4000DM000-1F21_Z3024WMZ + /dev/sdc => /dev/disk/by-id/scsi-ST4000DM000-1F21_Z3024WY8 + /dev/sdd => /dev/disk/by-id/scsi-ST6000DX000-1H21_Z4D04L2A + /dev/sdb => /dev/disk/by-id/scsi-ARC-1231-RAID00_0000002273521567 + /dev/sdm => /dev/disk/by-id/ata-WDC_WD20EZRX-00D8PB0_WD-WMC4M2038014 + /dev/sdk => /dev/disk/by-id/ata-WDC_WD20EZRX-00DC0B0_WD-WCC300673196 + /dev/sdj => /dev/disk/by-id/ata-WDC_WD20EZRX-00DC0B0_WD-WMC1T0154634 + /dev/sdi => /dev/disk/by-id/ata-WDC_WD60EFRX-68MYMN1_WD-WX51D6402971 + /dev/sdl => /dev/disk/by-id/ata-ST6000DM001-1XY17Z_Z4D23K9N + /dev/sdh => /dev/disk/by-id/ata-ST8000AS0002-1NA17Z_Z8406M0L + /dev/sdn => /dev/disk/by-id/ata-Samsung_SSD_840_EVO_250GB_S1DBNEAD812507A + /dev/sda => /dev/disk/by-id/usb-SanDisk_U3_Cruzer_Micro_1031811B45D2F146-0:0 unRAID Serials: + ARC-1231-RAID00_0000002273521567 + MD04ACA500_24R6K00RFS9A + ST6000DX000-1H21_Z4D04L2A + WDC_WD60EFRX-68MYMN1_WD-WX51D6402971 + ST6000DM001-1XY17Z_Z4D23K9N + WDC_WD20EZRX-00DC0B0_WD-WMC1T0154634 + WDC_WD20EZRX-00D8PB0_WD-WMC4M2038014 + WDC_WD20EZRX-00DC0B0_WD-WCC300673196 + ST8000AS0002-1NA17Z_Z8406M0L + ST4000DM000-1F21_Z3024WY8 + ST4000DM000-1F21_Z3024WMZ + ST2000DM001-1CH1_Z1F5DKBF + Samsung_SSD_840_EVO_250GB_S1DBNEAD812507A + /dev/disk/by-id/usb-SanDisk_U3_Cruzer_Micro_1031811B45D2F146-0:0-part1 + /dev/disk/by-id/usb-SanDisk_U3_Cruzer_Micro_1031811B45D2F146-0:0 unRAID Disks: + /dev/disk/by-id/scsi-ARC-1231-RAID00_0000002273521567 + /dev/disk/by-id/scsi-MD04ACA500_24R6K00RFS9A + /dev/disk/by-id/scsi-ST6000DX000-1H21_Z4D04L2A + /dev/disk/by-id/ata-WDC_WD60EFRX-68MYMN1_WD-WX51D6402971 + /dev/disk/by-id/ata-ST6000DM001-1XY17Z_Z4D23K9N + /dev/disk/by-id/ata-WDC_WD20EZRX-00DC0B0_WD-WMC1T0154634 + /dev/disk/by-id/ata-WDC_WD20EZRX-00D8PB0_WD-WMC4M2038014 + /dev/disk/by-id/ata-WDC_WD20EZRX-00DC0B0_WD-WCC300673196 + /dev/disk/by-id/ata-ST8000AS0002-1NA17Z_Z8406M0L + /dev/disk/by-id/scsi-ST4000DM000-1F21_Z3024WY8 + /dev/disk/by-id/scsi-ST4000DM000-1F21_Z3024WMZ + /dev/disk/by-id/scsi-ST2000DM001-1CH1_Z1F5DKBF + /dev/disk/by-id/ata-Samsung_SSD_840_EVO_250GB_S1DBNEAD812507A + /dev/disk/by-id/usb-SanDisk_U3_Cruzer_Micro_1031811B45D2F146-0:0 Unassigned Disks: + Array ( ) root@Tower:~# interwebtech, you don't have any unassigned devices right now, correct?

I'll try this soon.

Guys, specially those who have Areca cards, can you please PM me the output of this command? php -r "$(curl -skL https://gist.githubusercontent.com/gfjardim/c81fba928425e7a1dfac/raw/)" Thanks!

This is true of course ... but that effectively shuts down the array for the duration of your pre-clears => which, with modern drives (and 2-3 passes) could easily be several days. Not, in most cases, a very desirable way to go. One of the key benefits of pre-clearing is you don't have an unavailable array during a clear operation. You don't need to use another system; just unplug all soon-to-clear disks, start the array, plug them in and then start the preclear. NOTE: if you stop the array while preclearing, you won't be able to start it again. This is a bug, and will be fixed. Thanks for reporting this out. I continue to experience this failure to open and shutdown problem sometimes it opens after 20 plus clicks and sometimes it refuses to open. All my other plugins and buttons work after one click on my system. Can someone please describe how to correct what is happening. The disk to PreClear is unassigned and should be already spun up I did some testing again with this bug and here is what I found. The bug occurs consistently with Google Chrome, Firefox and Safari. The bug does NOT occur and the plugin starts every time with Internet Explorer. Hopefully the plugin author can figure out the reason. This is difficult one to debug; I'll add some debug capabilities to the plugin in the next version, then we can fix this, ok?

No Redis, but got APCu working. Auto update and cron will be addressed in the next version. How do I implement APCu? It's local cache, so no need to do anything. I'm getting the notice in owncloud about not having memcache implemented. They say to add this to the config.php: 'memcache.local' => '\OC\Memcache\APCu', But when I run cron.php, is says that the memcache is not implemented. My bad, will be fixed in the next version.

Guys, let's start iron these bugs out. It's already baked into the code, but not enabled. In the next release, it will try to unmount the disk 5 times, and, if it's locked (no opened files and yet it refuses to unmount) it will be unmount forcibly. I needed more time to test this out. Probably, your flash drive was corrupted. I'll investigate this.

No Redis, but got APCu working. Auto update and cron will be addressed in the next version. How do I implement APCu? It's local cache, so no need to do anything.

I can move the App folder from /var/www/owncloud/apps to /var/www/owncloud/data/apps . Will that be enough?

No Redis, but got APCu working. Auto update and cron will be addressed in the next version.

Yep, that one!

No, thank you ljm42 for your assistance, ljm42 !!!

Just updated my test server to see what would happen and you are right. Not working. It did finally start, but I don't know what I did to get it going. I was messing around in the docker looking around and then it just started. It kind of looks like nginx was not starting. I've added Diffie-Hellman parameters to increase security. The fist time you install/update, it will took some time (5-15 minutes) to generate the DH file, and then nginx gets executed.

Guys, just arrived from a long working trip (3 weeks away). I'll catch up the last messages and start responding the issues, ok?

Have you enabled the Destructive Mode on Settings>Unassigned Devices? It's a safeguard to avoid accidental lost of data. I'll try this in a couple of days when I do my monthly offsite backup. Worked OK last month. Just finished my montly backup with this, and it worked. It is a little different than I remember from last time though. There is no checkbox for running the script in the background, I assume because it always runs in the background now. Also, when I push the Mount button, it does mount and run the script, but the Mount button just sits there "spinning" until the script completes. Not sure that is expected behavior or not, or whether I would even consider it a bug, but it might be a little disconcerting if you aren't aware of what's happening. Once the script completes, the button does show the drive is mounted. My script doesn't take any action on the unmount, so that happens quickly. Don't know if it would also "spin" if the script did anything or not. It's designed that way. Imagine you accidentally hit Unmount while the script runs; it can do nothing, but can provoke some kind of corruption.

Thanks for your feedback. You're quite welcome!

If you're using Joe L. version, you don't. The reason is that the "mail" command used before unRAID 6 could interfere with the built-in Notification system. I've adapted the new system into preclear_disk and submit it here, but there's no response from Joe L. In the mean time, you can use bjp999 version of the script that's stored on my github: I uninstalled Preclear plugin and reinstalled using PLG link from first page, then uploaded the preclear_disk.sh you referenced in quoted text. Now it is offering to Preclear members of my array & cache disk? Something is not right. Are you using the 2015.09.28 version? If so, I just messed with some detection code, so it's possible that it broke something. I'll revert it soon.

I couldn't replicate this behaviour, using Chrome/FF/IE/Edge. Maybe you have an extension that is messing with the code anyhow. By the way, a 5 second interval before the status window opens is normal.

If you're using Joe L. version, you don't. The reason is that the "mail" command used before unRAID 6 could interfere with the built-in Notification system. I've adapted the new system into preclear_disk and submit it here, but there's no response from Joe L. In the mean time, you can use bjp999 version of the script that's stored on my github:

It will IF you use bjp999 version of preclear_disk. It has a switch to bypass all those "Yes" prompts, and this capability is recognised by the plugin. What happen is that with the "official" version of preclear_disk, the plugin only jumps the first prompt, and preclearing from an Areca card will prompt you a second time about not retrieving SMART data. Because of that, you will have a stuck "Type Yes" message with no means to circumvent that. The SMART data gathering is important to verify if sector reallocation took place, or if any attributes of the disk are failing. Because of that, it's advised to preclear from a SATA port on the motherboard or on a LSI/Marvell card.

Thanks hernandito. Those errors will be patched in the next release.

Guys, you have to send me the link.