I tried to perform an update after installing a new system on a new SD card.
Initially, the system made a backup on the new system, which had nothing set up, not even initial settings.
The process was painfully slow (the SD card is an original Pi 15GB), and eventually, the system began restarting.
At that point, errors related to remounting started appearing.
Unfortunately, I was unable to restore the functionality of the card.
This is already the second card I’ve damaged because Volumio system. At first ever Volumio install I didn’t know during the initial installation that I needed to wait for the SD card partitions to expand, so I damaged one card thinking something was wrong. It turns out I just needed to wait.
I don’t understand why this expansion can’t happen after the web GUI is up and running. So i can choose to do so.
Overall, the management of SD cards isn’t ideal, and I don’t understand the logic behind creating a backup before update of a newly installed not even configured system.
SD card corruption can be frustrating, and we’re here to help you resolve this effectively.
Key Details About Volumio’s System:
Auto-Resizing Data Partition:
Volumio employs a SquashFS-based root system, which is read-only to enhance stability. During the first boot, the system auto-resizes the data partition to utilize the full capacity of your SD card. This is critical for storing user data, configurations, and updates. If this process is interrupted (e.g., due to power loss or an incompatible SD card), it may result in issues like the one you’re describing.
Compact System Image for Downloads:
To make downloads manageable for users, the Volumio system image is kept intentionally small. The resizing mechanism during the initial boot ensures that the system dynamically adjusts to the available SD card size while minimizing the initial download size.
Initial Boot Messages:
During the initial boot process, important system messages are displayed on the attached screen (if your device supports it). These messages include details about the auto-resizing process and potential errors if something goes wrong. These on-screen messages are critical for diagnosing any problems that occur during setup and may have been missed. If possible, consider rebooting the device with a screen attached to monitor these messages.
Risks of Improper SD Card Removal:
It’s important to note that removing the SD card while the Raspberry Pi is powered on or actively using it can cause:
Damage to the SD Card: Corruption of data, unresponsiveness, or even physical wear due to sudden disconnections.
Damage to the Raspberry Pi Electronics: Electrical surges or unexpected discharges from improper SD card removal can harm components of the Raspberry Pi, potentially leading to hardware failures. Always ensure the device is powered off before removing the SD card.
Steps to Resolve and Prevent Issues:
Reflash the SD Card:
Download the latest Volumio image from our official downloads page and reflash your SD card using a tool like Balena Etcher or Raspberry Pi Imager. Ensure the SD card is properly formatted before flashing.
Check SD Card Integrity:
SD cards are prone to wear, especially under heavy usage. If the issue persists, try using a new, high-quality SD card from another reputable brand.
Monitor Initial Boot:
Attach a screen during the first boot after flashing. Carefully observe the messages displayed, particularly those related to the partition resizing process. These messages may provide clues about any potential problems.
Backup Your Data:
To safeguard against future issues, create regular backups of your playlists, settings, and configurations. This makes recovery much easier in the event of unexpected problems.
Update Safely:
Use a stable power supply to prevent interruptions during updates.
Ensure sufficient free space is available on the data partition.
Avoid Removing the SD Card or abrupt removal of power While in Use:
Always power off the Raspberry Pi properly before removing or replacing the SD card. This simple precaution can prevent both data loss and hardware damage.
Update Safely:
Ensure a stable power supply during updates.
Confirm that the data partition has sufficient free space before updating.
Community Support:
Feel free to provide additional details, such as your device model, Volumio version, and specific symptoms encountered. This information helps us offer more tailored advice and investigate potential trends.
Thank you @nerd for your very detailed response. Unfortunately, both SD cards are fried; nothing worked for them. Neither reformatting nor deleting partitions… they’re simply destroyed.
I understand my mistake the first time because I didn’t wait. However, the issue with the update is unclear to me.
But it doesn’t matter; it’s not the end of the world. I just wanted to point out that for new users, the current system—where an upgrade is offered during the initial setup and then the backup process starts—may not be optimal.
On the other hand, perhaps you could include a small amount of space for user data in the initial image so that the web interface or mobile app can show when card expansion is in progress.
Because many users, idiots like me, don’t even connect a monitor; we just expect the web, mobile app, or SSH to work when setting up things like Volumio.