Will badblocks help me identify if it's a drive problem or PSU/electronics problem?

I doubt it, it will just identify if it is working correctly.  Only a manufacturer's diagnostic disk could possibly tell you where the issue lies if random errors occur, and even that might only work in their tester.  (in the factory)

My new PSU should arrive any day. After installing, should I rerun the preclear on disk2? If it ends up with zero pending sectors, then maybe we've determined it was a bad PSU. If it still has pending sectors, then I get an RMA and swap it out with my spare.

 

Then, before I try rebuilding, I need to deal with the pending sectors of disk4.

I would try

dd if=/dev/md4 of=/dev/null bs=16K oflag=noerror

 

It will read the entire contents of disk4 and send it to /dev/null.    If my understanding of unRAID is correct, it should when it encounters an unreadable sector from the OS reconstruct the contents of the sector and pass it onward to the "dd" command and ALSO write the reconstructed sector back to the disk allowing the SMART firmware to re-allocate it.    That "should" result in the pending sectors being handled.  (You can get a new SMART report afterwords to verify what it did)

 

As long as the "pending" sectors on the two disks are not on the exact same sector, this should fix things.  Since it is a read-only operation, it cannot do too much harm. (unless you mis-type the "dd"command)

 

Joe L.

I would try

dd if=/dev/md4 of=/dev/null bs=16K oflag=noerror

 

It will read the entire contents of disk4 and send it to /dev/null.    If my understanding of unRAID is correct, it should when it encounters an unreadable sector from the OS reconstruct the contents of the sector and pass it onward to the "dd" command and ALSO write the reconstructed sector back to the disk allowing the SMART firmware to re-allocate it.    That "should" result in the pending sectors being handled.  (You can get a new SMART report afterwords to verify what it did)

 

As long as the "pending" sectors on the two disks are not on the exact same sector, this should fix things.  Since it is a read-only operation, it cannot do too much harm. (unless you mis-type the "dd"command)

 

Joe L.

 

Can I do this while I am still copying files (backing up) from disk2 and disk4? Or should I wait, until there is no activity on these drives?

I would try

dd if=/dev/md4 of=/dev/null bs=16K oflag=noerror

 

It will read the entire contents of disk4 and send it to /dev/null.    If my understanding of unRAID is correct, it should when it encounters an unreadable sector from the OS reconstruct the contents of the sector and pass it onward to the "dd" command and ALSO write the reconstructed sector back to the disk allowing the SMART firmware to re-allocate it.    That "should" result in the pending sectors being handled.  (You can get a new SMART report afterwords to verify what it did)

 

As long as the "pending" sectors on the two disks are not on the exact same sector, this should fix things.  Since it is a read-only operation, it cannot do too much harm. (unless you mis-type the "dd"command)

 

Joe L.

 

Can I do this while I am still copying files (backing up) from disk2 and disk4? Or should I wait, until there is no activity on these drives?

You do not have to wait, although having disk4 being read by two different processes will slow both down as the disk heads have to keep seeking from track to track.

 

Joe L.

Unless I'm not following correctly. you can't do that dd command right now because disk2 isn't assigned to the array and is just being simulated. That might work on an array with all the disks in place but it won't work on a simulated disk. There are no bad sectors on a simulated disk.

 

My understanding is that presently you have the following.

- disk2 is not assigned to the array and you are preclearing it. It keeps showing bad sectors.

- disk4 has a bad sector.

- you are running the array with disk2 missing and it is being simulated.

- you have a brand new drive that hasn't been touched yet.

 

If this is correct then I would do the following.

 

- Finish copying any data you want from disk2 and disk4.

- Install the new PS.

- Preclear the new drive so that you have a good preclear with no pending sectors.

- Replace disk2 with the new drive and let it rebuild.

 

If you can complete the above then we can evaluate what you should do next If necessary, address disk4 at this time.

 

This thread is jumping around so badly that it's no wonder you are confused. I'm confused just trying to follow all the conflicting advice.

 

Unless I'm not following correctly. you can't do that dd command right now because disk2 isn't assigned to the array and is just being simulated. That might work on an array with all the disks in place but it won't work on a simulated disk. There are no bad sectors on a simulated disk.

 

My understanding is that presently you have the following.

- disk2 is not assigned to the array and you are preclearing it. It keeps showing bad sectors.

- disk4 has a bad sector.

- you are running the array with disk2 missing and it is being simulated.

