Jump to content

SFyffe

Members
  • Posts

    15
  • Joined

  • Last visited

Posts posted by SFyffe

  1. After a failed upgrade from 6.8.3 to 6.9.2  I restored my USB flash drive.   When I boot UNRAID OS I get an error due to Invalid Expansion.

     

    Here is a screenshot of how the disks were arranged prior to the upgrade:

    1966130258_Screenshotfrom2021-05-2708-45-24.thumb.png.74463f250f3f66a4f8f5df286a2cbf78.png

     

     

    And here is a screenshot of how they are coming up currently:

     

    1953823544_Screenshotfrom2021-05-2708-44-12.thumb.png.a134af1632e84cedf14a8fa5455dbae4.png

     

    1021571566_Screenshotfrom2021-05-2708-44-40.thumb.png.0e663163a9d886942f132852fe44c0d2.png

     

     

     

    My DISK_ASSIGNMENTS.txt file  looks like this currently.   

     

    1185050090_Screenshotfrom2021-05-2709-00-16.png.20ac04ab967bfcfb9134e0f96fc6dae5.png

     

     

     

    Can I just manually edit this file with the correct assignments?    If not, is there another way to get the disk organized back to the way they were and bring the array back online?

     

    Note:  The diagnostics file attached is from before the restore of the flash drive just after the upgrade attempt.

     

    Best Regards.

    tower-diagnostics-20210523-0914.zip

  2. Thanks for the reply.   I have a pretty recent back up of my flash drive so I think I am ok.  This is really strange though.   Hope it is not a defect in the upgrade process.

     

    Is there a log file written somewhere specific to the upgrade and the steps that were taken?

  3. If you just started the array then from what i read UNRAID did not do anything to the drives.     Did you get them reconnected back to your controller in the correct order?   If any of the drives got mixed up then I think that would lead to problems like what you  are seeing.

  4. I had this same type of problem when I first started working with UNRAID.   

     

    If you are having this error:

     

    /dev/disk/by-LABEL/UNRAID not found!

     

    UNRAID will not work properly.   Getting the label correct on you USB boot media is critical and Windows 10 with large USB drives does not seem to do it correctly.   My guess is that Windows does not assign the label to the partition where it needs to be and uses metadata some way.

     

    Maybe this will help..

     

    https://help.ubuntu.com/community/RenameUSBDrive

     

    I wound up formatting in my wife's MacBook the smallest USB I had in a junk drawer and this boots perfectly.    I read in a Lime-Tech forum post that one person partitioned  below 1Gig and he got his to work.   This also may be related to our BIOS not being able to properly read the USB stick if it is partitioned to the full amount.

     

    Don't give up!!  UNRAID is really cool..

  5. Once you are in this condition you may want to test and see how long your ping responses are both on the machine you are RDP'ing in with and another machine on the subnet.   This may let you know if the remote machine is responding network-wise.  

     

    If you end the RDP session and reconnect is the problem remedied at least for some time?.    Some times these problems are difficult to fix unless you uses something like WireShark to see how things are behaving. 

  6. You may want to try:

     

    1.  Different RDP client on the affected laptop.   You could try with "Remote Desktop Connection Manager" or "MobaXTerm"

    2.  Check the Connection Experience under Advanced Settings.  Hard set it to your connection speed and see if there is any difference.

    3.  Verify that the laptop can resolve the hostname of the UNRAID server and VM correclty and not take a lot of time.  Could be a strange DNS issue.

    4.  This one is a stretch but you could run an elevated CMD prompt and turn off TCP AutoTuning  ( netsh interface tcp set global autotuninglevel=disabled)

     

     

     

     

  7. You may want to look at the Local Security Policy of the machine.  

     

    Start >>RUN>>Local Security Policy

     

    Expand Local Policies and then User Rights Assignments.  Something could be missing in the "Allow log on through Remote Desktop Services."

     

    There is also a "Deny log on through Remote Desktop Services" that can lead to problems as well.

×
×
  • Create New...