PDA

View Full Version : Boot disk issue



yssong
07-Jun-2014, 00:37
http://cronos/Capture.JPG

I booted from DVD using Rescue option and was able to mount my root device /dev/cciss/c0d0p2 on /mnt without any problem.

But when it boots up, it tries to use the long device path and fails.

Thank you much in advance!!!


- Steve

hendersj
07-Jun-2014, 01:19
On Fri, 06 Jun 2014 23:44:01 +0000, yssong wrote:

> [image: http://cronos/Capture.JPG]
>
> I booted from DVD using Rescue option and was able to mount my root
> device /dev/cciss/c0d0p2 on /mnt without any problem.
>
> But when it boots up, it tries to use the long device path and fails.
>
> Thank you much in advance!!!

It might be useful if you told us what version of SLES you're running -
the screenshot you posted is not accessible from the 'net (as it only
includes a hostname), so it's difficult to diagnose what you're seeing....

When the system boots on its own, what do you mean by the "long device
path"? Is it not using the device name you end up with using rescue mode?

Jim



--
Jim Henderson, CNA6, CDE, CNI, LPIC-1, CLA10, CLP10
Novell/SUSE/NetIQ Knowledge Partner

yssong
09-Jun-2014, 17:20
Sorry for no screenshot included in my earlier posting.

Here's what I see.

Could not find /dev/disk/by-id/cciss-3600508b10010363336202020202000007-part2
Want me to fall back to /dev/cciss/c0d0p2? (Y/n)

Then, it hangs, and I cannot answer to (Y/n).


Thanks.


- Steve

hendersj
10-Jun-2014, 01:19
On Mon, 09 Jun 2014 16:24:02 +0000, yssong wrote:

> Sorry for no screenshot included in my earlier posting.
>
> Here's what I see.
>
> Could not find
> /dev/disk/by-id/cciss-3600508b10010363336202020202000007-part2 Want me
> to fall back to /dev/cciss/c0d0p2? (Y/n)
>
> Then, it hangs, and I cannot answer to (Y/n).

You might boot into rescue mode and then modify the /boot/grub/device.map
and /etc/fstab files to point to /dev/cciss/c0d0p2. Make sure you make
those changes on the hard drive rather than the rescue mode.

It seems that the disk ID might have changed for some reason (though it /
shouldn't/, unless you've imaged the drive and restored it to a different
device). This will change it to the device so you can boot the system
and find out what the new by-id value should be.

Back those two files up before you change them - that way if that doesn't
work, you can revert them.

Jim



--
Jim Henderson, CNA6, CDE, CNI, LPIC-1, CLA10, CLP10
Novell/SUSE/NetIQ Knowledge Partner