Re: Boot Problem

[Felix Miata]

Stephen P. Molnar composed on 2023-12-05 13:33 (UTC-0500):

> I decided to try something. I logged in to the rescue  mode as root and 
> entered startx at the prompt. This generated the error:

I believe if xserver-xorg-legacy is not installed that startx failure is 
expected.
I keep it installed on all mine, so I'm not sure what happens if it is not.

> Unable to contact settings server
> failed to execute child process "dbus-launch" (No such file or directory) 

If you have not already, and have not already tried with a virgin user and 
reached
the same failure, while logged out of XFCE, delete all content of ~/.cache/, 
then
try logging in normally. This is known to occasionally succeed in Plasma, and
might apply to XFCE as well.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata

Re: Boot Problem

[Cindy Sue Causey]

Please forgive me if I somehow messed up the quote attribution. There
was a lot of stuff I was able to cull. :)

On 12/5/23, David Christensen  wrote:
> On 12/5/23 10:33, Stephen P. Molnar wrote:
>  > I decided to try something. I logged in to the rescue  mode as root and
>  > entered startx at the prompt. This generated the error:
>  >
>  > Unable to contact settings server
>  > failed to execute child process "dbus-launch" (No such file or
> directory)
>
>
> That looks like a meaningful clue.


I run into that message occasionally after brand new installs via
debootstrap. I can't remember what triggers it. It's something like
trying to right click then open a file via mousepad or use that "Open
Terminal Here" option from within Thunar (for both).

At some point in my own experience, I tried "apt-cache search
dbus-launch" because the "No such file or directory" told me the
system thought there should be a file by that name. Search returned
"dbus-x11" as the only potential option. It wasn't installed so I
attempted installing it. It works immediately every time for my
situation.

As an aside, if "apt-cache search" doesn't find anything for a not
found file, maybe something like apt-file will show a package that
might be missing.

A second thing that could be tried is to rename
"/home//.Xauthority"  to something else. If this was me, I'd
rename it singularly definitive as e.g. .Xauthority20231205-1626 (time
and date). I'll often also add on a couple words that describe the
problem I was having when renaming the file. Makes it easy to decide
whether to delete it if the system starts working properly with the
new replacement.

Then try logging in. I haven't had to do this in a LONG time, but it
seems like the system will simply generate a new file. For some
reason, the old one just gets corrupted and starts failing.

Getting kicked back to the login GUI is exactly what happens to me
when this file is corrupted. When I haven't properly installed that
GUI and am having to login from the console screen, startx will just
keep kicking me back to the command line in this same situation.

As a matter of fact, I think that may also be where I learned about
.Xauthority. Seems like it gets a head nod during that type of login
fail.

You shouldn't have to do anything like create a new empty file or
anything because /etc/skel does not include .Xauthority as one of the
default files for all new adduser creations. That was my hint to
attempt this option years ago when it felt like I had tried every
other option at the time.

That's all I've got. Best wishes fixing this soon...

By the way, the dbus-launch error has happened for me on both xfce4
and lxqt desktop environments.

Cindy :)
-- 
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

Re: Boot Problem

[Michael Kjörling]

On 5 Dec 2023 11:05 -0500, from s.mol...@sbcglobal.net (Stephen P. Molnar):
> I have Bookworm installed on a 1TB SSD. When I attempted logging this
> morning I failed! Rather than opening my XFCE desktop I was sent back tot he
> login screen, over and over and . I got the same result
> attempting to login as root. I have to assume that grub has been corrupted>

As others have already pointed out, this likely has absolutely nothing
to do with GRUB. If you're getting a graphical login/password prompt,
you are well past anything that GRUB is likely to have any impact on.

Try switching to a text virtual terminal; Ctrl+Alt+F1, F2, F3, ...
until you get to one that will give you a "login:" prompt. Log in
there using your normal username and password. What happens when you
try that? Please be as specific as possible.

The few times I've seen anything similar to what you describe,
something has been amiss with the home directory; not mounted,
permissions, some critical file has been corrupted or deleted, ...
Logging in at a text virtual terminal will eliminate several layers of
complexity and _even if_ it won't allow you to log in, might very well
tell you more directly what the problem is.

-- 
Michael Kjörling  https://michael.kjorling.se
“Remember when, on the Internet, nobody cared that you were a dog?”

Re: Boot Problem

[David Christensen]

On 12/5/23 08:05, Stephen P. Molnar wrote:
I have Bookworm installed on a 1TB SSD. When I attempted logging this 
morning I failed! Rather than opening my XFCE desktop I was sent back 
tot he login screen, over and over and . I got the same 
result attempting to login as root. I have to assume that grub has been 
corrupted>


As it happens I also have Bookworm installed on a second SSD on my 
platform. I'm there sending this email


I have Grub Customizer installed in both. I have also just downloaded 
and burned debian-12-2-0-ams64.


I am very nervous about messing with the OS. What might be my best 
course of action to fix the problem (short of reinstalling)?


Thanks in advance




> On 12/05/2023 12:47 PM, Tom Furie wrote:
>> When you say "back to the login screen", do you mean back to a graphical
>> login screen, or to a text console login screen?

On 12/5/23 09:56, Stephen P. Molnar wrote:
> Xfce4 graphical login screen


XFCE is the desktop environment.  The graphical login manager is another 
program (lightdm?).



On 12/5/23 10:02, Stephen P. Molnar wrote:
> I've attached the log. I hope that someone can tell me what the 
problem is.

>
> Thanks inn advance.


Searching Xorg.0.log for "error", I see one comment and no error messages.


We need to know the context that created the attached file:

1.  What OS instance generated it?  How did you obtain the file?

2.  What happened when?  E.g. when was the graphical desktop manager 
displayed?  When did you try to login?  More than once?  How and when 
did you shut down the machine?



On 12/5/23 10:33, Stephen P. Molnar wrote:
> I decided to try something. I logged in to the rescue  mode as root and
> entered startx at the prompt. This generated the error:
>
> Unable to contact settings server
> failed to execute child process "dbus-launch" (No such file or directory)


That looks like a meaningful clue.


On 12/5/23 12:07, Stephen P. Molnar wrote:
> My Os is up to date and running the version XFCE4
>
> I've attached the log files that i could find. I hope that it will help.


Searching Xorg.0.log for "error", I see one comment and no error messages.


Search Xsession-errors for "error", I do see error messages that may be 
meaningful clues.



If you have the expertise to "find the needle in the haystack" and "put 
Humpty Dumpty back together again", then go for it.



Otherwise,d o you have a recent image of your OS disk (e.g. dd(1), 
Clonezilla)?  If so, restore the most recent image onto a blank drive. 
If not, do a fresh install onto a blank drive and start taking images on 
a regular basis.  Once you have a recovered/renewed OS drive, mount the 
damaged drive read-only and recover settings, data, etc..  Take an image 
of the OS disk, and backup your configuration settings and data, when 
you are done.



David

Re: Boot Problem

[Stephen P. Molnar]

My Os is up to date and running the version XFCE4

I've attached the log files that i could find. I hope that it will help.


On 12/05/2023 02:26 PM, Alexander V. Makartsev wrote:

On 05.12.2023 23:33, Stephen P. Molnar wrote:
I decided to try something. I logged in to the rescue  mode as root 
and entered startx at the prompt. This generated the error:


Unable to contact settings server
failed to execute child process "dbus-launch" (No such file or 
directory)


I vaguely remember having similar behavior as you described in the 
first message, but I can't recall what was the root cause of that problem.
Probably it was Xfce4 user session failing to start because of config 
file or cache corruption.
Try to create a new test user and login using these new credentials, 
just to test it out.


It would be great if you'd also share an information about your 
system, installed version of Xfce, etc.
Contents of log files in your user's home directory 
"~/.xsession-errors" and "~/.xfce4-session.verbose-log".

You can use Debian Pastezone [1] to share long text files.


[1] https://paste.debian.net/
--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄


--
Stephen P. Molnar, Ph.D.
https://insilicochemistry.net
(614)312-7528 (c)
Skype:  smolnar1

(base) comp@AbNormal:~$ cat Xorg.0.log
[ 7.958]
X.Org X Server 1.21.1.7
X Protocol Version 11, Revision 0
[ 7.958] Current Operating System: Linux AbNormal 6.1.0-11-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-4 (2023-08-08) x86_64
[ 7.958] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-11-amd64 root=UUID=5b89d91f-1709-4d1c-9421-32aef272fac5 ro quiet
[ 7.958] xorg-server 2:21.1.7-3 (https://www.debian.org/support)
[ 7.958] Current version of pixman: 0.42.2
[ 7.958] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[ 7.958] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 7.958] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Dec  5 09:53:34 2023
[ 7.965] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 7.971] (==) No Layout section.  Using the first Screen section.
[ 7.971] (==) No screen section available. Using defaults.
[ 7.971] (**) |-->Screen "Default Screen Section" (0)
[ 7.971] (**) |   |-->Monitor ""
[ 7.972] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[ 7.972] (==) Automatically adding devices
[ 7.972] (==) Automatically enabling devices
[ 7.972] (==) Automatically adding GPU devices
[ 7.972] (==) Automatically binding GPU devices
[ 7.972] (==) Max clients allowed: 256, resource mask: 0x1f
[ 7.980] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 7.980] 	Entry deleted from font path.
[ 7.984] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/100dpi/:unscaled,
	/usr/share/fonts/X11/75dpi/:unscaled,
	/usr/share/fonts/X11/Type1,
	/usr/share/fonts/X11/100dpi,
	/usr/share/fonts/X11/75dpi,
	built-ins
[ 7.984] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 7.984] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 7.984] (II) Loader magic: 0x55ab5609bf00
[ 7.984] (II) Module ABI versions:
[ 7.984] 	X.Org ANSI C Emulation: 0.4
[ 7.984] 	X.Org Video Driver: 25.2
[ 7.984] 	X.Org XInput driver : 24.4
[ 7.984] 	X.Org Server Extension : 10.0
[ 7.985] (++) using VT number 7

[ 7.985] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 7.986] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 7.986] (II) Platform probe for /sys/devices/pci:00/:00:02.0/:01:00.0/drm/card0
[ 7.992] (--) PCI:*(1@0:0:0) 1002:68f9:1545:5450 rev 0, Mem @ 0xc000/268435456, 0xfea2/131072, I/O @ 0xe000/256, BIOS @ 0x/131072
[ 7.993] (II) LoadModule: "glx"
[ 7.995] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 8.017] (II) Module glx: vendor="X.Org Foundation"
[ 8.017] 	compiled for 1.21.1.7, module version = 1.0.0
[ 8.017] 	ABI class: X.Org Server Extension, version 10.0
[ 8.017] (II) Applying OutputClass "Radeon" to /dev/dri/card0
[ 8.017] 	loading driver: radeon
[ 8.017] (==) Matched radeon as autoconfigured driver 0
[ 8.017] (==) Matched ati as autoconfigured driver 1
[ 8.017] (==) Matched modesetting as autoconfigured driver 2
[ 8.017] (==) Matched fbdev as autoconfigured driver 3
[ 8.017] (==) Matched vesa as autoconfigured driver 4
[ 8.017] (==) Assigned the driver to the xf86ConfigLayout
[ 8.017] (II) 

Re: Boot Problem

[Hans]

Am Dienstag, 5. Dezember 2023, 18:56:48 CET schrieb Stephen P. Molnar:
Not good! You have to start startx from the shell.

However, when you see the login screen (gdm, lightdm, kdm, whatever), that 
means, the X-server is running and ok.

So you have a problem with XFCE.

Look at ~/.config/xfce4 and move this folder out of the way.

Also look in your /home directory, if any files are set ownership root:root. 
This caqn happen, when you change from a normal user to root. I had this 
problem, that .xerrors were set to ownership root:root thus X started no more. 
So iz might be, that some files of XFCE are set root:root,m and can not be 
overwritten.

So my suggestion: move any folders related to xfce4 away (just to somewhere 
else) and try it again.

If XFCE4 is starting, move all the removed files partly back and see, which is 
causing the problem.

Hope this helps.

Best

Hans 


> Xfce4 graphical login screen
> 
> On 12/05/2023 12:47 PM, Tom Furie wrote:
> > "Stephen P. Molnar"  writes:
> >> I have Bookworm installed on a 1TB SSD. When I attempted logging this
> >> morning I failed! Rather than opening my XFCE desktop I was sent back
> >> tot he login screen, over and over and . I got the
> > 
> > When you say "back to the login screen", do you mean back to a graphical
> > login screen, or to a text console login screen?

Re: Boot Problem

[Alexander V. Makartsev]

On 05.12.2023 23:33, Stephen P. Molnar wrote:
I decided to try something. I logged in to the rescue  mode as root 
and entered startx at the prompt. This generated the error:


Unable to contact settings server
failed to execute child process "dbus-launch" (No such file or directory)

I vaguely remember having similar behavior as you described in the first 
message, but I can't recall what was the root cause of that problem.
Probably it was Xfce4 user session failing to start because of config 
file or cache corruption.
Try to create a new test user and login using these new credentials, 
just to test it out.


It would be great if you'd also share an information about your system, 
installed version of Xfce, etc.
Contents of log files in your user's home directory "~/.xsession-errors" 
and "~/.xfce4-session.verbose-log".

You can use Debian Pastezone [1] to share long text files.


[1] https://paste.debian.net/
--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: Boot Problem

[Stephen P. Molnar]

I decided to try something. I logged in to the rescue  mode as root and 
entered startx at the prompt. This generated the error:


Unable to contact settings server
failed to execute child process "dbus-launch" (No such file or directory)


On 12/05/2023 01:03 PM, Tom Furie wrote:

"Stephen P. Molnar"  writes:



On 12/05/2023 12:47 PM, Tom Furie wrote:

"Stephen P. Molnar"  writes:


I have Bookworm installed on a 1TB SSD. When I attempted logging this
morning I failed! Rather than opening my XFCE desktop I was sent back
tot he login screen, over and over and . I got the

When you say "back to the login screen", do you mean back to a graphical
login screen, or to a text console login screen?


Xfce4 graphical login screen

Then the problem is not a display issue, but something wrong in loading
the desktop. I don’t use XFCE, but hopefully this means dead-end lines
of enquiry such as display drivers are halted, and that someone with
XFCE experience can chime in and offer advice.



--
Stephen P. Molnar, Ph.D.
https://insilicochemistry.net
(614)312-7528 (c)
Skype:  smolnar1

Re: Boot Problem

[Tom Furie]

"Stephen P. Molnar"  writes:


> On 12/05/2023 12:47 PM, Tom Furie wrote:
>> "Stephen P. Molnar"  writes:
>>
>>> I have Bookworm installed on a 1TB SSD. When I attempted logging this
>>> morning I failed! Rather than opening my XFCE desktop I was sent back
>>> tot he login screen, over and over and . I got the
>> When you say "back to the login screen", do you mean back to a graphical
>> login screen, or to a text console login screen?
>>
> Xfce4 graphical login screen

Then the problem is not a display issue, but something wrong in loading
the desktop. I don’t use XFCE, but hopefully this means dead-end lines
of enquiry such as display drivers are halted, and that someone with
XFCE experience can chime in and offer advice.

Re: Boot Problem

[Stephen P. Molnar]

I've attached the log. I hope that someone can tell me what the problem is.

Thanks inn advance.


On 12/05/2023 11:59 AM, Joe wrote:

On Tue, 5 Dec 2023 11:05:15 -0500
"Stephen P. Molnar"  wrote:


I have Bookworm installed on a 1TB SSD. When I attempted logging this
morning I failed! Rather than opening my XFCE desktop I was sent back
tot he login screen, over and over and . I got the
same result attempting to login as root. I have to assume that grub
has been
corrupted>

As it happens I also have Bookworm installed on a second SSD on my
platform. I'm there sending this email

I have Grub Customizer installed in both. I have also just downloaded
and burned debian-12-2-0-ams64.

I am very nervous about messing with the OS. What might be my best
course of action to fix the problem (short of reinstalling)?


As Hans has said, this is a display issue, long after grub has
finished, if you're seeing a login prompt. Almost always, that means
your X session is not starting.

Something you could try first is to look at /var/log/Xorg.0.log as
there may be a clue there to the problem.



--
Stephen P. Molnar, Ph.D.
https://insilicochemistry.net
(614)312-7528 (c)
Skype:  smolnar1

[ 7.958] 
X.Org X Server 1.21.1.7
X Protocol Version 11, Revision 0
[ 7.958] Current Operating System: Linux AbNormal 6.1.0-11-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-4 (2023-08-08) x86_64
[ 7.958] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-11-amd64 root=UUID=5b89d91f-1709-4d1c-9421-32aef272fac5 ro quiet
[ 7.958] xorg-server 2:21.1.7-3 (https://www.debian.org/support) 
[ 7.958] Current version of pixman: 0.42.2
[ 7.958] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[ 7.958] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 7.958] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Dec  5 09:53:34 2023
[ 7.965] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 7.971] (==) No Layout section.  Using the first Screen section.
[ 7.971] (==) No screen section available. Using defaults.
[ 7.971] (**) |-->Screen "Default Screen Section" (0)
[ 7.971] (**) |   |-->Monitor ""
[ 7.972] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[ 7.972] (==) Automatically adding devices
[ 7.972] (==) Automatically enabling devices
[ 7.972] (==) Automatically adding GPU devices
[ 7.972] (==) Automatically binding GPU devices
[ 7.972] (==) Max clients allowed: 256, resource mask: 0x1f
[ 7.980] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 7.980] 	Entry deleted from font path.
[ 7.984] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/100dpi/:unscaled,
	/usr/share/fonts/X11/75dpi/:unscaled,
	/usr/share/fonts/X11/Type1,
	/usr/share/fonts/X11/100dpi,
	/usr/share/fonts/X11/75dpi,
	built-ins
[ 7.984] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 7.984] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 7.984] (II) Loader magic: 0x55ab5609bf00
[ 7.984] (II) Module ABI versions:
[ 7.984] 	X.Org ANSI C Emulation: 0.4
[ 7.984] 	X.Org Video Driver: 25.2
[ 7.984] 	X.Org XInput driver : 24.4
[ 7.984] 	X.Org Server Extension : 10.0
[ 7.985] (++) using VT number 7

