Jump to content

ridley

Members
 View Profile  See their activity

  • Posts

    303

  • Joined

  • Last visited

 Content Type 

Posts posted by ridley

    Rebuild lost Array..

    in General Support

    Posted

    2 hours ago, trurl said:

    Not entirely sure I understand what you propose. So there is a dead server, another live server, and a new server to be built?

     

    You can mount ReiserFS disks with the Unassigned Devices plugin and copy their data to XFS array disks. I don't know if that answers your question or gives you some other ideas.

    I have a server that died but has lots of data on it that I by have just got going again and want to preserve the data.

     

    I have also just built a new server of bigger capacity but fewer disks, I thought it may be an idea to transfer the data from the old server to the new.

     

    Did not know about the unassigned devices plugin, that sounds interesting. Cheers I will look into that 

    Rebuild lost Array..

    in General Support

    Posted

    12 minutes ago, trurl said:

    Your question makes me wonder if you understand that Unraid IS NOT RAID. Parity has no data, and each data disk is an independent filesytem that can be read by itself on any linux.

     

    I am aware that unraid is not raid (the name is s clue) but I am being ultra cautious here I really don't want to mess anything up and lose data that took years to accumulate because I "think" it will be ok.

     

    I have a second empty server of comparible size (orig was about 30tb of data) and the old dead sserver with the data is reiserfs which needed updating.

     

    Would I be best to just copy the data across rather that trying to rebuild the original server?

     

    I could then format the older drives to the new FS and incorporate them into the new server.

     

    If do any ideas on how best to do it? 

    Rebuild lost Array..

    in General Support

    Posted

    I used to have a 17 disk array and then the motherboard died taking out the USB flash drive and my backup of the config was dead too...

     

    I have just rebuilt the server and assigned the drives in the order/assignments that they were in before the death of the motherboard etc. However I cannot remember the shares etc. 

     

    I have not yet brought the array online as I am afraid that the parity check would destroy any chance of preserving my data. Will bringing the array online start a format on the drives? Will a parity check destroy the data?

     

    How can I best try and rebuild the array whilst preserving the data?

    Supermicro AOC-SASLP-MV8 not detected.

    in Storage Devices and Controllers

    Posted

    I have looked around but cannot see an answer. 

     

    Any idea why my Supermicro AOC-SASLP-MV8 is not detected on boot? 

     

    I have tried it in all my slots with or without cables connected and it once showed its BIOS but try as I might I cannot get it to be detected again. I have tried disabling pretty much everything in the bios but still no joy.

     

    Any ideas?

    Disastrous Upgrade

    in General Support

    Posted

    Maybe so but the Supermicro does not work in the top slot either. 

     

    I cross flashed it in a second PC that I still have so I will try the H200 in that. 

     

    Still, leaves me with what appears to be a dead slot or I am missing something here.

    Disastrous Upgrade

    in General Support

    Posted

    I have a supermicro card and the H200 in the system, both were working before.

     

    Now if I place either in the top PCIE they do not work, but the Supermicro works in the bottom slot and the H200 doesn't. Looks like I fried the H200 and the slot it was in?

    Disastrous Upgrade

    in General Support

    Posted

    8 minutes ago, bjp999 said:

    Rebuilding a key from scratch isn't terribly difficult if you know your drive placements, which I am assuming your have (you called it allocations - not sure if we are talking the same thing).

     

    Rebuilding your Docker configs might be a bit more trouble.  You'll have to re-establish the mappings. But the appdata is on the cache drive and will not have to be redone.

     

    VM configs are safe in libvirt.

     

    Much better to have fried a USB than a disk.

     

    The first step will be to set up a new key. Hope you have a backup of your keyfile. Otherwise you might need to contact LimeTech.

     

     

    Will my key work with Different USB Drive? I have found a copy of a file named Pro1.key is that the file I need?

     

    I have a recent screenshot of the drive positions serial numbers etc.

    Disastrous Upgrade

    in General Support

    Posted

    I was upgrading my CPU/RAM and managed to damage the motherboard CPU socket, which I have fixed.

     

    But now I seem to have a corrupt USB Pen Drive with my UNRAID on it. It cannot be read in my Server or my Windows PC ("The USB device you just connected malfunctioned and Windows does not recognise it") In device manager it states "Device Descriptor Request Failed.

     

    I assume the USB Pen Drive is dead and I will need to replace, tricky bit is the config. I know the drive allocations but how can I get everything else back?

    Before I do something stupid

    in General Support

    Posted

    I think that it started copying, as per the instructions using rsync but then the server became unresponsive and the transfer failed.

     

    I have found that one drive on the array looks like the one I was copying from but some of the data has changed since then, some added and some removed.

    Before I do something stupid

    in General Support

    Posted

    I am trying to convert my disks to XFS but last time I tried the server failed half way through (server lock ups is the reason I have been advised to convert)

     

    Now I have come back to it I want to check that I am not about to destroy my array. I think the "new" swap drive is the last in the array, Disk17. If I go to Settings→Global Share Settings then I can see that Disk 17 is excluded. However, my user shares show that they are set to "All Disks" and if I click on that it shows Disk1→Disk16. 

     

    So I presume I am OK to format Disk 17, which has some data on it (from the last transfer that failed?) and restart the process described here https://wiki.lime-technology.com/File_System_Conversion#Mirroring_procedure_to_convert_drives

     

    Please just let me know, I would hate to lose a load of data.

     

    Server unresponsive, now multiple errors

    in General Support

    Posted

    I think we are talking at cross purposes.

     

    I have 17 drives, 16 data plus parity. All but two are on reiserfs. So I add an 18th drive, names by UNRAID as drive 17, and this is formated as xfs. Drive 14 is reiserfs and similar size to XFS drive 17 I have just added. I now use rsync to clone the data on drive 14 to the the new xfs drive ie drive 17.

     

    Whilst the cloning is taking place the GUI becomes unresponsive. The console shows process 1620 SMBD is out of memory and I cannot powerdown or reboot via telnet or the console. However it does appear that the cloning has finished successfully. 

     

    Now I have to hard reboot but drive 17 the new drive is still there and so a parity rebuild would include a parity built from the 16 data drives PLUS the 17th "swap" drive I have added, this isnt ideal as I had wanted to preserve parity throughout changing the file system on the drives.

     

    Is that any cleared or have I muddied the waters more?

    Server unresponsive, now multiple errors

    in General Support

    Posted

    I am in the process of changing the file system on my drives from ReiserFS to XFS. To do this I have added a "swap" drive to transfer the data from a ReiserFS drive to the "Swap" drive as per the instructions here http://lime-technology.com/wiki/index.php/File_System_Conversion#Mirroring_procedure_to_convert_drives 

     

    Unfortunately the server became unresponsive during the transfer of the data, which I believe completed successfully, but I could not powerdown the server at this point or access the GUI just user telnet or the console. So I have had to hard reboot the server which of course now wants to rebuild parity with all my data drives PLUS the swap drive. I had hoped to complete the file system changes without affecting parity.

     

    I may be wrong here but when my system locks like this it seems to be an out of memory error associated with SMB, is there anything I can do to try and prevent this happening?

×
×
  • Create New...