(maybe due to a voltage drop due to drive spinup)
This doesn’t go up for a ssd / usb sticks so it could be something else.
(maybe due to a voltage drop due accessing/activating) the SSD/USB.
I think it’s just given as an example…
oke i understand 
Yeah or any other event that udev recognizes as partition removal…
1 Like
@ volumio
Thank you very much for quick reviewing and finding clues even though my info is not that precise. Thank you.
I’ve never had a problem with my HDD since I chose ext4 as format.
Today, after updating to Volumio 3.251, all my music libray is gone 
Don’t know if it’s actually deleted or is just not visible for some reason.
What can I do to check?
Fortunately I have a backup of the libray on my pc, but before I start copying the files I’d like to know if a deletion is actually happened or not
EDIT: solved by adding the UUID and path in /etc/fstab 
(the line was gone)
#Raspberry Pi fstab
proc /proc proc defaults 0 0
/dev/mmcblk0p1 /boot vfat defaults,utf8,user,rw,umask=111,dmask=000 0 1
tmpfs /var/log tmpfs size=20M,nodev,uid=1000,mode=0777,gid=4, 0 0
tmpfs /var/spool/cups tmpfs defaults,noatime,mode=0755 0 0
tmpfs /var/spool/cups/tmp tmpfs defaults,noatime,mode=0755 0 0
tmpfs /tmp tmpfs defaults,noatime,mode=0755 0 0
tmpfs /dev/shm tmpfs defaults,nosuid,noexec,nodev 0 0
UUID=f62fc3e8-6c28-469d-9136-cf635af0b88d /media/MUSICA ext4 defaults 0 2
Last line is the one I added
Library is not erased: simply the HDD is not mounted.
See: V 3.251 - mounting USB drive problem - #4 by volumio
1 Like
UPDATE: This new release has a fix for this problem of erased drives.
I hope and think that we will never see it happening again.
2 Likes
Yeah, take a look at my “EDIT” in the previous post.
Don’t know if I chose the best way to fix the problem, but I edited fstab to make the system recognize the unit.
1 Like
Actually, doing that could have been dangerous with the previous release. Now it’s not. I suggest to remove this line when you do the next update
@volumio I am freaking out right now. All my files are gone, almost 3TB of music…
I am running a Rpi4 with a 3TB HDD which has been working flawlessly for several years. Volumio 3.179 on the Pi. The Pi is connected via USB to a MiniDSP SHD as preamplifier.
I disconnected the USB cable from the Pi so I could work with the SHD on some filters, when I reconnected this cable to the Pi, Volumio started to update the music library (which is ok), however it finished in a moment and it only has 400 MB of music. I connected my HDD to my computer just to get the nastiest surprise: all my music is gone except 10 folders or so (those 400 MB). WTF???
At this point I am not sure what happened, is there a way to get it back…?? I don’t think so, it does not seem to be just the cache - the HDD itself is almost empty (and no backup! This is years and years of rips from my own music).
Can someone please help? I am gutted.
Edit: I did not update Volumio recently, I am on this build since it was released - I take my time to update just to avoid issues.
Edit 2: logs here: http://logs.volumio.org/volumio/orQSNz2.html
Was the rPi powered when you connected or disconnected the HDD, as It sounds like a power failure.
What you can try is:
- shutdown the rPi.
- Disconnect the HDD
- Connect the HDD to your Windows PC
- Right click on the disk
- Select Properties => Tools => Check => Scan drive
And do update, as the current version is pretty stable.
Thanks for replying @Wheaten
-
yes the Pi was powered, but please note I did not disconnect the HDD from the Pi. I disconnected the USB cable between the Pi and the preamp, to connect it to my computer.
-
I performed a check disk as you suggested and it found errors. The log has been uploaded here: HDDkaput - 2e788c31
It worked, partially. It recovered 39 GB of data, nowhere near the almost 3TB that seemingly are lost forever
Checking the Volumio logs you can see the now almost empty HDD:
Filesystem Size Used Avail Use% Mounted on
/dev/mmcblk0p2 2.2G 855M 1.3G 41% /imgpart
/dev/loop0 375M 375M 0 100% /static
overlay 27G 1.4G 25G 6% /
devtmpfs 1.9G 0 1.9G 0% /dev
tmpfs 1.9G 4.0K 1.9G 1% /dev/shm
tmpfs 1.9G 13M 1.9G 1% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
tmpfs 1.9G 0 1.9G 0% /var/spool/cups
tmpfs 1.9G 16M 1.9G 1% /tmp
tmpfs 20M 28K 20M 1% /var/log
tmpfs 1.9G 0 1.9G 0% /var/spool/cups/tmp
/dev/mmcblk0p1 61M 51M 9.2M 85% /boot
/dev/sda1 2.8T 397M 2.8T 1% /media/WD3TB
What could have happened…? It’s not like I disconnected the HDD carelessly, the only thing I can think of is that Volumio suddenly lost the output source (as I disconnected the USB cable from the preamp), and this might have triggered something causing the data loss? A very long shot, but honestly not sure what else could it be. The USB cable between HDD and the Rpi was not removed, and the Pi was not restarted or powered off. Each device is in a separate power strip which was powering other devices and they remained powered while this happened.
Seems the location table got corrupted.
As thumb of rules Never plug an unplug active USB devices on a powered rPi. It will/can cause issues. For the same reason Windows has a feature to “Safely remove USB Devices”.
In your case it seems that unplugging a USB device, caused a dip or swell in the voltage regulation of the rPi, for which the disk paid the penalty.
Is your HDD powered by the rPi or an external PSU?
Powered by an external PSU. It’s a 3’5 inch WD drive.
Always remove and unmount your external drives before a update
Is my 2 cents advice.
Ps you can always try to Search on files level and recover it That way.
The last thing you can do is trying to recover the content with a professional tool, depending on your disck partition, like for FAT: RecoverIt
But I have never done this, as I only use a NAS for my Music to avoid loosing data.
Thanks @Wheaten this was my next attempt. I found an old backup from 2020 which obviously is (very) incomplete, but that’s something.In the meantime will with a recovery tool.
Thanks again, appreciated.
Which version included the reduction of possible data loss, as I recall there where some improvements done on this point, as ManuCV is still running on V3.179. (version > 3.251)?
1 Like
I am very sad to say that this happened also to me. Imagine hundreds of hours of editing tags, renaming directories, creating album art pictures and so on. It is lost. 1,2TB of music. 4 years of effort. Really great!
To run recovery tools will take hours. An even if I will manage to get files back I cannot be sure that they are not disrupted. Many thanks.
1 Like