[ 7.985] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 7.986] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 7.986] (II) Platform probe for /sys/devices/pci:00/:00:02.0/:01:00.0/drm/card0
[ 7.992] (--) PCI:*(1@0:0:0) 1002:68f9:1545:5450 rev 0, Mem @ 0xc000/268435456, 0xfea2/131072, I/O @ 0xe000/256, BIOS @ 0x/131072
[ 7.993] (II) LoadModule: "glx"
[ 7.995] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 8.017] (II) Module glx: vendor="X.Org Foundation"
[ 8.017] 	compiled for 1.21.1.7, module version = 1.0.0
[ 8.017] 	ABI class: X.Org Server Extension, version 10.0
[ 8.017] (II) Applying OutputClass "Radeon" to /dev/dri/card0
[ 8.017] 	loading driver: radeon
[ 8.017] (==) Matched radeon as autoconfigured driver 0
[ 8.017] (==) Matched ati as autoconfigured driver 1
[ 8.017] (==) Matched modesetting as autoconfigured driver 2
[ 8.017] (==) Matched fbdev as autoconfigured driver 3
[ 8.017] (==) Matched vesa as autoconfigured driver 4
[ 8.017] (==) Assigned the driver to the xf86ConfigLayout
[ 8.017] (II) LoadModule: "radeon"
[ 8.017] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[ 8.035] (II) Module radeon: vendor="X.Org Foundation"
[ 8.035] 	compiled for 

Re: Boot Problem

[Stephen P. Molnar]

Xfce4 graphical login screen


On 12/05/2023 12:47 PM, Tom Furie wrote:

"Stephen P. Molnar"  writes:


I have Bookworm installed on a 1TB SSD. When I attempted logging this
morning I failed! Rather than opening my XFCE desktop I was sent back
tot he login screen, over and over and . I got the

When you say "back to the login screen", do you mean back to a graphical
login screen, or to a text console login screen?



--
Stephen P. Molnar, Ph.D.
https://insilicochemistry.net
(614)312-7528 (c)
Skype:  smolnar1

Re: Boot Problem

[Tom Furie]

"Stephen P. Molnar"  writes:

> I have Bookworm installed on a 1TB SSD. When I attempted logging this
> morning I failed! Rather than opening my XFCE desktop I was sent back
> tot he login screen, over and over and . I got the

When you say "back to the login screen", do you mean back to a graphical
login screen, or to a text console login screen?

Re: Boot Problem

[Joe]

On Tue, 5 Dec 2023 11:05:15 -0500
"Stephen P. Molnar"  wrote:

> I have Bookworm installed on a 1TB SSD. When I attempted logging this 
> morning I failed! Rather than opening my XFCE desktop I was sent back 
> tot he login screen, over and over and . I got the
> same result attempting to login as root. I have to assume that grub
> has been 
> corrupted>  
> 
> As it happens I also have Bookworm installed on a second SSD on my 
> platform. I'm there sending this email
> 
> I have Grub Customizer installed in both. I have also just downloaded 
> and burned debian-12-2-0-ams64.
> 
> I am very nervous about messing with the OS. What might be my best 
> course of action to fix the problem (short of reinstalling)?
>

As Hans has said, this is a display issue, long after grub has
finished, if you're seeing a login prompt. Almost always, that means
your X session is not starting.

Something you could try first is to look at /var/log/Xorg.0.log as
there may be a clue there to the problem.

-- 
Joe

Re: Boot Problem

[Hans]

Am Dienstag, 5. Dezember 2023, 17:05:15 CET schrieb Stephen P. Molnar:
To get closer to the cause, I suggest to remove temporaryly any loginmamanger 
out of the way  Either /usr/bin/xdm, /usr/bin/kdm, /usr/bin/gdm or /usr/bin/
xdm, whatever. Copy it somewhere, i.e. to /root

Then reboot and from thhe cli use the command "startx" to start into graphical 
mode. Mostly the X-server is the problem.

But now you can see, if the required kernel module is started and the required 
acceleration module is started. Or just get the error message.

In most cases I got into trouble, it was the module of NVídia, which was not 
built correctly or unavailable.

Creating temporarily a simple xorg.conf file copied to /etc/X11/ let you force 
to load different graphical drivers. Mostly "vesa" should work. but depending 
on your hardware it might be "nvidia" or "nouveau" or "ati" whatever.

As we do not know, which graphic chip you are using, we can only guess.

Please also note, that in the past I got into problems with the nouveau kernel 
module, whilst the proprietrary driver from NVidia worked perfectly. However, 
this is only related to NVidia cards. 

My greatest problems with NVidia cards was mostly after a kernel upgrade, as 
the kernel module could often not be built with a newer kernel.

This might also happen by AMD or ATI graphiccards, as they (as far as I know), 
also depend a kernel module and a related graphics module.

Hope this helps a little bit.

Good luck!

Hans 

> I have Bookworm installed on a 1TB SSD. When I attempted logging this
> morning I failed! Rather than opening my XFCE desktop I was sent back
> tot he login screen, over and over and . I got the same
> result attempting to login as root. I have to assume that grub has been
> corrupted>
> 
> As it happens I also have Bookworm installed on a second SSD on my
> platform. I'm there sending this email
> 
> I have Grub Customizer installed in both. I have also just downloaded
> and burned debian-12-2-0-ams64.
> 
> I am very nervous about messing with the OS. What might be my best
> course of action to fix the problem (short of reinstalling)?
> 
> Thanks in advance

Boot Problem

[Stephen P. Molnar]

I have Bookworm installed on a 1TB SSD. When I attempted logging this 
morning I failed! Rather than opening my XFCE desktop I was sent back 
tot he login screen, over and over and . I got the same 
result attempting to login as root. I have to assume that grub has been 
corrupted>


As it happens I also have Bookworm installed on a second SSD on my 
platform. I'm there sending this email


I have Grub Customizer installed in both. I have also just downloaded 
and burned debian-12-2-0-ams64.


I am very nervous about messing with the OS. What might be my best 
course of action to fix the problem (short of reinstalling)?


Thanks in advance

--
Stephen P. Molnar, Ph.D.
https://insilicochemistry.net
(614)312-7528 (c)
Skype:  smolnar1

Re: RPI boot problem (some OT) [solved]

[ghe]

On 8/10/19 11:19 AM, ghe wrote:

Fixed. I did a few things differently, and it came up:

I verified the NOOBS file with sha256 (match).
I unzipped directly to the SD chip.
I moved the HDMI connector to the one toward the back.

Even though I saw nothing in any dox about it making any difference, I'm
inclined to think moving the HDMI cable was the fix, but when I booted
with it in the other one, the square rainbow didn't come up this time.
That makes me think that unzipping to the chip might have made some
difference. And of course, there's always the phase of the moon...

-- 
Glenn English

Re: RPI boot problem (some OT)

[deloptes]

ghe wrote:

> I know this isn't the best place to talk about Raspberry Pis, but there
> are people here who are familiar with them, and probably people who can
> point me to the correct place. And they do run Debian...

I don't have that modern RPI, but usually there are ready images to use. Did
you try one?

I personally ended up using TFTP boot. The only thing I had to prepare was
an old SD card to hold the boot loader.

If the HDMI does not come up ... I don't know - this should be there  IMO
regardless of boot.

RPI boot problem (some OT)

[ghe]

I know this isn't the best place to talk about Raspberry Pis, but there
are people here who are familiar with them, and probably people who can
point me to the correct place. And they do run Debian...

My 2G RPi4 arrived yesterday, and it doesn't boot, not all the way
anyway. The red power led goes on, the green 'disk' activity led
flashes, it displays the square rainbow flash image, but doesn't go any
farther than that (the green led stays on). The rainbow display stays on
forever, as far as I can tell.

I've already tried:

Loading a known working 3+ Buster -- did nothing; no surprise. But that
chip was built from the same Buster NOOBS file as the one I prepared for
the 4.

Replacing the SD chip -- no difference.

Reloading the SD chip -- no difference in the boot process. When I went
to gparted to repartition the chip, it looked like it had begun some of
the Raspian partitioning. But it hadn't finished; there was a huge area
that was still available.

Downloading and installing a different NOOBS file (lite instead of full)
-- no difference.

Looking for help on the RPi website -- very little help; they talked
about a new bootloader and told me how to see if I needed it. I didn't
(the green led comes on and blinks). And I already knew how to plug in
the HDMI cable :-)

Looked for help anywhere on the web -- lots of other RPi4 boot problems
discussed, but not mine.

Giving it an hour or so to cogitate and go on to the next step -- the
rainbow was still on the monitor, but the green led had gone out.

This is not the first 'Pi I've loaded a Raspian OS into (the 2 was the
first), and I followed the same procedures I always have. It is,
however, the first time I've had any trouble at all.

The 'Pi seems OK to me -- it does display that flash screen, and that
takes working some CPU cycles and some working RAM. I don't think the
software's bad -- it seems to do quite a bit of stuff trying to boot.

I'm at a loss. A solution/suggestion or a URL would be greatly appreciated.

-- 
Glenn English

Re: Boot Problem

[Pascal Hambourg]

Le 16/06/2019 à 15:53, Stephen P. Molnar a écrit :

I have just installed a new SSD in my 64 bit Stretch platform.

When I boot the machine I get the following error:

error: file '/boot/grub/i386-pc/normalmod' not found
Entering rescue mode .. . .
grub rescue>_

Pressing Contro-Alt-Delete reboots the system.  Pressing Delete , or 
F-8,during the post opens the ASUS UFEI Bios Utility - EZ mode 
(actually, F-8 opens the boot selection).


Clicking  on P0 boots the machine normally.

(...)

Sda1 is the Stretch OS (P0), sdd1 is the new drive.

(...)

     1. What might be the source of the error?


My first guess, like bw, would be that adding the new SSD has somhow 
changed the BIOS/UEFI boot order and now it defaults to boot another 
disk which contains an incomplete GRUB (maybe a remain of a deleted 
installation).


At the grub rescue prompt, you could type the commands "ls" and "set" 
and report the returns (not all variables, only "cmdline" and "prefix" 
are interesting).
You could also run bootinfoscript from the boot-info-script package and 
post the initial part of the report (before the contents of grub.cfg).


     2. More importantly, what is the solution, would running 
update-grub solve the problem?


No. A missing or corrupted grub.cfg does not cause this kind of error. 
The error means that the GRUB core image successfully loaded but failed 
to find the contents of /boot/grub where it expected it.


The best solution is to fix the boot order in the BIOS/UEFI settings. A 
workaround when the former is not applicable is to run grub-install to 
install a copy of GRUB on the actual boot drive.

Re: Boot Problem

[bw]

In-Reply-To: <5d0649da.40...@sbcglobal.net>

On Sun, 16 Jun 2019, Stephen P. Molnar wrote:

> 
> On 06/16/2019 12:16 PM, bw wrote:
> > In-Reply-To: <5d0649da.40...@sbcglobal.net>
> > > Stephen P. Molnar, Ph.D. says...
> > > I have just installed a new SSD in my 64 bit Stretch platform.
> > > 
> > > When I boot the machine I get the following error:
> > > 
> > > error: file '/boot/grub/i386-pc/normalmod' not found
> > > Entering rescue mode .. . .
> > > grub rescue>_
> > > 
> > > Pressing Contro-Alt-Delete reboots the system. Pressing Delete , or
> > > F-8,during the post opens the ASUS UFEI Bios Utility - EZ mode (actually,
> > > F-8 opens the boot selection).
> > > 
> > > Clicking  on P0 boots the machine normally.
> > > ...
> > Since the machine boots normally when you select P0 then why
> > not just use ASUS UFEI Bios Utility to set that as default?
> > 
> > Since the new drive has a filesystem, I'd say you did more than just
> > install it?  Drive/Boot order is nothing to take lightly, if you set grub
> > to depend on it, then you can't rearrange drives without causing an issue.
> > 
> > If you are going to remove that drive, then you don't want to boot from it
> > as a permanent solution.  You will need to migrate the bootloader off
> > this drive altogether.  Do some reading first, multi boot is extensively
> > well represented topic on the interwebs.
> > 
> > Good Luck
> > 
> > 
> 
> I have not installed the OS on the new drive.  I did, however, format it so
> that I  put it into the fstab.
> 
> -- 
> Stephen P. Molnar, Ph.D.  Life is a fuzzy set
> www.molecular-modeling.netStochastic and multivariate
> (614)312-7528(c)
> Skype:  smolnar1
> 
> 

There are several ways to setup dual boot that might work well for you.  
If all you want to do is try out buster and see if you like it, then I'd 
probably use a Live System though instead of installing right now.  
There's no hurry.  I like David Christensen's ideas for getting you on a 
good reliable setup with some redundancy... and maybe using VM to see how 
you can migrate your software into the newer os.

If the idea is to switch back to a single GNU/Linux os installation, with 
multiple physical drives, then I would probably go ahead now and rearrange 
the drives so that whichever drive you wish to install the boot manager on 
is the first physical drive.

What happens is, when you run grub-install, or allow the debian installer 
to do it, grub sets and stores something called the $prefix on the drive.  
This is a reference to the order of the drives, that tells grub where to 
load files during the boot process.  Some BIOS have a habit of always 
making the boot device (hd0) and some don't.  Some bioses will rearrange 
devices when you add one, so you really have to be careful.

This is a good link that might help you understand, and has some links to 
how you can use grub to examine the setup.

https://unix.stackexchange.com/questions/70538/grub-error-file-grub-i386-pc-normal-mod-not-found

It's not too complicated, but it is complicated so make sure and have a 
backup plan for when you have problems.  A good live usb/cd, or knowing 
how to use the install media in rescue mode can help.

L8r,
bw

Re: Boot Problem

[David Christensen]

On 6/16/19 6:53 AM, Stephen P. Molnar wrote:

I have just installed a new SSD in my 64 bit Stretch platform.

When I boot the machine I get the following error:

error: file '/boot/grub/i386-pc/normalmod' not found
Entering rescue mode .. . .
grub rescue>_

Pressing Contro-Alt-Delete reboots the system.  Pressing Delete , or 
F-8,during the post opens the ASUS UFEI Bios Utility - EZ mode 
(actually, F-8 opens the boot selection).


Clicking  on P0 boots the machine normally.

Here are the drives:

blkid
/dev/sda1: UUID="b780b7fb-05a5-4996-8ad5-cd2a578bb4f2" TYPE="ext4" 
PARTUUID="a14552f2-01"
/dev/sda5: UUID="2e6c48ee-b1b5-441e-ae90-549f5e3b6134" TYPE="swap" 
PARTUUID="a14552f2-05"
/dev/sdc1: UUID="1f363165-2c59-4236-850d-36d1e807099e" TYPE="ext4" 
PARTUUID="eb2be395-01"
/dev/sdb1: UUID="900b5f0b-4f3d-4a64-8c91-29aee4c6fd07" TYPE="ext4" 
PARTUUID="0bc7db76-01"
/dev/sdb5: UUID="7c386aca-a547-475f-8616-f7664f93c595" TYPE="swap" 
PARTUUID="0bc7db76-05"
/dev/sdd1: UUID="51941391-3c92-4370-a330-270d2c4d7003" TYPE="ext4" 
PARTUUID="7809855e-01"


Sda1 is the Stretch OS (P0), sdd1 is the new drive. I had no problems 
installing the new drive, nor making it known to Stretch. My intention 
is to install Buster on sdd1, while maintaining Stretch on sda1 for a 
hopefully short period of time.  I should note that I have added the 
i386 applications to /etc/apt/sources.list as a number of my 
applications require i386 libraries.


I have absolutely no idea as to why the new boot error, nor the solution:

     1. What might be the source of the error?
     2. More importantly, what is the solution, would running 
update-grub solve the problem?


Comments will be appreciated.

Thanks in advance.



Did you read my reply to your previous post?

https://lists.debian.org/debian-user/2019/06/msg00335.html


David

Re: Boot Problem

[songbird]

Stephen P. Molnar wrote:

> I have just installed a new SSD in my 64 bit Stretch platform.

  what do you mean by "installed"?  there is a lot
of difference between plugging it in vs. plugging 
it in and putting something on it.

  what did you do?

  give details.  we don't know what you did nor can
we read your mind.


> When I boot the machine I get the following error:
>
> error: file '/boot/grub/i386-pc/normalmod' not found
> Entering rescue mode .. . .
> grub rescue>_
>
> Pressing Contro-Alt-Delete reboots the system.  Pressing Delete , or 
> F-8,during the post opens the ASUS UFEI Bios Utility - EZ mode 
> (actually, F-8 opens the boot selection).
>
> Clicking  on P0 boots the machine normally.

  so you can boot the system into Stretch ok.


> Here are the drives:
>
> blkid
> /dev/sda1: UUID="b780b7fb-05a5-4996-8ad5-cd2a578bb4f2" TYPE="ext4" 
> PARTUUID="a14552f2-01"
> /dev/sda5: UUID="2e6c48ee-b1b5-441e-ae90-549f5e3b6134" TYPE="swap" 
> PARTUUID="a14552f2-05"
> /dev/sdc1: UUID="1f363165-2c59-4236-850d-36d1e807099e" TYPE="ext4" 
> PARTUUID="eb2be395-01"
> /dev/sdb1: UUID="900b5f0b-4f3d-4a64-8c91-29aee4c6fd07" TYPE="ext4" 
> PARTUUID="0bc7db76-01"
> /dev/sdb5: UUID="7c386aca-a547-475f-8616-f7664f93c595" TYPE="swap" 
> PARTUUID="0bc7db76-05"
> /dev/sdd1: UUID="51941391-3c92-4370-a330-270d2c4d7003" TYPE="ext4" 
> PARTUUID="7809855e-01"
>
> Sda1 is the Stretch OS (P0), sdd1 is the new drive. I had no problems 
> installing the new drive, nor making it known to Stretch.

> My intention 
> is to install Buster on sdd1, while maintaining Stretch on sda1 for a 
> hopefully short period of time.  I should note that I have added the 
> i386 applications to /etc/apt/sources.list as a number of my 
> applications require i386 libraries.

  i have no idea how to run a mixed system like that
so you are out of my range of experience there.

  i just use the amd64 debs.

  if it was running ok before i see no reason why you'd
add that now?


