Almost all files and folders deleted after latest update !!

Zitat von SeanMiddleton

After the update virtually all of my files/folders are no longer there. They seem to have been deleted.

If that were the case the forum would be flooded. Your files have not been deleted.

Zitat von SeanMiddleton

The Dashboard shows my HDD as now only 5GB used, whereas before the update I had used about 15GB (I use large HDD's).

Do you have your data on the system disk?

Zitat von SeanMiddleton

the machine has been a little odd

You specify, give us more details.

Zitat von SeanMiddleton

Why on earth did the OMV team drop Portainer ?

For all this.

omv6:docker_in_omv [omv-extras.org]

Zitat von SeanMiddleton

It was a superb Container management and App tool.

If it seems essential to your use case, you can continue using that tool. No one recommends it but no one prevents it either.

Zitat von SeanMiddleton

A very regressive move in my opinion ( I know I can still access it on port 9000)

In my opinion it is quite the opposite, a logical evolution that should be appreciated.

Zitat von SeanMiddleton

ANybody got any ideas what may have happened ?

If you don't provide more details it's hard to say. We don't see your screen.

Zitat von SeanMiddleton

I hope the latest update packages are not bugged and there has been a mass wipe of peoples data !

Definitely not. Your data has not been deleted.

Zitat von SeanMiddleton

All my data is (was ??) stored in \\ODROIDH3\odroidh3\ODROIDH3\ODROIDH3\storage ( as seen Windows) and /srv/dev-disk-by-uuid-3cce5dd9-f4ae-4d23-baf7-4b4ba7eb63ff/ODROIDH3/ODROIDH3/storage (as seen by Bitvise/Putty).

Before the update I had many folders/files in that location but since the update I now have only 4 folders.

If they were there before, I guarantee that they are still there, unless you have done something else yourself.

Zitat von SeanMiddleton

Again, since update, my Logitech Media Server Container has 'lost' all its preferences and no longer ses any music. The Container itself though is still working

The OMV Dashboard now shows File Systems as "Missing" and '"dev/mmcblk0p2 26.85 GiB"

I have no idea what has happened. Prior to the update all worked fine but during the update process the GUI stalled and I had to reboot Chrome browser.

Again some action done by you, the plugin or updates do not cause this.

Zitat von SeanMiddleton

I have just noticed that on the GUI File Systems tab what used to be my EXT4 data disk is now show as "Missing". Also, since Compose was installed the "SharedFolders" tabe now has a compose folder listed and there are two additional folders. The page looks like the attached:

So, it looks like the update has somehow rearragnged Shared Folders and File Systems

This is weird. I have no idea where to go from here

No update causes a file system to disappear. Neither update causes a new "compose" folder to appear anywhere.

You have followed a guide or you have read something somewhere and you have followed it with closed eyes.

I recommend that you read the procedures, in the first publication of this thread you have them all.

Thema

omv-extras 6.3 / openmediavault-compose 6.7

I just released a new version of openmediavault-omvextrasorg 6.3 and openmediavault-compose 6.7.

IF YOU DON'T UNDERSTAND DOCKER WELL, WAIT to FOLLOW THESE DIRECTIONS UNTIL THEY ARE IMPROVED!!!

• The docker, portainer, and yacht installs have been removed from omvextras. You will only enable the docker repo in omv-extras now.
• The docker install has been added to the openmediavault-compose plugin.
• If you were using portainer created by omv-extras, you should be able to use the "add example" option the

…

ryecoaaron

29. Mai 2023

If you have a problem you want to solve maybe someone wants to help you. But that attitude of blaming OMV or OMV updates is not going to win you many friends. You can start by saying exactly what you have done so far.

Zitat von SeanMiddleton

I'm not blaming anybody. I'm simply stating the facts. Which are that all was perfectly fine. I did the update then it wasnt fine.....simple as that. I havent done anything else whatsoever to the server; nothing at all, other than restart it.

I'm sorry. That's impossible. As I already said no update unmounts file systems, deletes folders or creates new shared folders.

A good start might be to change the title of this thread to something like "After the last update I did something that broke my system. Help please."

Perhaps this is a coincidence. Have you considered that, maybe, your hard drive failed?

Have you checked under Storage, Disks, to see if your drive is still recognized?

(And)

Have you checked Storage, SMART, Devices, (and the stat's button) to see what SMART stat's are available for the drive? (This assumes SMART monitoring is enabled.)

Zitat von crashtest

Perhaps this is a coincidence. Have you considered that, maybe, your hard drive failed?

That would not create a shared folder called "compose" as the OP says.

Although it could be that this coincidence has also occurred.

Zitat von SeanMiddleton

Why on earth did the OMV team drop Portainer ? It was a superb Container management and App tool. A very regressive move in my opinion

It wasn't the OMV team. It was only me. omv-extras is third party. I didn't drop it either. I moved it to the compose plugin which I think is a superb, native-OMV container management and app tool. It takes less than three minutes to add the functionality back that you had in omv-extras. I made a video and posted it on the first post of the upgrade thread omv-extras 6.3 / openmediavault-compose 6.7

Zitat von chente

Although it could be that this coincidence has also occurred.

Post #5 shows that the user has 2 file systems, total. One must be the boot drive, or the OMV instance could not exist. The other filesystem appears to represent a missing, but referenced, data drive. (I can't see how the compose plugin change could be related to a missing filesystem.)

Setting the compose update change aside:
Determining what happened to the missing filesystem seems to be the key issue in determining "where" the user's data went. I don't believe his data was "deleted". I believe it's on the 2nd drive, with an EXT4 filesystem, that is now missing.

That's all that is possible to know until the user responds with more information about the missing drive.

Zitat von SeanMiddleton

On the face of it it appears to be a problem with the HDD.

I agree. I'm going to assume that you've reviewed this hard drive before and that it produced normal SMART stat's versus the errors that it's currently showing.

Zitat von SeanMiddleton

So, I guess I need to figure out a way to examine the HDD further (any ideas beyond Gparted ????)

If it was me, I'd go with the OEM's drive -> diagnostic tools. They know their drives better than anyone else.

Wether you use the Linux or Windows Sea Tools package wouldn't matter. The results should be the same so go the route you're most familiar with - there's no point in adding guess work at this stage. If you're not very familiar with Linux, it's easy enough to physically remove the drive and temporarily plug the drive into a Windows client SATA port. (For testing, I've connected drives out the side of a PC with the cover removed.)
In any case, take note that some OEM drive tests can be destructive. The tool(s) should tell you this before you use them.

If you want to try to recover data, -> Spinrite (a paid product) is the only tool I'm familiar with but it requires a good bit of time to run which means it would work best in the early stages of drive failure. Spinrite works, primarily, at recovering data from defective magnetic media. In your case, while it's pure speculation based on the SMART errors, I'm guessing there may be a problem with your drive's interface board. Spinrite can't do anything about that. In any case, I would do the OEM tests first, before considering the purchase of Spinrite.

Frankly, the above is me being optimistic. I hope you have backup because, while I don't like being the bearer of bad news, I think you're going to find that the drive is toast. Given the SMART responses, it doesn't look good.

Zitat von SeanMiddleton

What is weird about all of this is that this problem occured immedaitelya fter the Update. I fully accept that this could be a pure coincidence, but to me the probability of such a simultanious event is remarkably low.

Do you mean, immediately after the update or immediately after a reboot?

Here's what you need to consider:
- The update couldn't fry your drive. Unexpected things might have happened with Docker, but that would be the extent of it.
- Is it possible that your boot drive is corrupted in a very specific way and this is a manifestation of that? I suppose it's possible but that's a real long shot, a light years distant remotely possible.

Testing the drive with the OEM's tools should tell you, definitively, if your drive is OK, dying or dead. I believe this is where you should start.

.

Zitat von SeanMiddleton

Well, checked out the HDD using Seagates utility and it is well and truly trashed. EXOS 18TB with less than 5000 hours use ! It is about a year old and supposedly has a 5Y warranty. Lets see.........I have read a few reports online re poor reliability of EXOS srives. Seems to have some truth in it. Thanks to everyone for your help and support

It's sad to read this, I hope you have a backup, or if not, you can recover the data. There are applications that could help you. The less you touch the drive, the better chance you have of recovering the data, if that's even possible. Good luck with that.

In my experience and my humble opinion, the drives that have given me the best results are the WD RED NAS class and CMR type.

Another point to take into account is to always have a UPS, this avoids forced shutdowns, they are very negative for mechanical drives.

Zitat von SeanMiddleton

Well, checked out the HDD using Seagates utility and it is well and truly trashed.

While I suspected as much, I'm sorry to hear that. Hopefully they'll replace the drive. Note that while their warranty may require them to replace the drive, you might not get a new drive. It might be an OEM "refurb".

For future use:

Back Blaze publishes studies of -> drive failures and longevity. You might give some of their doc's a quick read and think about picking a replacement from one the models they have found to be reliable. (If one of them is on sale. )

Also, you might want to set up -> server notifications. Server notifications will provide a "heads up" if SMART detects something out of the ordinary. Generally, most drives will give at least some warning before it's too late.

-> Full data backup is not difficult or very expensive to implement. A local rsync disk-to-disk backup is easy to set up and recover but there numerous more sophisticated backup options that might better fit what you may want to do. A forum search might turn up something you'd be interested in.

Again, regrets.