mifronte

Once I restore my cache drive prior to the move process. How can I ensure that this will not happen again in the future? It appears that with the split level of manual, there is no checking to ensure an entire folder can be moved unto a disk prior to moving the folder. I would have expected that I receive an error and no files in the folder have been moved. This way, I would add another empty disk to the server and rerun mover again.

Now I just need a recommendation as to the Linux commands to use as I move files back to the cache drive to reassemble the partially moved movie folders. I have set my share allocation method to most free.

Found the settings in the Share tab. Looked like I used to use High Water, and then changed it to Fill Up. I assume that folders would not be moved if there were not enough space for the entire folder. What should the setting be to ensure entire folders are moved? I have the policy at manual.

I keep my Blu-ray rips in folder format. The lastest mover process only moved the small files and not the large mts file. The reason being is that one of my disk is full ( the other disks have space, one is even empty). My disk writing policy is to not split folders across disks. I did not realized that this would create the problem with the mover deciding to move all the small files in each movie folder to one disk and then attempting to move the large mts file. Since my writing policy does not allow splitting folders across multiple disc, the mover errors out with not enough disk space. Of course this leaves me with incomplete movie folders. 1. With unRaid 6.6.6 where can I find the disk writing policy? I tried looking in Disk Settings, but that only has the thresholds. 2. Doesn't the mover check to ensure the entire folder can be moved to a disk before moving it if my policy is to not split folders across disks? 3. What is the cleanest way to restore the partially moved folders back to the cache drive to restore everything back prior to the move? 4. This used to work for several years, but I think I may have changed something in the writing policy a couple of version ago. What should it be and where can I set it (see #1)?

Can anyone make sense what is a stable version combination of the Unifi controller and firmware? I see that this docker container is now at controller version 5.6.37 and the latest Unifi firmware is 3.9.27. I am skeptical of the current 3.9.27 version since its thread on the Ubiquiti forum is at 18 pages which is a sign that lots of users are having problems. I am currently at controller version 5.6.30 and firmware version 3.9.3.7537. I am mostly concerned about iOS clients not reconnecting. Just wondering if it is safe to update my Unifi docker container to 5.6.37 and staying at firmware 3.9.3.7537 unless there is a more current stable firmware.

B&H Photo Video has the HGST 10TB Deskstar 7200 rpm NAS drive for $288. Is this a good drive for unRAID or is it too many eggs in one basket given its size (one drive failure is whole lot of data)?

Looks like following the Wiki article solved my disk problem. Nothing was in the lost+found folder so hopefully no corrupted files.

Diagostics attached. diagnostics-20180223-1732.zip I fould the Check Disk Filesytem wiki. Will try and follow the article.

I am encountering a lot of these errors on one of my disk as I try to move files off it: Feb 23 12:59:56 Beanstalk kernel: REISERFS error (device md18): vs-5150 search_by_key: invalid format found in block 420557987. Fsck? Feb 23 12:59:56 Beanstalk kernel: REISERFS error (device md18): vs-5150 search_by_key: invalid format found in block 420557987. Fsck? Feb 23 12:59:56 Beanstalk kernel: REISERFS error (device md18): vs-5150 search_by_key: invalid format found in block 420557987. Fsck? Feb 23 12:59:56 Beanstalk kernel: REISERFS error (device md18): vs-5150 search_by_key: invalid format found in block 420557987. Fsck? Using MC to move files and MC is reporting read errors. SMART is not reporting any disk problems. What should I do?

Does unRAID support hot swap? Can I just pop out a drive that is not in my array and is not mounted and pop in a new drive?

After 3 runs of preclear here is what the disk SMART attributes were doing: 0 sectors were pending re-allocation before the start of the preclear. 37 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 100 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 60 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 96 sectors are pending re-allocation at the end of the preclear, a change of 96 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. 1 sector is re-allocated at the end of the preclear, a change of 1 in the number of sectors re-allocated. Disk failed SMART extended self-test. Looks like a drive for the trash bin. I was thinking of doing a secure erase using ATA commands as specified here at the unRAID command line. Is that a good idea?

Well the disk completed its 3rd run of preclear and pending sector is back up to 60, but allocated sector count and uncorrectable are stable and hasn't change. I am getting a lot of read erros in the unRAID log. It appears there is an area on the disk that are giving read errors at around the 95% mark of the preclear post-read step. Anyone know where in the unRAID GUI can I just pull up the log entries for a disk? I remember once accidentally finding the feature, but now I can't seem to recall how I did it.

Has the preclear plugin been cleared to work with unRAID 6.4.1? I was under the impression that it was incompatible with the latest unRAID.

It doesn't. I am just saying at the time I initiated the batch file move, there was no indication that the disk was bad. Only after the batch move did the disk get flagged by unRAID. By that time, all the files had already been moved. I am sure one or more files may be corrupted as a result and I will not know which, but the worse is the corrupted files will just show up as an anomaly during the playback of a movie and I will just have to replace the corrupted movie from the original disc.