- you have a brand new drive that hasn't been touched yet.

 

If this is correct then I would do the following.

 

- Finish copying any data you want from disk2 and disk4.

- Install the new PS.

- Preclear the new drive so that you have a good preclear with no pending sectors.

- Replace disk2 with the new drive and let it rebuild.

 

If you can complete the above then we can evaluate what you should do next If necessary, address disk4 at this time.

 

This thread is jumping around so badly that it's no wonder you are confused. I'm confused just trying to follow all the conflicting advice.

 

Yes, I think you understand my present situation. I didn't think I could rebuild until both drives had no pending sectors.

Will badblocks help me identify if it's a drive problem or PSU/electronics problem?

I doubt it, it will just identify if it is working correctly.  Only a manufacturer's diagnostic disk could possibly tell you where the issue lies if random errors occur, and even that might only work in their tester.  (in the factory)

My new PSU should arrive any day. After installing, should I rerun the preclear on disk2? If it ends up with zero pending sectors, then maybe we've determined it was a bad PSU. If it still has pending sectors, then I get an RMA and swap it out with my spare.

 

Then, before I try rebuilding, I need to deal with the pending sectors of disk4.

I would try

dd if=/dev/md4 of=/dev/null bs=16K oflag=noerror

 

It will read the entire contents of disk4 and send it to /dev/null.    If my understanding of unRAID is correct, it should when it encounters an unreadable sector from the OS reconstruct the contents of the sector and pass it onward to the "dd" command and ALSO write the reconstructed sector back to the disk allowing the SMART firmware to re-allocate it.    That "should" result in the pending sectors being handled.  (You can get a new SMART report afterwords to verify what it did)

 

As long as the "pending" sectors on the two disks are not on the exact same sector, this should fix things.  Since it is a read-only operation, it cannot do too much harm. (unless you mis-type the "dd"command)

 

Joe L.

 

This plan is not possible with disk2 physical missing. You'll have to attempt to rebuild disk2 using disk4 as is. It may take a long time to work or could fail.

Yes, I think you understand my present situation. I didn't think I could rebuild until both drives had no pending sectors.

 

There are only 2 options.

 

#1 - Attempt to rebuild disk2 with the replacement drive and then address disk4 if the rebuild is successful. The 1 bad sector on disk4 might cause a file to be corrupted on disk2, it might cause the rebuilt to fail or it might just read the data and succeed without issue.

 

#2 - Pull all the data off disk2 and disk4 and then reset the array with those disks left unassigned. Install a "new" disk into each location once you have a hard drive you trust and at that point you can start using the disk for storing data again. The 1 bad sector showing on disk4 might mean that you will pull a corrupt file off disk4 or you might get an error copying a file from disk4 or it might succeed reading the sector and not cause an issue.

 

I'll start with option 1 and if that fails I'll go to option 2. I'm running out of space on all the other PCs attached to my network. And, I've avoided writing to the unRAID server. Would it mess up parity if I copied files from disk2 or disk4 to other trouble free drives in the array? I'm guessing that could be a problem with disk2 physically offline.

You can do that. It would work.

Things just keep going from bad to worse. I had to go out of town last night (Friday). The server was running and everything seemed to be fine, except disk2 was unassigned. However, after returning today, I could no longer access the server using the web interface, via a telnet session or even with a monitor plugged in. So the only thing I could think of trying was to power it down and restart the machine. Unfortunately, now I'm not sure if I can use my unRAID server and proceed as I had planned.

 

Here's a review of what's been going on since I first reported this problem on January 23rd: (For those of you that have been following this post and helping me out, feel free to skip this quoted section)

 

I had problems with performance, so I sought advice from this forum. Was advised to run SMART status reports on all my drives. Discovered disk4 had pending sectors and was told to unassign it, pre-clear it, and re-assign it and rebuild my array. This seemed to solve the problem. A follow up SMART status test on disk4 showed there were no more pending sectors and after reassigning disk4 and rebuilding my array, the performance was back to normal. Then, on February 5th the performance problems reappeared. I ran SMART status reports on all my drives and discovered that disk2 reported pending sectors and disk4 reported pending sectors again. Now the problem was a lot more complicated because I couldn't simply unmount/pre-clear 1 drive and rebuild my array. I have to deal with 2 problem drives and you can't rebuild the array with 2 bad drives. I maybe didn't help matters by unmounting disk2 and pre-clearing it. Anyhow, since disk4 was still assigned, I could access all the contents in my server because the data on disk2 could be emulated by parity and the other data disks.

 