> I have absolutely no idea as to why the new boot error, nor the solution:
>
>  1. What might be the source of the error?
>  2. More importantly, what is the solution, would running 
> update-grub solve the problem?
>
> Comments will be appreciated.

  since we don't know what you've done i don't know
for sure what has changed.  running update-grub may
make no change at all.

  the more you can say what you did the better 
context we have for replying.


  songbird

Re: Boot Problem

[bw]

In-Reply-To: <5d0649da.40...@sbcglobal.net>
>Stephen P. Molnar, Ph.D. says...
>I have just installed a new SSD in my 64 bit Stretch platform.
>
>When I boot the machine I get the following error:
>
>error: file '/boot/grub/i386-pc/normalmod' not found
>Entering rescue mode .. . .
>grub rescue>_
>
>Pressing Contro-Alt-Delete reboots the system. Pressing Delete , or 
>F-8,during the post opens the ASUS UFEI Bios Utility - EZ mode (actually, 
>F-8 opens the boot selection).
>
>Clicking  on P0 boots the machine normally.
>...

Since the machine boots normally when you select P0 then why 
not just use ASUS UFEI Bios Utility to set that as default?

Since the new drive has a filesystem, I'd say you did more than just 
install it?  Drive/Boot order is nothing to take lightly, if you set grub 
to depend on it, then you can't rearrange drives without causing an issue.

If you are going to remove that drive, then you don't want to boot from it 
as a permanent solution.  You will need to migrate the bootloader off 
this drive altogether.  Do some reading first, multi boot is extensively 
well represented topic on the interwebs.

Good Luck

Boot Problem

[Stephen P. Molnar]

I have just installed a new SSD in my 64 bit Stretch platform.

When I boot the machine I get the following error:

error: file '/boot/grub/i386-pc/normalmod' not found
Entering rescue mode .. . .
grub rescue>_

Pressing Contro-Alt-Delete reboots the system.  Pressing Delete , or 
F-8,during the post opens the ASUS UFEI Bios Utility - EZ mode 
(actually, F-8 opens the boot selection).


Clicking  on P0 boots the machine normally.

Here are the drives:

blkid
/dev/sda1: UUID="b780b7fb-05a5-4996-8ad5-cd2a578bb4f2" TYPE="ext4" 
PARTUUID="a14552f2-01"
/dev/sda5: UUID="2e6c48ee-b1b5-441e-ae90-549f5e3b6134" TYPE="swap" 
PARTUUID="a14552f2-05"
/dev/sdc1: UUID="1f363165-2c59-4236-850d-36d1e807099e" TYPE="ext4" 
PARTUUID="eb2be395-01"
/dev/sdb1: UUID="900b5f0b-4f3d-4a64-8c91-29aee4c6fd07" TYPE="ext4" 
PARTUUID="0bc7db76-01"
/dev/sdb5: UUID="7c386aca-a547-475f-8616-f7664f93c595" TYPE="swap" 
PARTUUID="0bc7db76-05"
/dev/sdd1: UUID="51941391-3c92-4370-a330-270d2c4d7003" TYPE="ext4" 
PARTUUID="7809855e-01"


Sda1 is the Stretch OS (P0), sdd1 is the new drive. I had no problems 
installing the new drive, nor making it known to Stretch. My intention 
is to install Buster on sdd1, while maintaining Stretch on sda1 for a 
hopefully short period of time.  I should note that I have added the 
i386 applications to /etc/apt/sources.list as a number of my 
applications require i386 libraries.


I have absolutely no idea as to why the new boot error, nor the solution:

1. What might be the source of the error?
2. More importantly, what is the solution, would running 
update-grub solve the problem?


Comments will be appreciated.

Thanks in advance.

--
Stephen P. Molnar, Ph.D.  Life is a fuzzy set
www.molecular-modeling.netStochastic and multivariate
(614)312-7528(c)
Skype:  smolnar1

Re: boot problem after updating dropbear [solved -- MANUAL initrd works required]

[Andrew McGlashan]

Hi,

Okay, it turns out that the only files that were missing were ones that
I had in the /etc/initramfs-tools/root/ directory.


The only files in the faulty initrd image were from the
/etc/initramfs-tools/root/.ssh/ directory, so missing .profile and other
required files.


I modified the initrd to include those missing files and everything is
functional again.

 - extract initrd
 - add files
 - rebuild initrd

 - replace /boot/initrd file with my new one.

So, it seems that "update-initramfs -u -k all" only missed those extra
custom files placed in the /etc/initramfs-tools/root/ directory.

There was not anything particularly special in the .profile, except for
the useful aliases -- however, those aliases /may/ have helped the /init
script find required binaries to boot properly.

I cannot seem to find any reason why those files were included properly
before, but not now (without manual intervention).

Here's the .profile fwiw:

# cat initrd-wrk--20160926b/root/.profile
# ~/.profile: executed by Bourne-compatible login shells.

alias l='ls -alrt'

# dropbear aliases
alias db1='/sbin/cryptsetup luksOpen /dev/md0 md0_crypt'
alias db2='/sbin/cryptsetup luksOpen /dev/md1 md1_crypt'
alias db3='/sbin/cryptsetup luksOpen /dev/md2 md2_crypt'
alias db4='/sbin/cryptsetup statusmd0_crypt'
alias db5='/sbin/cryptsetup statusmd1_crypt'
alias db6='/sbin/cryptsetup statusmd2_crypt'
alias db7='ps|grep askpass;echo kill -9 $(pidof askpass)'


# mdadm aliases
alias mdadm='/sbin/mdadm'
alias mdstat='cat /proc/mdstat'
alias md0='mdadm -D /dev/md0'
alias md1='mdadm -D /dev/md1'
alias md2='mdadm -D /dev/md2'


# /sbin/ binary aliases
for binary in badblocks blkid fdisk hdparm lvm parted
do
alias $binary="/sbin/$binary"
done


# /usr/bin/ binary aliases
for binary in nohup pv screen tee vim who
do
alias $binary="/usr/bin/$binary"
done

alias|sort

if [ "$BASH" ]; then
  if [ -f ~/.bashrc ]; then
. ~/.bashrc
  fi
fi

#mesg n


Kind Regards
AndrewM




signature.asc
Description: OpenPGP digital signature

boot problem after updating dropbear

[Andrew McGlashan]

Hi,

After dropbear update as follows:

< ii  dropbear   2012.55-1.3
   amd64lightweight SSH2 server and client
---
> ii  dropbear   2012.55-1.3+deb7u1
   amd64lightweight SSH2 server and client

Debian Version 7.11 (Wheezy)

Before the update I could ssh to box, connecting with dropbear, and
unlock crypt volumes, then kill the askpass process to continue the boot.

After the update, the ssh session with dropbear is missing all sorts of
stuff; my aliases and other setup files aren't available.

I managed to manually boot by  attaching a keyboard to the box and doing
the following:

  - answer "askpass" prompt, it unlocks md0_crypt device which has root

  - it fails to mount other lvm2 volume groups, so Iogin at the
maintenance prompt.

  - I open the two other crypt volumes using:

  cryptsetup luksOpen /dev/md1 md1_crypt

  cryptsetup luksOpen /dev/md2 md2_crypt

  - then I exit from the maintenance prompt and the machine boots
normally from there.

Once back in to the machine, I run the following:

# update-initramfs -k all -u -v
Available versions:  3.2.0-4-amd64
Execute: /usr/sbin/update-initramfs -u -k "3.2.0-4-amd64" -b /boot -v
Keeping /boot/initrd.img-3.2.0-4-amd64.dpkg-bak
update-initramfs: Generating /boot/initrd.img-3.2.0-4-amd64
Adding module
/lib/modules/3.2.0-4-amd64/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko
Copying module directory kernel/drivers/hid
(excluding hid-*ff.ko hid-a4tech.ko hid-cypress.ko hid-dr.ko
hid-elecom.ko hid-gyration.ko hid-icade.ko hid-kensington.ko hid-kye.ko
hid-lcpower.ko hid-magicmouse.ko hid-multitouch.ko hid-ntrig.ko
hid-petalynx.ko hid-picolcd.ko hid-pl.ko hid-ps3remote.ko hid-quanta.ko
hid-roccat-ko*.ko hid-roccat-pyra.ko hid-saitek.ko hid-sensor-hub.ko
hid-sony.ko hid-speedlink.ko hid-tivo.ko hid-twinhan.ko hid-uclogic.ko
hid-wacom.ko hid-waltop.ko hid-wiimote.ko hid-zydacron.ko)
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/hid/hid.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/hid/hid-ezkey.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/hid/hid-keytouch.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/usb/usb-common.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/usb/core/usbcore.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/hid/usbhid/usbhid.ko
Adding module
/lib/modules/3.2.0-4-amd64/kernel/drivers/hid/hid-logitech-dj.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/hid/hid-chicony.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/hid/hid-roccat.ko
Adding module
/lib/modules/3.2.0-4-amd64/kernel/drivers/hid/hid-roccat-common.ko
Adding module
/lib/modules/3.2.0-4-amd64/kernel/drivers/hid/hid-roccat-arvo.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/hv/hv_vmbus.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/hid/hid-hyperv.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/hid/hid-ortek.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/hid/hid-belkin.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/hid/hid-primax.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/input/ff-memless.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/hid/hid-sjoy.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/hid/hid-logitech.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/hid/hid-samsung.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/hid/hid-cherry.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/hid/hid-microsoft.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/hid/hid-monterey.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/hid/hid-topseed.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/sound/soundcore.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/sound/core/snd.ko
Adding module
/lib/modules/3.2.0-4-amd64/kernel/sound/core/seq/snd-seq-device.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/sound/core/snd-rawmidi.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/hid/hid-prodikeys.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/hid/hid-sunplus.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/hid/hid-apple.ko
Copying module directory kernel/drivers/net
(excluding appletalk arcnet bonding can hamradio irda pcmcia tokenring
usb wan wimax wireless)
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/net/sungem_phy.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/fs/configfs/configfs.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/net/netconsole.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/net/mii.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/net/ifb.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/net/sb1000.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/net/macvlan.ko
Adding module /lib/modules/3.2.0-4-amd64/kernel/drivers/net/macvtap.ko
Adding module 

Re: boot problem

[Thiago]

Hi, you can open the Terminal and type:
# grub-install /dev/sda1

And
# update-grub2

This will do what you need.

Em 06-03-2016 03:55, lina escreveu:
> Hi,
>
> After install the debian,
>
> it goes to debian OS system directly, without showing me the option of
> start Mac OS or debian OS.
>
> Any suggestions, thanks,
>

Re: boot problem

[Keith Bainbridge]

Good morning Lina

I don't get that the partitions aren't showing sda1 to sda15.  I would expect 
osx to be on sda3 or sda4 from memory.  And my version of osx didn't have a 
separate swap partition. So what are the other missing partitions? 

Are there any  other partitions listed in the devices section of your file 
manager that didn't mount? I haven't had a dual boot system for so long I don't 
recall the names, but you will recognise the names from your osx install. 

Failing that have you checked what gparted lists. 

What is /etc/fstab listing?   I think the osx partitions will be listed as not 
auto mounting. 


I did think later last night, when I said hold the alt key, I meant hold it 
from when the boot process starts (power button on cold start) until you get 
the menu of icons. This feels like forever on my 2008 macbook. I trust it is 
getting quicker.  And you will get a menu. 


 Original Message 
From: lina <lina.lastn...@gmail.com>
Sent: Mon Mar 07 01:01:31 AEDT 2016
To: Keith Bainbridge <keithrbaugro...@gmail.com>
Cc: Debian Lists <debian-user@lists.debian.org>
Subject: Re: boot problem

df -h
Filesystem  Size  Used Avail Use% Mounted on
/dev/sda4   641M  235M  360M  40% /
udev 10M 0   10M   0% /dev
tmpfs   1.6G  9.1M  1.6G   1% /run
/dev/sda819G  3.6G   14G  21% /usr
tmpfs   3.9G   68K  3.9G   1% /dev/shm
tmpfs   5.0M  4.0K  5.0M   1% /run/lock
tmpfs   3.9G 0  3.9G   0% /sys/fs/cgroup
/dev/sda13  181M   32M  136M  20% /boot
/dev/sda11  547M  720K  507M   1% /tmp
/dev/sda715G  1.2G   13G   9% /home
/dev/sda12  3.7G  7.6M  3.4G   1% /usr/local
/dev/sda9   3.7G 1010M  2.5G  29% /var
/dev/sda10  6.3G   15M  6.0G   1% /var/local
/dev/sda1   197M   16M  182M   8% /boot/efi
/dev/sda15  393G   71M  373G   1% /scratch
tmpfs   788M  4.0K  788M   1% /run/user/116
tmpfs   788M  8.0K  788M   1% /run/user/1000

On Sun, Mar 6, 2016 at 3:56 PM, Keith Bainbridge
<keithrbaugro...@gmail.com> wrote:
> Good afternoon Lina
>
> Try holding the alt key as you boot.  You should get a few icons to choose 
> osx or linux.
>
>
> If not, please send us output of command df -h
>
>
>  Original Message 
> From: lina <lina.lastn...@gmail.com>
> Sent: Sun Mar 06 17:55:17 AEDT 2016
> To: Debian Lists <debian-user@lists.debian.org>
> Subject: boot problem
>
> Hi,
>
> After install the debian,
>
> it goes to debian OS system directly, without showing me the option of
> start Mac OS or debian OS.
>
> Any suggestions, thanks,
>
>
> Keith Bainbridge
>
> 0447 667 468
>
> keithrbaugro...@gmail.com
>
> Sent from my APad

Keith Bainbridge

0447 667 468 

keithrbaugro...@gmail.com 

Sent from my APad 

Re: boot problem

[lina]

df -h
Filesystem  Size  Used Avail Use% Mounted on
/dev/sda4   641M  235M  360M  40% /
udev 10M 0   10M   0% /dev
tmpfs   1.6G  9.1M  1.6G   1% /run
/dev/sda819G  3.6G   14G  21% /usr
tmpfs   3.9G   68K  3.9G   1% /dev/shm
tmpfs   5.0M  4.0K  5.0M   1% /run/lock
tmpfs   3.9G 0  3.9G   0% /sys/fs/cgroup
/dev/sda13  181M   32M  136M  20% /boot
/dev/sda11  547M  720K  507M   1% /tmp
/dev/sda715G  1.2G   13G   9% /home
/dev/sda12  3.7G  7.6M  3.4G   1% /usr/local
/dev/sda9   3.7G 1010M  2.5G  29% /var
/dev/sda10  6.3G   15M  6.0G   1% /var/local
/dev/sda1   197M   16M  182M   8% /boot/efi
/dev/sda15  393G   71M  373G   1% /scratch
tmpfs   788M  4.0K  788M   1% /run/user/116
tmpfs   788M  8.0K  788M   1% /run/user/1000

On Sun, Mar 6, 2016 at 3:56 PM, Keith Bainbridge
<keithrbaugro...@gmail.com> wrote:
> Good afternoon Lina
>
> Try holding the alt key as you boot.  You should get a few icons to choose 
> osx or linux.
>
>
> If not, please send us output of command df -h
>
>
>  Original Message 
> From: lina <lina.lastn...@gmail.com>
> Sent: Sun Mar 06 17:55:17 AEDT 2016
> To: Debian Lists <debian-user@lists.debian.org>
> Subject: boot problem
>
> Hi,
>
> After install the debian,
>
> it goes to debian OS system directly, without showing me the option of
> start Mac OS or debian OS.
>
> Any suggestions, thanks,
>
>
> Keith Bainbridge
>
> 0447 667 468
>
> keithrbaugro...@gmail.com
>
> Sent from my APad

Re: boot problem

[Keith Bainbridge]

Good afternoon Lina

Try holding the alt key as you boot.  You should get a few icons to choose osx 
or linux. 


If not, please send us output of command df -h 


 Original Message 
From: lina <lina.lastn...@gmail.com>
Sent: Sun Mar 06 17:55:17 AEDT 2016
To: Debian Lists <debian-user@lists.debian.org>
Subject: boot problem

Hi,

After install the debian,

it goes to debian OS system directly, without showing me the option of
start Mac OS or debian OS.

Any suggestions, thanks,


Keith Bainbridge

0447 667 468 

keithrbaugro...@gmail.com 

Sent from my APad 

boot problem

[lina]

Hi,

After install the debian,

it goes to debian OS system directly, without showing me the option of
start Mac OS or debian OS.

Any suggestions, thanks,

Re: bewildering boot problem -- a little more info

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Oct 05, 2015 at 11:05:20PM -0600, Glenn English wrote:

[...]

> > Hmmm. Sorry to be so unspecific.
> 
> No prob. Everybody's happy now. I just have some data to copy over from the 
> old disk. At least it wasn't the hardware...

In any case, glad you solved it :-)

regards
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlYTaO4ACgkQBcgs9XrR2kZ0uQCffpzX+e3a0RKH3LYbRYxR4PfA
E4UAnjT4Y1tWNs9wDqf8bC6SpjVmnuid
=Vkux
-END PGP SIGNATURE-

Re: bewildering boot problem -- a little more info

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Oct 05, 2015 at 11:53:06AM -0600, Glenn English wrote:
> 
> On Oct 5, 2015, at 1:04 AM, to...@tuxteam.de wrote:
> 
> > Then try "ssh @localhost".
> 
> Works, kinda. It does the same thing to localhost or the hostname, from the 
> console or from a terminal in XFCE. (I've got SSH running with keys around 
> the local net(s) (no login required)). The MOTD comes up right away, but 
> there's a long delay before the shell prompt comes up. 

Hmm. Weird. I dimly remember that tcpwrappers did something
similar: to check the host name they sometimes tried a
reverse host lookup, which took its time when it failed.

But perhaps I'm up the wrong alley.

Possibly watching the connection attempt with tcpdump or
wireshark sheds light on this.

The behavour of ssh you describe is weird indeed -- the
MOTD must be coming from the server side, so the connection
is established already. As if the shell were checking something
before it decides to talk to you.

Hmmm. Sorry to be so unspecific.

regards
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlYSuRkACgkQBcgs9XrR2kanRACcDe2WUz17WUUBnX4nVmO3r+NM
ly4AnRXwUaIlYD5RqSw+lsflkqArgEf6
=WQFH
-END PGP SIGNATURE-

Re: bewildering boot problem

