Assuming I unmount first?
Code
root@omv-server:~# mdadm --stop /dev/md127
mdadm: Cannot get exclusive access to /dev/md127:Perhaps a running process, mounted filesystem or active volume group?
Filesystem Mountpoint Missing
-
- OMV 5.x
- claredad
-
Assuming I unmount first
Yes sorry
-
Yes sorry
Im disappointed in you
Unfortunately the option to unmount is greyed out. Is this Do I need to remove the shared folder first? The other partition with a share on it (my Downloads parition), has a share on it too, and I cant download that either. My backup USB HDD can be unmounted, and its doesnt have any shares.
-
-
Unfortunately the option to unmount is greyed out.
I would rather not do any of this from the cli, the fact that you cannot unmount the array suggests there are underlying issues as all of this can be done in the WebUI. I would therefore suggest that Option 2 is the way forward.
Do I need to remove the shared folder first
You can unmount a file system without deleting shares associated with it.
-
You can unmount a file system without deleting shares associated with it.
From GUI you can only unmount, if the FS is not referenced. So you need to remove shared folders first.
-
From GUI you can only unmount, if the FS is not referenced. So you need to remove shared folders first.
I'm having a bad day, my concern is Raid Management doesn't appear to be working as it should. I still think the best option is to completely remove it and start again. -
-
I'm having a bad day, my concern is Raid Management doesn't appear to be working as it should. I still think the best option is to completely remove it and start again
So if that's the best option in your opinion, what are next steps?
-
Why not remove shared folders (NOT the content), unmount and proceed as planned?
-
Why not remove shared folders (NOT the content), unmount and proceed as planned?
That's what I'm assuming, but have made missteps before, so want to make sure I'm right and not going to detonate the server 🙈
-
-
-
That's what I'm assuming,
macom right that's the way proceed or at least to start, but I'm sure you have to remove SMB first then the share.
-
Display More
madam --stop /dev/md127
mdadm --fail /dev/sdc
mdadm --remove /dev/sdc
The above will hopefully work and show the raid with just the two drives /dev/sd[bd] to confirm that run mdadm --detail /dev/md127 but you may get an error on the --fail
OK, so I eventually for the first command to work, but the second gives me this error:
Coderoot@omv-server:~# mdadm --fail /dev/sdc mdadm: /dev/sdc does not appear to be an md device -
-
OK, so I eventually for the first command to work, but the second gives me this error:
I said it might, #49 and if the third command fails then as far as mdadm is concerned sdc does not belong in the array, which should mean you can wipe that drive and when complete use recover in raid management to add sdc back.
EDIT: However, I have reservations, from #46 mdadm --detail /dev/md127 that shows the following at the end;
Number Major Minor RaidDevice State
it sees sdc as faulty
-
Display More
I said it might, #49 and if the third command fails then as far as mdadm is concerned sdc does not belong in the array, which should mean you can wipe that drive and when complete use recover in raid management to add sdc back.
EDIT: However, I have reservations, from #46 mdadm --detail /dev/md127 that shows the following at the end;
Number Major Minor RaidDevice State
it sees sdc as faulty
OK. Is there a way to confirm that sdc is faulty? Of do I just need to buy a new drive?
-
Is there a way to confirm that sdc is faulty
Have a look at SMART and run an extended test on the drive.
-
-
Have a look at SMART and run an extended test on the drive.
I havent done one of these before, so hopefully this is right. It ran over night, and this is the information from the Extended Information tab
-
I havent done one of these before
Replace the drive!! According to a search that's an Enterprise Class drive
are they all the same? I use WD Red's NAS or Seagate Ironwolf NAS drives, in fact I'm about to replace two of mine as they are over six years old. Whilst they are reporting no errors (unlike yours) I would rather replace now and repurpose the old ones. -
Replace the drive!! According to a search that's an Enterprise Class drive
are they all the same? I use WD Red's NAS or Seagate Ironwolf NAS drives, in fact I'm about to replace two of mine as they are over six years old. Whilst they are reporting no errors (unlike yours) I would rather replace now and repurpose the old ones.Yes, all three are the same. So you think overtime I should replace all three? Ill replace the first one now for sure.
-
-
Yes, all three are the same.
most home users, me included wouldn't spend that sort of money, for the cost of that drive I could build a new system 
and still have some money left over for a few beers. But to confirm I'll tag crashtest to check the pastebin output, but IMHO that drive should be replaced.So you think overtime I should replace all three
Not necessarily but you do need to keep a check on the SMART output and run SMART short tests once a month
-
most home users, me included wouldn't spend that sort of money, for the cost of that drive I could build a new system and still have some money left over for a few beers. But to confirm I'll tag crashtest to check the pastebin output, but IMHO that drive should be replaced.
Not necessarily but you do need to keep a check on the SMART output and run SMART short tests once a month
Well I didn't pay enterprise money for them 🙈. Same as you, I couldn't afford that. I got them for less than NAS HDD costs.
I'll set up SMART monitoring on all drives now.
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!
