HT203176: Resolve startup issues and perform disk maintenance with Disk Utility and fsck
Learn about Resolve startup issues and perform disk maintenance with Disk Utility and fsck
Q: cannot mount root, errno = 19
-
Jul 1, 2012 12:28 AMby zdavatz,Thanks for your replies.
Command+Shift+V got me to Verbose mode where I took this picture:
https://twitter.com/zdavatz/status/219156103206928384/photo/1/large
Next I will check if I have something strange in Startup-Volume.
Best
Zeno
-
Jul 1, 2012 12:42 AMby X423424X,Do you have any external drives attached to your system? If so, detach them and reboot and see what happens.
Also I notice some errors possibly related to a "marvell yukon gigabit adapter". Does that require drivers? Are they up to date? Can you uninstall all the stuff related to that as an experiment?
-
Jul 1, 2012 2:23 AMby X423424X,Well according to that segment of verbose boot log, that stuff is in there. It's why I asked. That Marvell stuff appears to be causing some (all?) of thoe errors in that boot log segment. It's either that or some kind of file system mount failure (why I asked about external volumes).
-
Jul 1, 2012 2:46 AMby zdavatz,If I unplug the Network then the Marvell Error goes away. I guess the error comes, because I can not connect to the network.
I am now doing
1. Booting from rescue USB
2. umount /dev/disk0s2
3. fsck_hfs -fy /dev/disk0s2
4. fsck_hfs -ry /dev/disk0s2
and the same for /dev/disk0s1 and /dev/disk0s3 -
I am normally a Linux guy and I have not yet figured out what the Lilo/Grub equivalent for OS X is. Can you help me with that? How do I rewrite the boot segement as with running "lilo" on Linux?
Thank you for your continued help and input!
Best
Zeno
-
Jul 1, 2012 3:07 AMby X423424X,Don't know linux. Looked up lilo and don't know what can be done during the boot process to mimic that, if anything at all. I've never had to deal with that low level of the OS. Sorry.
Odds are pretty high someone will chime in here with some suggestions. Maybe tomorrow. For me it's bed time.
-
Jul 1, 2012 3:11 AMby zdavatz,How do I run
fdisk -u: update MBR code, preserve partition table
on OS X? On what disk do I have to run that? There are so many disks in /dev whitch is the right one?
Is it
/dev/disk2s3
or is it
/dev/disk0s1
I do not understand the difference between these devices.
Best
Zeno
-
Jul 1, 2012 10:09 AMby zdavatz,Ok, I solved my issue by reinstalling OS Lion. Lion is smart enough not to overwrite my existing data, so all is fine.
Good to know!
I did rebuild the b-tree with fsck and also done several checks on /dev/disk0s2 which seems to be the "Macintosh HD" Volume...
Best
Zeno