[rlharris]

On Mon, October 5, 2015 12:53 pm, Glenn English wrote:
> It seems to me that there's a networking problem, but
> intermittent and from several directions. I don't understand it at all.
>
> Maybe it's hardware...

Have you had a lightning storm in the area recently?  And is everything
connected to the machine plugged into a power strip with a surge arrestor?

Reportedly, most lightning damage to computer gear is due to transients
entering through the telephone line, rather than from the power line.

And even without nearby lightning strokes, transients are found on power
lines, due to connection and disconnection of inductive and capacitive
loads.

Electrical transients can cause cumulative damage without causing
immediate failure.  A good analogy is the damage inflicted upon a large
boulder by repeatedly striking it with a sledge.  Even after many blows,
no damage may be apparent, but eventually a blow shatters the boulder,
because the damage is cumulative.  In this respect, solid-state devices
are like the boulder.

By the way, a surge arrestor also suffers cumulative damage; but it is
meant to be sacrificial.

Russ

Re: bewildering boot problem -- a little more info

[Glenn English]

On Oct 5, 2015, at 1:04 AM, to...@tuxteam.de wrote:

> Then try "ssh @localhost".

Works, kinda. It does the same thing to localhost or the hostname, from the 
console or from a terminal in XFCE. (I've got SSH running with keys around the 
local net(s) (no login required)). The MOTD comes up right away, but there's a 
long delay before the shell prompt comes up. 

startx takes a very long time and prints some error messages, but eventually 
runs XFCE as expected. Minicom works from a terminal in XFCE, but not from the 
console. iwconfig says wlan0 is connected to my wifi AP (Ethernet isn't 
available where the laptop is). A ping to a host on the LAN says there's no 
route available -- but there are a couple valid ones in the table.

OTOH, the kernel's startup messages are gone this morning. I'm thinking a bare 
metal reinstall is in order. One or more things are really bent in there 
somewhere. It seems to me that there's a networking problem, but intermittent 
and from several directions. I don't understand it at all.

Maybe it's hardware...

Thanks, everyone, for the suggestions.

-- 
Glenn English

Re: bewildering boot problem -- a little more info

[Felix Miata]

Glenn English composed on 2015-10-04 18:14 (UTC-0600):

> I disabled XDM (sure is nice to have text config files) and rebooted. It
> came up at a regular login prompt, and no error messages. startx took a
> *very* long time -- said it couldn't find the hostname (something like
> that) -- but it eventually started XFCE. And the messages were back.

> Something I forgot to mention: When XFCE starts and I open a terminal, the
> terminal comes up right away, but it takes  a long time (30+ seconds, it
> feels like) to display the prompt.

Do you have an entry in /etc/hosts matching your actual IP to the content in
/etc/hostname when you observe this delay?
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: bewildering boot problem -- a little more info

[Glenn English]

On Oct 5, 2015, at 11:53 AM, to...@tuxteam.de wrote:

> Hmm. Weird. I dimly remember that tcpwrappers did something
> similar: to check the host name they sometimes tried a
> reverse host lookup, which took its time when it failed.

I've never seen or heard of anything like this -- the kernel complaining of the 
wrong #defines in the source code? That, to me, is massively broken. Anyway, 
it's all OK now; it got a new Jessie this afternoon :-)

> But perhaps I'm up the wrong alley.

Probably. I claim there were just too many wrong alleys. And certainly not 
worth the time to try to fix it.

> Hmmm. Sorry to be so unspecific.

No prob. Everybody's happy now. I just have some data to copy over from the old 
disk. At least it wasn't the hardware...

-- 
Glenn English

Re: bewildering boot problem -- a little more info

[Glenn English]

On Oct 5, 2015, at 12:51 PM, Felix Miata  wrote:

> Do you have an entry in /etc/hosts matching your actual IP to the content in
> /etc/hostname when you observe this delay?

Yup. I rely on the host files, so I keep then correct and accurate.

-- 
Glenn English

Re: bewildering boot problem

[Glenn English]

On Oct 5, 2015, at 12:45 PM, rlhar...@oplink.net wrote:

> On Mon, October 5, 2015 12:53 pm, Glenn English wrote:

>> Maybe it's hardware...

It wasn't. A new install fixed everything.

> Have you had a lightning storm in the area recently?  

Yeah. That's common in Colorado.

> And is everything
> connected to the machine plugged into a power strip with a surge arrestor?

UPS. Where everything coming in goes to the battery, and everything out is 
generated by an oscillator and an amplifier.

> Reportedly, most lightning damage to computer gear is due to transients
> entering through the telephone line, rather than from the power line.

Nope again. This is a WiFi box.

-- 
Glenn English

Re: bewildering boot problem -- a little more info

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sun, Oct 04, 2015 at 06:14:44PM -0600, Glenn English wrote:
> I disabled XDM (sure is nice to have text config files) and rebooted. It came 
> up at a regular login prompt, and no error messages. startx took a *very* 
> long time -- said it couldn't find the hostname (something like that) -- but 
> it eventually started XFCE. And the messages were back.
> 
> Something I forgot to mention: When XFCE starts and I open a terminal, the 
> terminal comes up right away, but it takes  a long time (30+ seconds, it 
> feels like) to display the prompt.

All those 30-ish seconds timeout and the error message you mention
above smell of something trying to resolve a host name, failing
and giving up (timeout). Although I can't, for the life of me, imagine
what DNS lookups might be involved in the starting of a term.

To poke a bit in the dark, try (in a console) "ping localhost". What
happens? Then try "ssh @localhost". But I'm poking in
the dark.

Regards
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlYSIQ0ACgkQBcgs9XrR2kZyEQCcCi00QkAOR9TyRc8Ut8834eGP
9YIAoIA9lMqPVjJQAC5ErN902IV6zWVH
=W1jA
-END PGP SIGNATURE-

Re: bewildering boot problem -- a little more info

[Glenn English]

On Oct 5, 2015, at 1:04 AM,   wrote:

> All those 30-ish seconds timeout and the error message you mention
> above smell of something trying to resolve a host name, failing
> and giving up (timeout).

Yup. The timeouts do, anyway. The error messages from the kernel when I start 
XFCE never time out.

> Although I can't, for the life of me, imagine
> what DNS lookups might be involved in the starting of a term.

It's not just a term, it's somewhere in the X software. Most likely in XFCE. 

I don't understand the name lookup either, and the resolve config is set to 
look at /etc/hosts before hitting DNS. All the local hosts are in there. But 
I've seen the XFCE startup whine about not being to do DNS type things before.

> To poke a bit in the dark, try (in a console) "ping localhost". What
> happens?

Works great.

> Then try "ssh @localhost".

Hadn't though of trying ssh, but I bet it works to localhost. I'll try it in 
the morning.


I found those two things the kernel error messages are about 
(CAP_NET_ and the other CAP_ thing). They're in the kernel source 
code, in a file called something like capabilities.h. They're both #defines -- 
one is 15; the other is a different small integer (17 or 18, IIRC). Now I 
really have no idea what the boot is talking about. Sounds like it's telling me 
the kernel needs to be recompiled. 

They do have to do with setting capabilities in networking, though.

-- 
Glenn English

Re: bewildering boot problem

[rlharris]

In reply to Glenn English :

Inasmuch as you are running Xfce, is there any particular reason for
staying with Wheezy, which was the release which introduced the new Gnome?
 If not, the investment of two or three hours should have you up and
running in Jessie.

I have had opportunity to install Jessie with Xfce on several machines,
both amd64 and i386; they all have been running perfectly.

Sometimes operator results in a corrupted file, and sometimes a drive near
the end of its life can cause problems.  Besides, a fresh installation is
an opportunity for housecleaning.

Russ

bewildering boot problem

[Glenn English]

A few hours ago, my laptop (after booting Wheezy) started saying that it was 
trying to load a module for a network interface (CAP_SYS_MODULE) that was 
deprecated -- I should use CAP_NET_ADMIN instead. 

I'm configuring an old Cicso router using Putty to get to the RS232 port on the 
router -- that was fine yesterday. At boot, nothing has any idea about Putty, 
I'm pretty sure. And RS232 is rarely considered a significant network protocol, 
anyway.

I've been turning eth0 and wlan0 off and on because I'm working on a live 
network, so I don't want to disturb anything going on there. 

This morning, I added a printer to the laptop using CUPS. But I've done that on 
several machines with no problems at all. And the messages started a while 
after I did that. Long enough after that I don't think that's causing the 
problem.

On the computer's console, the message keeps repeating over and over, for a 
very long time, it looks like. It doesn't bother the text going back and forth 
to the router, but if I open a significant GUI (like a web browser), the CPU 
performance approaches a Z-80. And I can't ping anything, even when there's a 
reasonable routing table. Well, I can ping localhost, but not the machine's IP.

I turned off all the network interfaces, even loopback, with no effect. I 
deleted the printer I just put in, also with no effect. "find / -iname 
"**"" can't find either of the modules. Just sitting there, the OS 
repeats the message. And "top" shows nothing interesting, nor does "ps".

I am using XFCE, and that works well as best I can tell -- it really does seem 
to have something to do with networking.

Anybody have any idea of what may be going on? Or better yet, how to make it 
quit and still work? 

-- 
Glenn English

bewildering boot problem -- a little more info

[Glenn English]

I disabled XDM (sure is nice to have text config files) and rebooted. It came 
up at a regular login prompt, and no error messages. startx took a *very* long 
time -- said it couldn't find the hostname (something like that) -- but it 
eventually started XFCE. And the messages were back.

Something I forgot to mention: When XFCE starts and I open a terminal, the 
terminal comes up right away, but it takes  a long time (30+ seconds, it feels 
like) to display the prompt.

-- 
Glenn English

LVM boot problem

[Paul van der Vlis]

Hello,

I boot my virtal machines from LVM and one of them has boot problems.

Sometimes it boots fine, but 3 out of 4 times I get systemd messages
about start jobs running. After some timeouts I see:

(1 of 2) A start job is running for Activation of LV... 9s / no limit)

Because everything is on LVM I think the problem is the activation of LVM.

I have 2 more virtual machines made from the same image, so very
identical. But they don't have problems. The libvirt, grub, and LVM
configuration is identical.

It are KVM/Qemu virtual machines with qcow2 images.
Host is Debian7, guests are Debian8.

Any ideas how to debug this problem?

With regards,
Paul van der Vlis.


-- 
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/mlpe42$qm5$1...@ger.gmane.org

semi-random boot problem

[Alex Andreotti]

Hello all,

I've a problem within the initrd, *sometime* it fail to mount the root
directory and after a while it fall back to the shell.
My guess is a timing issue, the ssd disk attach before some process
(udev?) is listening for disk events, but it is only a guess.

I recently added an ssd disk, the grub is in sda, the / is in sdb.
sdb is partitioned as GPT and the grub entry is by uuid.

The initrd try to mount /dev/disk/by-uuid/blablabla, when it fail
/dev/disk doesn't exist at all.

kernel version: 3.14-1-686-pae
initramfs-tools 0.115

k command line:
/boot/vmlinuz-3.14-1-686-pae
root=UUID=0feeec25-eea0-487d-906e-1590990911a0 ro noresume
gfxpayload=true quiet ipv6.disable=1

Somebody experienced this problem already or have suggestions where to
look?

Thanks in advance
Cheers


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140513122135.GC8969@hellspawn

Re: Weird boot problem. How can this be?

[Darac Marjal]

On Sat, Nov 09, 2013 at 09:49:57AM -0800, Ray Dillinger wrote:
 On 11/09/2013 06:08 AM, didier gaumet wrote:
 
 The machine is an Asus Sabertooth X79 motherboard, IA64 Sandy Bridge
 architecture,
 [...]
 
 On the Asus website, this is not an IA64 motherboard, but a X86-64
 (amd64) one. Trying an amd64 version of Debian could help...
 
 On the ASUS website the board has an Intel Chipset with LGA 2011 CPU socket:
 https://www.asus.com/Motherboards/SABERTOOTH_X79/#overview
 
 LGA 2011 is compatible with Intel 64-bit processors including Sandy Bridge:
 https://en.wikipedia.org/wiki/LGA_2011
 
 And that seemed to clinch it, except that the damn thing wasn't working, so I
 went to a third source and discovered why I was wrong:
 https://en.wikipedia.org/wiki/amd64
 
 The news to me is that INTEL ever deigned to release something whose 
 instruction
 set is commonly known as AMD-anything.  I've been assuming that Intel 64 
 would
 be IA64 instruction set and AMD 64 would be AMD64 instruction set.  
 So...

Just to bring up a point of history, you are in a sense correct. Intel
DID design a 64-bit instruction set which they named IA-64. This was
introduced in 2001 on the Itanium series of processors. As I understand
it, Itanium processors natively run in 64-bit mode, but can execute
32-bit (IA-32) instructions through a form of emulation. (As a result
most of the code that was available at the time ran unnecessarily slowly
on Itanium processors).

In contrast, AMD introduced the AMD64 architecture in 1999/2000 on the
AMDK8 series processors. AMD64-based processors start in 32-bit mode and
are switched into 64-bit mode (long mode) by a knowledgeable kernel. As
such, 32-bit code runs natively fast on such a processor.

In 2004, Intel became convinced that the IA-64 (Itanium) architecture
wasn't going to be a commercial success, so began to implement their own
processors compatible with the AMD64 instructions (they called this
IA-32e, EMT64 or Intel 64).

Debian, however, chooses to keep amd64 as the architecture name for
this popular architecture. For one, it reminds people that it was AMD
who developed the architecture in the first place and honours them for
that. Secondly, it's churlish to change the name of an architecture
(with resulting change in compiler, libraries and so on) just because of
market forces :)



signature.asc
Description: Digital signature

Re: Weird boot problem. How can this be?

[berenger . morel]

Le 09.11.2013 09:26, Ray Dillinger a écrit :

I have a strange problem where my computer does not recognize *ANY*
boot device
or boot medium other than one single hard drive where a badly
configured debian
linux is installed.  I don't think the particulars of that messed-up 
install
are relevant, but I've put a note about it at the bottom just in 
case.


I don't understand how it can possibly happen, because I have
completely unplugged
that hard drive, flashed the BIOS of the machine with the most recent
update, installed
a brand new blank hard drive, and it *STILL* doesn't recognize any
boot medium or
boot device unless I plug the drive with that messed-up install back 
in.


The machine is an Asus Sabertooth X79 motherboard, IA64 Sandy
Bridge architecture,
with an ASUS SATA DVD-ROM in the chassis and a generic DVD-ROM
attached via USB2.  If
I don't have the single bootable hard drive (incidentally a 3 TB
Seagate drive)
installed in the chassis, NO device will boot.  And if I do have it
installed in
the chassis, no OTHER device will boot.


I am sorry, but I have no clue about how to fix your BIOS. Could it be 
an issue related to UEFI replacing BIOS? I do not know.



I want to fix my confused install by creating a clean
Jessie/Testing system to
migrate data to.


If you have a working system, then depending on how it is partitioned, 
you can boot any bootable ISO image, if your boot loader supports it. 
Note that grub, lilo and syslinux at least supports those operations.


However, you will have to tinker carefully:

You will have to not alter the boot partition, since it seems that your 
computer only recognize this one. You will also have to avoid trying to 
modify the partition on which you will copy the ISO. And you will 
probably need to tinker through some problems because it's not the usual 
way to use install ISOs, but given your history, I think you will be 
able to do so easily.



My main relevant current limitation in using the messed up install is
that su and
sudo are both broken; to do anything as root, I have to be logged
in as root.
There are some others, and lots of documentation that's just plain
wrong about where
things are installed etc, but not being able to su or sudo is the
most annoying.


A solution different from reinstalling the whole system from scratch, 
is to purge everything, removing probable configuration files related to 
them, and then reinstall things, with their default configurations.


To do that, go into aptitude, and ask the system to purge all packages. 
It will ask you to write a phrase for some of the packages, that you 
will not enter (those ones are essential packages).
When all those packages are marked for purge, take care that at least a 
linux image and apt-get or aptitude is still here. If you are working 
via ssh or other network tool, take care to keep that tool, obviously, 
but also network related packages and boot loader. When you are sure 
that you still are able to install stuff, apply the changes. You should 
have less than 400 packages remaining, and that list can be understood 
quite easily in less than an hour.
Next step is to go into /etc, to take a look if things belonging to 
purged packages are still here. Theoretically, they should not, but 
since your system seems heavily inconsistent, it won't hurt, and since 
you will probably never have as few packages, it will be pretty fast to 
do.
Then, obviously, return into aptitude, and add what you want. KDE 
desktop, I guess. Probably bash, bash-completion, vim or emacs, and 
other tools you need. You know which ones better than I.



Next I wanted something from
the Experimental distro, so I downloaded it - and forgot to take
Experimental out of my debian sources list immediately afterward.


You should not have removed it, but setup a /etc/apt/preferences file. 
It's the easier way to install only some packages from a repository, and 
it works well.


Over the next couple of weeks, about half the software got upgraded 
to flaky versions not

available in Wheezy.


It is strange that experimental stuff has been automatically added. 
They should, accordingly to various documents I have read, have a very 
low preference, so that they could only be installed explicitly by the 
user.


Then I realized I had Experimental in my sources, got rid of it, 
Added Testing
(which by this time was Jessie heading into the current freeze), and 
used dpkg to
get RID OF every version of everything that it couldn't still 
download.


Again, here, the best solution would have be to use preferences files. 
Still according to various documents, giving some packages' version (you 
can use regex, so you can specify all packages) a priority higher than 
1000 will force the installation of that version, even if there is a 
more recent one installed.


Anyway, this is driving me bonkers.  If anybody has any clues as to 
what could be
wrong on such a basic level as to affect boot behavior on a blank 
hard drive and 

Weird boot problem. How can this be?

[Ray Dillinger]

I have a strange problem where my computer does not recognize *ANY* boot device
or boot medium other than one single hard drive where a badly configured debian
linux is installed.  I don't think the particulars of that messed-up install
are relevant, but I've put a note about it at the bottom just in case.

I don't understand how it can possibly happen, because I have completely 
unplugged
that hard drive, flashed the BIOS of the machine with the most recent update, 
installed
a brand new blank hard drive, and it *STILL* doesn't recognize any boot medium 
or
boot device unless I plug the drive with that messed-up install back in.

