Bug 150203

Summary:	rescue has boot errors
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Jon Nelson <jnelson-suse>
Component:	Other	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Beta 3
Target Milestone:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	a screenshot

Description Jon Nelson 2006-02-12 04:45:00 UTC

I booted the 10.1 beta 3 cd in 'rescue' mode. While booting, I saw this (apologies for spelling errors):

Initializing /devcp: will not create hard link '/dev/shm' to directory '/dev/pts'
chmod: cannot access '/dev/shm': No such file or directory

/bin/mknod: '/dev/shj/root': No such file or directory

...

Just FYI.

Comment 1 Michael Gross 2006-02-13 11:53:32 UTC

When is is message getting outputted? You can photograph the boot-screen and attach the picture here if it helps you.

Comment 2 Michael Gross 2006-02-17 11:44:37 UTC

Please reopen this bug if you can provide more information.

Comment 3 Jon Nelson 2006-02-18 03:21:26 UTC

Created attachment 69164 [details]
a screenshot

Comment 4 Jon Nelson 2006-02-18 03:22:03 UTC

As requested, screenshot.

Apologies that it took so long!

Comment 5 Michael Gross 2006-02-20 15:01:35 UTC

OK that looks like a problem with the boot scripts.
Does this happen on other machines, too or did you test this only on one machine?

Comment 6 Jon Nelson 2006-02-20 15:09:39 UTC

Just the one machine.

Comment 7 Jon Nelson 2006-02-20 15:10:29 UTC

I need to clarify that. Hit commit too quickly.
I have only tested this on the one machine.
I can test on others but not for 11 hours or so.

Comment 8 Michael Gross 2006-02-20 15:16:12 UTC

Would be helpful, on my test-machine I receive no such messages.
You could give more information about the used machine (hwinfo).

Comment 9 Jon Nelson 2006-02-21 02:25:56 UTC

I just tried the 10.1 beta4 CD1 rescue mode and it worked fine (on the same machine).

I think this bug can probably be closed.

Thanks!

Comment 10 Michael Gross 2006-02-21 15:14:40 UTC

I suppose this was already fixed then. You can try it with future versions, if it reappears, reopen this report (I also tested it with B4).

Comment 11 Michael Gross 2006-03-03 17:08:56 UTC

Jon: Which hardware do you use? Is this a x86-64 machine?

Comment 12 Jon Nelson 2006-03-03 19:50:50 UTC

The hardware in this is a Dell laptop, I think it's a Mobile Celeron, 1.6 GHz. I don't recall the exact model.