MacOS – Backup files from corrupt disk to usb drive in single user mode

backupcommand linemacossingle-user

I try to backup my files of a corrupt system. I can start into the single user mode and want so store my home folder to my backup system. To mount my usb drive I need to mount the root disk as writeable. Therefor I used the command

/sbin/mount -uw /

The command will be executed withoud any response, after that I tried to create a folder

mkdir /backup

But this returns

mkdir:backup: File exists

But there is no folder or file which has been created??? What am I doing wrong?
Thanks

Best Answer

Single user mode is the wrong tool for this job. Connect an external drive if you want to use one and then restart in to Recovery HD ( or Internet recovery).

Use the terminal application from there to make your copies and backups. It's handles mounting all the filesystems properly so you can move things around.

Related Solutions

MacOS – Mavericks: User no longer owner of Home folder and content

An erroneous extended attribute has been applied to this directory somehow, but it can only be removed using the xattr Terminal command. You should take a look at a brief explanation here. A more detailed question and answer can be found at this StackOverflow page.

MacOS – How to repair permissions after removing the “wheel” group from the hard drive

This not-really-an-answer answer probably doesn't solve your problem, though the result is so astounding/interesting not to dump it in the comment section:

I set up a virtual machine with Snow Leopard Server (10.6.8). After deleting (not just disabling rwx!) all wheel group permissions of /bin, /sbin, /private, /System and all subsequent files and folders as well as those of all relevant folders in /Library with either an admin or the root account and afterwards totally removing the group wheel with the workgroup manager, the system still boots properly. Some apps don't work properly (e.g. Terminal in the admin account; it still works in the root account).

Consequently I can't reproduce your problem.

You may try the following in Single User Mode:

At the prompt enter:

/sbin/fsck -fy
/sbin/mount -uw /
launchctl load /System/Library/LaunchDaemons/com.apple.notifyd.plist
launchctl load /System/Library/LaunchDaemons/com.apple.diskmanagementd.plist
launchctl load /System/Library/LaunchDaemons/com.apple.securityd.plist
launchctl load /System/Library/LaunchDaemons/com.apple.configd.plist
launchctl load /System/Library/LaunchDaemons/com.apple.diskarbitrationd.plist
diskutil repairPermissions /

If the loading of com.apple.configd.plist doesn't find an end you may just enter launchctl load /System/Library/LaunchDaemons/com.apple.diskarbitrationd.plist or after entering ctrlC continue with launchctl load /System/Library/LaunchDaemons/com.apple.diskarbitrationd.plist

If you don't get a new prompt :/ root# after waiting some time, you may just enter the next command. You may also modify the sequence of the five load commands. I needed three attempts to get that working.

You should now see a wall of notifications. It should take about 20-30 minutes to repair everything.

Best Answer

Related Solutions

MacOS – Mavericks: User no longer owner of Home folder and content

MacOS – How to repair permissions after removing the “wheel” group from the hard drive

Related Question