best practice to change Datadisk (Hardware Crash)

  • hi all,


    need some tipps plz.


    my main Datadisk is going down (today some services dosen't work, and then the shock: sdb is going down - could reup it as sdd but, its time for a new disk ...)


    what is the best practice to do?


    cloning the disk by using a other system and tools like hdd clone?

    build the new one in and copy everything?

    whats about the lable? most of my services connect to the disk by the lable name "disk-by-lable-nas1" so the new disk need the same lable.


    thx and regards

    draddy

    ___________________________
    OMV5@AsRock j3455 8GB RAM

    • Offizieller Beitrag

    The problem with cloning a known bad disk, is it is very likely the clone is going to be bad as well, especially if you have services not working, etc.... You should have cloned (or backed up) a working disk long before now.


    Yes, you'd need to either have the same label, or adjust any volume to point at a new location (which would probably be a pain)

  • the data will not be that big problem, have backups of important things.


    i discovered it when nextcloud stop working (nextcloud data are saved on that disk) - so a copy job would also ok for me.


    how can i manage that lable part? i can't just build in the new disk and name it NAS1 i think ;)

    on windows i would just add the new one, copy all data, disconnet the old one and set drive letter of the new disk to that from the old one^^

    ___________________________
    OMV5@AsRock j3455 8GB RAM

  • i can't just build in the new disk and name it NAS1 i think

    You can: e2label /dev/device new-label-name-here


    Something like: e2label /dev/sdX1 NAS1 where X is your drive letter

  • But this will not change the mountpoint

    You can always edit the config.xml, ;)

  • First a DISCLAIMER: Do this at your own risk. This steps aren't mentioned from devs/moderators/experts (never seen anyone mention to do it) since there is a "symlink plugin".

    This requires some knowledge and understanding of linux commands and also, some trust of what you're doing.


    But it's doable: change the mount point to label instead of UUID (PATH, ID, etc)

    This assume you already have the drive recognized/mounted on OMV.


    I'll have this as a Spoiler, since it's not a procedure that I think people should use unless are willing to take the risks.

    Nonetheless, knowledge is power.



    Good luck....

  • hi,

    first, THX will try later.



    1 question, my damaged HDD got Lable NAS1 - so i just put in the new one, copy all data to the new one, shutdown, plug off the old on, restart and follow your instructions, right?

    ___________________________
    OMV5@AsRock j3455 8GB RAM

  • hi,

    first, THX will try later.



    1 question, my damaged HDD got Lable NAS1 - so i just put in the new one, copy all data to the new one, shutdown, plug off the old on, restart and follow your instructions, right?

    The way I see it, yes.


    I just edited the last step, so to make sure you're data is seen on the new mount.

  • hi all,


    1st, system is online!


    i just try to clone that HDD with HDClone - the tool called some errors on 6 Sectors and i decide to just ignore that.

    after change the old to the new HDD the nas starts as normal, all data in place, all services work - i think i will see if somethink wrong with it the next few days, but all in all it looks consistent.

    so again, thx all :)

    ___________________________
    OMV5@AsRock j3455 8GB RAM

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!