mifronte

Why not just create a "Staging" share and set it to cache only ( mover will not touch files in a cache only share ) then after your QC process move it to a share that mover will put onto the array when it runs? Seems better than having an option to disable mover that only a handfull of users will need/want to use. Having a separate share means users and software must be reconfigured when something moves from staging to array. Disabling mover works better because everything shows up in the same share regardless if it is in the array or on cache. Don't forget, the option to disable mover is there prior to V6. So technically, instead of a feature request, I should be submitting a bug report.

Please add the ability to disable the mover scheduler so that it does not automatically move files and folders from the cache drive to the array automatically. This is not the same as disabling the mover function. I would like the ability to execute the mover on demand only and not have it run automatically. Prior to version 6, the mover can be prevented from automatically running by scheduling a fictitious date like annually on Feb 30. This ability has been removed in V6.

I missed the voting because I don't come to the forum too often since unRAID never gives me problem. However, I have used Spin Up Groups since my very first unRAID server. Spin up groups elminate lag and timeouts from application when the pause for disks to spin up takes too long. If it wasn't for Spin Up Groups, I would have never gone beyond the trial license since the delay was a deal breaker and having the disks constantly spinning was also a deal breaker.

Just installed the Unassigned Devices plugin. Very slick, however, for my needs, it is too much dependency to worry about when it comes to upgrading. I managed to correct my mount command. It turned out unRAID V6 changes the namings in the /dev/disk/by-id.

Are plugins the recommended way to extend unRAID? I have to read up in plugins vs Dockers. I still don't know the difference between the two and which would be the preferred way.

Now that I have my server running on unRAID V6.0.1, one issue that does not seem to work is mounting and sharing a non-assigned device. In V5.0.5 I would have these commands in my go script: mkdir -p /mnt/ext_disk1 mount -rw -o noatime,nodiratime -t reiserfs /dev/disk/by-id/scsi-SATA_WDC_WD15EARS-00_WD-WCAYY0239185-part1 /mnt/ext_disk1 hdparm -S 242 /dev/disk/by-id/scsi-SATA_WDC_WD15EARS-00_WD-WCAYY0239185 I would also have the share defined in smb-extra.conf file as follows: [Public] path = /mnt/ext_disk1 comment = Public Share browseable = yes read only = no guest ok = yes writeable = yes create mask = 0666 directory mask = 0777 force user = nobody force group = users However, on V6.0.1, when I access the share I don't see any of my files. I look at /mnt/ext_disk1 and the uid and gid is 0 and not 99/100 if that matters. Note: I am not fluent in Linux, but is comfortable with CLI.

Reducing the number of connected devices down to 25 did the trick! Looks like my array is back online under V6.0.1 with the cache pool working. Thanks for all the help. Now you will probably see a few threads with some minor issues to iron out.

Where can I request the feature to disable the mover? In the previous version, I would set it to run on a fictitious date. Why do I need to disable the mover and still need cache shares? So that I can control when to move cached items after a manual QC process. So for example, if I have a new spreadsheet I am automating, I want it to appear in the array to normal users. Only when the spreadsheet has passed QC will I commit it to the array. Sometime the file (a spreadsheet or database file) contains a lot of test data that don't need to be on the array, so when I commit the file, I remove all the test data. Having on the cache drive is a great staging area because other users or devices can access beta files just like production files (all from the same share).