I spent the next several days backing up all the files from disk2 and disk4 to other computers on my network. This was a challenge because all the spare drive space on my other computers didn't quite equal the amount of data on these two drives on my server. Each of these were 2 TB drives. I ended up burning several Blu-rays and DVDs to make sure all our precious family photos and videos were backed up. I also have a lot of music CDs and movies (DVD and Blu-rays), but since I have the original discs it's not a big deal. It's just a little bit of a hassle to re-rip those things.

 

When this problem first appeared I thought it could be a bad hard drive, but was told the drive was probably fine. During the 2nd episode, with 2 drives with pending sectors it was suggested that the problem with pending sectors could be caused by a failing power supply or some other hardware problem. It was recommended that I run memtest over night, which I assume would test my RAM for any errors. Since I hadn't backed everything up, I decided to wait on memtest until the backup was complete. In the mean time, I also decided to purchase a new 2TB hard drive and a new power supply. I figured if the drives were still fine after all was said and done, I'd have a spare or I could add it to my array and increase the server's storage space. Next, I planned to swap out the old PSU for my new 500W Corsair PSU and then pre-clear my new 2TB drive. Then I would swap out the unmounted disk2 (with pending sectors) and replace it with my new 2TB drive, and then re-assign the new drive and rebuild my array. If I was lucky, the rebuild would work even though there were pending sectors with disk4. Then I could try unmounting disk4 and then pre-clear it to remove any pending sectors and then reassign it and rebuild the array. Hopefully at this stage, I'd be back to normal. A functional server with all drives showing no pending sectors. Then finally, I would preclear the old disk2 and then add it to the array.

 

Now back to my current situation:

 

So, I powered down my server by flipping off the power supply's switch and unplugging the power cord. At that point, I decided to proceed with my previous plan. This is what I've done:

[*]Disconnected the existing power supply and installed the new power supply.

[*]Moved the disk2 drive (a Western Digital WD20EARX drive), that was in my 3rd slot, to the 7th slot in my case.

[*]Installed the new 2 TB drive (a Western Digital WD20EURS) in the 3rd slot where disk2 was located.

 

I was very careful to pay attention to all the previous connections and made sure the new power supply was plugged into the motherboard, drives, case fans, etc., etc. I connected a keyboard, monitor, the ethernet cable, my unRAID flash drive and flipped on the switch. The BIOS information appears on the screen and displayed the normal bootup information. The BIOS bootup info shows a listing of ports followed by the drive. When it gets to the 4th port, it displays an error:

 

Port 00: Hitachi ...                  2000 GB

Port 01: Hitachi ...                  2000 GB

Port 02: WDC WD20EURS ...  2000 GB

Port 03: Hitachi ...                  2000 GB

Port 04: Reset Port Error!!

Port 05: WDC WD10EACS ...  1000 GB

 

then some other information appears below this list and is followed by:

 

0    WDC WD10EACS ...          931 GB

 

Then, on the next screen, it shows:

 

HDD0: WDC WD20EARX ...    2000 GB

 

(the "..." is just serial numbers)

 

I can't figure out what's going on here. I'm assuming these port numbers correspond to the sata ports on my motherboard.

 

If that's the case:

Port 00 = my parity drive, which is connected to SATA1

Port 01 = disk1, which is connected to SATA2

Port 02 = disk2, which is connected to SATA3 (note: this is where I installed the new WD20EURS 2TB drive)

Port 03 = disk3, which is connected to SATA4

Port 04 = disk4, which is connected to SATA5 (note: this is displaying an error at the BIOS level)

Port 05 = disk5, which is connected to SATA6

 

Now that's the end of the list. The Bios doesn't list Port 06, Port 07, Port 08, etc.

 

I think what should be listed as Port 06, would be the drive that is located in my 7th slot and connected to SATA7 on my motherboard. This is the one that is listed as 0 WDC WD10EACs... 931 GB. So it is probably last drive in my array - disk6. The drive moved from the 3rd slot, which was disk2 in my array is the one getting listed on the following page as HDD0: WDC WD20EARX.

 