The machine is an Asus Sabertooth X79 motherboard, IA64 Sandy Bridge 
architecture,
with an ASUS SATA DVD-ROM in the chassis and a generic DVD-ROM attached via 
USB2.  If
I don't have the single bootable hard drive (incidentally a 3 TB Seagate drive)
installed in the chassis, NO device will boot.  And if I do have it installed in
the chassis, no OTHER device will boot.

I want to fix my confused install by creating a clean Jessie/Testing system to
migrate data to.  But when I put a bootable 'Jessie' netinst disk into it (in 
either
drive) and a blank hard disk to format for a new system, and I get

No Operating System Found if I go straight into the BIOS boot menu and tell it
to boot off the drive that contains the netinst disk, or

No bootable medium found; Please insert bootable disk into boot drive and 
press any
key if I set the boot order so that the drive with the netinst is included.

I have also tried booting directly from a USB stick; it does exactly the same 
thing.

My main relevant current limitation in using the messed up install is that su 
and
sudo are both broken; to do anything as root, I have to be logged in as root.
There are some others, and lots of documentation that's just plain wrong about 
where
things are installed etc, but not being able to su or sudo is the most annoying.


My messed up install started as Sarge in a different IA64 machine a long time 
ago,
got upgraded to Lenny and then Wheezy when Wheezy was still experimental.
Wheezy was very definitely not ready for prime time, and I did some major 
config
hacking just to get a usable KDE desktop on it.  Used it that way for several
years, then I moved the drive to the current chassis and motherboard and sorted
out several new issues that that caused, by hand.  Next I wanted something from
the Experimental distro, so I downloaded it - and forgot to take 
Experimental
out of my debian sources list immediately afterward.  Over the next couple of
weeks, about half the software got upgraded to flaky versions not available in
Wheezy.  I started trying to sort out issues and do configuration, and I wound
up with a bizarre mutant hybrid.

Then I realized I had Experimental in my sources, got rid of it, Added 
Testing
(which by this time was Jessie heading into the current freeze), and used dpkg 
to
get RID OF every version of everything that it couldn't still download.  That 
broke
a bunch of stuff, and I've managed fix some by hand and work around the rest of 
it
for several weeks now.   I don't see how it can be relevant when this drive 
isn't
even attached and I'm still having this problem, but if you can think of any 
reason
why it might be, do let me know.

Anyway, this is driving me bonkers.  If anybody has any clues as to what could 
be
wrong on such a basic level as to affect boot behavior on a blank hard drive 
and a
net install disk, and that immediately after flashing the BIOS, please do let 
me know.

Bear


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/527df1b0.4070...@sonic.net

Re: Weird boot problem. How can this be?

[Jude DaShiell]

Okay, your bios settings are messed up on that computer.  You need to go 
into bios settings and give them some clues about what's actually on the 
computer in terms of hardware.  The bios settings on your machine have 
lost their mind somehow.

On Sat, 9 Nov 2013, Ray Dillinger wrote:

 
 I have a strange problem where my computer does not recognize *ANY* boot
 device
 or boot medium other than one single hard drive where a badly configured
 debian
 linux is installed.  I don't think the particulars of that messed-up install
 are relevant, but I've put a note about it at the bottom just in case.
 
 I don't understand how it can possibly happen, because I have completely
 unplugged
 that hard drive, flashed the BIOS of the machine with the most recent update,
 installed
 a brand new blank hard drive, and it *STILL* doesn't recognize any boot medium
 or
 boot device unless I plug the drive with that messed-up install back in.
 
 The machine is an Asus Sabertooth X79 motherboard, IA64 Sandy Bridge
 architecture,
 with an ASUS SATA DVD-ROM in the chassis and a generic DVD-ROM attached via
 USB2.  If
 I don't have the single bootable hard drive (incidentally a 3 TB Seagate
 drive)
 installed in the chassis, NO device will boot.  And if I do have it installed
 in
 the chassis, no OTHER device will boot.
 
 I want to fix my confused install by creating a clean Jessie/Testing system
 to
 migrate data to.  But when I put a bootable 'Jessie' netinst disk into it (in
 either
 drive) and a blank hard disk to format for a new system, and I get
 
 No Operating System Found if I go straight into the BIOS boot menu and tell
 it
 to boot off the drive that contains the netinst disk, or
 
 No bootable medium found; Please insert bootable disk into boot drive and
 press any
 key if I set the boot order so that the drive with the netinst is included.
 
 I have also tried booting directly from a USB stick; it does exactly the same
 thing.
 
 My main relevant current limitation in using the messed up install is that
 su and
 sudo are both broken; to do anything as root, I have to be logged in as
 root.
 There are some others, and lots of documentation that's just plain wrong about
 where
 things are installed etc, but not being able to su or sudo is the most
 annoying.
 
 
 My messed up install started as Sarge in a different IA64 machine a long
 time ago,
 got upgraded to Lenny and then Wheezy when Wheezy was still
 experimental.
 Wheezy was very definitely not ready for prime time, and I did some major
 config
 hacking just to get a usable KDE desktop on it.  Used it that way for several
 years, then I moved the drive to the current chassis and motherboard and
 sorted
 out several new issues that that caused, by hand.  Next I wanted something
 from
 the Experimental distro, so I downloaded it - and forgot to take
 Experimental
 out of my debian sources list immediately afterward.  Over the next couple of
 weeks, about half the software got upgraded to flaky versions not available
 in
 Wheezy.  I started trying to sort out issues and do configuration, and I
 wound
 up with a bizarre mutant hybrid.
 
 Then I realized I had Experimental in my sources, got rid of it, Added
 Testing
 (which by this time was Jessie heading into the current freeze), and used dpkg
 to
 get RID OF every version of everything that it couldn't still download.  That
 broke
 a bunch of stuff, and I've managed fix some by hand and work around the rest
 of it
 for several weeks now.   I don't see how it can be relevant when this drive
 isn't
 even attached and I'm still having this problem, but if you can think of any
 reason
 why it might be, do let me know.
 
 Anyway, this is driving me bonkers.  If anybody has any clues as to what could
 be
 wrong on such a basic level as to affect boot behavior on a blank hard drive
 and a
 net install disk, and that immediately after flashing the BIOS, please do let
 me know.
 
 Bear
 
 
 

---
jude jdash...@shellworld.net
Avoid the Gates Of Hell, use Linux!


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/alpine.bsf.2.01.1311090352590.51...@freire1.furyyjbeyq.arg

Re: Weird boot problem. How can this be?

[didier gaumet]

Le 09/11/2013 09:26, Ray Dillinger a écrit :
[...]
 I don't understand how it can possibly happen, because I have completely
 unplugged
 that hard drive, flashed the BIOS of the machine with the most recent
 update
[...]

Asus website says that Bios rev = 1203 needs to be converted by an
utility program before being updated

 The machine is an Asus Sabertooth X79 motherboard, IA64 Sandy Bridge
 architecture,
[...]

On the Asus website, this is not an IA64 motherboard, but a X86-64
(amd64) one. Trying an amd64 version of Debian could help...


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/l5lflg$9kh$1...@ger.gmane.org

Re: Weird boot problem. How can this be?

[Ray Dillinger]

On 11/09/2013 06:08 AM, didier gaumet wrote:


The machine is an Asus Sabertooth X79 motherboard, IA64 Sandy Bridge
architecture,

[...]

On the Asus website, this is not an IA64 motherboard, but a X86-64
(amd64) one. Trying an amd64 version of Debian could help...


On the ASUS website the board has an Intel Chipset with LGA 2011 CPU socket:
https://www.asus.com/Motherboards/SABERTOOTH_X79/#overview

LGA 2011 is compatible with Intel 64-bit processors including Sandy Bridge:
https://en.wikipedia.org/wiki/LGA_2011

And that seemed to clinch it, except that the damn thing wasn't working, so I
went to a third source and discovered why I was wrong:
https://en.wikipedia.org/wiki/amd64

The news to me is that INTEL ever deigned to release something whose instruction
set is commonly known as AMD-anything.  I've been assuming that Intel 64 would
be IA64 instruction set and AMD 64 would be AMD64 instruction set.  So...

You're right.  I shouldn't have said IA64 in the first place, to describe
either of the machines this is from.  I should have said Intel 64-bit 
processor
which I had been assuming was the same thing.  More to the point I should not 
have
downloaded the IA64 images.

Thank  you.

Ray


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/527e75c5.2010...@sonic.net

Re: Debian wheezy boot problem - Boot sector not identified by board

[Marko Randjelovic]

On Tue, 8 Oct 2013 23:08:07 +0200
Roland RoLaNd r_o_l_a_...@hotmail.com wrote:

 All,
 I have an intel dh77kc board. it previously had windows 7 installed on it.i 
 tried installing debian wheezy net install. installation goes perfectly fine 
 up untill reboot.once reboot is done, i get  Initializing and establishing 
 link and immediately goes into network bootI tried resetting bios settings 
 to default, i even upgraded the bios itself. and changed from AHCI to 
 IDEnothing is working so far.
 Note: i thought it's not debian specific, by installing windows 7 again. and 
 it worked fine..
 Any hint on what might be going on ?

Did you check if it isn't a Secure Boot problem? If you have UEFI instead of 
BIOS, try finding something like Boot Mode - Legacy/Secure in UEFI setup and 
set it to Legacy.

-- 
http://mr.flossdaily.org


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131009104840.0a140...@eunet.rs

RE: Debian wheezy boot problem - Boot sector not identified by board

[Roland RoLaNd]

for future reference if anyone faced this issue.disabling EFI in bios 
settings and initiating a clean install does the trick.
From: r_o_l_a_...@hotmail.com
To: debian-user@lists.debian.org
Subject: Debian wheezy boot problem - Boot sector not identified by board
Date: Mon, 7 Oct 2013 09:54:11 +0200




All,
I have an intel dh77kc board. it previously had windows 7 installed on it.i 
tried installing debian wheezy net install. installation goes perfectly fine up 
untill reboot.once reboot is done, i get  Initializing and establishing link 
and immediately goes into network bootI tried resetting bios settings to 
default, i even upgraded the bios itself. and changed from AHCI to IDEnothing 
is working so far.
Note: i thought it's not debian specific, by installing windows 7 again. and it 
worked fine..
Any hint on what might be going on ?



  

Debian wheezy boot problem - Boot sector not identified by board

[Roland RoLaNd]

All,
I have an intel dh77kc board. it previously had windows 7 installed on it.i 
tried installing debian wheezy net install. installation goes perfectly fine up 
untill reboot.once reboot is done, i get  Initializing and establishing link 
and immediately goes into network bootI tried resetting bios settings to 
default, i even upgraded the bios itself. and changed from AHCI to IDEnothing 
is working so far.
Note: i thought it's not debian specific, by installing windows 7 again. and it 
worked fine..
Any hint on what might be going on ?


  

Re: Recovery mode: impossible to run dpkg ( was Re: boot problem: stuck at Switching to clocksource tsc )

[berenger . morel]

Le 06.10.2013 18:34, Curt a écrit :

On 2013-10-06, berenger.mo...@neutralite.org
berenger.mo...@neutralite.org wrote:


Any idea about how to be able to run terminal stuff correctly in
recovery mode? Maybe changing the terminal (if so, how could I do
that?)?



export TERM=linux

says google


Thanks. But, this line does obviously not change the terminal: it lure 
the softwares so that they can not check that the real running terminal 
is not the good one.
Remember the context: I am trying to save an installation from recovery 
mode, which is in TTY.


However, I've just tried it, in case it would work. The dialog box is 
very ugly, since the formating is completely destroyed, but since 
changing kernel only shows a dialog box to say that one could have to 
install firmwares, it's ok. So, thanks you.


Sadly, it does not resolve my original problem of clocksource... I 
guess I'll have to reinstall.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/36b8e96a3b4d8f802e18f77a2c148...@neutralite.org

Re: Debian wheezy boot problem - Boot sector not identified by board

[berenger . morel]

Le 07.10.2013 09:54, Roland RoLaNd a écrit :

All,

I have an intel dh77kc board. it previously had windows 7 installed
on it.
i tried installing debian wheezy net install. installation goes
perfectly fine up untill reboot.
once reboot is done, i get  Initializing and establishing link
and immediately goes into network boot
I tried resetting bios settings to default, i even upgraded the bios
itself. and changed from AHCI to IDE
nothing is working so far.

Note: i thought it's not debian specific, by installing windows 7
again. and it worked fine..

Any hint on what might be going on ?


Are you sure the flag boot is set on the right partition?


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5d36dfb019ac15e1577048f18e5cf...@neutralite.org

Recovery mode: impossible to run dpkg ( was Re: boot problem: stuck at Switching to clocksource tsc )

[berenger . morel]

Le 05.10.2013 14:54, berenger.mo...@neutralite.org a écrit :

Hi.
Since my last kernel update my desktop can not boot anymore, it is
stuck at Switching to clocksource tsc. Also, nothing at all reply,
even the keyboard does just nothing.

Of course, I was stupid enough to remove the last kernel without
testing it, and I have no idea about what is wrong.
The kernel currently installed on that computer is 3.10-3, which
works perfectly on that computer ( a netbook ).
I thought it was a problem with my lilo.conf, but I checked it for
the 4th time ( which is not fun on recovery mode, since vim is just
highly bugged in ansi mode ) and it seems fine.
Few searches on the web indicates that it could be a compilation
problem, but I have used the Debian's kernel without any change.
I also tried to reinstall everything (just in case), but it does not
changed anything (of course).


I think I have no other choice than trying to downgrade, so I have used 
ssh to send the packages ( that I kept on that computer ) to the target.
Now, bterm which is used in recovery mode starts to be *very* annoying, 
and avoid dpkg to work!

Here is what the system says:
===
Running depmod.
Error opening terminal: bterm.
debconf: dialog output the above errors, giving up!
dpkg: erreur de traitement de linux-image-3.10-2-amd64 (--install) :
 le sous-processus script post-installation installé à retourné une 
erreur de sortie d'état 255

Des erreur ont été rencontrées pendant l'exécution :
 linux-image-3.10-2-amd64
===

dpkg uses french messages, but I think they are useless. What is 
important is that I can not install package in recovery mode, so I can 
not revert my changes, which is very annoying in recovery mode.


I checked if all files were correctly generated in /boot, just in case, 
but the initrd.img file is not. I suppose it is generated by depmod?


Any idea about how to be able to run terminal stuff correctly in 
recovery mode? Maybe changing the terminal (if so, how could I do 
that?)?


Honestly, recovery mode is easier than using the unusable busybox ( I 
stopped installing them when I understood that they allow to do nothing 
else than cd and ls. ), but having it unable to correctly run basic 
tools like text editors and dpkg is not nice. I could use a debian live 
or anything else, but I would like to be able to use the tools debian 
give us to repair damaged systems.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/cdae5ac3b2e4d42fa201d590c4810...@neutralite.org

Re: Recovery mode: impossible to run dpkg ( was Re: boot problem: stuck at Switching to clocksource tsc )

[Curt]

On 2013-10-06, berenger.mo...@neutralite.org berenger.mo...@neutralite.org 
wrote:

 Any idea about how to be able to run terminal stuff correctly in 
 recovery mode? Maybe changing the terminal (if so, how could I do 
 that?)?


export TERM=linux

says google


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/slrnl534ar.2dr.cu...@einstein.electron.org

boot problem: stuck at Switching to clocksource tsc

[berenger . morel]

Hi.
Since my last kernel update my desktop can not boot anymore, it is 
stuck at Switching to clocksource tsc. Also, nothing at all reply, 
even the keyboard does just nothing.


Of course, I was stupid enough to remove the last kernel without 
testing it, and I have no idea about what is wrong.
The kernel currently installed on that computer is 3.10-3, which works 
perfectly on that computer ( a netbook ).
I thought it was a problem with my lilo.conf, but I checked it for the 
4th time ( which is not fun on recovery mode, since vim is just highly 
bugged in ansi mode ) and it seems fine.
Few searches on the web indicates that it could be a compilation 
problem, but I have used the Debian's kernel without any change.
I also tried to reinstall everything (just in case), but it does not 
changed anything (of course).



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/5beaeb9d67317109f033517b4487c...@neutralite.org

Re: Boot problem : Operating System not found.

[Bruno Costacurta]

It would've been helpful not to have snipped the drive partition
info section! :)



You have a gpt-labelled disk but sda1 isn't OK. As File system, it
should have BIOS Boot partition. Boot sector type and Boot sector
info cannot be right but I don't know what they should be.



The two looks at sector seem *very* wrong.


OK, hereafter I added the drive info produced by boot_info_script.sh.
I'll also try the SuperGrub2Disk ASAP.

Bye.
Bruno

= Boot Info Summary:  
===


 = Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector
946507840 of the same hard drive for core.img. core.img is at this
location and looks for  on this drive.

sda1:  
__


File system:   vfat
Boot sector type:  Grub2 (v1.99)
Boot sector info:   Grub2 (v1.99) is installed in the boot sector of sda1
   and looks at sector 932584136 of the same hard drive
   for core.img. core.img is at this location and looks
   for  on this drive. According to the info in the boot
   sector, sda1 has 0 sectors.
Operating System:
Boot files:

sda2:  
__


File system:   ext4
Boot sector type:  -
Boot sector info:
Operating System:  Ubuntu 11.10
Boot files:/boot/grub/grub.cfg /etc/fstab

sda3:  
__


File system:   swap
Boot sector type:  -
Boot sector info:

sda4:  
__


File system:   ext4
Boot sector type:  -
Boot sector info:
Operating System:  Debian GNU/Linux 6.0
Boot files:/boot/grub/grub.cfg /etc/fstab /boot/grub/core.img


[snip]

 Drive/Partition Info:  
=


Drive: sda  
_


Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition  Boot  Start SectorEnd Sector  # of Sectors  Id System

/dev/sda1   1   976,773,167   976,773,167  ee GPT


GUID Partition Table detected.

PartitionStart SectorEnd Sector  # of Sectors System
/dev/sda1  3439,09639,063 EFI System partition
/dev/sda2  39,097   926,705,663   926,666,567 Data partition  
(Windows/Linux)

/dev/sda3 968,710,973   976,773,118 8,062,146 Swap partition (Linux)
/dev/sda4 926,705,664   946,236,91419,531,251 Data partition  
(Windows/Linux)

