Frank1940

What version did you upgrade to? Version 6.2 beta series requires that the registration be verified on boot by accessing the unRAID server. (This is is to assure that if they release a beta version that can endanger data, unRAID can stop the system from booting.) You seem to having some issues with access the Internet from your unRAID server. Post up a diagnostics file if you can get to 'Tools', 'Diagnostics' icon.

You might be better served to do a manual upgrade. Here is a thread with instructions on how-to-do-it: http://lime-technology.com/forum/index.php?topic=39032.0 At the bottom of the first post, you will find a link to a upgrade WIKI that has even more information including solutions to about every problem which folks encountered in earlier upgrades. (The simpler your configuration is, the less likely you are to have a problem!) The most important instruction is make a backup of your current Flash Drive BEFORE you start!!!!!!!

Did you modify the preclear_disk.sh file to incorporate the change to work with Ver 6.2.X? You can find the command to do this modification in this post: http://lime-technology.com/forum/index.php?topic=39985.msg477756#msg477756 You use the second one (the one not in the quote). I know this now because I am just finishing up a 3Tb using the modified script using that second command line.

The reason why bit rot is not a major problem is that all of the drive manufacturers know that it occurs and they have error detecting and correcting algorithms that are suppose to check and correct it. If you look at the raw data read error rates, you would quickly realize that large hard drives are not practical EXCEPT for these algorithms... Are there conditions when they don't catch and correct an error? Absolutely, but since we don't have access to exactly what scheme is being used, it is impossible for us to know what conditions will allow an error to slip through. These failures are probably what most people call 'bit rot'. Obviously, if they detect but can't correct an error, the drive will report a read failure. (The manufacturer hopes that latter is the default and not the former for his algorithm!) As an aside, I can remember being exposed to extended error detection and correction schemes in Grad School almost fifty years ago. I never used it after that brief exposure and the state of the art is probably many times more advanced than it was back then...

I only (very) recently put 6.2 beta on my server. I did not have any issue pre-clearing the second parity disk I have just added to my array. The fix will need to wait until I add/replace one of the existing disks with a larger one. (Otherwise, I have no way to test the process. ) Whatever the fix might be, it must be backwards compatible with the older releases of unRAID. In the interim, you can type this command to "patch" the preclear_disk.sh command First change directory to the directory holding the preclear_disk.sh command. For most, it will be cd /boot then type (or copy from here and paste) the following: sed -i -e "s/print \$8 /print \$9 /" -e "s/sfdisk -R /blockdev --rereadpt /" preclear_disk.sh Your preclear disk script will be edited and should work with the two changes you mentioned. (actually, each occurs in two places, so there are a total of 4 lines changed) Joe L. Joe L. Shouldn't this command be: sed -i -e "s/print \$9 /print \$8 /" -e "s/sfdisk -R /blockdev --rereadpt /" preclear_disk.sh (It has been some forty years since I last used sed so I might be mistaken.... )

Found this after the completion of a two-cycle preclear. There was also no report in the /preclear_reports folder! (also note that in the RESULTS line that successfully is incorrectly spelled!) --> ATTENTION: Please take a look into the SMART report above for drive health issues. --> RESULT: Preclear finished succesfully. /usr/local/emhttp/plugins/preclear.disk.beta/script/preclear_disk.sh: line 1382: /boot/preclear_reports/preclear_report_WD-XXXXXXXXXXXXX_2016 .07.04-19:54:05.txt: Invalid argument root@Rose:/usr/local/emhttp# EDIT: It was late last night when I posted and I woke up in the middle of the night and realized that I had forgotten to post a lot of information!!! I am using the Preclear Disk beta and running unRAID 6.2-b23. I have also attached the Diagnostics file. rose-diagnostics-20160705-0659.zip

1. Computer boots showing bios alternatives (F2 & F10) 2. Computer shows the following message SYSLINUX 4.03 2010-10-22 EED Copyright © 1994-2010 H. Peter Anvin et al Error: No configuration file found No DEFAULT or UI configuration directive found! boot: Regards Jens IF no one else jumps in you may want to go to this WIKI: http://lime-technology.com/wiki/index.php/Upgrading_to_UnRAID_v6 Be sure to make a backup of your flash drive BEFORE you go any further!!!!!!! (Hopefully, you also followed LimeTech instructions to make a backup of your flash drive before you started.) There are some trouble shooting hints for the plugin in the third paragraph and you might find some help there. However, I suspect that you might be better served to reformat you flash drive and do an new install of unRAID 6.1.9. There are instructions on which configuration files you should copy over from the backup that Limetech recommended However, you will have to look for them if you have to use that backup that I told you to make since the plugin moved things around.

