Jump to content

Nebula

Members
 View Profile  See their activity

  • Posts

    29

  • Joined

  • Last visited

 Content Type 

Posts posted by Nebula

    HELP PLS - Inode allocation btrees are too corrupted

    in General Support

    Posted · Edited by Nebula

    ofc I understand that but that leads me to my questions above or below:

    Is it because Disk 3 is now a part of the array and there for I cant change it with the dmg Disk1?

    I guess it is from your answer.

     

    Should I have'd set Disk 1 to no device first and then change it with the new disk 3 (before preclear) followed up with preclearing, rebuild?

     

    https://wiki.unraid.net/Replacing_a_Data_Drive 

    1: Stop the array

    2: Unassign the old drive if still assigned (to unassign, set it to No Device)

    3: Power down

    4: [ Optional ] Pull the old drive (you may want to leave it installed for Preclearing or testing)

    5: Install the new drive  (from a noob view it does only tell you to install new drive and not it has too be the same disk slot you want to replace before preclear, rebuild)  

     

    And thats why I ended up with one extra added disk to my array instead. Now its pretty clear ofc but I thought I might delete data or something.
    If I want to remove disk 3 and start over I follow this ? https://wiki.unraid.net/Shrink_array

     

    or should I just buy a new hard drive. I might need the data storage anyway.

     

    HELP PLS - Inode allocation btrees are too corrupted

    in General Support

    Posted · Edited by Nebula

    Hello again.

     

    I'm back after long traveling with my family.

     

    New disk (DISK 3) is installed and precleared and it took almost 6 hours.

    Capture1.PNG.78f2a672929c67395e76d99ccc36f479.PNG 

     

     

    Now when I set Disk 1 to "no device" and chose new disk it's says DISK 3 missing and can't start up server due to wrong/missing disk
    Capture2.PNG.a03e9a31f34b24594a37688da9caf674.PNG

     

    Capture3.thumb.PNG.a075db9e462859b9e935198e0a0a75e0.PNG

     

     

     

    But if I go back to settings in first picture above its good to go but then I can't rebuild.

    I did som research and maybe I did something wrong installing the new disk. 

     

     

    Is it because Disk 3 is now a part of the array and there for I cant change it with the dmg Disk1?
    Should I have'd set Disk 1 to no device first and then change it with the new disk 3 (before preclear) followed up with preclearing, rebuild?

     

     

     

    HELP PLS - Inode allocation btrees are too corrupted

    in General Support

    Posted · Edited by Nebula

    IT WORKS !!!!!!!!!!!!!!!!!  Up and running with all data accessible

     

    First backup the missing data.

     

    I will upgrade to latest version after.

     

    Disk 1 still disabled but I will pull it out and install the new one I bought 2 weeks ago. I'll try format this later on and see how it goes

     

    image.png.460498884387169486ea8384faaffd88.png

     

     

     

    Thanks for help! Without you guys I was lost BIG TIME. 

    True community who helps and don't give a fuck!

     

     

     

    Thanks guys!

     

     

    HELP PLS - Inode allocation btrees are too corrupted

    in General Support

    Posted · Edited by Nebula

    Somethings not right here or I'm just a complete Noob regarding this unraid server.

     

    Look here under "shares"    It says array must be started to view shares  and text below says: array stopped - stale configuration

     

    1.PNG.004b19d605567baa03790d377fdefa2a.PNG

     

     

     

     

    Under Array options there is not even an stop bottom /take array offline - only reboot and power down

     

    2.PNG.2eb77685619c1a0c6d75190a961d163b.PNG

     

     

    Under array devices it still not active

     

    3.PNG.f20b1c2a59c97c4d146a3264ab71bd39.PNG

     

     

    Open for any ideas - don't know nothing about this

     

    Trying reboot again and we what happends

    HELP PLS - Inode allocation btrees are too corrupted

    in General Support

    Posted · Edited by Nebula

    Okay, I did first check - attach txt-file


    First check.txtCan someone take a look at this?

     

    Whats next step in this proces - guides leads me to this one. What to chose? https://wiki.unraid.net/Check_Disk_Filesystems#xfs_repair
     

    One of these?

     

    Syntax

    The filesystem to be repaired must be unmounted, otherwise, the resulting filesystem may be inconsistent or corrupt. For unRAID, start the array in Maintenance mode.

    xfs_repair [ -dnvLP ] device

    xfs_repair -V

     

    Should I try copy disk first?    "A possible method is using dd(8) to copy the data onto a good disk"

     

    HELP PLS - Inode allocation btrees are too corrupted

    in General Support

    Posted · Edited by Nebula

    On 5/17/2019 at 10:14 AM, johnnie.black said:

    I would first try to repair filesystem on the emulated disk1, and for now make sure to keep old disk1 intact.

     

    IMHO parity swap isn't really an option since if parity is really failing it will fail during the parity copy phase and abort, so if it comes to that might as well just try to replace disk1, maybe parity is not so bad despite the SMART report, and if it is the rebuild will at least continue skipping the read errors (but would obviously result in some corrupt data).

     

    Update

     

    Sorry guys, but I'm been away and still is until Friday this week.

    I will start repair filesystem when I'm back Friday and we see how that goes. Thanks for input johnnie.black 👍

     

    If this is the best solution to start with I'll try that first.

    HELP PLS - Inode allocation btrees are too corrupted

    in General Support

    Posted · Edited by Nebula

    8 hours ago, trurl said:

    The real question it seems to me is what size disks to get. No point in going for less than 4TB for each of the 2 disks, since you are going to replace a 4TB parity and a new data disk can be as large as parity. But it might depend on what we come up with whether you can go larger with both or not. Maybe you don't want to go larger anyway. And the original disk1 can probably be reused and assigned to a new slot after everything.

     

    Doesn't matter minimum 4TB but if 6 TB is better options for rebuilding data I take this instead.

    HELP PLS - Inode allocation btrees are too corrupted

    in General Support

    Posted · Edited by Nebula

    Hello,

     

    Server is stopped and shutdown for now. Going for 4TB disks and will buy two hdd for sunday. My question was more about the type of hdd but maybe it's not that important and they work in the same way. Some just keep telling me to use the NAS drive like WD Red but why, my hdd's don't run 24/7 so why pay more. They don't secure my data anyway if writes get corrupted.

     

    I will keep an eye on this thread during the weekend.

     

     

    Thanks for all input. You have been very helpful for now.

    HELP PLS - Inode allocation btrees are too corrupted

    in General Support

    Posted · Edited by Nebula

     

    Thx man, I really mean it THANK YOU! 👍

     

    Some good newz to me!

    I meantime waiting for my sentences from you, I found allmost the rest of the data thx to google on multiple accounts, but still missing some.... Really have been so damn secure about this data and protected this in many years (allways with one extra hdd data outside arrraws) using synology NAS, Win10 array and and now I wanted to test UNRAID and this happens. Maybe I'm a bit of noob and not read carefully how to set things up. I must admit the learning curve is a bit harder than Synolgy/Win10 server but it serve much much much better my needs as mediaserver.

     

    Its past midnight now, unfortunately I'm away the hole weekend and back again on sunday. Unfortunately I cant do anything before that, need to take care of other stuff before I go to bed. This array meltdown sets everything unhold!

     

    I will return on sunday and buy some couple of new hdd as well for this rebuild. Any hdd I should stay away from?

     

    Again thx for help

     

     

     

     

×
×
  • Create New...