/dev/sda5 946,237,440   968,710,14322,472,704 EFI System partition

blkid output:  



Device   UUID   TYPE   LABEL

/dev/sda1DAA7-3EEF  vfat
/dev/sda21f2cac6a-301f-48f7-a83e-70485ad3a653   ext4
/dev/sda3cc3d3f3f-d38e-4741-adc1-7807282fdc16   swap
/dev/sda4b6ebc0b2-59cc-4ceb-81ba-c60d90be2fdc   ext4
/dev/sda55c1fb0d9-aafd-42cd-9626-ce4d1c170d7f   ext4

[snip]

=== sda4/etc/fstab:  




# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# file system mount point   type  options   dump  pass
proc/proc   procdefaults0   0
# / was on /dev/sda4 during installation
UUID=b6ebc0b2-59cc-4ceb-81ba-c60d90be2fdc /   ext4 
errors=remount-ro 0   1

# swap was on /dev/sda3 during installation
UUID=cc3d3f3f-d38e-4741-adc1-7807282fdc16 noneswapsw
   0   0

/dev/scd0   /media/cdrom0   udf,iso9660 user,noauto 0   0


=== sda4: Location of files loaded by Grub:  



   GiB - GB File  
Fragment(s)


 442.020458221 = 474.615853056  boot/grub/core.img 
 1
 450.046794891 = 483.234066432  boot/grub/grub.cfg 
 2
 442.517547607 = 475.149598720  boot/initrd.img-2.6.32-5-amd64 
 1
 442.415344238 = 475.039858688  boot/vmlinuz-2.6.32-5-amd64
 1
 442.517547607 = 475.149598720  initrd.img 
 

Re: Boot problem : Operating System not found

[Camaleón]

On Fri, 16 Mar 2012 20:52:37 +, luizlmarins hotmail.com wrote:

(please, no html... thanks)

 See here:
 
 http://linuxmeu.wordpress.com/grub-nao-aparece/

But GRUB does appear in this case. What happens is that it hangs when 
booting Debian.
 
Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jk2f4t$q5l$8...@dough.gmane.org

Re: Boot problem : Operating System not found.

[Bruno Costacurta]

[snip]

I'll also try the SuperGrub2Disk ASAP.

[snip]

Yes, it works when booting using a SuperGrub2Disk CD.

From SuperGrub2Disk boot menu :
Detect any OS - Debian correctly found on /dev/sda4 - boot is OK.

So I suppose the GRUB on the hard disk is incorrectly setup.
As the boot-info script reported in previous email.
Note that others distros (Xubuntu and Sabayon) boots correctly.

So how to correct GRUB regarding Debian problem ?
Manually or using tools (certainly preferred solution )?
I already ran update-grub but without any success.

Bye.
Bruno


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: 
http://lists.debian.org/20120317183051.horde.8dtrbb5-3onpzmplyb3n...@webmail.costacurta.org

Re: Boot problem : Operating System not found.

[Camaleón]

On Sat, 17 Mar 2012 18:30:51 +0100, Bruno Costacurta wrote:

Bruno, you MUA is somehow deleting both References: and In-Reply-To: 
header fields and thus your posts are kept unthreaded.

 [snip]
 I'll also try the SuperGrub2Disk ASAP.
 [snip]
 
 Yes, it works when booting using a SuperGrub2Disk CD.
 
  From SuperGrub2Disk boot menu :
 Detect any OS - Debian correctly found on /dev/sda4 - boot is OK.

Good :-)

 So I suppose the GRUB on the hard disk is incorrectly setup. As the
 boot-info script reported in previous email. Note that others distros
 (Xubuntu and Sabayon) boots correctly.
 
 So how to correct GRUB regarding Debian problem ? Manually or using
 tools (certainly preferred solution )? I already ran update-grub but
 without any success.

I would first try to manually boot Debian from GRUB2 console. Based on 
the information you've provided and the link I previously sent, it should 
be something like this:

***
set root=(hd0,gpt4)
linux /boot/vmlinuz root=/dev/sda4 ro
initrd /boot/initrd.img-2.6.32-5-amd64
boot
***

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jk2luf$q5l$1...@dough.gmane.org

Re: Boot problem : Operating System not found (was : how to make it verbose ?)

[Tom H]

On Thu, Mar 15, 2012 at 2:55 PM, Bruno Costacurta tec...@costacurta.org wrote:

 Another thing you can test is manually booting your Debian system from
 GRUB2 boot menu by reaching the command line. This way if you're lucky
 any error you get will be printed on the screen.

 Indeed you're right.
 'Operating System not found' is displayed once boot via GRUB command line.
 I suppose this is an interesting info.
 What happened ?
 How to correct this ?

 I check the UUID (via GRUB2 - ls) it is identical as the one specified in
 the GRUB parameters.

What's the output of bootinfoscript?

http://sourceforge.net/projects/bootinfoscript/files/bootinfoscript/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOdo=SwgFxr19GAoy=mRqKG6=tatytgyvzmsaxvftufasuj...@mail.gmail.com

Re: Boot problem : Operating System not found (was : how to make it verbose ?)

[Camaleón]

On Thu, 15 Mar 2012 19:55:39 +0100, Bruno Costacurta wrote:

 ..
 Another thing you can test is manually booting your Debian system from
 GRUB2 boot menu by reaching the command line. This way if you're lucky
 any error you get will be printed on the screen.
 ..
 
 Indeed you're right.
 'Operating System not found' is displayed once boot via GRUB command
 line. I suppose this is an interesting info. What happened ?
 How to correct this ?

I don't know what's going on, but I would try to manually boot the Debian 
kernel from GRUB2 console. As you're using GRUB2 from Ubuntu, you could 
try these steps:

https://help.ubuntu.com/community/Grub2#Boot_a_Specific_Kernel_Manually
 
 I check the UUID (via GRUB2 - ls) it is identical as the one specified
 in the GRUB parameters.

Maybe what can't find is the root disk/partition (hdx,x).

Besides, it can be an error coming from GRUB2 itself, that's why I still 
suggest that you try to boot your Debian system from SuperGrub2Disk which 
is distribution-unaware.

As a side note, when using a multi-boot configuration I prefer to install 
the bootloader of every operating system inside its own partition, 
whether possible (windows does not allow this, I guess, it puts its NT 
loader on the MBR we like it or not). But on linux and bsd systems you 
can install both, Ubuntu and Debian, and each of them with their own 
GRUB2.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jjvt4g$gio$7...@dough.gmane.org

Re: Boot problem : Operating System not found.

[Bruno Costacurta]

'Operating System not found' is displayed once boot via GRUB command line.

[snip]


What's the output of bootinfoscript?

[snip]

So I ran boot_info_script.sh.
Which returns the following (snipped to mainly show /dev/sda4 on which  
Debian is installed) :



Boot Info Script 0.60from 17 May 2011

= Boot Info Summary:  
===


 = Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector
946507840 of the same hard drive for core.img. core.img is at this
location and looks for  on this drive.

sda1:  
__


File system:   vfat
Boot sector type:  Grub2 (v1.99)
Boot sector info:   Grub2 (v1.99) is installed in the boot sector of sda1
   and looks at sector 932584136 of the same hard drive
   for core.img. core.img is at this location and looks
   for  on this drive. According to the info in the boot
   sector, sda1 has 0 sectors.
Operating System:
Boot files:

[snip]
sda4:  
__


File system:   ext4
Boot sector type:  -
Boot sector info:
Operating System:  Debian GNU/Linux 6.0
Boot files:/boot/grub/grub.cfg /etc/fstab /boot/grub/core.img
[snip]
=== sda4/boot/grub/grub.cfg:  
===



#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default=0
if [ ${prev_saved_entry} ]; then
  set saved_entry=${prev_saved_entry}
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
  fi
}

function load_video {
  insmod vbe
  insmod vga
  insmod video_bochs
  insmod video_cirrus
}

insmod part_gpt
insmod ext2
set root='(hd0,gpt4)'
search --no-floppy --fs-uuid --set b6ebc0b2-59cc-4ceb-81ba-c60d90be2fdc
if loadfont /usr/share/grub/unicode.pf2 ; then
  set gfxmode=640x480
  load_video
  insmod gfxterm
fi
terminal_output gfxterm
insmod part_gpt
insmod ext2
set root='(hd0,gpt4)'
search --no-floppy --fs-uuid --set b6ebc0b2-59cc-4ceb-81ba-c60d90be2fdc
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian  
--class gnu-linux --class gnu --class os {

insmod part_gpt
insmod ext2
set root='(hd0,gpt4)'
search --no-floppy --fs-uuid --set  
b6ebc0b2-59cc-4ceb-81ba-c60d90be2fdc

echo'Loading Linux 2.6.32-5-amd64 ...'
linux   /boot/vmlinuz-2.6.32-5-amd64  
root=UUID=b6ebc0b2-59cc-4ceb-81ba-c60d90be2fdc ro  quiet

echo'Loading initial ramdisk ...'
initrd  /boot/initrd.img-2.6.32-5-amd64
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64 (recovery  
mode)' --class debian --class gnu-linux --class gnu --class os {

insmod part_gpt
insmod ext2
set root='(hd0,gpt4)'
search --no-floppy --fs-uuid --set  
b6ebc0b2-59cc-4ceb-81ba-c60d90be2fdc

echo'Loading Linux 2.6.32-5-amd64 ...'
linux   /boot/vmlinuz-2.6.32-5-amd64  
root=UUID=b6ebc0b2-59cc-4ceb-81ba-c60d90be2fdc ro single

echo'Loading initial ramdisk ...'
initrd  /boot/initrd.img-2.6.32-5-amd64
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry Ubuntu, with Linux 3.0.0-16-generic (on /dev/sda2) {
insmod part_gpt
insmod ext2
set root='(hd0,gpt2)'
search --no-floppy --fs-uuid --set  
1f2cac6a-301f-48f7-a83e-70485ad3a653
linux /boot/vmlinuz-3.0.0-16-generic  
root=UUID=1f2cac6a-301f-48f7-a83e-70485ad3a653 ro acpi=off splash  
vt.handoff=7

initrd /boot/initrd.img-3.0.0-16-generic
}
menuentry Ubuntu, with Linux 3.0.0-16-generic (recovery mode) (on  
/dev/sda2) {

insmod part_gpt
insmod ext2
set root='(hd0,gpt2)'
search --no-floppy --fs-uuid --set  
1f2cac6a-301f-48f7-a83e-70485ad3a653
linux /boot/vmlinuz-3.0.0-16-generic  
root=UUID=1f2cac6a-301f-48f7-a83e-70485ad3a653 ro recovery nomodeset  
acpi=off

initrd /boot/initrd.img-3.0.0-16-generic
}
menuentry Ubuntu, with Linux 3.0.0-15-generic (on /dev/sda2) {
insmod 

Re: Boot problem : Operating System not found.

[Tom H]

On Fri, Mar 16, 2012 at 3:13 PM, Bruno Costacurta tec...@costacurta.org wrote:

  = Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector
    946507840 of the same hard drive for core.img. core.img is at this
    location and looks for  on this drive.
 ...
 sda1:

    File system:       vfat
    Boot sector type:  Grub2 (v1.99)
    Boot sector info:   Grub2 (v1.99) is installed in the boot sector of sda1
                       and looks at sector 932584136 of the same hard drive
                       for core.img. core.img is at this location and looks
                       for  on this drive. According to the info in the boot
                       sector, sda1 has 0 sectors.
 ...
 set root='(hd0,gpt4)'

It would've been helpful not to have snipped the drive partition
info section! :)

You have a gpt-labelled disk but sda1 isn't OK. As File system, it
should have BIOS Boot partition. Boot sector type and Boot sector
info cannot be right but I don't know what they should be.

The two looks at sector seem *very* wrong.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOdo=SyofqPWFQbZ=XttS=fp-uni8yifybfxh4un9qoflfx...@mail.gmail.com

Re: Boot problem : how to make it verbose ?

[Camaleón]

On Wed, 14 Mar 2012 20:48:03 +0100, Bruno Costacurta wrote:

 I installed Debian Squeeze on a multi-boot PC where Ubuntu is the
 first and bootable distro.
 Are you chainloading GRUB2s or are you loading Debian directly from
 Ubuntu's own GRUB2 version?
 
 I boot direclt from the Ubuntu's own GRUB2 version.

Mmm... so you did not install GRUB2 when you installed Debian, right?
 
 Using GRUB2, the options 'nosplash debug --verbose' are used, but
 Debian freezes silently.
 How to make boot verbose to see what happen ?
 (...)
 The changes you have done should be enough.
 
 However other options were also tried without any result.

Because the hang occurs at a very early stage, I'd say.

 In what stage is the system hanging at? What can you see in the screen?
 Can you at least reach the GRUB2 boot menu? I would try to load Debian
 from SuperGrub2Disk or any other LiveCD just to test if it hangs at the
 same point.
 
 Yes, the GRUB2 menu is reached (in fact, it's used to boot the other
 system on same PC). The Debian system hangs direcly. Nothing is
 displayed.

A complete black screen, then?

Can you copy/paste the GRUB2 stanza for your Debian menu entry?

 Yes, a LiveCD Debian 6 works fine (however it was a i386, the installed
 Debian is a amd64, the working Xubuntu is also a amd64).

:-)

Well, I wanted you to try to boot your current Debian installation *from* 
a LiveCD (IIRC tehre is usually an option called boot from installed 
disk or something similar) not that you tested a LiveCD. I asked this to 
avoid using Ubuntu's GRUB2 and see if that way you can get any further. 
That's also the reason I asked for you to try SuperGrub2Disk.

Another thing you can test is manually booting your Debian system from 
GRUB2 boot menu by reaching the command line. This way if you're lucky 
any error you get will be printed on the screen.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jjt0pd$b0n$5...@dough.gmane.org

Boot problem : Operating System not found (was : how to make it verbose ?)

[Bruno Costacurta]

..

Another thing you can test is manually booting your Debian system from
GRUB2 boot menu by reaching the command line. This way if you're lucky
any error you get will be printed on the screen.

..

Indeed you're right.
'Operating System not found' is displayed once boot via GRUB command line.
I suppose this is an interesting info.
What happened ?
How to correct this ?

I check the UUID (via GRUB2 - ls) it is identical as the one  
specified in the GRUB parameters.


Thanks for help.
Bruno

--
Linux Counter # 353844
https://linuxcounter.net/user/353844.html



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: 
http://lists.debian.org/20120315195539.horde.ubqpel5-3onpyjsrspr3...@webmail.costacurta.org

Boot problem : how to make it verbose ?

[Bruno Costacurta]

Hello,

I installed Debian Squeeze on a multi-boot PC where Ubuntu is the  
first and bootable distro.
Using GRUB2, the options 'nosplash debug --verbose' are used, but  
Debian freezes silently.

How to make boot verbose to see what happen ?

Hereafter the /boot/grub/grub.cfg :

menuentry test Debian GNU/Linux, with Linux 2.6.32-5-amd64 (on  
/dev/sda4) --class gnu-linux --class gnu --class os {

insmod part_gpt
insmod ext2
set root='(hd0,gpt4)'
search --no-floppy --fs-uuid --set=root b6ebc0b2-59cc-4ceb-81ba-c60d90be2fdc
linux /boot/vmlinuz-2.6.32-5-amd64  
root=UUID=b6ebc0b2-59cc-4ceb-81ba-c60d90be2fdc ro nosplash debug  
--verbose

initrd /boot/initrd.img-2.6.32-5-amd64


The original entry in grub.cfg was created by update-grub under Xubuntu.
From this entry was added in file /etc/grub.d/40_custom the option  
'quiet( was replaced by 'nosplash debug --verbose' as a try to obtain  
verbosity.

Then again update-grub to update grub.cfg file.

Thanks for attention and clue.
Bruno

--
Linux Counter # 353844
https://linuxcounter.net/user/353844.html


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: 
http://lists.debian.org/20120314110604.horde.uxjhjl5-3onpyg2mhw7d...@webmail.costacurta.org

Re: Boot problem : how to make it verbose ?

[Brian]

On Wed 14 Mar 2012 at 11:06:04 +0100, Bruno Costacurta wrote:

 I installed Debian Squeeze on a multi-boot PC where Ubuntu is the first 
 and bootable distro.
 Using GRUB2, the options 'nosplash debug --verbose' are used, but Debian 
 freezes silently.
 How to make boot verbose to see what happen ?

 Hereafter the /boot/grub/grub.cfg :

 menuentry test Debian GNU/Linux, with Linux 2.6.32-5-amd64 (on  
 /dev/sda4) --class gnu-linux --class gnu --class os {
 insmod part_gpt
 insmod ext2
 set root='(hd0,gpt4)'
 search --no-floppy --fs-uuid --set=root b6ebc0b2-59cc-4ceb-81ba-c60d90be2fdc
 linux /boot/vmlinuz-2.6.32-5-amd64  
 root=UUID=b6ebc0b2-59cc-4ceb-81ba-c60d90be2fdc ro nosplash debug  
 --verbose
 initrd /boot/initrd.img-2.6.32-5-amd64

Are 'nosplash' and 'debug --verbose' parameters the kernel knows about?
Anyway, when GRUB comes up edit the entry (hit the 'e' key) to remove
them and then boot.

 The original entry in grub.cfg was created by update-grub under Xubuntu.
 From this entry was added in file /etc/grub.d/40_custom the option  
 'quiet( was replaced by 'nosplash debug --verbose' as a try to obtain  
 verbosity.
 Then again update-grub to update grub.cfg file.

The usual place to put kernel parameters is /etc/default/grub. Just
removing 'quiet' should get you more verbosity.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120314130015.GY4889@desktop

Re: Boot problem : how to make it verbose ?

[Camaleón]

On Wed, 14 Mar 2012 11:06:04 +0100, Bruno Costacurta wrote:

 I installed Debian Squeeze on a multi-boot PC where Ubuntu is the first
 and bootable distro.

Are you chainloading GRUB2s or are you loading Debian directly from 
Ubuntu's own GRUB2 version?

 Using GRUB2, the options 'nosplash debug --verbose' are used, but Debian
 freezes silently.
 How to make boot verbose to see what happen ?

(...)

The changes you have done should be enough.

In what stage is the system hanging at? What can you see in the screen? 
Can you at least reach the GRUB2 boot menu?

I would try to load Debian from SuperGrub2Disk or any other LiveCD just 
to test if it hangs at the same point.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jjqej8$3nj$7...@dough.gmane.org

Re: Boot problem : how to make it verbose ?

[Bruno Costacurta]

I installed Debian Squeeze on a multi-boot PC where Ubuntu is the first
and bootable distro.

Are you chainloading GRUB2s or are you loading Debian directly from
Ubuntu's own GRUB2 version?


I boot direclt from the Ubuntu's own GRUB2 version.


Using GRUB2, the options 'nosplash debug --verbose' are used, but Debian
freezes silently.
How to make boot verbose to see what happen ?

(...)

The changes you have done should be enough.


However other options were also tried without any result.


In what stage is the system hanging at? What can you see in the screen?
Can you at least reach the GRUB2 boot menu?
I would try to load Debian from SuperGrub2Disk or any other LiveCD just
to test if it hangs at the same point.


Yes, the GRUB2 menu is reached (in fact, it's used to boot the other  
system on same PC). The Debian system hangs direcly. Nothing is  
displayed.
Yes, a LiveCD Debian 6 works fine (however it was a i386, the  
installed Debian is a amd64, the working Xubuntu is also a amd64).


Bye,
Bruno


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: 
http://lists.debian.org/20120314204803.horde.xkkaj75-3onpypxzxwj1...@webmail.costacurta.org

Re: Boot problem : how to make it verbose ?

[Brian]

On Wed 14 Mar 2012 at 20:48:03 +0100, Bruno Costacurta wrote:

 Yes, the GRUB2 menu is reached (in fact, it's used to boot the other  
 system on same PC). The Debian system hangs direcly. Nothing is  
 displayed.
 Yes, a LiveCD Debian 6 works fine (however it was a i386, the installed 
 Debian is a amd64, the working Xubuntu is also a amd64).

Go to the commandline from the GRUB menu. Type 'ls' for a list of the
disks and partitions on them. It seems (hd0,gpt4) is where you have
Debian. 'ls -l (hd0,gpt4) should allow you to check the UUID of the
partition. With 'ls -l (hd0,gpt4)/boot' the kernel and initrd.img can be
checked.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120314230720.GB4889@desktop

Re: Passwordless root shell is offered when boot problem occurs.

[Arno Schuring]

Sthu Deus (sthu.d...@gmail.com on 2011-12-06 01:18 +0700):
 Thank You for Your time and answer, Arno:
 
   a) locking the root account (passwd -l root), which will give you
  sulogin: root account is locked, starting shell
 
 That's the point - sudo is used on the system and the root account is
 blocked.

Que?
http://lists.debian.org/debian-user/2011/12/msg00075.html


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111206201500.3ef0f...@neminis.intra.loos.site

Re: Passwordless root shell is offered when boot problem occurs.

[Sthu Deus]

Thank You for Your time and answer, Arno:

 Thank You for Your time and answer, Arno:
 
   a) locking the root account (passwd -l root), which will give you
  sulogin: root account is locked, starting shell
 
 That's the point - sudo is used on the system and the root account is
 blocked.

