![]() I note that during this process the fan is kicking in, which seems odd given I wouldn't think deleting a volume should be too computationally intensive. This happened on the encrypted or unencrypted volumes.Įventually after several reboots diskutil unmountDisk force /dev/disk2s1 worked to the point that the deleteVolume would get as far as "Deleting Volume" with an ASCII progress bar getting to 50% however after many minutes with no progress, the machine hangs with a black screen and has to be force-restarted. I then tried deleting the volumes individually ( diskutil apfs deleteVolume /dev/disk2s1) after five minutes or so I got "Error: -69888: Couldn't unmount disk". I then tried deleting the Container ( diskutil apfs deleteContainer /dev/disk2) this failed at the point at which it tried to unmount the volumes. I can ctrl-c out of this but the disk remains encrypted. ![]() Nothing seems to happen for several hours. I tried decrypting the volume ( diskutil apfs decryptVolume /dev/disk2s1 -user UUID) it accepts the password and says it's decrypting in the background but won't return me to the command line. There's an APFS container (disk2) with four volumes (disk2s1 to disk2s4). When I tried just running the Mojave install from a USB drive, it got to the point of prompting me for a password for the drive (it takes several minutes for the prompt to come up from the point I click Unlock.) and then just seems to hang, as if it's unable to decrypt the drive. However I can't wipe the APFS-formatted drive - each method I try I get a different setback. If I try to use Disk Utility from Recovery mode or a USB boot drive, anything I try to do with the APFS drive hangs Disk Utility, so I'm working from the Terminal in Recovery mode.Īt this point all I want to do is wipe the drive so I can install Mojave from scratch. If I boot into Single User mode I can't run fsck without it throwing up an endless loop of errors to do with spaceman_freed. (I can enter the Filevault password but the progress bar gets to 100% and then stalls. # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.I have a MBP with SSD which won't boot. # Accessible filesystems, by reference, are maintained under '/dev/disk/'. # Created by anaconda on Tue Dec 17 03:28:04 2019 It happens mostly when you have a remote filesystem. In my case, I want to edit the tekneed filesystems that are preventing my system from booting by commenting it out (#). mount the real rootfilesystem depending on the way you boot to single user mode # chroot /sysroot 3. boot into single usermode as done above 2. Some filesystems defined in the fstab can prevent the system from booting, to make changes to fstab, do the following. To be able to perform some tasks and make some changes, the root filesystem is required to be mounted on “/”, hence it will require the use of chroot tool to be able to mount the root filesystem on “/” logically. More so, using some of these methods will make the root filesystem to be mounted on /sysroot. To be able to make any changes, the root filesystem permission needs to be changed to read-write (rw). Going forward, with these methods we are going to use in the “ ACTION TIME” section, the root filesystem, after being mounted will have a read only (ro) permission. This mode is basically used for maintenance like we earlier said, and troubleshooting such as, resetting a lost root password, repairing bad filesystems (fsck), editing the fstab file to make the system boot properly, stopping services disrupting the system from booting, etc In single user mode, the system is booted to a minimal environment with filesystems(local filesystems) being mounted, but without network services, the full operating system is not functional in this mode and most services will be manually started. In this subject matter, we will look at how to boot into a single user mode (runlevel 1) without the imputing the root password. However, both methods will require the input of the root password. In one of the articles on this site, I discussed how a system runlevel/runtarget can be changed from an operational/command mode and how it can also be changed from the boot menu. Single user mode is also referred to as runlevel 1 and can be called emergency or maintenance mode.īooting in this mode can be done in many ways. From the word single, single user mode is the mode in a Linux system where only one user, the root is allowed to perform system tasks. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |