Device or resource busy
Means it's running, apt install nmon
Device or resource busy
Means it's running, apt install nmon
root@NAS:~# apt install nmon
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
linux-image-4.19.0-16-amd64 linux-image-4.19.0-17-amd64
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
nmon
0 upgraded, 1 newly installed, 0 to remove and 13 not upgraded.
Need to get 67.2 kB of archives.
After this operation, 179 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian buster/main amd64 nmon amd64 16i+debian-2 [67 .2 kB]
Fetched 67.2 kB in 0s (520 kB/s)
Selecting previously unselected package nmon.
(Reading database ... 75770 files and directories currently installed.)
Preparing to unpack .../nmon_16i+debian-2_amd64.deb ...
Unpacking nmon (16i+debian-2) ...
Setting up nmon (16i+debian-2) ...
Processing triggers for man-db (2.8.5-2) ...
Alles anzeigen
now type in nmon you'll be greeted with a menu, hit d on the keyboard and wait, it will then display drive information on your system, post a screen shot
Blinks in this condition
are you using W10 and putty
yes, right
Ok to stop nmon hit q on the keyboard and exit putty, on windows search type in cmd this will display Command Prompt, left click and run as administrator. Type in ssh root@<ip address or hostname of omv> hit enter now it will ask for the root password just like putty
Once logged into OMV run nmon again and select/hit d and post a screenshot
OK, done. Looks the same as before
Looks the same as before
Yes but without the odd borders, OK, you have a hardware problem somewhere;
1) sdf which is part of the array is the only drive being read
2) sdc which is the one you added is not being written too
3) md0 I would expect a message 'disk busy not available'
4) Transfer Rate of 1.5 sec would support a hardware issue
Where do you go from here cos at this moment in time you have a good chance of losing everything unless you have another drive large enough to copy your data to whilst it's stuck in recovery.
Without a drive the only option I can suggest it to shutdown and unplug sdc and restart, hopefully the raid will come back as inactive, but I have no idea if that will work. If it did that's solvable, but you then have the issue of sdc, it can't be plugged back into OMV unless all the other raid drives are disconnected, whereby it could be wiped, reconnect the raid, which will hopefully remain clean/degraded and will not re add sdc.
Or you purchase some temporary cloud storage copy everything to the cloud, rebuild and copy it back.
The most convenient way would seem to be a temporary cloud, right? Do you have any idea of the costs? The space needed is about 3 TB
Costs are neglectable but consider you upload speed an calculate the time it takes to upload 3TB of data.
If you do not live in the nowhere it is better to get a nice USB hard disk in the next store you can use for backup later on. And backup via USB is mch faster than over the internet.
OK, please tell me the best way to recover the data and I' m doing what you advice me.
Does data recovery have to be on a single hard disk or can I split it up over several hd?
Thank you
Not much to add, to what geaves said, but I would not go for a cloud storage but grad a usb disk at the next store.
But check yourself how long the upload takes given you upload bandwith: https://www.omnicalculator.com/other/data-transfer
for me it would be > 250 hrs (10 days)
For me 350 hrs
Do you mean if I have access to the shared folders again? If it's so, no: I can see them, but I have not access to them
but I have not access to them
So you can see them in File Explorer but they won't open
Yes, I see the three shared folders but I have no access to them.
Yes, I see the three shared folders but I have no access to them
Then you're not going to be able to copy the data via SMB, this further confirms the hardware problem, even when a raid is rebuilding the data is still accessible.
Do you have WinSCP installed on W10
Can you access the files from the cli (I have not too much hope, but nevertheless try it)
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!