Describe what is happening as you go through the boot process. Are you seeing the boot choices screen and the notice that you are unpacking(?) bzimage and bzroot? If it is getting that far, you might want to run chkdsk on your flash drive.

I am not a real guru in Windows networking but I have been using them for about thirty years and they can be a real pain when there is a problem because every windows computer can be both a client and a server. But I suggest that you check EVERY computer and device on your network to see if any of them at assigned to the NASA workgroup/network and are sharing anything under that name that requires a login. It only takes one computer acting as a server to constitute a network.

I forgot to have you check one very important thing! Your statement that everything was working after an hour was the clue. Got to 'Settings', 'SMB' icon. Then click on the 'Workgroup Settings'. Now, set 'Local master browser:' to 'Yes'. The Local master browser is the DNS server for the SMB network. (It converts each computer name -- NASA --- to it current IP address.) Any Windows computer on the network can become the Local Master. Now SMB was designed back in the day when the 386 20MHx processor was the state of the art. So to reduce the overhead of networking, the election and polling of the network to establish the 'DNS' table was done every so many MINUTES! It can take up to an hour for everything to settle down and every computer that is powered on is identified and connected. One way to reduce this problem is to have one computer always be that Local Master. On an unRAID serviced network, things will run much smoother if your unRAID is that Local Master. Now for this to happen two things are basically required, First, you must allow your server to become the Local Master (See above) and, second, that server should be left on 24-7. There are ways to influence the election and MS has uses one of them by giving precedence to the latest version of Windows. So, if all things are equal, any Win 10 computer will end up as the Local Master. There is also a plugin called 'Dynamix Local Master' which will show which computer is currently the Local Master. ( https://lime-technology.com/forum/index.php?topic=36543.0 ) Look in the first post. If doing the above does keep your server as the Local Master, post back here and I will post up a file which will virtually guarantee it.

Do the Win 7 computers have any problems access your unRAID server? I have never used the Homegroup setup for my SMB network. I just set up a network that I call 'Home'. (Of course, I did this when I was running either Windows for Workgroups 3.1 or Win 95.) You might want to consider doing the same. As I recall, it really isn't that difficult. I can also feel your pain. Back when Vista was introduced I got a laptop (mostly for 'road' use--- emails, web access and notes trip reports) and I never did get it connected to my network at home. While having a connection to my network was never really essential, I can't tell you how many hours I spent troubleshooting and searching the web for a magic bullet to make it work. I finally gave the d@mn thing to one of my grandchildren...

Since you know how to do screen shots, let's go to 'Shares', left click on the 'Media' (in the 'Name' column). Now click on the 'SMB Security Settings' and get a screen shot of that screen. I am assuming that you are trying to access your shares with Windows Explorer. Did you map the share as a drive on Windows? Or are you getting to the share by using Windows Explorer and clicking on 'Network' and going from there? Is there another Computer that you can try to see if the problem still exists? (BTW, Windows 10 has has presented SMB issues with unRAID since its introduction but I thought things had settled down...) Your Windows 10 computer is not a 'work' laptop, is it? As I seem to recall, Windows can do some funny things if it thinks a password is going to be required. That is why you were asked to delete the credentials in the Windows Credential Manager.

Something is wrong! You said you had 7TB of Plex files on your server. You should be aware that the New Permissions script will change the permission and owners of EVERY file that is on your data disks. All 7 TB of them. I would expected it to take a few hours to finish...

Post up which Plex you are running and your diagnostics file (Go to 'Tools' and run 'Diagnostics') While you are waiting for a response, Go to 'Tools' and run the 'New Permissions' script. It may take a long time so let it finish. Then report back if it solved the problem. Are you familiar with the Linux/UNIX command line? If you are, there are some checks you can do from there that could be helpful.

johnnie.black ---- First, thanks for your reply! After reading this, am I correct in assuming that if I install the Preclear Disk Beta in a server running 6.2-beta from here: http://lime-technology.com/forum/index.php?topic=39985.510 That I don't need to install the preclear_disk.sh script? The reason that I am asking is that the disk I was using to test the Preclear plugins is now my second parity disk in my Test Bed server and I don't have a disk to experiment with at the present time.

You are not the only one. I am another person who would like a complete explanation of both Preclear Disk Plugin and Preclear Disk Beta Plugin and their dependencies on one coherent post. With regard to the code for the preclear_disk.sh script, I have actually seen TWO versions of this simple command line. Here is the other one: sed -i -e "s/print \$9 /print \$8 /" -e "s/sfdisk -R /blockdev --rereadpt /" preclear_disk.sh ($8 and $9 are in a different order) It would be nice if someone could clarify all of this in a simple post and have some direct link to it so that one is not force to search through a 48+ page thread to try to find it!

Any chance that you might consider adding 'Turbo Write' as an 'Tips and Tweaks' option for ver 6.1.9 and earlier? I know that it has been added to the beta series but it would be nice to have it available from the GUI for the stable versions. I also realize that it will not be in the "standard" place but anything is better than have to go to the CLI!

Some observations on Flow Control settings: First, if you look at my hardware listings for my two servers, you will note that they both have low power CPU's and an Intel Network card installed. The network cards were installed during the ver 6 beta program because of problems with playback of high data-rate BluRay ISO's. The Intel cards solved that playback problem but they introduced a new issue with a large number of dropped packets when playing back a BluRay ISO. Since this didn't cause a problem, I simply lived with the situation. The players I use are Netgear NTV550 media players and they are installed at each three different media centers throughout my home. (Apparently, the NTV550 flood the server with packet requests when playing high bit rate material!) Second, connecting everything together was (and remains) a logistical nightmare. The main switch is a 16-port Gb switch to which the router and its associated modem are connected. Both servers are also connected to this switch. One on the media centers is on the same floor as this router and it is connected directly to this switch. The other two media centers are on a different floor of the house. I managed to get a cat5 cable to a center location on that floor and I installed a 8-port Gb switch there. During construction, I did install a cat5 cable to the general areas where these media centers are. What I never realized at the time was that in a few short years everything in the media center would expect to have its own Internet connection! So the solution to that problem was to install 5-port 10/100 switches at each one and all of AV gear at that location is connected to it. (10/100 switches were much cheaper and most of the time, only one device will ever require at high data rate.) As you can see, one media center is on the same switch as both servers and the other two media centers are three switches away from either server. So the Tips and Tweaks plugin gets released and I installed on my Test Bed server to see how it worked. Wow, I thought as I looked at it and read the help files that were included with it. Plus, I had seen a post in another thread that said that turning off the Flow Control would solve the dropped packet problem. So I decided to test it. I did this by determine the number of packets received turning a timed fifteen minute segment of the same BluRay ISO. (I used the same segment for all of the tests.) With both Flow Control 'on' NIC Offloading 'on', the percentage of drops was 152% of the total packets received. With the Flow Control 'off' and NIC Offloading 'on', the percentage of drops was 1.96%. With both settings 'off', the percentage dropped to 1.48%. Wow, thought I. This looks like a no brainer. I next installed the new plugin on my Media server and set both Flow Control and NIC Offloading to 'off'. After a lunch, I went down to one of the other media centers to watch a movie. I picked a nice comedy that was contained in a BluRay ISO. The studio logo had not finished before the video playback stalled and proceeded in 'slooow moootion'. I thought perhaps it was an anomaly. I stopped the playback and restarted. Same thing. Tried another movie, same thing. I ran up the stairs to change both setting back to 'on'. The problem was gone. To make a long story short, it appears that if you go through more than ONE switch, you could have problem with playback if you turn the Flow Control and NIC Offloading 'off'. One point I want to make at this juncture is that you may want to tone down your recommendation about turning these two parameters 'off' and suggest that issues can arise in networks that have any complexity in their makeup. If one wishes to experiment to be sure to test with high data-rate material on all of the end points to make sure that problems are not being introduced!

I don't know if you will get a response from bonienl or not. S3 sleep is/has been a source of problems for the past few years. Some people have absolutely not problems using it and other have absolutely no luck! One thing, I do recall from a few years back is that the MB often has a part in any problems. You should check to see if your MB has a BIOS update. Google your MB and s3 problems. Go to the manufacturer's website and download all manuals, search his forums. Read those manuals and see if you have the BIOS set up correctly. Try posting your problem in a separate thread in the User Customization portion of this forum. A separate thread (properly titled) will focus on YOUR problem and is much more likely to be seen by someone who can help.

I got this one a couple of weeks ago. Works fine in my Media Server and was plug-n-play. Only caution is that the chip set has had issues in the past with virtualization.

Well, one reason is if you use NFS. Whenever I have setup a device to use NFS (although the reason to do so is much reduced with the more recent versions of SAMBA), I have had to use the server's IP address to setup the mount point. If there is a way to do it without having that IP address, I am not aware of it... I have the IP address. I just assign it in my router instead of in unRAID. unRAID used DHCP to get the assigned IP from the router. It is always the same, known IP because my router has that specific IP address reserved for the MAC address of my unRAID server. Same for all of my other devices. They all use DHCP but they all have known, unchanging IP addresses because I set them up in my router. Everything managed in one place but everything has a known, unchanging IP address. True, you can do that. On my old cheap router (pre 2010), there is a table for up to eight reservations. (I have 15 addresses currently assigned on my router via DHCP and that does not include the two servers!) Of course, you have to know the MAC address. I know that the Network Settings page for unRAID servers has that information but then you have to explain to how to find both that address, the current IP address of the server that was assigned through DHCP and how to find the proper place in the router settings to be able to make the proper entries. Either way will work, you make your choice. Perhaps, you would like to write up an explanation of how to do the reservation method in any user's router that will be easy for the neophyte to follow?

Well, one reason is if you use NFS. Whenever I have setup a device to use NFS (although the reason to do so is much reduced with the more recent versions of SAMBA), I have had to use the server's IP address to setup the mount point. If there is a way to do it without having that IP address, I am not aware of it...

In the "Use static IPs" section, I would suggest setting the IP address in the upper end of the range. The reason being is that not all ( if any) of the cheaper routers keep track of static IP addresses. Many of them depend on the user to enter the appropriate IP address in a reservation table on the router. If the static IP address is at the bottom of the range, then the router may assign that address to some new device that requests an IP address via DHCP. (There was a fellow who had this happen a while back and I only suceeded in helping him when I noticed that there were no DHCP requests in his log file. He had used an address of 192.168.1.12 and something was coming on line and grabbing that address. He can tell you that two devices with the same IP address don't coexist peaceably!) I think this problem may be a much bigger issue as more and more wireless devices starting using the Internet (Internet of Things). I know when My kids and Grandkids arrive at my house, the first thing they do is turn on the wireless access point and my network suddenly acquires another half dozen or so devices (phones, tablets, laptops, etc.) Plus, every AV and video device in my house now wants to be connected. I can wait until my refrigerator and door bell want to connect... Going to the high end of the range, means that you have two hundred plus devices that connect before you get into address conflict trouble and most of the cheaper routers will choke trying to handle that many devices simultaneously. (I have a friend who was an IT guy at a High School and he said that 50 active connections was about the limit.)

Try this: Run the make_bootable script/batch file If in Windows XP, double-click make_bootable (make_bootable.bat). It should open a DOS window, and run syslinux.exe. If in Windows 7 or later, right-click on make_bootable (make_bootable.bat) and select Run as Administrator. If using a Mac, double-click the file make_bootable_mac and enter your admin password when prompted. Note: during the process of running this script, the flash device may seem to disappear and reappear. I surmise you will also have to run as Administrator on Win10. EDIT: It has been a long time since I did this but I seem to remember that you do have to hit the 'Enter' key at least one time in the DOS window.

I would be believing what the kernel is telling you until you have more substantial evidence that that assumption is wrong! What I suspect is happening is that you have a problem with the bonding of the CPU cooler to the CPU chip. Perhaps it is old/misapplied heat sink compound or a loose heat sink. You should also check that CPU cooling fan is running.