-
Transferring license to new flash without a backup
I had a flash drive fail and I don't have any backups with the correct configuration but I have a screenshot of the configuration. I replaced the flash drive and rebooted and I am trying to figure out how to transfer my license to the new flash drive. The instructions online say to "If needed, copy your existing license key file into boot/config on the new device." I don't have an existing license key file because I do not have a backup. Then it says to go to tools/registration and hit replace key ... I do not get that option. Any assistance is appreciated. EDIT: I no longer need assistance. I did have a correct backup but it was on my cache drive, I was able to use unassigned devices to access the config folder with some help from Grok AI giving me steps. Once I got the config folder from the cache drive I was able to do a mostly normal usb device switch.
-
Rebuild gone wrong
Thank you so much for your response. This appears to be working. I had a superblock error as well that is what caused the drive to go offline to begin with. I found a solution for that and used the new config section to reset the array, parity is resetting now. I can see my lost data in the file system so we should be good to go once the parity runs. I really appreciate your help. I think the superblock error came from a hard shutdown due to power outage and my UPS didn't have enough juice to keep it running. It makes a lot of sense now.
-
Rebuild gone wrong
I had what I thought was a disk fail, it was showing as unmountable. I had an already cleared backup and so I swapped it out. The original disk is 8tb, the new one is 12tb. After assigning the new disk to slot 1, it showed still as unmountable. I thought this was odd since it was precleared. There was a button to format so I clicked it. I thought this was formatting my new drive which was already empty, instead this formats the emulated drive and I lost all the data on that drive. So I realized this now and stopped the rebuild (its about 3/4 done). So ... I pulled my old drive I thought was bad and I can see it in windows (I can't access the files because its xfs but I can see that it runs and is recognized) so I think the drive wasn't actually bad now. So I tried putting the old drive back into the array and replacing the new drive with the old one again. My plan was to try to build the array again how it was then clear the parity. Well, as you may have guessed due to the size difference of the drives, I cannot go back to the 8tb drive that has my data on it. My drives on the array are all 8tb except for my parity which is 12tb and this one I was trying to use to replace the "dead" drive is a 12tb. Any help would be appreciated. I am good with either finding a way to use that 8tb drive on the array where the 12tb backup was, or continuing with the 12tb backup and accessing that data on the 8tb drive some other way (I dont know how). If I could access it I can pick through the important stuff and move it back to the array. EDIT: I tried mounting the old drive as an unassigned device and it will not mount. It gives an error "can't read superblock on /dev/sdd1". EDIT 2: I got it to mount in unassigned devices using this old thread Bad superblock when trying to re-mount external drive [help] - General Support - Unraid
-
6.8.0 rc3 Shares not available on Android
I had this issue on rc2 as well. On 6.7.2 previously and for all releases before that I used, I could access my shares on my phone on the same network. rc3 seems to block that access. I checked before upgrading to rc3 and was able to access my shares, I then updated and checked after the server was updated for 10 minutes. I could not access any shares on my android device. Then I went back to 6.7.2 and was able to access them again within a minute of booting, so its definitely related to 6.8. This was all over local network and my phones wifi was on, tested over a 10-15 minute period of updating then downgrading, no network settings changed. My phone is using an app called ES file explorer to access the server. I can use my phone to access my main computer as well and tested that when I could not reach the shares to make sure it was not an issue on my phones side. The fact that I could reach my server before upgrading, then could not on rc3 but could reach my desktop, then could reach my server again when downgraded back to 6.7.2 indicates the issue is with rc3. My server is visible on my network to my phone, I just click on it and it does not respond. Shares work as normal on my desktop running windows 10 and connected via ethernet. EDIT: This appears to be related to the implementation of SMB2.0 and dropping SMB1 … my app used SMB1. I am not sure if there is a fix other than changing apps.
-
6.8.0 rc2 auto log off and network not available on android
I am getting an auto log off after a few minutes. It started at around 5 minutes it would kick me to the login screen after I first installed. It has gotten worse the longer I was on. SSH stays logged in, its just webui. I also was unable to access my shares with an android device. I previously used ESfile explorer to access my shares. I went back to the last stable version and both of these issues are resolved, so its with the rc2 version. EDIT Solved with RC3
Bakerking31
Members
-
Joined
-
Last visited