Leaderboard

I'm making good progress on the next version but I'd like to get your help in populating a collection of drive models. I currently have details on over 300 Western Digital & Seagate drives 1TB and larger along with a few scattered ones to complete my own personal set. The time consuming part is finding the model numbers and a image representation of that drive to display instead of a default/generic drive image. If you'd like to help and to ensure your run is more pleasant, please run the attached "diskmodels.sh" script. What it does is to send the drive models of the drives you have connected to a web site app and it'll return either it was added, previously added, or contains unexpected characters. I've spent the past 4 days working on the drive model database and I'd rather work on the website code for now so any help on getting models for non-Seagate/non-WD or old no-longer-sold drives in use will help. If the diskmodel.sh execution of "lshw" seems to be running very slow (more than a couple seconds), spin up your hard drives. The drive information list contains the model number, along with interface, RPM, and cache size if known. The rest of the drive details (not displayed yet in the images) is fetched from the OS itself. To Do: Display full controller information Display full drive information including which port it's hooked to on the controller Perform bandwidth tests on a controller using one and more drives Perform speed testing on one or more drives, allowing 1 drive per controller to be tested at the same time Display speed results in a graph with optional historical graph comparison from past runs to see if the drive is performing worse over time Display a heat map of the drive and hopefully a heat map of the drive by platter I'm developing this on an UNRAID server running a Lucee (ColdFusion app server) self-contained install and will see about porting it to PHP in the RC phase. I've been coding in ColdFusion since 1998 so I can develop code fast but I haven't done much development of new PHP code, just modifying existing apps. In the plugin app itself on the UNRAID GUI, the user will have the option to enable/disable the Lucee server as the server itself will use up to 256MB of RAM in addition to however much file space the app server takes - so it won't run on a system with less than 2 GB of available RAM (1.25GB of that is for the speed testing itself). I'm pretty excited about this project. It seems like there's nothing else out there like it. The closest thing was an old text-only app. Attached are screen shots of my two UNRAID systems listing the controllers & the drives attached to those controllers. diskmodels.sh

I agree. One of the main reasons I continue with it is because it is so damn useful to me. I keep a disk mounted to do daily backups (using a scheduled User Scripts script) and I have USB drives I plug in to create on and off site backups. Quite nice to just plug in a USB drive and have it fire off a script to do a backup and then let me know with a notification it is done. I know a lot of people are mounting UD disks for VMs and Docker use. I don't do that, but I can see the value of UD in that case. I won't abandon UD, but eventually I expect LT will have pick up the UD functionality and include it in unRAID. It has become a "must have" plugin. I finally got to that point with the powerdown script. It was becoming very difficult for me to keep up with the changes, and it was time for LT to clean up the powerdown process. They did it and it works much better than the powerdown plugin.

Not looking at the readme, but you can't do that. Every additional folder requires an additional mount point. IE: Add another volume mount mapped to the additional host mount.

With your permission we'd be happy to integrate into 'webGui'. You can still work on it if you wish by submitting Pull Requests against our code base on github.

Honestly, ever since @limetech made the decision to base licensing on all attached devices instead of assigned array devices, it became their responsibility to properly manage unassigned devices. I think it's very unfair to @dlandon to expect him to support UD at all. I suspect the only reason he does is the overwhelming need, but I would totally understand if he decided to just abandon it so limetech HAS to pick up the slack. This has become one of the core functions of unraid. It doesn't belong in community support, it belongs in limetech's realm.

Better?

Adding this to the format dialog: Couldn't be any clearer than that. It's not a matter of disagreeing. I think the feature would be useful, just not in the UD plugin.

When I said it was not worth my time, I meant that I invest what little spare time I have to features that are useful to a wider crowd. I don't have the time to invest in features that a small group of users will benefit from when there are other answers - i.e. proper backups. I do not get paid for any of this work, and I get no benefit from the license fee that LT charges. If there is a shortcoming in unRAID, then you should be lobbying LT for the feature. I'm sorry you feel that I didn't take your ideas seriously, but trying to sell me on this with all your reasoning does not change the fact that I just don't think it appropriate for UD to format disks for the array.

Not quite fair to blame this on @dlandon is it? As you are aware he makes this plugin on his free time and it's up to him to decide if it's worth it or not to implement. He is after all not paid to develop this plugin. Better to push this on LT to make it simpler if you mean this is an important feature, in my opinion.

It should solve the audio issue too, I used this very method with I used to use a hdmi switcher, if it wasn't on the right input it used to default to 1024x768 as you described.

I think I fixed it. Check also if you have any python packages in /boot/config/plugins/NerdPack/packages/6.4/

This appears to be an edge case that would not be worth the investment in time on my part to implement. I feel that it is outside the scope of what UD was designed to do. Using UD is not the proper way to prepare a disk for the array. I could see a lot of support come up when users try to perform the odd gyrations you describe here. Your process might be fine for you, but it is rife with potential errors by the casual user. When replacing a disk in unRAID, just install it and let it rebuild. Why use unRAID and then don't trust it to rebuild a disk? Use dual parity for a multiple disk failure situation. If you need this capability desperately, ask LT to add a feature to format a new disk not in the array to be array compatible.

