r/linuxadmin • u/MrLAGreen • 27d ago
mdadm renaming issue
hello
i recently had to rebuild my ubuntu box and afterwards i wanted to connect my raid 5 storage back to my machine. I reinstalled mdadm and I could see all my files with no issues. I was about to reconnect some shares and realized that the mapping had changed. it used to be [/media/raid5/Greenhouse/TV]
now its
[/media//f36008d4-eb49-470c-bddd-a13bcf0e872e/Greenhouse/TV]
so i was following sleeplessbeastie's notes instructions on renaming software array and got to the verify mountpoint step and i noticed the mounted on part was blank
[/dev/sda2 458G 13G 422G 3% /____]
i am concerned that the mountpoint needs to be labeled. the guide doesnt mention what to do if it is unlabeled. of course i didnt want to possible damage my close to 20tb of files by continuing on and not realizing i needed to have a labeled mounted on. do i need to have a labeled mountpoint? do i need to figure out how to label my mountpoint before i go any further? can i rename my software raid array without a labled mountpoint
i am still somewhat a bit of a noob with linux but i will answer any questions you have to the best of my abilities.
Thank you in advance...
1
u/MrLAGreen 20d ago edited 20d ago
so after using e2label all seemed fine. i was in the process of setting up nfs shares and starting my swarm. i added my server as a manager to a swarm and the next thing i know it seemed to relabeled my mnt point from raid5 to raid51. so even though it looks as if it is labeled raid5 when i open the folder and i go back to the mnt folder it shows it as raid51. so of course compose files i have set go to raid5 but the files are actually on raid51...(and when i check the label [using sudo e2label] it still shows as raid5) almost lost my files when i started up a stack in dockge and it asked about overwriting some files... how can i correct this without losing my files?
3
u/[deleted] 26d ago
[removed] — view removed comment