Que?
http://lists.debian.org/debian-user/2011/12/msg00075.html

Sorry. I did misunderstand You there.

What is 'que'?

How I can set password when root account is blocked - in favor of
requiring sudo user's password?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4edf0c55.c820cc0a.64ba.0...@mx.google.com

Re: Passwordless root shell is offered when boot problem occurs.

[Sthu Deus]

Thank You for Your time and answer, Arno:

  a) locking the root account (passwd -l root), which will give you
 sulogin: root account is locked, starting shell

That's the point - sudo is used on the system and the root account is
blocked.

So, what's the strategy to protect systems in such cases as mine when
root account is blocked? Why, for example, the sudoers users are no
asked for their passwords, if You know?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4edd0aee.c820cc0a.2104.9...@mx.google.com

Re: Passwordless root shell is offered when boot problem occurs.

[Andrei Popescu]

On Lu, 28 nov 11, 13:47:59, Sthu Deus wrote:
 Good time of the day.
 
 Once mount error occurs while OS booting, I get root shell - w/o even
 asking for password... How I can change the behavior (to ask for
 password before granting root shell)?

Hi Sthu,

From reading the thread I understand your goal is to secure your box 
even in case of physical access. Since you provided little information I 
will assume you want to prevent somebody like a room mate to use the 
computer and possibly also access files without your knowledge.

A BIOS and/or grub password will help in most cases, unless the persons 
would have to possibility to reset the BIOS (needs opening the case) or 
physically installing your harddisk in another computer. In such case 
partial/full disk encryption would help.

Hope this helps,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Re: Passwordless root shell is offered when boot problem occurs.

[Sthu Deus]

Thank You for Your time and answer, Arno:

 Hmm. I thought everybody has the same OS behavior in such
 condition... And the problem here is only improper/default
 configuration.

That could very well be, but I haven't had a boot problem in years
(well, except when trying out systemd). A standard Debian config should
not offer a passwordless root shell unless you explicitly ask for it,

Oh, no! I didn't! :)

Do You have an idea where to look for that? - I have no ideas,
absolutely.

Early boot messages should be found in /var/log/boot, but bootlogd
seems very hitmiss on my systems. Filesystem checks are logged
in /var/log/fsck.

Same here.

It's not about emergency situations, although it certainly can be used
as such. It's about accesss: if anyone has physical access to your
machine, there are so many ways to access your system that it is silly
to protect against one of them.

That's right. But it is just a link in a chain of undertakings to
protect the computer totally or, to make one's life harder. :)

On other hand, if we pursue this idea - that physical access makes a
host absolutely undefended, - we can let root account to be
password-less - for why worrying?

I understand the things You are speaking about - but I want ot all I
can to make it more secure - even having physical access to the host.

So yes, protecting yourself from physical attacks by insisting on a
root password is abnormal behaviour. How are you going to prevent an
attacker from opening your PC and connecting the harddisk to his own
machine?

Probably, to supply a dynamite? :) - I think it goes beyond Debian
security, doesn't it?

 - and in case I want to commit
 what I have targeted, I have to develop the solution myself (that is
 there is no a config. file that I might simply turn on the password
 prompt for root shell in such cases)?

In short, yes. If you really want to be that paranoid (and there are
good reasons for it, especially on laptops), you should be looking at
encryption as your solution (dm-crypt, truecrypt, bitlocker), not
passwords.

Oh, OK... Thanks again.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ed9ffc7.c48dcd0a.3323.8...@mx.google.com

Re: Passwordless root shell is offered when boot problem occurs.

[Sthu Deus]

Thank You for Your time and answer, Joel:

Recently had fun with Fedora, when it didn't like the way I specified
my HDs, it would drop me into the ctrl-d prompt, but I couldn't go
anywhere beyond that. Any key I pressed, including ctrl-d, would cycle
me another ctrl-d prompt.

When I had the prompt - I had no problems w/ getting root shell since I
correctly entered its password. But situations probably differ in what
has been mounted - root or of secondary importance (like /usr)
partitions.

If / partition was absent/not-mounted then, what did provide the prompt itself 
- the linux (kernel)? Were
there any parameters passed to kernel at boot (in grub or whatever loader You 
used)?

There's a half-fixed bug on that still over there, but I'm not
interested in testing any further, so I simply changed my fstab to
spec the drives by UUIDs. (I always forget the command for getting the
UUID from the drive. These days, I list /dev/disk/something and use
the extra information. I think that's the same on Debian. Yeah, I'm
logged in on Fedora right now.) Similar issues, different symptoms,
I'm thinking. It'd try to offer my the password prompt, but it wasn't
mounting the root drive, so there was no /bin/passwd to run, and it
just exceptioned it's way back to the ctrl-d prompt.

Yea, it seems logical.

Anyway, the question I'd ask is whether you can force this behavior if
your configuration is correct. (By current definition of correct,
which appears to be to refrain from trying to mount /dev/sdb4 and such
in your fstab, and mount UUID=long-hex-string instead. Or
/dev/mapper/vol-group for LVM volumes.) And, I guess you imply that
you can mount your drives in this password-less shell, but is that the
case?

Yes, the drives are mounted OK. I just skipped one - of secondary
importance to boot process when ended up w/ password-less root shell -
I was amazed - how easily it is for Debian to get the shell - just boot
it skipping a single partition and You are there - whole the system is
under Your control - no need even to take off the drive or boot own OS
from other media!


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4eda1949.8872cd0a.0b8a.a...@mx.google.com

Re: Passwordless root shell is offered when boot problem occurs.

[Arno Schuring]

Sthu Deus (sthu.d...@gmail.com on 2011-12-03 17:53 +0700):
 [..] A standard Debian config
 should not offer a passwordless root shell unless you explicitly ask
 for it,
 
 Oh, no! I didn't! :)
 
 Do You have an idea where to look for that? - I have no ideas,
 absolutely.

Just as a pointer, you can get a passwordless root shell by:

- interrupting initramfs: specify break=init on the kernel command
  line
