Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

no backup on systems with only "one" partition #28

Closed
wemsras opened this issue Nov 24, 2017 · 7 comments
Closed

no backup on systems with only "one" partition #28

wemsras opened this issue Nov 24, 2017 · 7 comments
Assignees
Labels
enhancement Enhancement request

Comments

@wemsras
Copy link

wemsras commented Nov 24, 2017

on a beaglebone black you can install your linux on "one" partiton. Specialy to the on-board EMMC storage. You get the error ??? RBK0142E: Unable to detect boot device. The /boot is on the / file system and there is no seperate mountpoint for /boot. This beaglebone is running Parabola Linux.
onefilesystem.txt

@framps
Copy link
Owner

framps commented Nov 24, 2017

Boot device detection assumes /dev/mmcblk0p1 as of now but your system uses /dev/mmcblk1p1

I just created a test branch for you which has dynamic boot device detection code added. Please try this version.

@framps framps self-assigned this Nov 24, 2017
@framps framps added the enhancement Enhancement request label Nov 24, 2017
@wemsras
Copy link
Author

wemsras commented Nov 24, 2017

Sorry ;-)
It seems to be the same error with the new version.
[root@parabb bin]# ./raspiBackup.sh
--- RBK0009I: parabb: raspiBackup.sh V0.6.3.1-hotfix (b1e7cc4) started at Fri Nov 24 20:39:03 CET 2017.
!!! RBK0173W: =========> NOTE <=========
!!! RBK0173W: This is a temporary hotfix and should not be used in production.
!!! RBK0173W: =========> NOTE <=========
??? RBK0142E: Unable to detect boot device.
--- RBK0105I: Deleting new backup directory /backup/parabb/parabb-tar-backup-20171124-203903.
??? RBK0005E: Backup failed. Check previous error messages for details.

and from /var/log/raspiBackup/parabb.log
20171124-203904: MSG ??? RBK0142E: Unable to detect boot device.
Invocation parms: ''

@framps
Copy link
Owner

framps commented Nov 24, 2017

:-( Could you please use option -l debug and provide the generated debug log? Make sure there is no sensitive information in the log.

@wemsras
Copy link
Author

wemsras commented Nov 24, 2017

Wow. Thanks for your fast reaction.
For me it looks like that the problem is that /boot is not a mountpoint, because of one filesystem /. The last lines of the attached log file shows something about that.
parabb.log

@framps
Copy link
Owner

framps commented Nov 24, 2017

You are right. /boot is not a mount point on your system. raspiBackup requires /boot and / to be a mount point (that's standard on raspbian). If you want to use raspiBackup on your system the only backuptype you can use is dd. Let me know if you want to use dd instead of tar and I create another fix so you can use dd on your system.

@wemsras
Copy link
Author

wemsras commented Nov 24, 2017

On all machines i use tar for backup. For now i will check to change my config to /boot and /.
I try that out and come back asap.

@wemsras
Copy link
Author

wemsras commented Nov 25, 2017

At this time i was not able to change my BB black to boot from a two partition sd card. I've formated und partitioned the card several times without success. So i will analyze this at a later date. For now i close this issue. Many thanks for your "dd" offer.

@wemsras wemsras closed this as completed Nov 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement request
Projects
None yet
Development

No branches or pull requests

2 participants