Well if this happens to you, and the machine freezes on bootup after (may be) one or 2 successful fscks on a drive, and then it continues to boot up in teh background (so networking works), but the screen is non-responsive.
Then.... the reason could be that the device mappings have changed for teh drives you mapped in fstab!
Yup that sucks....
in my case /dev/sdc1 changed to /dev/sdb1
This happened when I migrated a VM from one ESX host to another, and then back again.
Then.... the reason could be that the device mappings have changed for teh drives you mapped in fstab!
Yup that sucks....
in my case /dev/sdc1 changed to /dev/sdb1
This happened when I migrated a VM from one ESX host to another, and then back again.
No comments:
Post a Comment