# Boot disk issue

**URL:** https://forums.suse.com/t/boot-disk-issue/25697
**Category:** SLES Install-Boot
**Created:** [June 7, 2014, 2:37am UTC](https://forums.suse.com/t/boot-disk-issue/25697 "2014-06-07T02:37:11Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![yssong](https://avatars.discourse-cdn.com/v4/letter/y/ce7236/32.png) [@yssong](https://forums.suse.com/u/yssong)
#### Post date: [June 7, 2014, 2:37am UTC](https://forums.suse.com/t/boot-disk-issue/25697/1 "2014-06-07T02:37:11Z")

</div>

![](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

---

<div class="post-metadata">

### Author: ![Jim1](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/jim1/32/9120_2.png) [@Jim1](https://forums.suse.com/u/Jim1)
#### Post date: [June 7, 2014, 3:19am UTC](https://forums.suse.com/t/boot-disk-issue/25697/2 "2014-06-07T03:19:32Z")

</div>

On Fri, 06 Jun 2014 23:44:01 +0000, yssong wrote:  
[color=blue]

> [image: [http://cronos/Capture.JPG]](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!!![/color]

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

---

<div class="post-metadata">

### Author: ![yssong](https://avatars.discourse-cdn.com/v4/letter/y/ce7236/32.png) [@yssong](https://forums.suse.com/u/yssong)
#### Post date: [June 9, 2014, 7:20pm UTC](https://forums.suse.com/t/boot-disk-issue/25697/3 "2014-06-09T19:20:11Z")

</div>

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

---

<div class="post-metadata">

### Author: ![Jim1](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/jim1/32/9120_2.png) [@Jim1](https://forums.suse.com/u/Jim1)
#### Post date: [June 10, 2014, 3:19am UTC](https://forums.suse.com/t/boot-disk-issue/25697/4 "2014-06-10T03:19:12Z")

</div>

On Mon, 09 Jun 2014 16:24:02 +0000, yssong wrote:  
[color=blue]

> 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).[/color]

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