Not released yet for Ubuntu. https://launchpad.net/~stebbins/+archive/ubuntu/handbrake-releases

This has been asked before. Why would someone want to format a disk in UD for the array? This is not what UD was designed to do.

That is the driver for Westmere CPUs, as long as turbo boost is enable in the bios it should work despite the turbo frequency not being displayed, you can check this thread for a way to confirm:

I've issued an update to UD that turns the diskinfo from preclear back on. When the preclear plugin is installed, there is a background daemon that preclear uses for disk information to cut down on disk queries. UD also takes advantage of this diskinfo. This was done because a preclearing operation can appear hung, or stop completely when there is too much disk query activity on the preclearing disk. UD now checks to be sure the rc.diskinfo daemon is running before using the diskinfo.json file for disk status. If the daemon is not running the diskinfo.json file will not be current and shouldn't be relied on. There were also a duplicate mounting attempt on ntfs disks with issues like an unclean shutdown, or a hibernated disk. The ntfs mount is successful in these cases, but the disks will be mounted as read only. This has apparently changed in the latest release of Linux and/or the ntfs driver. In the past when there was an error from these situations, the disk would not be mounted and UD would have to mount the disk read only. UD now checks that the disk is actually mounted and won't try another mount unless it actually did not mount. Let me know if you have any issues with mounting ntfs disks.

The backup finished. But then it went through and was trying to delete the old dated backup sets. This is where it was when you grabbed the diagnostics: rm -rf /mnt/user/backups/appdata_backup/[email protected] Assuming that this backup set was ~200Gig all small files, this will take a while to complete. However, the command itself will not impact anything else in unRaid. There is nothing that I see in the diagnostics as to why your system was running at a snail's crawl. (And your CPU is better than mine) One or two users have issues with the standard bash commands used by the backup script (rsync & rm). No specific cause has been found, and any issue with those commands is completely out of my control. The best I can offer is to install the tips & tweaks plugin and try this:

I think I've sorted it out. I'm sure it was caused from my mounting an already mounted disk. The result I am getting from the unclean shutdown disk mount is: Jul 08 15:02:51 Mount failed with error: The disk contains an unclean file system (0, 0). Metadata kept in Windows cache, refused to mount. Falling back to read-only mount because the NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting.) I always assumed in UD that this was a mount failure, but in fact the mount is successful and the disk is mounted read only. I then tried to mount the device read only, but it was already mounted. It seems that the ntfs mount has changed and a disk in this situation is now mounted read only, when in the past it would fail to mount with this condition and I then mounted it read only myself. I'll post an update to UD that will fix this situation.

Wait for next RC of unRAID 6.4...

So, this stumped me for hours, and after reading over my troubleshooting steps I came to the conclusion I hadn't gone through my BIOS settings after adding a new CPU. Everything looked correct, but I had one setting that I thought was suspicious, since I was able to virtualize without any issue with a single cpu. It turns out with 2 CPU's it actually complicates the whole IOMMU paths, so this setting is crucial to have enabled. On my motherboard it was under advanced settings, and under PCI EX "Single Root IO virtualization support" (SR-IOV) Hopefully if anyone runs into this issue they can find this being their solution.

You shouldn't need to remove it. But its actually easy. Stop the service. Delete the img file. Start the service. Apps Tab, Previous Apps, reinstall your apps. They'll all come up with the exact same settings as before, so you just need to hit apply. After the downloads are done your finished. But, I'm out of ideas otherwise... (Not a plex guy)

Actually, I don't see any evidence in the lspci output that there's even an ethernet controller installed. Is it disabled in the BIOS?

You have this error in your syslog. I am not quite sure what the actual problem is but I would start by pulling the Flash Drive and running chkldsk on it. Jul 8 17:24:34 Tower kernel: read_file: error 2 opening /boot/config/super.dat Jul 8 17:24:34 Tower kernel: md: could not read superblock from /boot/config/super.dat I also could not find any evidence that any Ethernet driver had been loaded in the syslog. The ifconfig.txt and ethtool.txt seem to support this observation. I am hoping at this point, some Guru with more knowledge then I have will jump in and provide some insight.

You really need to post up your diagnostics file. You can do this from the monitor console by typing diagnostics after logging in. The file will be saved in the logs folder on the Flash Drive.

Select the memtst option from the boot menu (with a monitor and keyboard) and let that run for twenty four hours.

First, I assume that you have a monitor/keyboard attached to the server. so type diagnostics on the command prompt. That will write the diagnostics file to the logs directory of the Flash Drive. Upload that with your next post. Second, have you look at the stickies at the beginning of this sub-forum? That are a lot of solutions to similar problems to be found there.