Apr 12, 2019 I love my Mac environment, from using macOS to continuity, to iCloud, it allows for me to be able to have a flexible workflow. Whether I'm working on my Mac mini at the start of my day in my office or changing to my back deck using my MacBook Pro in the afternoon, macOS's features allow it to happen since all of my files are accessible to me via iCloud. Jul 05, 2017 Select the drive or partition you need to repair and click the “First Aid” button. The Disk Utility interface is the same one you’ll see on your Mac OS X desktop, but run it from here and it’ll be able to repair problems with your system drive. Use fsck in Single-User Mode. In some cases, even Safe Mode or Disk Utility in OS X Recovery. Aug 30, 2012 Mounting drives in single user mode: How Pixar almost deleted Toy Story 2 with rm.:http://www.y. May 02, 2017 Now you are saying single user mode you are in have you done the mount / rw it suggests when entering that mode on boot plus the fsck it recommends doing on the volume it tells you to do as well? Also it should be possible if you get access to the drive contents to list the files that you can simply attach a USB drive and copy the files off the. Sep 10, 2006 My thought was that if you could boot from a non FUBAR drive, even in single user mode, you might not be restricted to read-only mode and could create a mount point on the working drive. If you have an external enclosure, you could take this a step further and remove the FUBAR drive and boot the system 'normally', then only hook it up when you. Jan 22, 2018 Single User Mode mounts the system volume as read-only. To mount the system drive as read/write, use this command: mount -uw / Single User Mode also only starts a minimal system, leaving many frameworks and daemons unloaded, including some required by diskutil. The following commands.may. load the necessary items to run diskutil.
mount_drive_in_single_user_mode.sh
#!/bin/sh |
#-----------------------------------------------# |
# mount usb drive in single user mode |
#-----------------------------------------------# |
# reboot the mac and press s to start up in single user mode |
# mount the internal mac drive |
/sbin/mount -uw / |
# list the volumes |
ls /Volumes |
# create a mount point directory in /Volumes |
mkdir /Volumes/drive/username |
# list the drives, the last drive listed should be the external usb drive |
ls /dev/disk* |
# check the drives partition type eg hfs |
fstyp /dev/disk1s2 |
# mount the external drive on the mount point |
mount –t hfs /dev/disk1s2 /Volumes/drive |
# copy files from the internal drive to the external drive |
cd /Users/username |
cp -rp /Users/username/Sites /Volumes/drive/username |
# -r = recurcive |
# p = Cause cp to preserve the following attributes of each source file in the copy: |
# modification time, access time, file flags, file mode, user ID, and group ID, |
# as allowed by permissions. Access Control Lists (ACLs) and Extended Attributes |
# (EAs), including resource forks, will also be preserved. |
Mac Single User Boot
![Mode Mode](/uploads/1/2/6/5/126531050/622459843.png)
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
Mac Os X Mount Usb Drive Single User Mode
An update for 10.5.x: Whether you plug the drive in before booting to single-user mode or after, the drive doesn't seem to show up in /dev here. It DOES in 10.6.x.
What worked for me in 10.5.8 was to load kernel extensions after plugging in the drive:
mount -uw /
launchctl load /System/Library/LaunchDaemons/com.apple.kextd.plist
[WAIT approx 30 seconds: various log messages scroll by; after the 'kernel link data' error re: /var/run/mach.sym existing already, I continued:]
mkdir /Volumes/usb
mount -t msdos -v /dev/disk1s1 /Volumes/usb
This was on a MacBook with no other disks present, so disk0 was the internal HDD, and I had already determined that disk1 was the flash drive. disk1s1 was the single MS-DOS FAT16 data partition on that drive; hence the '-t msdos' parameter, above. Refer to the man page for mount for other options relevant to other file systems.
If you're on a system with multiple internal disks, you may want to review the disks present in /dev before loading the kexts:
ls /dev/disk*
Then load the kexts as above, then rerun
ls /dev/disk*
and compare to learn the disk ID of your flash (or other) drive.
Note also that the 'root' of each physical disk appears as disk0, disk1, disk2, etc. Those entries are not mountable or accessible. They are the command-line designation of the top-most entry of a disk as listed in Disk Utility's GUI, beneath which the disks data partitions are displayed. Data partitions are labeled e.g. disk0s1, disk0s2, disk1s1, etc.
One more note: you can in fact continue typing your command despite being interrupted by new log messages that crop up (e.g. diskarb errors). It can be tough to keep track of where you are in your command, but if you continue to type it correctly, it will execute.
In 10.6.x, if the drive is connected prior to booting into single-user mode, you need only mount it as usual ('mkdir' and 'mount' lines, above, modified to reflect the ID of your drive).
An aside: the reason I wanted to mount a flash drive here was to be able to run a shell script that reset a clean install after initial setup/login/updates back to 'out-of-box' no-users, Apple Setup Assistant state. See my comment to '10.5: How to reset Leopard back to the setup assistant' here: http://hints.macworld.com/article.php?story=2007110800450816 (can't seem to pin down the link: code syntax, sorry!).
What worked for me in 10.5.8 was to load kernel extensions after plugging in the drive:
mount -uw /
launchctl load /System/Library/LaunchDaemons/com.apple.kextd.plist
[WAIT approx 30 seconds: various log messages scroll by; after the 'kernel link data' error re: /var/run/mach.sym existing already, I continued:]
mkdir /Volumes/usb
mount -t msdos -v /dev/disk1s1 /Volumes/usb
This was on a MacBook with no other disks present, so disk0 was the internal HDD, and I had already determined that disk1 was the flash drive. disk1s1 was the single MS-DOS FAT16 data partition on that drive; hence the '-t msdos' parameter, above. Refer to the man page for mount for other options relevant to other file systems.
If you're on a system with multiple internal disks, you may want to review the disks present in /dev before loading the kexts:
ls /dev/disk*
Then load the kexts as above, then rerun
ls /dev/disk*
and compare to learn the disk ID of your flash (or other) drive.
Note also that the 'root' of each physical disk appears as disk0, disk1, disk2, etc. Those entries are not mountable or accessible. They are the command-line designation of the top-most entry of a disk as listed in Disk Utility's GUI, beneath which the disks data partitions are displayed. Data partitions are labeled e.g. disk0s1, disk0s2, disk1s1, etc.
One more note: you can in fact continue typing your command despite being interrupted by new log messages that crop up (e.g. diskarb errors). It can be tough to keep track of where you are in your command, but if you continue to type it correctly, it will execute.
In 10.6.x, if the drive is connected prior to booting into single-user mode, you need only mount it as usual ('mkdir' and 'mount' lines, above, modified to reflect the ID of your drive).
An aside: the reason I wanted to mount a flash drive here was to be able to run a shell script that reset a clean install after initial setup/login/updates back to 'out-of-box' no-users, Apple Setup Assistant state. See my comment to '10.5: How to reset Leopard back to the setup assistant' here: http://hints.macworld.com/article.php?story=2007110800450816 (can't seem to pin down the link: code syntax, sorry!).