tazman

Happy to report that the upgrade using Tools.Update OS worked this time. Thanks, JorgeB!

Thanks, JorgeB, I copied the root folder files from the 6.12.8 backup to the USB stick and ran make_bootable.bat. Server booted and it looks ok. What to do now with 6.12.9? Should I try the upgrade again from the GUI or is there a better way? USB Tool is the Creator from here? https://unraid.net/getting-started

Update from 6.12.8 failed. The USB stick will not boot anymore. First time I used the new update dialog. USB stick is still readable and I was able to make a backup without read errors. Looking into this now. Tipps welcome. Thanks!

Just found this statement: My understanding is that the next WD release, the 24TB (Gold and U/star), will be the largest they'll be able to make in CMR format so that may indeed be the one to have in future years. Source: https://www.backblaze.com/blog/backblaze-drive-stats-for-q3-2023/ (in the comment section)

I tried one which immediately failed. The RMA replacement is running fine since 4 years. I have not re-considered them and stick to WD reds instead.

Hi, With "best" I mean: this size will be available by all providers (=competition) and has the chance of being the most cost-effective in cents/GB for the next couple of years and has a technology that is reliable and proven. When I started with unRAID back in 2011 2TB drives were the only choice. Relatively soon, 4TB drives became the standard and were the ones with the lowest cost per GB until now. I mostly use WD reds now after HGST was bought by them with some bad experiences with Seagate and Toshiba in-between. At the moment it seems that higher capacities start to challenge the 4TB prices. WD currently has an attractive Black Friday deal for their 18TB Pros. I am wondering if it is the time to swap out the drives starting with my two parity drives. But is 18TB the "right" size to adopt as the new standard? I know that unRAID does not care about drive size as long as the parities are the biggest ones. But with so many new large capacity drives that add yet another TB or two on top I don't want to constantly swap out the parity drives. So I wonder what the your opinion is about: 1. What hard disk sizes are, from a technology perspective, the most reliable ones? I always thought that doubles 2-4-8-16 would be a a logic. 2. Which disk size has the potential to become the new "lowest cost per TB" leader for the next years? I researched this but could not find any clear answers. BackBlaze thinks that the cost will come down to 1ct/GB in 2025: https://www.tomshardware.com/news/backblaze-expects-one-cent-per-gb-hdds-by-2025. They seem to use 16TB drives now but the reports says that the 1ct will be achieved by the 22/24TB drives. 24 would be doubles again. Interim sizes like 16, 18 or 20 would be shorter-lived in-betweens!? So wait for the 24TB? The prospect of parity checks/rebuilds taking 3.5 days with 24TB (my 4TB take 14 hours) scares me a bit. Overall, the WD Reds Plus 12TB seems to be the current non-deal sweet spot and every provider has 12TB drives. So is 12TB a good size to go for now? Appreciate you insights and wisdom. Thanks! Tazman

Dear all, I have .nfo files excluded, as they change frequently. So the Export correctly states that files are skipped: Finished - exported 216628 files, skipped 122 files. Duration: 00:01:59 Yet, upon export, the syslog is flooded with error messages like: Aug 30 17:08:47 SS bunker: error: no export of file: /mnt/disk8/Movies/Brooklyn (2015)/movie.nfo Yes, Mr. Fileintegrity, .nfos should not be exported as configured. Why do you complain about this? It was so bad that the syslog partition (standard size: 128mb) overflowed and nothing was logged anymore. Yet, unraid continued to run like a charm (!!!!). The error message is only generated for excluded files (ie. *.nfo) , not folders. Bug? Please fix! Feature? Please make it configurable! Thanks! The bigger issue at hand seems to be that files handled by Mover are not recognized as modified. Like .nfo files when they are touched by Sonar when a new episode is added. So excluding them is my attempt to prevent me getting flooded by bunker verify warnings. Now, my syslog gets flooded. Can't avoid the flood. Maybe it's global warming! Ultimately, this makes the plugin less useful as you constantly need to remember to run manual Builds and Exports. Could this be schedulable? Tazman

Triple Parity

+1. I am running 22 mostly 4TB data drives with overall 82T I also experienced dual drive failure for the second time recently. Surely a nail biting and nerve wrecking experience I do not want to go through again.

Hi Vr2Io, thanks, they are red when a drive is in only. The headers are clean. I just replaced the backplane with most problems (some of the slots were not working, the drives in the other two with a red middle LED are all ok) with a one from Supermicro that I had lying around and so far, the preclears are going good. I am also hanging towards your suspicion of a board failure as power and the SATA cables are working ok now. Best regards, Thomas

Dear all, I have six ICYDOCK 5-3 MB455SPF bays of which 3 show a red HDD light in the middle bay. Red indicates a failed drive. However... According to the manual, the HDD red light needs to be signalled by the host adapter via a specific FAIL connector/cable which is not connected. So it should not be possible to be red. Moving a drive from one slot to another ie. a drive that shows green in one slot into the red one changes nothing. Removing the fan does not change anything. Switching the SATA cable does not change anything. The drives work as expected. The slot is just red, whatsoever. I could find anything online that explains this. Has anybody seen this and can advise what the middle HDD light = red means or has a tipp what I could try to debug this further? Thanks! Best regards, Thomas

Upgrade from 6.7.2 -> 6.8.3 without problems.

The stability and functionality make me confident about unRAID today, the responsiveness and great support of Tom, the developer team and the community make me confident about unRAID in the future. Simply said: thank you I keep close track of my hard disks and track the development of especially wear SMART values manually. It would great if unRAID would keep a log of the SMART history for me, e.g. by polling a drive once a day (customizable) and keeping track of changes.

I have two disks with 1 and 2 files that fail to export. I understand that an export failure is due to the fact that no hash has been generated for them. I (re)Build both drive but the error still persists. Here is one example: xfs_repair (without -n) did not do anything either. All files and can be read and copied without problems and are identical to their sources. Note, though, that the folder has actually a whopping 25000+ file in it. When I ran into this problem I had thousands of export errors on several drives. After Build, I am down to those three. I also noticed that the number of files that were reported as having an export error was not identical to the ones that are reported as added when I run the Build. Added is higher. I would have expected it to be the same. E.g. Export = cannot find the hash <=> Build = adding the hash. Appreciate your advice how to judge this and which measure to take to either assess more or rectify. Thanks!

The extended SMART test on the partity 2 drive completed without errors. I then restarted the rebuild and it continued with the normal speed. The read speeds which showed around 4.5MB in the picture above increased to ~75 and the write speed to ~65. After the rebuild was complete I ran DiskSpeed again and it did complete for all drives. Although I obviously like the fact, that it fixed itself, I will keep Parity 2 on close watch.