gfjardim

Just updated my repository with code properly GPL'd. Good luck Dan.

You closed it. Fork my repo, remove my files, put yours, commit it an then send the PR.

I'm not threatening you, just making sure it's legally licensed to protect our community users in the case a third party make contributions to the code and later demand any rights over it. If I surrender my copyrights it will be in favour of all community. So I'm correcting an error, not making a new one.

Ok, you won. Let's make things right then. I still have all copyrights over the code and your license manifests are illegal, null and voided. Please remove them, submit your changes in a PR to my repository. I'll accept it, GPL it, an then you can fork it over your repo and continue the development. I'll deprecate my version when it's over.

As I said before, I did not criticize dlandon, just his decision. I know it's difficult to pick some code and start to fix it, and I do appreciate that effort. It's not about control the code, it's about to make things evolve forward, not sideways. I'm being selfish, I know, I wanted to pick the code debugged and start to improve it.[emoji41] Well, it's done and now I have to try to keep up. Now that you all know my idea about my last version, do you think it's valid to revert it back, iron the bugs out and add image mount? I would appreciate if you guys to join the effort.

Nmap was used to map NFS servers on the current network, so if you didn't include the NFS part of the code, it isn't necessary. As you took the 19.09 version of gfjardim as a basis for further development, I wonder which features of the newer gfjardim versions are no longer available in your newest version? gfjardim's change log: 2015.11.18 - Fix: better logging - Add: force unmount after 5 attempts 2015.09.28b - debug: debug version 2015.09.25 - Fix: minor fixes 2015.09.22b - Add: NFS share mount The NFS share mount was added to this version. I don't know why, but he was in the process of rearranging the code. As I looked through his latest version, I saw a lot of things that were broken. I extracted what I could use from that version. I chose not to use his 2015.11.18 version because I didn't want to troubleshoot half-written code and too much was not working. If anyone that was successful in using his latest version sees any feature I missed, let me know. This was because I was modularizing the code, so with little work we could map NFS shares and mount ISO or other images. It wasn't half-written, just had some bugs to iron out. I'm disappointed you took this step and forked an inferior version of the code. Now, when I resume the development, it will be more difficult to include any improvements you made. See, I don't blame you on moving ahead since I had some setbacks and didn't had the time to work on this. But this arbitrary choice of yours resulted in two codes that can't be reconciled without a lot of work.

You can support multiple kernels with one plg file, just need to check the unRAID version from /etc/unraid-version file and then use insmod to load the appropriate one.

But I need to confirm this to post a bug report. Can you please send me the output of that command?

I think it's a bug in the core of unRAID. If you didn't setup a time zone in the UI, it's still relevant.

Can you please post the result of this command: ls -lah /etc/localtime*

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!

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?

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, thank you ljm42 for your assistance, ljm42 !!!

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

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:

Thanks for your feedback, Frank1940! Today I've made real use of this plugin, because I haven't expanded the array in a while. I must say it has a breeze! ;D ;D

As user GK20 said once: The fact that they disappeared mean that after some data was written to those sectors (the second zeroing), the firmware tested the media surface and found it wasn't damaged at all, and no reallocation was needed. The disk appears to be healthy.

Testing the update right now.

I was not... somehow I missed the latest upgrade.... I have upgraded, but it still shows the issue. I assume its because I started the process on the older x.18 version. Do you think this is why? Thank you. I just updated to 2015.09.20 . I don't know if it will affect current or only future instances.