Hi AjA,

sorry to hear you're running into a problem.

So this very much sounds like your original SD card may be dying. The reason I think this is that ApplePi-Baker does not write to the original SD card, ever. So the corruption of the original SD card must be caused by something else. SD cards are not known for being the best and most reliable storage devices - so this happens to others as well.
Sounds like ApplePi-Baker made a copy of an already corrupted SD card, and as such restoring the created backup will most likely be "damaged" as well.
Lot of talk, but no solution yet, right 😉 

Now how to fix this ...

First thing I would try (if possible):
1) Make sure the contacts of the SD card are clean, and try again.
2) If that still does not work and you have another Pi laying around: test it in another Raspberry Pi.
3) If that doesn't work or is not an option: restore the backup to yet another SD card and try if that works.

If none of that works:

This will not be easy to fix since we do not know what is damaged on the SD card.
Since it will not boot from the backup or the original SD card, the only thing left is to try to mount the SD card either on a Linux device, or on your Mac.

Note that your Mac will not know the Linux file system unless you've got something like Paragon ExtFS (commercial) or MacFuse (free, EXT filesystem and other plugins can be found here) installed. I would use this as a last resort, since mounting the SD card may trigger your Mac writing something to it.

Based on that you can look on the filesystem, if readable (!), and see if you can find your files.

In cases like this I usually create a new SD card, with a clean OS and clean install of the tools you used.
Once that works, I'd add the files from the damaged SD card.

I know, it's a pain ... especially when you're not digging in Linux filesystems daily. 😞 

Hope this is helpful - feel free to ask, I'd be happy to try and help.

ps. please respond in the forum, emails are most likely to be overlooked, missed, or spam filtered - I noticed your email just now by accident.

Your email:

Hello 

Hi Andreas,

First thing with SD cards, even from the same manufacturer: they appear never to be the same size.
This is why I added the resize option in ApplePi-Baker.

(resize option enabled by clicking this icon)

However, I have no idea what the partitioning of your SD card looks like.
APB's resize option only works for a standard partition table (max 4 standard partitions, MBR), with the first one being a FAT partition and the second one being a EXT formatted Linux partition. For some unclear reason, some distros like to use GUID and/or extended partitions, neither of which are supported.

It should look something like this (official Raspbian image):

(standard partitions, FAT and EXT, MBR)

Now if the format of your SD card is support for a resize, then one would make a backup first with the resize option enabled.
This will make a full backup, and then resize the Linux partition to it's minimum size. Of course ideal for storing backup images 😊 

Next, on restore, ApplePi-Baker will look how much space you have on your SD card (or USB drive) and expand a copy of the backup to that size, and then write that resized partition to your SD card.

I'd say most of the time, making a backup like this will result in a smaller (often much smaller) backup IMG file.
Restoring now can be done to any SD card (or any drive for that matter) that is at least as big (roughly) as the IMG file.

Tip: A little trick to keep in mind:
If your mount and IMG or ISO file on your Mac (double clicking the file), then ApplePi-Baker will see them as "disks" as well.
So if you have a full backup and want to make it smaller because you forgot to check the "resize" option, then you can make a new backup of the mounted ISO/IMG file. This will be significantly faster than reading the SD card again.

I hope this is helpful 😊 
Let me know how this works out! 😊 

@hans Hello Hans,

Tried to open the last backup it produced a file called "disk.img" with 64,09 GB!. Then I started a new backup with the resize option enabled it produced the following error message (after 6 hours):

Can you help again?

Thanx

Andreas

Hi Andreas,

Just curious, since this error doesn't tell us much: how much diskspace do you have left?
Worse case you'd need 128Gb free (most likely less than that of course).
Make sure your empty the Trashcan (I forget that every now and then as well) to get more space 😊 

Delete the .tmp and the .LinuxPartition file before trying again.

Also note: if you already have a backup IMG, double click it so your Mac mounts it, and then in ApplePi-Baker choose that disk - things will go a LOT faster 😊

Always feel free to ask 😊 

@hans hei Hans

i ve tried to open the disk.img but it says that I don’ t have the rights to open it (even as Admin). 
ok I will retry on a disk with enough space. Let s see

regards

Andreas

Hei

nowq I tried a new backup. Which seems to work, but extracting the zip and clicking the IMG, brings again the "no rights error".

Trying to do a restore with APB, started correctly but than hangs, no reaction of APB any more (waited > 10 Min and Diskspace is > 250 GB:

Sorry for asking you again for help

Regards

Andreas

Don't worry - you're most welcome to ask for help 😊 

For the no-right error, you could try this changing the file attributes:

cd <directory where the IMG file is>
sudo chmod 777 RaspBack4_io_ubnt_07-08-24.img
sudo xattr -c RaspBack4_io_ubnt_07-08-24.img

• chmod 777 is going overboard, but at least we've got everything covered.
• I've used sudo to elevate your privileges.
• xattr removes extended attributes (may not be needed).

From what I can see, it is a Rasbpian Image and it is quite small (~11Gb). So we should be able to work with that 😊 

Hope this helps, and always feel free to ask 😊 

@hans hei

i m not very familiar with command line actions in Mac terminal. trying sudo .... requires a password??? I activated root user and gave him a password, but won' t work.

Next thing I was out for while and let APB in the state he was. Surprisingly he come back to work something. But in the end another error appears: he can't open the sd card???

 Getting more and more confused here

Should I reformat the card?

Good morning!

"sudo" does require your password indeed - apologies for not mentioning that.
Not sure what you mean with "activated root user"? (normally under Unix like systems, this would be the "su" command - but MacOS will not let you use this)

Disk access: Oh that's not cool to see that error after resizing (although we now DO know that resizing will work).
You can try formatting the SD card, or use the "prepare for NOOBS option" (Advanced Disk Panel in ApplePiBaker, right click the drive, if you do not see any drives, click the drive icon in the upper right corner to toggle what drives will be shown).

p.s. you're probably experienced with this: on my Intel MacBook Pro, when inserting the SD card, the "write protect" switch sometimes moves to the write protect position. Make sure that didn't happen. 😉