Open MrRedness opened 6 years ago
I just remembered that ubuntu would not even show my OSes (even though it showed the data partition was over 50% full). It did though show my boot partition fine. Windows only detected the boot partition (because the other one is linux) and it asked to search for issues, but none where found.
Also, if it helps, my sense hat LEDs did not go blank after the rainbow screen, as they usually do after berryboot loads.
Hello, export the images that you need + the data and write a fresh berryboot installation
Export from where? Ubuntu? I can't get into berryboot. Also, I already backup up the sd with windisk32imager and restored an older version that I backup up. I had to reinstall some things, and my documents are still not recovered, but I think I am better now.
I've had the same problem with a fresh install of berryboot-20170527-pi2-pi3.zip on two different RPi3B v1.2 with two different 32GB SD cards. I've tried to troubleshoot using the disc rescue option from berryboot and also http://fasterland.net/raspberry-berryboot-fixing-cannot-find-data-partition.html. But that didn't seem to be a consistent fix. Looking at SD on an Ubuntu box with gparted gives the following:
I've tried various tools to fix the unrecognized partitions, but get 'bad superblock' and other errors. At first I assumed I had a bad SD card, but I when I tried doing this with a new card over a VPN I got the following,
I ordered a 16GB card to see if that changes things, but haven't received it yet.
To follow up on my previous post. I reinstalled the SD car that only showed a FAT16 and unknown partition (second image above). It gave me the berryboot install screen so I asked it to install berryboot on the SD card. It went through the creating EXT4 partition process then gave:
with the same gparted output as before (one FAT16 and one unknown partition)
Error formatting data partition is likely a write error (as in broken SD card). Think you can see exact error by pressing ctrl+alt+f2, logging in as root, and typing "cat /tmp/debug"
So I can't see the far left of the screen so what I see is incomplete, but here it is
tener thread started
tble tmpfsspace: 375.672 MB
ng keymap ..
ng keymap ...
cords in
cords out
cords in
courds out
at: warning - lower case labels might not work properly with DOS or Windows
1.42.12 (29-Aug-2014)
mounting /dev/mmcblk0p2 on /mnt failed Invalid argument
I got a new 16GB SD card and had no problems setting up berryboot. To be clear I tried two different 32GB SD cards and had the similar issues. I have had no problem with partitioning or using these cards after I've cleared the partition table created by berryboot. As a result I think there's a bug with the install.
Thanks, maybe I will get a new card for Christmas. Hopefully they will fix the issue in the next update.
If you get the issue, and you want to re-install your os, you can: (Optional) 1. Backup your sd card - https://thepihut.com/blogs/raspberry-pi-tutorials/17789160-backing-up-and-restoring-your-raspberry-pis-sd-card
Wipe your sd - https://www.youtube.com/watch?v=-Z9k3FxexeI or https://www.youtube.com/watch?v=8ae2aWYv_iI
Install your new os - (assuming it is a img) - https://computers.tutsplus.com/articles/how-to-flash-an-sd-card-for-raspberry-pi--mac-53600
Install your new berryboot - download zip from http://www.berryterminal.com/doku.php/berryboot
Try https://github.com/maxnet/berryboot/issues/444 first, it is the most promising, if not, try something else listed above.
If anyone else has a suggestion, please comment.
Hello!
I have the same problem. It seems like the partition was badly damaged. I might go for investigations.
Hans
That was my experience. I seem to have destroyed two 32GB microSD cards. I tried reformatting them multiple times and they always reverted to a corrupted state.
Hello,
I have made a small analysis of the two USB Memory Sticks. The first USB Stick contains the destroyed Filesystem and the second USB Stick contains a new Installation. Resultat is that the damaged Filesystem is completly clear, but why? Bot are 8GB and were prepared with BerryBoot on Ext4.
Is there are a bug with Ext4 and Trim?
Harddisk5/Physicaldrive5 = destroyed Filesystem after third boot Harddisk6/Physicaldrive6 = working BerryBoot installation
Is there are a bug with Ext4 and Trim?
More likely a bug in the firmware of your USB stick. But if you suspect trim, try disabling it by selecting file system "ext4 (no trim/discard)" during formatting.
My USB Stick is not support Trim but I used formatting Ext4 (with Trim). I think there no negative effect. I will test Ext4 (no Trim/Discard).
I have install an Raspberry Image over "network share" but whats the way to go back to the standard Window for installing images ?
My Images where installed over network share dont want to boot with "Ext4 (no Trim/Discard) "Partition
Sorry, don't understand the question.
Hello maxnet. Ok, I was installed with BerryBoot my Raspberry Images "2017-11-29-raspbian-stretch-lite.img" and a lot of other on my clean formatted USB Stick with Ext4 (no Trim/Discard) The source of the image file was my NAS Storage. The Image does not boot, it calls an error (Image file is ok without error). So i want new install an Image from the internet and I can not open the standard Image tree, it loads all time my source on my NAS.
In the "add OS" window, press the "network settings" button. Remove your NAS repository there.
Did it work?
Thank you maxnet for the solution! Thank you josephdfarkas for the demand.
I have testet the BerryBoot installation very often on two 8GB Sticks, all time it destroy the Filesystem. I have testet at last an "Platinum 16GB Stick" and there wirks great. Very Strange.
All of us as a community should create a compatibility / incompatibility list
Best Regards Hans
Please help everyone with:
Title: Berryboot 2.0 compatible and incompatible list https://github.com/maxnet/berryboot/issues/471
Just for reference (I can post elsewhere if needed) : this error "cannot find your data partition" happened to me when I updated from Raspbian Jessie to Stretch, from within the image. It seems that BB does not support this ? At least in the 2016.11 version I had.
Anyway, the error was resolved by updating BB to 20180929 (copying .zip content to SD card). T-I selected "use existing disk" as my image location, and BB found my image and was able to boot from it.
So thanks for the work, I guess 🙂
Just for reference (I can post elsewhere if needed) : this error "cannot find your data partition" happened to me when I updated from Raspbian Jessie to Stretch, from within the image. It seems that BB does not support this ? At least in the 2016.11 version I had.
Anyway, the error was resolved by updating BB to 20180929 (copying .zip content to SD card). T-I selected "use existing disk" as my image location, and BB found my image and was able to boot from it.
So thanks for the work, I guess 🙂
Thanks you very much @Jaxom99 ! That saved me a lot of time! Found this thread via google (my berryboot suddenly stopped working) and just copying the newest version to my sd-card did the trick! My PiDrive was recognized correcty afterwards and "use existing disk" worked perfectly to start my NextCloudPi again. Thanks a lot!
I have always loved berryboot for it's flexibility, but I have already got this issue a lot. I got this issue a few months ago, but I think I ended up getting access to the settings and then running partition recovery. First, yesterday, my Raspberry Pi 3 asked to run fsck. It ran and then let me access the Pi fine. Next, all yesterday, when ever I tried to reboot the Pi, I had to run fsck after selecting Rasbian (the first time it asked me before it gave me the list of OSes). This morning it asked me again to run fsck before listing the Oses, but instead of finding lots of errors, it simply did nothing. It then showed me a message "Cannot Find Your Data Partition" and then it takes me to an emergency terminal where I can't even reboot. I tried following this guide (http://fasterland.net/raspberry-berryboot-fixing-cannot-find-data-partition.html) on ubuntu, and even after I changed the directory, it still did not work. Instead it told me that the partition had no capacity (even though file manager said it had some free space and some used space out of the 32 gigs) or that I need to reboot because it was in use. I had 5 OSes installed and many, many items (such as python scripts and the Amazon Alexa service). I really hope somebody can help me.