Since the data on the disk were all archived movies and my array was only 50% full, my guess is that the disk has not seen a write for 7 years. unRAID only flagged the disk when I started moving files to free the disk for other use. Otherwise the disk always showed up as healthy. Normally with a bad disk, I do replace it and rebuild the array, however in this case, the disk was flagged after I moved the files. I will run preclear a few more time and probably will not put it back into the array. Anyone know the commands to perform a secure erase or pre_clear takes care of it?

The disk just started the post-read of the 3rd preclear run and reallocated sector count is at 0, pending sector is at 0, uncorrectable is still at 7. At the end of the post-read of the 2nd run, the pending sector went up to as high as 138, but it looked like no sectors were remapped or marked uncorrectable. As of now the disk looks heathly as can be. I will wait toward the end of the 3rd run post-read to see if the pending sector goes back up, which could mean that part of the disk may be wacky. This is very odd since I would think if the pending sector count goes to 0, then reallocated or uncorrectable should go up, right?

Recently I was moving media files between my disks to consolidate and free up disks. This is when unRAID flagged one disk and it turned out it had developed 7 pending sectors (attribute 197). So after I moved all files off the disk I performed the extended SMART self-tests. It passed the the short offline SMART self-test, but failed the extended offline self-test with a read error. I ran the extended self-test again and again it failed with a read error at the exact same LBA. So I removed the disk from the array and started preclear_bjp.sh on it to fully test it. After the first run, the 7 pending sectors were moved to offline uncorrectable (attribute 198) and pending sector went down to 0 and reallocated sector count (attribute 5) remained at 0. UnRAID then showed the disk wiht the green thumb up. On the second run, pending sector went to 5 at the pre-read, dropped to 1 during post-read (with no changes in attribute 197 or 5) and is now at 28 at pending sector at 96% into the post-read of a 2TB disk. So the pending sector count is fluctuating, but the reallocated sector count remain unchanged at 0 and offline uncorrectable is constant at 7. So what is going on with this disk? Why is pending sector count increasing and decreasing, but reallocated count or offline uncorrectable not changing? Most importantly, should I trust this disk or trash it? Diagnostics attached and /dev/sdg is the troubled drive. diagnostics-20180220-1308.zip

I read somewhere that 48-bit LBA support is essential in supporting drives over 127GB. Since 48-bit LBA is in the SATA specs, larger than 2TB drives should work. Well I guess I will have to bite the bullet and purchase a couple of new drives greater than 2TB.

Upgraded from 6.4.0 to 6.4.1 with no problems. Server has been running for 2 days and 8 hrs. Well done!

Installed 6.4.1 and set VLAN interface to no IP for unRAID. Then configured docker with the appropriate network. Everything looks good. The UniFi docker container is in a separate VLAN and unRAID is not available in that VLAN. Complete segration achieved! Great job @bonienl! Now, just for curiosity, if I have another VLAN where I wanted to selectively have unRAID available, but with only certain shares and no other services, would that be feasible some time in the future? For example, if I have these shares on my unRAID server: Sales, Finance, Engineering, Executives. In the Sales VLAN, unRAID would be available with just the Sales share and so on for the other VLANs. The management web GUI would not be available nor any other services or ports. Kind of like having a Docker container that allow you to specify which SMB shares to expose and the permissions allowed. This way I can run multiple instances of the containers in their own VLAN. Why would I want to do this? Well I am just looking into the future where I become less trusting of all these "smart devices". So I can see having a VLAN where these devices are segregated from my main LAN, but I would give them access to just certain shares while unRAID is completely isolated. Kind of like a Docker container so that if for some reason the container is compromised, my unRAID server is still safe.

Would anyone know if my current system (see signature) will support 8TB drives? If not, what would be the largest drive that my current system supports beyond 2TB? Basically the primary SATA I will be using for unRAID array will be the onboard SATA ports and the two SuperMicro SAT2-MV8.

Just updated to unRAID 6.4.1 and reconfigured to use Docker on VLAN without IP being assigned to unRAID on the VLAN interface. Now my UniFi docker with ports opened to the Internet is isolated in its own VLAN properly without having to worry about unRAID also being available in the same Docker VLAN. Great job!

I see there's an update for this container. This will be the first time I upgrade using this container. Does this container retains all configurations and the UniFi controller will start without having to restore the configuration from backups? I assumed since the properties file is kept on the appdata, the answer would be yes. The last container I used, I would have to backup the configuration and restore it after every upgrades.

I am using my own self-signed certificate for SSL. Will this survive the upgrade or should I plan on reapplying my certificate? I believed I named my certificate file the same as the unRAID default and just overwrote the default unRAID certificate.

Just curious how does that works when you are running your pfSense in a VM on unRAID and have to reboot unRAID. Does that mean your entire network is down until you can get the pfSense VM up? Also if pfSense is your DHCP server, aren't you caught in the chicken and egg loop?