Jump to content

Spaceherpe

Members
  • Content Count

    50
  • Joined

  • Last visited

Posts posted by Spaceherpe


  1. 1 hour ago, Squid said:

    At the command prompt, 

    
    diagnostics

    It'll get saved onto the flash drive (logs folder).  Post the entire zip here

    I was able to upgrade to 6.7.0, but anything beyond that errors out. Right now, I am running the backup and restoring some lost file, which will take the better part of a day. Once that is done, I will run the diagnostics and post it here. Thank you for the help!


  2. This still has not been resolved. Any attempt to install 6.7.2 or 6.7.1 returns failure to initiate errors and a whole mess of other line that move too fast to read. When it finially finishes, I show the login prompt, but when I check my router, there is no serever hard connected to use the ip address to bring up the GUI. I am beyond pissed. I paid for the software, I should be able to upgrade past the latest version I can use which is 6.5.1.

    PLEASE HELP!!!


  3. I forgot to add my server stats....

     

    Model: Custom

    M/B: Gigabyte Technology Co., Ltd. - AB350M-DS3H-CF

    CPU: AMD Ryzen 3 2200G with Radeon Vega Graphics @ 3500

    HVM: Disabled

    IOMMU: Enabled

    Cache: 384 kB, 2048 kB, 4096 kB

    Memory: 16 GB (max. installable capacity 256 GB)

    Network: bond0: fault-tolerance (active-backup), mtu 1500 
     eth0: 1000 Mb/s, full duplex, mtu 1500

    Kernel: Linux 4.18.10-unRAID x86_64

    OpenSSL: 1.1.0i


  4. I currently use Version: 6.6.1. I attempted to update to 6.6.2 using the upgrade option on the server....it failed. I attempted to upgrade via downloading>make bootable>failed. At one point, it loaded, but wasn't locatable. I even checked my router to locate an unidentified IP and nothing. 

    This has become the norm, at least for me, when upgrading. 

    For me, since 6.6.1 is working without any issues, I don't think I will be upgrading any time soon. I'm not willing to lose my server nor all of my current settings because of upgrades. 

    The reason for this post is to see if anyone else is having the same issues?


  5. I ran my troubleshooter and received all of the following information:

     

    Internet Connections

    Publisher details

    Issues found

    Windows could not automatically detect this network's proxy settings

    Windows could not automatically detect this network's proxy settings

    Detected

    Contact your network administrator

    Completed

    Issues found

    Detection details

    6

    Windows could not automatically detect this network's proxy settings

    Detected

    Contact your network administrator

    Completed

    Windows could not automatically detect this network's proxy settings.

    Detection details

    Network Diagnostics Log

    File Name:46030BE8-2DF4-49A7-9DB6-5D195498C173.Diagnose.0.etl

    Other Networking Configuration and Logs

    File Name:NetworkConfiguration.cab

    Collection information

    Computer Name:SCUBA-PC2

    Windows Version:

    10.0

    Architecture:

    x64

    Time:

    Wednesday, January 2, 2019 2:09:25 PM

    Publisher details

    Windows Network Diagnostics

    Detects problems with network connectivity.

    Package Version:

    4.0

    Publisher:

    Microsoft Windows

    Internet Connections

    Find and fix problems with connecting to the Internet or to websites.

    Package Version:

    3.0

    Publisher:

    Microsoft Corporation


  6. 1 minute ago, trurl said:

    Assuming you are on WIndows. In Windows File Explorer, can you browse to the Unraid shares on the network from that computer?

    Yes, I am on a Windows computer and I used to be. My previously mapped drives no longer connect to the address. I am positive the address is correct, as my other computer is connecting to the same address. My main computer however, is not able to locate that address.

    I am also receiving an error "Windows Could not Automatically Detect Network’s Proxy Settings" which I am currently troubleshooting. 

     


  7. 1 minute ago, trurl said:

    If you are getting lots of errors on any disk during the rebuild you should try to correct the situation and try again. All bits of all disks must be reliably read in order to reliably rebuild all bits of the disabled disk.

     

    Any time you are mucking about in the case you must always double-check all disk connections, power and SATA.

     

    If you only have one parity disk then you can only rebuild one data disk at a time. Parity itself doesn't have any of your data. As I said above, ALL other disks are required to rebuild a disabled disk. While it would be possible to attempt one of those other rebuilds after disk1 rebuild completes, I really don't see how that should be necessary and doubt it would be helpful. If they aren't disabled they shouldn't need rebuilding.

     

    I think it's more likely that you just have some bad connections or some other hardware problem (controller?) and nothing is wrong with those other disks or their contents.

     

    Just shut down, check all connections, try disk1 rebuild again, and post new diagnoistics.

    It will have to wait until tomorrow. I have to get to bed. Wake up for work at 0445. I'm going to let the parity run it's course for now and reassess tomorrow. The absolute worst case scenario is a full reset of my server and reinstalling all of my media...again.

     

    Thank you for your help. I'll post an update when I get off work tomorrow afternoon.

     


  8. Question... 

    Disk 1 being rebuilt

    Disk 2 showing empty but shouldn't be.

    Disk 3 showing it has files, but those files aren't available when using windows to access the files on the server.

     

    Can I force a parity rebuild of Disk 2 and 3 by doing the same thing we did for disk 1?

    Stop>remove disk>start then stop>re-add disk>start?


  9. Diagnostics running but not downloading. 

    On the main page, it still shows rebuilding however, everything on disk 2 (not the drive being rebuilt) is showing millions of errors and counting.

    I'm starting to think it might just be worth it to start from scratch! 

     

    I'm out of ideas and patience at this point.


  10. Just now, trurl said:

    Maybe a limitation of the webUI I didn't know about that prevents getting a result from that folder icon during a rebuild. You should be able to access any of your files though, including from the emulated disk, over the network as usual.

    I thought the same thing, so I double checked and everything is gone. The server says rebuilding. One drive shows files, but when looking through windows, everything is blank. Empty. 

     


  11. Now I'm really confused, as all of my drives show empty. I guess I will let the parity run it's course and see if it returns anything. Otherwise, I will re-add from my backup storage drives back to my server. That's always fun!


  12. 3 minutes ago, trurl said:

    No need to put it back. johnnie seems to think your diagnostics indicated an empty disk though. I just looked at them myself and it does look like disk1 has little or no data on it.

     

    While rebuilding, you should be able to look at the contents of the emulated disk. Just go to Main - Array Devices and click on the folder icon at far right on the line for the disk and it will allow you to see what is on the emulated disk. And the contents of the emulated disk is exactly what will be rebuilt on the new disk.

    Weird. It says it is rebuilding it, but the folder to the right shows nothing in the folder. I have a backup on a separate unconnected drive, just in case this happens. I can re-add everything. This is my media server, so....

     

    I'm learning what not to do AND to be patient.


  13. 1 minute ago, trurl said:

     

    Stop the array.

    Unassign the disk.

    Start the array with the disk unassigned. This will reset that disk assignment.

    Stop the array again.

    Assign the disk.

    Start the array to begin rebuild.

    Attempting now...