- overriding init: specify init=/bin/bash on the kernel command line
- configuring inittab: either add a bootwait line spawning /bin/*sh
  or tell getty to bypass login with -l /bin/*sh
- setting SULOGIN=yes in /etc/default/rcS, and either
  a) locking the root account (passwd -l root), which will give you
 sulogin: root account is locked, starting shell
  b) deleting root's password (passwd -d root), which will give you
 Press enter for maintenance(or type Control-D to continue)

All four methods above will give you an unconditional root shell. Since
yours only spawns on error, none of the above applies.

 
 On other hand, if we pursue this idea - that physical access makes a
 host absolutely undefended, - we can let root account to be
 password-less - for why worrying?

Setting a root password will still protect you from remote users that
have access to login programs (such as su). Locking the root account
reduces the attack surface to your sudoers configuration.


Regards,
Arno


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111203150013.1fa5b...@neminis.intra.loos.site

Re: Passwordless root shell is offered when boot problem occurs.

[Camaleón]

On Fri, 02 Dec 2011 14:04:15 +0700, Sthu Deus wrote:

 Thank You for Your time and answer, Camaleón:
 
You mean Busybox? :-?
 
 I do not know - it appears when something wrong during boot process.

It should be printed out, something like:

***
BusyBox v1.10.2 (Debian x-x-x-x) Built-in shell (xxx) ***
 
 Oh, no. It's not my case. Nor I have the packages installed.

Hmmm... are you sure? It is installed by default in all of my Lenny 
systems and also in wheezy.

sm01@stt008:~$ dpkg -l | grep busy
ii  busybox  1:1.10.2-2 Tiny 
utilities for small and embedded system

If that's what you get it cames out when there is a problem when
booting, for instance, a missing kernel module for the hard disk
controller, a bad hard disk identifier at GRUB's menu file, etc. So
instead having you no option at all and display a black screen (because
the system is halted), we are presented with the BusyBox.
 
 That's great, just why not to protect it w/ a password prompt? - Or
 again, nobody listening, no exploits are available, etc?! ;o)

It is very easy to access into a system when you stand in front of it, I 
mean, when you have physical access to the computer. Unless you have 
secured GRUB with a password, you can append init=/bin/sh to the kernel 
line at boot menu and then again, no password will be prompted for you.

 That's good, but how I can provide password prompting? I remember in
 past times there was a prompt for Ctrl-d to press and type root's
 password.

I think that's a different thing :-?
 
 For sure, it is.
 
For example, when you go fall into init 1 you are prompted with root's
password to get into the maintenance console or continue by pressing
Ctrl +D, so here you are indeed asked for root's password because you
are inside the full shell and not inside the limited BusyBox
environment.
 
 So, where I get into - in my case - having no busybox installed, yet
 password-less root shell is granted? 8-0

I'm not sure about the scenario you are describing... I think busybox is 
installed by default and comes up when there are boot problems.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.12.03.14.55...@gmail.com

Re: Passwordless root shell is offered when boot problem occurs.

[Sthu Deus]

Thank You for Your time and answer, Arno:

From here it's all guesswork. You'd need to provide a full bootlog up
to the point where the shell is started to get any meaningful answers.

Hmm. I thought everybody has the same OS behavior in such condition...
And the problem here is only improper/default configuration.

I have grepped through my logs on HDD partition that caused the boot
stop (because one partition was not mounted that set to be auto
mounted) - yet I did not find any statements on the mounting problems
and therefore I could not find the place in log files to see the
messages around the moment the stop or root password-less shell occurs.
What should I look for (the event recorded in the logs)?
 
 the like. But if you find yourself needing to secure against that,
 then you must also set a bootloader password, lock out alternative
 boot methods, set a BIOS password and put your machine behind lock
 and key. Do you really need that?
 
 At least I want that. Do You know how to do that?
 

I know the theory, that is all I know. The Debian initramfs is
generated from scripts in /usr/share/initramfs-tools. To add files to
it, you need to create a file in /etc/initramfs-tools/hooks that
copies the required files (/sbin/sulogin, /etc/passwd and /etc/shadow)
into the initramfs, and then you need to edit the panic() function
scipts/functions to spawn sulogin instead of a shell.

In general, am I correct in understanding the situation, that what I
gonna do is abnormal behavior in Debian distro., and to have the root
password-less shell in emergency cases is OK for some (to
developers / security team) reasons - and in case I want to commit what
I have targeted, I have to develop the solution myself (that is there
is no a config. file that I might simply turn on the password prompt
for root shell in such cases)?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ed889b7.c798cc0a.1b8c.e...@mx.google.com

Re: Passwordless root shell is offered when boot problem occurs.

[Arno Schuring]

Sthu Deus (sthu.d...@gmail.com on 2011-12-02 15:17 +0700):
 
 From here it's all guesswork. You'd need to provide a full bootlog up
 to the point where the shell is started to get any meaningful
 answers.
 
 Hmm. I thought everybody has the same OS behavior in such condition...
 And the problem here is only improper/default configuration.

That could very well be, but I haven't had a boot problem in years
(well, except when trying out systemd). A standard Debian config should
not offer a passwordless root shell unless you explicitly ask for it,
but I can think of at least four ways to get such a root shell -- not
including misconfiguration, bugs or alternative boot devices.

 
 I have grepped through my logs on HDD partition that caused the boot
 stop (because one partition was not mounted that set to be auto
 mounted) - 

I don't think you'll find anything in the system logs. From the little
information you have given, it is clear that the system has not fully
started, so there is no reason to assume that /var/log is accessible or
that syslog is running.

Early boot messages should be found in /var/log/boot, but bootlogd
seems very hitmiss on my systems. Filesystem checks are logged
in /var/log/fsck.

 
 In general, am I correct in understanding the situation, that what I
 gonna do is abnormal behavior in Debian distro., and to have the root
 password-less shell in emergency cases is OK for some (to
 developers / security team) reasons

It's not about emergency situations, although it certainly can be used
as such. It's about accesss: if anyone has physical access to your
machine, there are so many ways to access your system that it is silly
to protect against one of them.

So yes, protecting yourself from physical attacks by insisting on a
root password is abnormal behaviour. How are you going to prevent an
attacker from opening your PC and connecting the harddisk to his own
machine?

 - and in case I want to commit
 what I have targeted, I have to develop the solution myself (that is
 there is no a config. file that I might simply turn on the password
 prompt for root shell in such cases)?

In short, yes. If you really want to be that paranoid (and there are
good reasons for it, especially on laptops), you should be looking at
encryption as your solution (dm-crypt, truecrypt, bitlocker), not
passwords.


Regards,
Arno


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111203000543.44f5a...@neminis.intra.loos.site

Re: Passwordless root shell is offered when boot problem occurs.

[Sthu Deus]

Thank You for Your time and answer, Camaleón:

 Once mount error occurs while OS booting, I get root shell - w/o even
 asking for password... 

You mean Busybox? :-?

I do not know - it appears when something wrong during boot process.

 How I can change the behavior (to ask for password before granting
 root shell)?

If you refer to busybox, AFAIK is not a pure root's shell but a self-
contained, separated and limited environment to run some diagnostic
tools within your machine so you can easily recover the system when
something is broken.

That's good, but how I can provide password prompting? I remember in
past times there was a prompt for Ctrl-d to press and type root's
password.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ed7b006.42a4cc0a.043b.5...@mx.google.com

Re: Passwordless root shell is offered when boot problem occurs.

[Sthu Deus]

Thank You for Your time and answer, Arno:

 Once mount error occurs while OS booting, I get root shell - w/o even
 asking for password... How I can change the behavior (to ask for
 password before granting root shell)?
 

Do you get a message 'root account locked, starting shell?'

No.

fsck errors should drop into a sulogin shell, which asks for the
password. The only way you could get a root shell is if your root
device cannot be found. In that case, there is no way to ask for a
password because there is no password file.

Well. There is root device - if You mean / mount point. Otherwise
whence sulogin comes from?

If you must, there might be a way to get what you want by adding files
to the initramfs by dropping a file in /etc/initramfs-tools/hooks/ or

Ahh. I have the dir. empty.

the like. But if you find yourself needing to secure against that, then
you must also set a bootloader password, lock out alternative boot
methods, set a BIOS password and put your machine behind lock and key.
Do you really need that?

At least I want that. Do You know how to do that?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ed7b162.4713cc0a.158a.5...@mx.google.com

Re: Passwordless root shell is offered when boot problem occurs.

[Camaleón]

On Thu, 01 Dec 2011 23:49:00 +0700, Sthu Deus wrote:

 Thank You for Your time and answer, Camaleón:
 
 Once mount error occurs while OS booting, I get root shell - w/o even
 asking for password...

You mean Busybox? :-?
 
 I do not know - it appears when something wrong during boot process.

It should be printed out, something like:

***
BusyBox v1.10.2 (Debian x-x-x-x) Built-in shell (xxx)
***

If that's what you get it cames out when there is a problem when booting, 
for instance, a missing kernel module for the hard disk controller, a bad 
hard disk identifier at GRUB's menu file, etc. So instead having you no 
option at all and display a black screen (because the system is halted), 
we are presented with the BusyBox.

 How I can change the behavior (to ask for password before granting
 root shell)?

If you refer to busybox, AFAIK is not a pure root's shell but a self-
contained, separated and limited environment to run some diagnostic
tools within your machine so you can easily recover the system when
something is broken.
 
 That's good, but how I can provide password prompting? I remember in
 past times there was a prompt for Ctrl-d to press and type root's
 password.

I think that's a different thing :-?

For example, when you go fall into init 1 you are prompted with root's 
password to get into the maintenance console or continue by pressing Ctrl
+D, so here you are indeed asked for root's password because you are 
inside the full shell and not inside the limited BusyBox environment.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.12.01.17.05...@gmail.com

Re: Passwordless root shell is offered when boot problem occurs.

[Arno Schuring]

Sthu Deus (sthu.d...@gmail.com on 2011-12-01 23:54 +0700):
 
 fsck errors should drop into a sulogin shell, which asks for the
 password. The only way you could get a root shell is if your root
 device cannot be found. In that case, there is no way to ask for a
 password because there is no password file.
 
 Well. There is root device - if You mean / mount point. Otherwise
 whence sulogin comes from?

sulogin should be in /sbin on your filesystem, but that is not
the first filesystem where programs are started from. Google early
userspace and initramfs' for background info.

From here it's all guesswork. You'd need to provide a full bootlog up
to the point where the shell is started to get any meaningful answers.

 
 If you must, there might be a way to get what you want by adding
 files to the initramfs by dropping a file
 in /etc/initramfs-tools/hooks/ or
 
 Ahh. I have the dir. empty.
 
 the like. But if you find yourself needing to secure against that,
 then you must also set a bootloader password, lock out alternative
 boot methods, set a BIOS password and put your machine behind lock
 and key. Do you really need that?
 
 At least I want that. Do You know how to do that?
 

I know the theory, that is all I know. The Debian initramfs is generated
from scripts in /usr/share/initramfs-tools. To add files to it, you
need to create a file in /etc/initramfs-tools/hooks that copies the
required files (/sbin/sulogin, /etc/passwd and /etc/shadow) into the
initramfs, and then you need to edit the panic() function
scipts/functions to spawn sulogin instead of a shell.


Regards,
Arno


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111202000209.2394c...@neminis.intra.loos.site

Re: Passwordless root shell is offered when boot problem occurs.

[Sthu Deus]

Thank You for Your time and answer, Camaleón:

You mean Busybox? :-?
 
 I do not know - it appears when something wrong during boot process.

It should be printed out, something like:

***
BusyBox v1.10.2 (Debian x-x-x-x) Built-in shell (xxx)
***

Oh, no. It's not my case. Nor I have the packages installed.

If that's what you get it cames out when there is a problem when
booting, for instance, a missing kernel module for the hard disk
controller, a bad hard disk identifier at GRUB's menu file, etc. So
instead having you no option at all and display a black screen
(because the system is halted), we are presented with the BusyBox.

That's great, just why not to protect it w/ a password prompt? - Or
again, nobody listening, no exploits are available, etc?! ;o)

 That's good, but how I can provide password prompting? I remember in
 past times there was a prompt for Ctrl-d to press and type root's
 password.

I think that's a different thing :-?

For sure, it is.

For example, when you go fall into init 1 you are prompted with
root's password to get into the maintenance console or continue by
pressing Ctrl +D, so here you are indeed asked for root's password
because you are inside the full shell and not inside the limited
BusyBox environment.

So, where I get into - in my case - having no busybox installed, yet
password-less root shell is granted? 8-0


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ed87872.8872cd0a.0b8a.e...@mx.google.com

Re: Passwordless root shell is offered when boot problem occurs.

[Camaleón]

On Mon, 28 Nov 2011 13:47:59 +0700, Sthu Deus wrote:

 Once mount error occurs while OS booting, I get root shell - w/o even
 asking for password... 

You mean Busybox? :-?

 How I can change the behavior (to ask for password before granting root
 shell)?

If you refer to busybox, AFAIK is not a pure root's shell but a self-
contained, separated and limited environment to run some diagnostic tools 
within your machine so you can easily recover the system when something 
is broken.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.11.28.15.16...@gmail.com

Re: Passwordless root shell is offered when boot problem occurs.

[Arno Schuring]

Sthu Deus (sthu.d...@gmail.com on 2011-11-28 13:47 +0700):
 Once mount error occurs while OS booting, I get root shell - w/o even
 asking for password... How I can change the behavior (to ask for
 password before granting root shell)?
 

Do you get a message 'root account locked, starting shell?'

fsck errors should drop into a sulogin shell, which asks for the
password. The only way you could get a root shell is if your root
device cannot be found. In that case, there is no way to ask for a
password because there is no password file.

If you must, there might be a way to get what you want by adding files
to the initramfs by dropping a file in /etc/initramfs-tools/hooks/ or
the like. But if you find yourself needing to secure against that, then
you must also set a bootloader password, lock out alternative boot
methods, set a BIOS password and put your machine behind lock and key.
Do you really need that?


Regards,
Arno


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2028171700.61ae3...@neminis.intra.loos.site

Passwordless root shell is offered when boot problem occurs.

[Sthu Deus]

Good time of the day.


Once mount error occurs while OS booting, I get root shell - w/o even
asking for password... How I can change the behavior (to ask for
password before granting root shell)?


Thanks for Your time.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ed32ea3.0611cc0a.0f76.e...@mx.google.com

Re: Debian 6 iSCSI root boot problem

[Stan Hoeppner]

On 9/14/2011 10:39 AM, Andrés Durán wrote:

Hello to all, and sorry for may bad english, i'm Spanish.

I'm trying to install Debian 6 on one server without internal disks, I 
have a Workstation running Debian 6 too that run as an iSCSI Target. This work 
station is configured as iSCSI target with the package iscsitarget, it is 
running without problems. The logical drive is exported perfectly.

On the other hand (the initiator), the server is an HP DL380 G6, it  
have an network controller with boot from iSCSI support, we like use it to 
start Debian 6 without PXE, BOOTP, usb or something else.
I'm using this post http://www.david-web.co.uk/blog/?p=188; to install Debian in 
the Target drive using iSCSI protocol (Debian is installed correctly in the remote drive using this 
method), but when I finish the installation and the server restart it is unable to boot. The grub 
is installed on the remote drive, and the Network firmware is well configured and it is connected 
to the remote drive at the moment of boot, but when the Grub of the remote drive try to start it 
show an error that says: Grub Read Error and the boot process is stopped at this time. 
At this time no grub rescue mode is available and no interactive methods is possible to debug the 
boot process.

Here is the details of the server and his network controller (Chipset Broadcom BCM5709C): 
http://h18000.www1.hp.com/products/quickspecs/13234_div/13234_div.HTML;

Because I'm using the iSCSI firmware provided by the network card, I'm not doing nothing in 
the last process of the post http://www.david-web.co.uk/blog/?p=188; where the post 
says: DON’T allow the system to reboot – the installed system can’t boot yet. I decided that 
I wanted to boot using BOOTP and TFTP.

Please, ¿could someone help me?


You're using an iSCSI HBA that provides the entire iSCSI solution in 
firmware, but you've followed instructions on installing Debian to boot 
using a software iSCSI initiator.  That combo won't work.


Read this:
http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c01555874/c01555874.pdf

HP has geared this doc toward Windows users, but it has all the settings 
information you need to get this working.


Do not use the software initiator.

Make sure you set Windows HBA mode to enable in the option ROM 
settings menu of the DL380 BIOS, and that the iSCSI config parameters 
are correct in the HBA firmware setup.  Then, boot the Debian installer 
CD/DVD in the DL380 G6.  If the correct driver module for the BCM5709C 
in full firmware iSCSI mode isn't automatically loaded, manually load it 
yourself.  One driver may handle both modes.  I've not used this HP HBA 
so I can't say for sure.


When you get to the partitioning menu you should see the disk device, 
just as if this were an SAS drive on a PCIe SAS card.  Partition and 
format it as you normally would, complete the installation, and reboot. 
 Unless the wrong driver module gets loaded, or you don't have all the 
BIOS/HBA firmware settings correct, it should work fine.  And without 
having to use the slower, less reliable, software iSCSI initiator.


--
Stan


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4e730b31.9050...@hardwarefreak.com

Debian 6 iSCSI root boot problem

[Andrés Durán]

Hello to all, and sorry for may bad english, i'm Spanish.

I'm trying to install Debian 6 on one server without internal disks, I 
have a Workstation running Debian 6 too that run as an iSCSI Target. This work 
station is configured as iSCSI target with the package iscsitarget, it is 
running without problems. The logical drive is exported perfectly.

On the other hand (the initiator), the server is an HP DL380 G6, it  
have an network controller with boot from iSCSI support, we like use it to 
start Debian 6 without PXE, BOOTP, usb or something else.
I'm using this post http://www.david-web.co.uk/blog/?p=188; to install 
Debian in the Target drive using iSCSI protocol (Debian is installed correctly 
in the remote drive using this method), but when I finish the installation and 
the server restart it is unable to boot. The grub is installed on the remote 
drive, and the Network firmware is well configured and it is connected to the 
remote drive at the moment of boot, but when the Grub of the remote drive try 
to start it show an error that says: Grub Read Error and the boot process is 
stopped at this time. At this time no grub rescue mode is available and no 
interactive methods is possible to debug the boot process.

Here is the details of the server and his network controller (Chipset Broadcom 
BCM5709C): 
http://h18000.www1.hp.com/products/quickspecs/13234_div/13234_div.HTML;

Because I'm using the iSCSI firmware provided by the network card, I'm 
not doing nothing in the last process of the post 
http://www.david-web.co.uk/blog/?p=188; where the post says: DON’T allow the 
system to reboot – the installed system can’t boot yet. I decided that I wanted 
to boot using BOOTP and TFTP. 

Please, ¿could someone help me?

Thanks and Best Regards,
Andrés Durán

Debian 6 iSCSI root boot problem

[Andrés Durán]

Hello to all, and sorry for may bad english, i'm Spanish.

I'm trying to install Debian 6 on one server without internal disks, I 
have a Workstation running Debian 6 too that run as an iSCSI Target. This work 
station is configured as iSCSI target with the package iscsitarget, it is 
running without problems. The logical drive is exported perfectly.

On the other hand (the initiator), the server is an HP DL380 G6, it  
have an network controller with boot from iSCSI support, we like use it to 
start Debian 6 without PXE, BOOTP, usb or something else.
I'm using this post http://www.david-web.co.uk/blog/?p=188; to install 
Debian in the Target drive using iSCSI protocol (Debian is installed correctly 
in the remote drive using this method), but when I finish the installation and 
the server restart it is unable to boot. The grub is installed on the remote 
drive, and the Network firmware is well configured and it is connected to the 
remote drive at the moment of boot, but when the Grub of the remote drive try 
to start it show an error that says: Grub Read Error and the boot process is 
stopped at this time. At this time no grub rescue mode is available and no 
interactive methods is possible to debug the boot process.

Here is the details of the server and his network controller (Chipset Broadcom 
BCM5709C): 
http://h18000.www1.hp.com/products/quickspecs/13234_div/13234_div.HTML;

Because I'm using the iSCSI firmware provided by the network card, I'm 
not doing nothing in the last process of the post 
http://www.david-web.co.uk/blog/?p=188; where the post says: DON’T allow the 
system to reboot – the installed system can’t boot yet. I decided that I wanted 
to boot using BOOTP and TFTP. 

Please, ¿could someone help me?

Thanks and Best Regards,
Andrés Durán

Boot problem after crashed update

[Simon Hoerder]

Hi,

I made a fresh install of debian squeeze just after its release and 
dutifully installed the updates suggested by the package manager 
whenever necessary.

1) This morning, I did the same (what the package manager calls a safe
   update, no packages where removed or installed) but in between the
   update crashed the system.
2) The only thing that worked was switching between x (ctrl+alt+f7) and
   the terminal (ctrl+alt+f1) but I couldn't log in to the terminal;
   instead I got some error messages about init (or initsomething -
   unfortunately I do not remember anymore) spawning to much and
   something (it wasn't being clear what) being delayed/suppressed for 5
   minutes.
3) After the 5 minutes the situation hadn't changed however and I had to
   get to work so I switched the laptop off. (ctrl+esc just produced an
   error message that /sbin/shutdown didn't work or was unavailable.)
4) When I booted the laptop at work, it crashed soon after grub, the
   rror message being:

udevd[58]: error: runtime directory '/run/udev' not writable, for now 
falling back to '/dev/.udev'

run-init: /sbin/init: No such file or directory
[  4.515687] Kernel panic - not syncing: Attempted to kill init!

5) Booting the failsafe debian doesn't work either.
6) Booting my old SuSE works and all disks are mounted properly.
7) I then tried to run the rescue system from the debian installation
   dvd:
   - Executing a shell in /dev/sda3 (my root) fails without any
 meaningful error message.
   - Executing a shell in the installer environment succeeds with
 /dev/sda3 mounted in /target. But 'chroot /target' fails with the
 following error message:
chroot: can't execute '/bin/sh': No such file or directory
 However, ls -la /target/bin tells me that /target/bin/sh is a link
 to /target/bin/dash which exists and is writable and executable.
   - reinstalling grub into the MBR fails without any meaningful error
 message.
8) Using the shell from the installer system, I checked that
   /boot/vmlinuz-2.6.35-5-amd64
   /boot/initrd.img-2.6.32-5-amd64
   exist where grub expects to find them.

I have some (limited) experience with linux but regarding the boot 
process I'm basically a complete novice. Unfortunately, I have no clue 
how to continue from here on. I have googled and found loads of bug 
reports for  boot problems but none seemed quite like mine and the tips 
given there weren't applicable or (e.g. reinstall grub, run a execute 
a rescue system shell on /) didn't work. (Given that I'm not sure how 
to diagnose the problem properly, I probably used the wrong google 
search terms.) All help appreciated.


My laptop is a Lenovo G550 with an Intel Core 2 Duop T6600 CPU. I have 
debian-6.0.1a-amd64 installed.


Many thanks,
Simon Hoerder
--
/***
  * Dipl. Ing. Simon Hoerder
  * Department of Computer Science
  * Merchant Venturers Building, 2.01
  * Woodland Road
  * Bristol, BS8 1UB
  * United Kingdom
  *
  * http://www.cs.bris.ac.uk/Research/CryptographySecurity/
  * UK mobile: +44 7564 035925
  ***/


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4dcbb1c2.2050...@hoerder.net

Re: Boot problem after crashed update

[Jochen Schulz]

 I made a fresh install of debian squeeze just after its release and
 dutifully installed the updates suggested by the package manager
 whenever necessary.

What's the content of your sources.list?

 2) The only thing that worked was switching between x (ctrl+alt+f7) and
the terminal (ctrl+alt+f1) but I couldn't log in to the terminal;
instead I got some error messages about init (or initsomething -
unfortunately I do not remember anymore) spawning to much and
something (it wasn't being clear what) being delayed/suppressed for 5
minutes.

The exact error message might have helped in identifying the issue.

 4) When I booted the laptop at work, it crashed soon after grub, the
rror message being:
 
 udevd[58]: error: runtime directory '/run/udev' not writable, for
 now falling back to '/dev/.udev'

That looks like you are actually running testing or unstable. A similar
issue has hit my sid machein recently. Descriptions of the problem and
solutions have been discussed here.

 run-init: /sbin/init: No such file or directory

Ouch. Can you confirm that /sbin/init still exists on your root
filesystem? You mentioned that you have another distro on the same
machine, so you can use that to inspect the filesystem. I'd do an fsck,
too.

 7) I then tried to run the rescue system from the debian installation
dvd:
- Executing a shell in /dev/sda3 (my root) fails without any
  meaningful error message.

If it doesn't mean anything to you, it still may mean something to us.
:)

J.
-- 
Watching television is more hip than actually speaking to anyone.
[Agree]   [Disagree]
 http://www.slowlydownward.com/NODATA/data_enter2.html


signature.asc
Description: Digital signature

Re: Boot problem after crashed update

[Sven Joachim]

On 2011-05-12 12:53 +0200, Jochen Schulz wrote:

 udevd[58]: error: runtime directory '/run/udev' not writable, for
 now falling back to '/dev/.udev'

 That looks like you are actually running testing or unstable.

FWIW, the error message has not been present in udev versions before
168, and that version is only in unstable.

 A similar
 issue has hit my sid machein recently. Descriptions of the problem and
 solutions have been discussed here.

The best thing is to ignore the udev error message, it's actually
harmless. 

 run-init: /sbin/init: No such file or directory

 Ouch. Can you confirm that /sbin/init still exists on your root
 filesystem? You mentioned that you have another distro on the same
 machine, so you can use that to inspect the filesystem. I'd do an fsck,
 too.

 7) I then tried to run the rescue system from the debian installation
dvd:
- Executing a shell in /dev/sda3 (my root) fails without any
  meaningful error message.

 If it doesn't mean anything to you, it still may mean something to us.

I suspect that Simon has upgraded libc6 to 2.13-3 and got hit by bug
#626450¹ (sometimes unstable actually deserves its name…).

Sven


¹ http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626450


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/878vuc89au@turtle.gmx.de

Re: Boot problem after crashed update

[Simon Hoerder]

Eccles, David wrote:

From: Simon Hoerder [mailto:si...@hoerder.net]

1) This morning, I did the same (what the package manager calls a safe
update, no packages where removed or installed) but in between the
   update crashed the system.
...
udevd[58]: error: runtime directory '/run/udev' not writable, for now 
falling back to '/dev/.udev'

run-init: /sbin/init: No such file or directory
[  4.515687] Kernel panic - not syncing: Attempted to kill init!


This sounds very similar to the problem I've had. Not quite sure how I should
be reporting it, but here's my attempt at a bug report:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626479

David Eccles (gringer)



Hi David,

seems you upgraded libc to 2.13-3 as Sven just pointed out ( 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626450). :-) At least 
you got the output from the update - my screensaver had turned on but 
couldn't be turned off anymore so I didn't see anything except the 
little bit I reported.


Cheers, Simon

--
/***
  * Dipl. Ing. Simon Hoerder
  * Department of Computer Science
  * Merchant Venturers Building, 2.01
  * Woodland Road
  * Bristol, BS8 1UB
  * United Kingdom
  *
  * http://www.cs.bris.ac.uk/Research/CryptographySecurity/
  * UK mobile: +44 7564 035925
  ***/


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4dcbc66c.8020...@hoerder.net