My motherboard, an ABIT AB9 Pro, has 9 SATA connectors. Labeled SATA1 thru SATA9. I was using 7 of these ports before this problem and when I added my new 2TB drive and moved the old one to a new slot, I am now using 8 SATA ports - SATA1 thru SATA8. The SATA ports are located in 3 different areas of my motherboard. A group of 6 (SATA1 - SATA6) are grouped together in 2 rows of 3 ports. This group is located near the lower right corner of the motherboard. The SATA7 port is located above the PCI and PCIe slots, closer to the CPU. And the ports for SATA8 and SATA9 are clumped together and located on the other side of the PCI/PCIe slots, closer to the bottom of the motherboard. There's also an eSATA1 port, that I have never tried using for anything.

 

The specifications for this motherboard say:

Serial ATA

- 6x SATA 3GB/s offered by Intel ICH8R supports Intel Matrix Storage Tech (AHCI & RAID 0/1/5/10)

- 2x SATA 3GB/s offered by JMicron JMB363 supports up to 0, 1, JBOD RAID function

- 2x SATA 3GB/s offered by Silicon Image 3132

 

Based I this, I think SATA1 - SATA6 use the Intel controller and are the ones displayed on the first screen as Port 00 - Port 05. Then SATA7 is shown below that, and it uses either the JMicron or Silicon Image controller and probably is listed a 0 and 1. Since only one is used (SATA7) it shows up as 0. And the last 2 ports (SATA8 and SATA9) are controlled by whichever 2 port controller is left. And since SATA8 is being used, it is showing up on the next screen as HDD0. If SATA9 were used, it would probably be listed as HDD1. I'm sure I could confirm this by swapping the cables around.

 

I did tried swapping the SATA cable from SATA4 to the disk drive located in my 7th slot. This is the one that was coming up in the BIOS as 0 WDC WD10EACS 931 GB. After that, all 6 of them, Port 00 thru Port 05, were listed. Port 04 no longer showed the error. So this leads me to believe that there is nothing wrong with the SATA port (SATA5) for Port 04 and the problem is with the Hitachi drive that was assigned to my array as Disk4.

 

So, I don't know how to proceed from here. How can I recover anything? I've already precleared disk2, which still has pending sectors. I have replaced it with a new drive, which hasn't been precleared or assigned to the array. Disk4 appears to be completely out of commission.

 

Does this malfunction of disk4 seem possible? This was a disk drive that had 1 pending sector. Based on the SMART status report, it was a healthy drive. It "passed", whatever that means. So why would it suddenly have this "Reset Port Error" on bootup? If I connect a different drive to that port, it works. I will contact Hitachi and ask for another RMA, but I'm not even sure how to report this as a defective drive.

 

How can I recover from this sort of thing, assuming I have everything backed up?

 

BTW, When I get to the "Lime Technology" menu that lists unRAID OS and Memtest86+, I highlighted the memtest and pressed enter. It does not run memtest, it just reboots the computer. Also, if I hit my DEL key to bring up the BIOS menu, I can't really navigate around very well. Only a few keys seem to work, F10, down arrow, left arrow, right arrow, Enter. It doesn't respond when I hit up arrow or Esc. So like I said, it's hard to navigate the BIOS menu. Maybe I have a defective keyboard. Unfortunately, it's the only wired keyboard I have in the house. That still doesn't explain why memtest won't run.

 

Any advice or help would be greatly appreciated. At this point, I'm pretty stressed out...

 

 

You'll need a working keyboard before further diagnosis can take place. The memtest also needs to run overnight. Try using only a single RAM stick or replace the current one.

Get rid of that old disk2. Pull the connections and leave it disconnected. Don't try to introduce a new SATA controller into the mix while you're having these other issues.

Thanks for the advice. I'll disconnect the old disk2 to remove an unnecessary variable at this time. I'll worry about trying to add it to the array after I have these more serious problems solved.

 

Still not sure what to do with disk4 now that it seems to be totally unresponsive.

 

I'm currently hunting down a replacement keyboard.

 

I finally got mdy hands on a working keyboard. I can now navigate the BIOS setup and double check that everything is set properly there.

 

However, I still can't run memtest.

 

When I select Memtest86+ from the menu, it still just restarts the computer.

 

I made sure the memtest file was located in the root directory of my flash drive. I also checked my syslinux.cfg file to make sure memtest is there (this is what is there):

 

default menu.c32

menu title Lime Technology LLC

prompt 0

timeout 50

label unRAID OS

  menu default

  kernel bzimage

  append initrd=bzroot

label Memtest86+

  kernel memtest

 

