• Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by captain_video

  1. I just ran into this same problem. There was a file stuck in my cache drive that I could not clear. There was a copy of the file in the Share folder so it was apparently moved at some point, but it must have only been copied and not actually moved. Just to be safe, I copied the file from the Share folder to my main PC and then deleted the file from the Share. I invoked the mover and it moved the file from the cache drive to the Share folder to restore the deleted file and then it was cleared from the cache automatically. FYI - I had all of the settings for the cache drive previously set to all of the settings recommended in the above posts. I can only assume that perhaps something glitched the transfer during a move and it copied the file but failed to delete it upon completion.
  2. Just wanted to update everyone on the situation. I was finally able to get the Intel NIC recognized in my server. I had to stop the array and then go into the Settings tab and select Network Settings. Scroll down to the area for Interface Rules and then swap the MAC addresses for the devices for eth0 and eth1 using the drop down menus. I hit apply, but once that was done the network interface no longer functioned since the ethernet cable on the server was still connected to the onboard NIC. I suppose I could have just swapped the cable between the onboard NIC and the Intel NIC, but I opted to shutdown the server using the keyboard and monitor attached directly to the server. Once the server was shut down I swapped the cable and powered it back up again. Once it booted I had activity LEDs on the Intel NIC showing a connection. I reconnected to the server from my PC via the web GUI and all is working well again. I had been getting transfer rates between my PC and the server at around 78 MBS using the Intel NIC whereas it dropped down to about 40 MBS using the onboard NIC. This whole thing came about when I swapped my USB flash drive with the unRAID files to a different USB port. I could not get the system to boot until I went in and moved the flash drive back to the top of the boot order. I can only assume that somehow the onboard NIC was automatically reconfigured as eth0 when that happened.
  3. OK, I just edited the network-rules.cfg file and renamed etho to eth1 and vice versa and swapped the position in the file so the group with eth0 was at the top followed by eth1. I booted it up with the ethernet cable connected to the Intel NIC and still got the error message that it could not find eth0. I did not disable the onboard Realtek controller when I did this so maybe it automatically scans onboard devices before PCI ports. In any case, the server is working with the Realtek controller and I'm not seeing any effect on file transfers or steaming of 4k videos so I guess if it ain't broke, don't fix it. Thanks for everyone's inputs. I'll probably still work on it when I have more time, but for now I'll just go with what's working.
  4. I have tried four different cards in the two PCIe x1 slots. Looking at the System Devices tab in unRAID it shows the Intel NIC as shown below. If I go into the UEFI BIOS and disable the onboard Realtek controller it won't connect or show any activity lights on the Intel controller with the ethernet cable attached. I get an error message at the very end of the boot screen saying it can't find eth0. I was looking at the network-rules.cfg file and it shows the following info: # PCI device 0x10ec:0x8168 (r8169) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="40:16:7e:a7:e4:85", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" # PCI device 0x8086:0x107d (e1000e) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:15:17:0d:ab:58", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" # PCI device 0x8086:0x10d3 (e1000e) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1b:21:53:c4:cf", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2" I'm wondering if I manually edit the file and swap etho and eth1 in the NAME attribute if it will then look for the Intel controller. I'll give that a try and see if it works. The LEDs on the Intel NIC do come on when I have the Realtek controller enabled and the ethernet cable plugged into the Intel card, but it doesn't have any connection, probably because it's only working with etho and not eth1. If I disable the Realtek onboard controller and plug the cable into the Intel card I get no activity lights at all. I'll try the manual edit of the network-rules.cfg file and report back.
  5. I installed a new (refurbished) Intel CT Gigabit adapter and disabled the onboard Realtek ethernet controller. When it boots up I get the message that it can't find eth0 so it can't set up the IP address even though the ethernet cable is connected to the Intel NIC. I have it set up with a static IP in a range that I set up outside of the DHCP range of addresses used by the router. I re-enabled the Realtek controller and now it works, but it's still refusing to recognize the intel NIC. This is confusing because I never had any issues with using an Intel NIC before and all of a sudden unRAID is just refusing to recognize it.
  6. Running unRAID Pro 6.9.2 with 184TB currently with 55.7 TB free. I'm using a 24-bay Supermicro server rack with an 8-bay Supermicro rack piggybacked onto the larger case. I cut a hole in the bottom of the 8-bay rack to feed the SATA cables from the controllers in the lower rack. I have three 8-port LSi SATA controllers plus six onboard SATA ports and two eSATA ports on an ASUS A88X-PRO motherboard with an AMD A10-7700K CPU and 32GB of DDR3 memory. I'm running 28 data drives of either 4TB or 8TB capacities with two parity drives and a 1TB SSD cache drive. I can expand the array to 224TB without having to upgrade the parity drives. I've got five 8TB drives sitting on the shelf already pre-cleared and ready to insert into the array should any of the drives die. Been running unRAID for over 13 years now. The pic with the drives in the anti-static bags are the drives that have been retired from the array over the years that were replaced by larger drives. There were more drives than than, but I destroyed any drives that failed and recycled them. The ones in the photo have all been wiped clean and tested good.
  7. I agree completely. The list of drives was buried in the BIOS so I had to dig deep to find it. What a ridiculous thing to have. I've been using the same setup for years and never noticed the boot drive list before.
  8. Success! I still couldn't get the system to boot after making the above changes. I never got around to trying options 1 or 2 from Frank1940's suggestions. I got back into the UEFI BIOS settings and I drilled down until I discovered that the boot order showed the USB drive as the 15th device in the boot order even though I had specified it as the first boot device elsewhere in the settings. Once I changed it so the Sandisk flash drive was the first device in the boot order it booted clean and I am able to access the server via the web GUI on my PC. Thanks to all for your help and suggestions. I guess when I swapped the flash drive to a different USB port it changed the boot order. The option to set that was buried in one of those options that made you scroll down in the screen to find it.
  9. OK, just copied the 6.9.2 bz* files over to the flash drive and reran make_bootable.bat as Administrator again just to be on the safe side, but still no love. I'll try it again with the /syslinux folder copied over
  10. I made a backup copy of the contents previously and it copied with no problems. I ran the make_bootable.bat script on the flash drive connected to my Windows 10 PC and it still would not boot. I just ran chkdsk.exe on the flash drive and it reported no errors. The server was shut down when I pulled the USB drive. I never disconnect anything while it's still powered up, except the ethernet cable. The system goes through the initial check of the HBA controllers and lists all of the drives attached. It cycles back to the initial Asus splash screen and blinks once or twice and then tells me to reboot and select the proper boot device. I've gone back into the UEFI setup screen numerous times and made sure the Sandisk flash drive is configured as the first boot device and it still won't boot. The system booted into 6.10.1-rc1 with no problems after updating the OS. I had been having issues with my Intel PCIe NIC and I had removed the flash drive to avoid damaging it. I moved it to another USB port and then tried to boot the system back up. That's when the problem started. It's got me completely stumped. So I can just copy the 6.9.2 files over from the downloaded zip file, but just copy the bz* files and leave everything else as is?
  11. Tried that with no luck. Can I just download unRAID 6.9.2 and overwrite the files on the flash drive? I'm wondering if this is a glitch in 6.10.1-rc.
  12. I'm running unRAID Pro version 6.10.0-rc1. My system was running fine before I removed the USB flash drive to access a couple of eSATA ports located right below it on the rear panel to attach some cables. I moved it so I wouldn't take the chance of damaging the flash drive. I relocated it to another USB port on the rear panel and then booted up into the BIOS to make sure it was still configured as the first boot device. Now it keeps telling me that I need to insert a proper boot device. I moved the flash drive back to the original USB slot and checked to make sure it was still configured as the first boot device but it still won't boot. I can see the flash drive internal LED flash when the system first starts up so it's being read. I've been using the same flash drive ever since I first purchased unRAID back in February of 2008 and it has never failed to boot before. I don't know if something somehow got corrupted on the flash drive that is preventing it from booting or what. Unfortunately, I have been extremely lax in making backups of the flash drive so the latest one I have is back in 2015. Here's a screenshot of the files contained on the current flash drive: I am unable to provide a diagnostics log since it won't boot.
  13. It's attached to the end of the first post. Sorry, that's the syslog file not the diagnostics. I'll run it and upload the file I'm using an Asus A88X-PRO motherboard with an AMD A10-7700K Radeon R7 CPU and 32 GB of DDR3 memory. I'm using three 8-port SATA controllers plus the six onboard SATA internal ports for the data drives and dual parity drives and currently one external eSATA port for the cache drive. I plan to connect the 2nd eSATA port to an empty slot in the server rack to use for pre-clearing new drives. I have a 24-bay Supermicro rack and an 8-bay Supermicro rack all running off the ASUS motherboard via the onboard SATA ports and 8-port controllers.
  14. I'm running unRAID Pro 6.9.2 on a 184TB server with 28 data drives, two parity drives, and a 1 TB SSD cache drive. I rebooted the array yesterday and now I can connect to the server. I'm using an Intel CT Gigabit PCI-e ethernet controller that has worked fine for as long as I can remember. I tried using a different Intel adapter in the same slot and still nothing. I had a two-port SATA controller in a PCI-e x1 slot for my cache drive so I pulled that and installed the NIC in the slot. Booted up and still no connection. I tried the onboard Realtek ethernet controller and it works fine. For some reason it seems that unRAID is either no longer recognizing the adapter or it's just not loading the drivers. I checked the System Devices under the Tools tab and both the Intel PCI-e NIC and the onboard Realtek NIC are both shown so I'm stumped as to why one works and the other one doesn't. I upgraded the unRAID OS to version 6.10.1-rc1 to see if that would help but still get the same result. I've attached the log file for anyone that can decipher
  15. Once the data rebuild was complete I shutdown the server and then restarted it. When it came back up everything was back to the way it should be so it's all good now. I think maybe I just switched screens too fast in the GUI and it just got stuck somehow. Been using UNRAID for about 12 years and this was the first time I had seen anything like this occur so I thought I'd share it with the rest of the class.
  16. I recently ran CCleaner the other day so there shouldn't be much in the cache to cause this issue. I think it just got hung up when I tried to switch screens too quickly. It says the array is stopped, but it is clearly up and running even though it thinks it isn't. I just cleared the cache and closed the web browser. I reopened Chrome and connected to the server. Still getting the same screen. I think it's just a Gremlin infestation.
  17. I have tried that and every other trick I can think of. I've closed my web browser and reconnected and still get the same screen. The weird part is that even though it says the array is stopped it is still allowing me access to my files. I can play videos and movies streamed from the server so it appears to be a glitch in UNRAID. I'm just going to let it finish the data rebuild and then reboot the array. Hopefully it will correct itself when it resets.
  18. UNRAID PRO version 6.9.2. I just installed a new replacement drive to upgrade to a larger one. I assigned the new drive to the old slot as always, but when I started the array to begin the data rebuild it updated the GUI to show that the data rebuild was in progress but the screen still shows the array as stopped and the only Array Operation options are REBOOT or SHUTDOWN. What's weird is that I'm still able to access the files from my computer even though it says the array is stopped. I've attached the system log. It indicates a Stale Configuration in the bottom left of the screen along with the data rebuild progress. I have no idea what that means. I don't want to do anything until after the data rebuild is complete. The dashboard tab shows all of the drives as being off-line. I've lost track of how many times I've performed a drive replacement over the past 12 years or so on my server, but this is a new one to me.
  19. Just ran the latest version of pre-clear on a new drive and it appears to have fixed the problems I was having earlier. The problem with it failing was fixed in a previous version, but this latest version is configured to only run the zeroing process once and not twice like it had been doing. I generally buy external drives and shuck them before running pre-clear, but someone had mentioned running pre-clear with the enclosure hooked up to a USB port before taking the drive out of the enclosure. I tried it and so far it's working great. It seems to be running as fast as when performing a pre-clear on a drive physically installed in the array. The real plus is that I don't have to shut down the array to install or remove it. That plus if there's an issue with the drive I won't take a chance of damaging the case when removing it in the event that I need to return it because of a bad drive. I forget who posted the tip, but kudos for that.
  20. Any update on the preclear issue I was having? I've run it on two 8TB drives and it ran the zeroing function twice on both drives. Total time to run preclear on a single drive was close to 80 hours. That includes the pre-read, zeroing x 2, and post-read sequences. Reducing the zeroing sequence to just a single pass would reduce that time by about 24-25 hours. I just use these drives to replace failed drives or ones that are nearing end of life or just upgrading from a smaller drive to increase storage. I don't really even need to run preclear on these dives, but I do it to ensure they're in good working order before installing them in the array. I pick them up when I see them on sale to have on hand in case of a drive failure. They're never on sale when you need one so I just have them as insurance.
  21. PM sent with diagnostics file and preclear log
  22. I'm running pre-clear on a 2nd 8TB drive and it is also performing the zeroing process twice. Is this really necessary? Can we get the option to just do this once?
  23. The preclear completed with no issues so it would appear that whatever bug was causing my problem has been corrected. The pre- and post-read functions took about 15 hours each, but the zeroing phase took about 49 hours for an 8 TB drive. This phase was performed twice for whatever reason even though I had selected only one cycle for the pre-clear process.
  24. Been running preclear on one of my 8TB discs and it appears that has run the zeroing function twice along with the pre-read function. It is currently performing the post read segment so I assume it should be completed by tomorrow morning. Does the latest preclear plugin automatically zero the disk twice? I don't recall changing the option when I initiated preclear. I generally only run preclear once on any new disk since most of them are used to rebuild data on either a failed disk or one that is being replaced due to the age of the disk.
  25. Great! I have a couple of disks that I'm running the long generic tests on before attempting to run a pre-clear on them. They're 8TB drives so it could take about 45 hours or so to run pre-clear on one of them. I'll post my results when the first one completes.