For my final attempt I kept everything as simple as possible and still the array will not start. Here are my steps (no other actions beyond what I listed) and attached is the latest log file. [*]Reformat flash drive. [*]Extract unRAID zip to flash. [*]Ran make_bootable.bat [*]edit ident.cfg changing Tower and WORKGROUP to my preferred names. [*]Copied Pro license key to config folder. [*]Verified all files and folders on flash is not marked as read only. [*]Safely disconnect USB flash from Windows. [*]Boot up unRAID 6.0.1 with newly prepared flash. [*]Assigned array devices and cache drive (not pool) to match my current V5.0.5 assignments. [*]Checked "Parity is already valid." and clicked start. [*]Status at bottom of page reads: Spinning up all drives...Start Arrary...Restart SMB... I don't know how much simpler I can make it and still the array will not start. I have 27 total devices connected as follows: 1 parity 1 cache drive 20 assigned to array 5 unassigned outside of array Another note: When I reboot, all my assigned devices with the exception of the cache drive is gone. Guess I am stuck on unRAID V5.0.5 for now :'( beanstalk-syslog-20150825-0932.zip

I had power down the server and then powered it back up and so all the array devices, with the exception of the cache devices, were unassigned again. I then proceeded to reassign the array devices again, but this time, I edited the disk properties to remove the spin group, comment, and reset the spin down to the default. I also disabled spin group on the Disk Settings. After all that, the array will still not start. Attached is the latest log. Edit: I will try one last clean install tomorrow before throwing in the towel. This time I am just going to assign the devices and see if the array starts before changing any settings. beanstalk-syslog-20150825-0013.zip

Third time is NOT a charm This third time, I prep the flash as a brand new install. So the only thing on the flash are what is in the unRAID download. I only edited the ident.cfg to change Tower to my preferred server name. After booting, I went ahead and configured all my settings as follows: [*]Added users [*]Configured Date & Time [*]Edit Disk Settings to enable auto start, spin group, and modify Tunable to 600 [*]Edit Identification to add model information [*]Edit Global Shares settings enable user shares and cach disk [*]Assigned all devices and edit properties (spin group, comments) [*]Assigned cache device (cache drive and not pool) [*]Checked parity is valid and then start So server went Sping Up Disks...Start Array...Refresh SMB and then the webgui flashes and the array is still stopped. So I decided to Reboot and see what happens. The server came back up with all settings except for the array device assignments! It remembered the assigned cache device and that's it. All other settings like users, time & date, global shares settings were also persisted. I give up unless someone has a good idea what could be going wrong. Reverting back to 5.0.5. for now :'( Edit: The log file is after the reboot and I reassigned the devices again. This time I tried to configure a cache pool instead of a cache drive. Same result, the array refuses to start. beanstalk-syslog-20150824-2326.zip

The second go around, I had reformatted the flash and just did a clean install where I only migrated my files in /config/shares. So I recreated all my users and reassigned all drives to their proper slots. There must be something in one of the share cfg files. I just reformatted the flash again for a third go around. I even ran a check disk. I will now unzip unRAID 6.0.1 to the flash drive and see if a pristine install will get the array running. This means I will recreate all shares, settings, users, and disk assignments. BTW, the downloaded unRAID 6.0.1 zip file MD5 checksum matches with what is on the download page. I will report back to see if a pristine install will get the array up and running. BTW, I am using the latest Chrome browser on Windows 7 Ultimate if that matters.

Still no go The array just refuse to start. The status is Stopped Initial Configuration. I will now have to try a pristine clean install without any of my shares cfg files. I even checked the disk.cfg file for the "startState=" as specified in the upgrade guide troubleshooting. This is not funny any more.

So I decided to do a clean install and reassigns all my drives. Can someone confirm the following before I start the array? [*]All my drives are showing up as a new device (blue square). [*]The FS column for all my data drives are showing Auto. [*]Parity drive FS column is blank. So can I safely start the array? I am afarid that unRAID might start to format all my drives.

Would the fact that the SSDs do not have a valid partition table be the problem? The two for my cache pool had invalid partition tables since they were in a RAID 0 set for a Windows system. The third SSD is brand new. I just went into fdisk to properly create a primary Linux partion for each of the SSDs. I am contemplating just going with a clean install and reassigning all 20+ drives to keep it simple.

Yeah, I may have too much confidence in unRAID since it has been simple, trouble-free, and rock solid The good thing is that I have two licenses and so I always use the spare for upgrades or testing and never have to jeopardize my current production flash drive. All is well just as long as I don't muck with any array drives. unRAID V6 true technical workings are scattered all over the forum, especially in the beta threads, and so I never know if I am reading the definitive specs. The Wiki is too general. So I am left with just jumping in with two feet and hope the new webgui is very intuitive. I don't know why the array will not start and there is absolutely no logging activities from the moment I press Start.

HELP! So I plugged in the spare unRAID V6.0.1 flash drive (configured with my drive config files to upgrade instead of clean install) and booted up. In the process of unRAID loading, I accidentally press the IPMI Ctrl+Alt+Delete button. So I let unRAID boots again and it came up with the array stopped with a message "Unclean shutdown detected." next to the Stopped status. I went ahead and remove my cache drive and added my two new SSD drives to create a drive pool. Then I press start and the message goes: Spinning up all drives...Start Array...Refresh SMB Then the webgui flashes and the array is still showing as stopped. All my drives are green balls except the two new cache SSD drives. They are showing a blue square. Attached is my log file. Edit: The two SSDs are not actually new, they were a from a Windows machine that had them as a striped RAID 0 system disk. I figured I would used them as my cache pool and let unRAID format them. Is this a correct assumption? beanstalk-syslog-20150824-0019.zip

Thanks robj. I have decided to migrate instead of a clean install. May take the leap tonight since the spare flash drive is ready to go. My parity check just completed and I will read through the upgrade guide on last time to make sure I did not miss anything. One more question: Upgrading to version 5.0.5, I ran the permission command and so I would not have to run that command again. Is this correct?

I am currently running unRAID 5.0.5 with a Pro license. My hardware setup is in my signature. Since unRAID has been so stable, I have not had a need to keep up with recent developments since I upgraded from 4.7 (been so long, can't remember actual date). I have tried reading as much as I can and have my spare USB Flash configured for a clean install of unRAID 6.0.1. My current installation is simple with only uuMenu and the following packages: SMTP, iperf, ntfs-3g. I plan to reassign my drives (1 parity, 1 cache, 20 data) and recreate my users. Here are a few last questions I have: [*]Is it better to reassign drives and recreate users than to migrate my current configuration or it doesn't matter? [*]Am I correct that the cache pool slots count toward the 25 device limit? [*]I plan to have drives outside of the array, so with the Pro license, am I limited to the attached devices limit? If yes, is the limit 25? [*]Is KVM the preferred VM? [*]My E6500 does not support VT-d, so does that mean drives on the PCIe & PCI-x slots cannot be used to run Winows 7? Mainly the first 3 questions is my main concerns for upgrading so that I can plan my cache pool appropriately (may have to free up some slots). Updated: My apologies, I should have posted in the sticky upgrade thread. I tried removing this topic, but it appears I cannot.

Possibly the fastest flash drive if you have the need for the speed: Sandisk Extreme USB 3.0 64GB. The 16 GB is also at $16 and the 32Gb is at $20.

According to the 3 camels, this is the lowest prices for these Sandisk Ultra Fit USB flash drives on Amazon. Anyone knows which size is recommended for UnRaid 6?

I would like some inputs from owners who are running unRAID on the Supermicro X7SBE motherboard as to what is the RPM of their fans? I am using a Norco 4224 case with the 120mm fan backplane. Here are the RPM of my fans a CPU Temp of Low and Sys Temp of 37C: 3x Delta AFC1212DE-PWM 120mm (4-pin PWM) @ 2400 RPM 2x Nexus SP802512H-03PWM 80mm (4-pin PWM) @ 2200 RPM 1x CPU Fan @ 900 RPM The BIOS setting for the fan headers is set to 4-pin Workstation. The 4-pin Server bumps the fan RPM an additional 500 RPM. I would love to find a way to slow these fans down since my drives are never abover 32C in my cool basement.

Thanks. I did not know there was a newperms script. I will definitely give it a try. Edit: After running the newperms script on the non-array disk, everything appears to be working fine.

I just upgraded from unRAID 4.7 to 5.0.5. I have a disk that I have been mounting and sharing outside of the array. However, after the upgrade, the permissions may not be correct because I cannot access some directories or files. I think the New Permissions utility ignored this non-array disk. How can I perform the same function on this non-array disk? I have executed the following command on the disk to match that of the New Permissions utility: chown -R nobody:users . Now how would I recursively change the directories to drwxrwxrwx and the files to -rw-rw-rw-? I have also modified the smb-extra.conf file to to set the mask as follows: create mask = 0666 directory mask = 0777 Is this correct for a Public share?

Thanks Frank1940 for all your help. I was able to intall unMENU on my unRAID 5.0.5 server with no problems. I will have to read more into Dynamix before deciding whether to install it. I tried running the upgrade GUI tool in the unRAID web interface, but it appeared nothing was done. Maybe 5.0.5 already has the latest GUI? Good point on the UPS. I just take it for granted because my local utility has been so reliable (1 outage in 17 years due to a car crashing into the junction box).