Still can't run memtest, so I thought maybe I need the latest version of memtest (I'm running unRAID v4.7) and the last time I upgraded unRAID from v4.6, I didn't update memtest or anything. The upgrade instruction seemed to say it wasn't necessary and that the AiO install just included the latest version. Anyhow, I decided to go to the memtest86+ website (www.memtest.org) and I downloaded the latest precompiled bootable binary (.gz) file. Then I extracted the memtest.bin file to the root directory of my flash drive. Then I booted up unRAID and after logging on, from the system console typed:

 

cd /boot

rm memtest

mv memtest.bin memtest

 

Then I restarted and tried running memtest from the Lime Technology menu again. Again, it just restarted my PC. Is there something I'm doing wrong here?

 

I'll try posting this question as a new thread because I don't want this one to keep jumping to so many different topics.

Just an idea regarding memory testing, if you have CD/DVD drive in the server you could boot from the UBCD, after setting your BIOS to boot from  CD, ( http://www.ultimatebootcd.com/ ) and run the memtest from there, UBCD is a compilation of many diagnostics tools, there are also versions of this tool available to downlaod to a bootable USB thumbdrive.

 

IIRC, from years gone by, the JMicron SATA controllers had a very poor reputation, and most of the advice was to use only for optical drives.

 

I would try loading a different flash drive with the free version of unRAID. not to run unRAID, but to see if the memtest will run from it. 

 

If it does, it indicates to me that your replacement of the "memtest" on the flash drive has probably introduced some fragmentation, and the boot loader expects that memtest will be contiguous on the flash drive. 

 

If it also does not run, then you'll need to look at the BIOS settings for memory on your server.  If the voltage, clock speed, or timing is not set as recommended by your specific RAM strips, then anything can occur.  As already mentioned, you can try running with only one memory strip or the other (although some MB need it in a specific slot to run in that fashion)

 

Joe L.

OK, this is strange...

 

Back in November, I decided to upgrade from a Plus license to a Pro license because I was expanding my array beyond the number of drives supported with unRAID Plus.

 

Before upgrading, I was using a flash drive with the storage capacity of only 128 MB. At that time I wanted to make sure I had enough space on my flash drive to install additional utilities, etc., and I had a spare 16 GB flash drive. So, I told Tom I was going to use a new flash drive and he instructed me to put the new GUID on the order form so he could transfer the key.

 

To use the 16 GB drive with unRAID, it was reformatted and the volume was labeled "UNRAID", then the contents from the old flash drive were dragged over to the new flash drive. I then had to delete the .key file from my config folder and run the 'make_bootable.bat' script. Then I copied the new Pro key to my config folder. That worked and I've been running off of the 16 GB flash drive ever since.

 

I still have the old 128 MB flash drive with the unRAID Plus version installed on it. I plugged it in and restarted my server and now I can run memtest.

 

So this seems to indicate that everything isn't quite right with my 16 GB flash drive. Is there any way to diagnose this? I wonder if this could cause any of the other problems I'm currently experiencing.

Just an idea regarding memory testing, if you have CD/DVD drive in the server you could boot from the UBCD, after setting your BIOS to boot from  CD, ( http://www.ultimatebootcd.com/ ) and run the memtest from there, UBCD is a compilation of many diagnostics tools, there are also versions of this tool available to downlaod to a bootable USB thumbdrive.

 

IIRC, from years gone by, the JMicron SATA controllers had a very poor reputation, and most of the advice was to use only for optical drives.

 

Thanks for the suggestion.

 

I don't have a CD/DVD drive installed on this server. Anyhow, I followed Joe's advice and used a different usb flash drive. That worked and now I'm running memtest.

Use a PC and run a check disk on the flash.

Use a PC and run a check disk on the flash.

 

Chkdsk doesn't reveal anything:

chkdsk h:/F

The type of file system is FAT32.

Volume UNRAID created 11/15/2012 9:11 AM

Volume Serial Number is R39N-8VNN

Windows is verifying files and folders...

File and folder verification is complete.

Windows has checked the file system and found no problems.

    15,30,400 KB total disk space.

                32 KB in 1 hidden files.

              288 KB in 9 folders.

        71,136 KB in 224 files.

  15,558,912 KB are available.

 

        32,768 bytes in each allocation unit.

      488,450 total allocation units on disk.

      486,216 allocation units available on disk.

 

When I run chkdsk h:memtest, it returns "\memtest contains 2 non-contiguous blocks."

 

I'll try running a defragmentation utility on my flash drive and see if that fixes the non-contiguous blocks.

 

After defragmenting my 16Gb flash drive, chkdsk no longer reports non-contiguous blocks for memtest. I haven't had a chance to test it with my server because I'm still running memtest with the other flash drive. It's been running for a little over 20 hours with 0 errors so far.

 

Now I'd like advice on how to proceed. Assuming my RAM is ok, and now I have a new power supply. I guess the next step is to replace these drives.

 

My disk4, which had only 1 pending sector, seems to have completely crapped out, because that was the one that would not even pass the system startup without generating a port error. This drive, which I've only had since this Fall, has been RMA'd and I should be receiving a replacement in a week or so.

 

I was hoping that I'd be able to rebuild my array after backing up all the data from the 2 HDs (disk2 and disk4). I had already unmounted disk2 and pre-clear'd it, but it still had pending sectors after completing this pre-clear. I assume the next step would've been to try the pre-clear again and if the 'Current_Pending_Sector' count was 0, then reassign it back to the array and then rebuild the array. If I couldn't get the count down to 0 with disk2, I'd replace it and try again. Since disk4 had only 1 pending sector maybe the rebuild would work. Then I would proceed with unmounting disk4, preclear it, reassign and rebuild. But now that's not going to happen.

 

I've already received an 'Advanced Return' RMA from Western Digital for Disk2. This means they will ship me a replacement and I have 30 days to return my defective drive before they bill my credit card.

 

Is there any reason why I should hang on to Disk2 at this point?

 

Once I have my replacement drives, how do I go about rebuilding my server and restoring the backed up data?

 

I assume the data on the other disks (disk1, disk3, disk5, disk6) are ok.

 

My thoughts are:

1. Preclear new drives thoroughly, preferably installed in the physical slot they will occupy permanently.

2. While the preclearing is proceeding, you could set a new configuration using only the good drives (parity, 1, 3, 5, 6)

3. After the initial calculation of parity is done, kick off a non-correcting parity check.

4. Once step 3 is done, browse around the array and see if your remaining data looks good.

5. Add the drives you precleared in step 1 to their array slots, one at a time, and kick off another non-correcting check after each new drive is added.

6. After the array is happy with both new drives, copy your backed up data from the old 2 and 4 back into place.

7. Return disk 2 after you are satisfied that any data from disk 2 is back in place.

8. Ponder a backup strategy that doesn't use this specific unraid server. A second unraid tower in another location, USB drives, whatever.

 

Step 1 and 2 will likely take several days.

Forget about that disk2. Just send it back and replace it.

 

I believe you posted that you do have a new disk and it has been precleared successfully. If yes, then install it and when you boot the server assign that new disk to a slot, unassign the failed disk4 and set a new config. Build the parity and get a valid array working again.

 

I'd be tempted to copy the key file and then format and re-install unRAID onto the flash drive. The big issue with 4.7 is that it can change the paritions of existing data disks if you start with a fresh install which you then also have to fix. So, I'd go with a version of 5.0 where that bug was fixed, preferrably the latest RC11 if you want to attempt this. I have read some cases here of odd issues being corrected with a fresh USB install even when the issue doesn't seem like something that would be fixed doing that.

 

I haven't had a chance to pre-clear the new drive, yet. I was still trying to get everything backed up and then I had to go out of town. When I returned, the server was running, but I couldn't access any data. It seemed like the unRAID OS was no longer running. When I rebooted, I got port errors where ever disk4 was installed. Anyhow, the backup wasn't complete, so I'll need to rerip the discs for some of my DVDs and Blu-rays.

 

So, I'll need to pre-clear the new disk first.

 

Is v5.0 RC11 as stable as v4.7? I'm usually pretty cautious when it comes to running pre-released software. If it's fixed a bug that could cause problems, then it makes sense to update/upgrade the software, but if it adds another unnecessary variable I should probably stick with v4.7.

 

Memtest has been running off my old flash drive for over the last 24 hours with zero errors. I quit the test and installed my recently defragged 16Gb flash drive and rebooted. When I choose memtest, it still just restarts. It's strange that memtest won't run off of this stick.

 

UPDATE: I decided to backup everything on my 16Gb stick, then reformat it and reinstall v4.7 as per the instructions for the unRAID Server Installation. I used the latest 'unRAID Server 4.7 AiO.zip' file. After rebooting and then picking memtest, it still didn't run. The fact that I cannot run memtest with this 16Gb USB flash drive has me baffled.