On 10/6/23 00:22, Bret Busby wrote:
On 10/6/23 00:05, Bret Busby wrote:
On 9/6/23 23:34, Bret Busby wrote:
On 9/6/23 18:43, Rodolfo Medina wrote:
Rodolfo Medina writes:
I want to install Debian on a new machine but don't manage to boot
from USB
stick. (I can do so regularly with another ma
Am Freitag, 9. Juni 2023, 18:37:14 CEST schrieb Stefan Monnier:
Hi Stefan,
this might e a problem of your BIOS. However, if your BIOS does not support
booting from USB,
here is a trick:
You can download a bootable CD-Rom from this site:
https://www.plop.at[1]
Look for the Bootmgr. It is a liv
On 6/8/23 11:36, Rodolfo Medina wrote:
I want to install Debian on a new machine but don't manage to boot from USB
stick. (I can do so regularly with another machine, so the USB stick is ok and
so is the Debian netinst I burned onto it.) At the boot I press F9 and a menu
appears where I can c
> I want to install Debian on a new machine but don't manage to boot
> from USB stick. (I can do so regularly with another machine, so the
> USB stick is ok and so is the Debian netinst I burned onto it.) At
> the boot I press F9 and a menu appears where I can choose to boot from
> USB stick; but
On 9/6/23 23:34, Bret Busby wrote:
On 9/6/23 18:43, Rodolfo Medina wrote:
Rodolfo Medina writes:
I want to install Debian on a new machine but don't manage to boot
from USB
stick. (I can do so regularly with another machine, so the USB stick
is ok
and so is the Debian netinst I burned onto
On 10/6/23 00:05, Bret Busby wrote:
On 9/6/23 23:34, Bret Busby wrote:
On 9/6/23 18:43, Rodolfo Medina wrote:
Rodolfo Medina writes:
I want to install Debian on a new machine but don't manage to boot
from USB
stick. (I can do so regularly with another machine, so the USB
stick is ok
and so
On 9/6/23 18:43, Rodolfo Medina wrote:
Rodolfo Medina writes:
I want to install Debian on a new machine but don't manage to boot from USB
stick. (I can do so regularly with another machine, so the USB stick is ok
and so is the Debian netinst I burned onto it.) At the boot I press F9 and a
me
On 09/06/2023 17:54, Rodolfo Medina wrote:
...And now I tried even with an MS Windows 10 installation CDROM but the
problem remains!
Check what devices are enabled in boot settings in system setup (BIOS or
firmware setting).
When you switching off a computer with windows, perhaps actually it
On Fri, 9 Jun 2023, Rodolfo Medina wrote:
Rodolfo Medina writes:
Rodolfo Medina writes:
I want to install Debian on a new machine but don't manage to boot from USB
stick. (I can do so regularly with another machine, so the USB stick is ok
and so is the Debian netinst I burned onto it.) A
Rodolfo Medina writes:
> Rodolfo Medina writes:
>
>> I want to install Debian on a new machine but don't manage to boot from USB
>> stick. (I can do so regularly with another machine, so the USB stick is ok
>> and so is the Debian netinst I burned onto it.) At the boot I press F9 and
>> a menu
Rodolfo Medina writes:
> I want to install Debian on a new machine but don't manage to boot from USB
> stick. (I can do so regularly with another machine, so the USB stick is ok
> and so is the Debian netinst I burned onto it.) At the boot I press F9 and a
> menu appears where I can choose to b
Am 08.06.2023 um 20:36 schrieb Rodolfo Medina:
> I want to install Debian on a new machine but don't manage to boot from USB
> stick. (I can do so regularly with another machine, so the USB stick is ok
> and
> so is the Debian netinst I burned onto it.) At the boot I press F9 and a menu
> appear
On 6/9/23 00:59, Rodolfo Medina wrote:
David Christensen writes:
On 6/8/23 11:36, Rodolfo Medina wrote:
I want to install Debian on a new machine but don't manage to boot from USB
stick. (I can do so regularly with another machine, so the USB stick is ok
and
so is the Debian netinst I burned o
Bret Busby writes:
> If you go to
>
> https://lists.ubuntu.com/archives/ubuntu-users/2022-July/thread.html
>
> and scroll down to the thread starting with the subject "Questions about
> Linux Mint and this list", read that message, and, work your way through the
> responses, especially, the ones
"Thomas Schmitt" writes:
> I understand from the link that it has a 64 bit Celeron J4105 CPU.
> So its EFI would want an "amd64" ISO.
>
> [...]
>
> You could try with
>
> https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-11.7.0-amd64-netinst.iso
> and CSM disabled.
Unfortunatel
David Christensen writes:
> On 6/8/23 11:36, Rodolfo Medina wrote:
>> I want to install Debian on a new machine but don't manage to boot from USB
>> stick. (I can do so regularly with another machine, so the USB stick is ok
>> and
>> so is the Debian netinst I burned onto it.) At the boot I pre
Hi,
i wrote:
> > I understand from the link that it has a 64 bit Celeron J4105 CPU.
> > So its EFI would want an "amd64" ISO.
Charles Curley wrote:
> A Celeron should be able to run i386 Debian. But the amd64 might be a
> better use of its capabilities.
Other than with legacy BIOS, EFI looks for
You might want to read the manual with the computer. My Lenovo would boot
automatically to Windows. In the manual, it had a hold on the side, trusty
paperwork clip press the hole, boots into bios. Install Linux
On Thu, Jun 8, 2023, 2:51 PM Bret Busby wrote:
> On 9/6/23 05:18, Bret Busby wrote:
>
On 6/8/23 11:36, Rodolfo Medina wrote:
I want to install Debian on a new machine but don't manage to boot from USB
stick. (I can do so regularly with another machine, so the USB stick is ok and
so is the Debian netinst I burned onto it.) At the boot I press F9 and a menu
appears where I can cho
On Thu 08 Jun 2023 at 15:36:27 (-0600), Charles Curley wrote:
> On Thu, 08 Jun 2023 23:15:36 +0200 "Thomas Schmitt" wrote:
>
> > I understand from the link that it has a 64 bit Celeron J4105 CPU.
> > So its EFI would want an "amd64" ISO.
>
> A Celeron should be able to run i386 Debian. But the am
On 9/6/23 05:18, Bret Busby wrote:
On 9/6/23 05:02, Bret Busby wrote:
On 9/6/23 04:52, Rodolfo Medina wrote:
Bret Busby writes:
My understanding is that Windows 11 computers have malware that is
designed
to prevent booting into anything other than the malicious Windows 11.
A procedure to g
On 9/6/23 05:26, Bret Busby wrote:
On 9/6/23 05:18, Bret Busby wrote:
On 9/6/23 05:02, Bret Busby wrote:
On 9/6/23 04:52, Rodolfo Medina wrote:
Bret Busby writes:
My understanding is that Windows 11 computers have malware that is
designed
to prevent booting into anything other than the mal
On Thu, 08 Jun 2023 23:15:36 +0200
"Thomas Schmitt" wrote:
> I understand from the link that it has a 64 bit Celeron J4105 CPU.
> So its EFI would want an "amd64" ISO.
A Celeron should be able to run i386 Debian. But the amd64 might be a
better use of its capabilities.
--
Does anybody read sig
On Thu, 08 Jun 2023 20:01:20 +
Rodolfo Medina wrote:
> Here it is:
>
>
> https://www.amazon.it/KUU-Notebook-Prozessor-Bluetooth-portatile/dp/B0C4TGXKBC/ref=sr_1_2_sspa?crid=3PK1MW55MAOA
Hmm, never heard of that vendor. You might do better with one of the
Debian Italian language lists.
htt
On 9/6/23 05:02, Bret Busby wrote:
On 9/6/23 04:52, Rodolfo Medina wrote:
Bret Busby writes:
My understanding is that Windows 11 computers have malware that is
designed
to prevent booting into anything other than the malicious Windows 11.
A procedure to get around the Windows 11 malware, an
Hi,
Rodolfo Medina wrote:
> https://www.amazon.it/KUU-Notebook-Prozessor-Bluetooth-portatile/dp/B0C4TGX
KBC/ref=sr_1_2_sspa?crid=3PK1MW55MAOA
> $ dd if=debian-11.7.0-i386-netinst.iso of=/dev/sdd bs=4M; sync
I understand from the link that it has a 64 bit Celeron J4105 CPU.
So its EFI would want
On 9/6/23 04:52, Rodolfo Medina wrote:
Bret Busby writes:
My understanding is that Windows 11 computers have malware that is designed
to prevent booting into anything other than the malicious Windows 11.
A procedure to get around the Windows 11 malware, and to be able to boot into
Linux, has,
Bret Busby writes:
> My understanding is that Windows 11 computers have malware that is designed
> to prevent booting into anything other than the malicious Windows 11.
>
> A procedure to get around the Windows 11 malware, and to be able to boot into
> Linux, has, I believe, been described on the
On 9/6/23 02:36, Rodolfo Medina wrote:
I want to install Debian on a new machine but don't manage to boot from USB
stick. (I can do so regularly with another machine, so the USB stick is ok and
so is the Debian netinst I burned onto it.) At the boot I press F9 and a menu
appears where I can cho
Thank you Andrew and Charles.
"Andrew M.A. Cater" writes:
> What model of machine is this - and how new?
Here it is:
https://www.amazon.it/KUU-Notebook-Prozessor-Bluetooth-portatile/dp/B0C4TGXKBC/ref=sr_1_2_sspa?crid=3PK1MW55MAOA
> How did you write the image to the USB stick?
This way:
On Thu, 8 Jun 2023 18:36:27 +
Rodolfo Medina wrote:
> I want to install Debian on a new machine but don't manage to boot
> from USB stick.
It might help if you identified the new machine.
You might also check web sites related to Linux on that manufacturer's
products. E.g. thinkwiki (https:
On Thu, Jun 08, 2023 at 06:36:27PM +, Rodolfo Medina wrote:
> I want to install Debian on a new machine but don't manage to boot from USB
> stick. (I can do so regularly with another machine, so the USB stick is ok
> and
> so is the Debian netinst I burned onto it.) At the boot I press F9 an
I want to install Debian on a new machine but don't manage to boot from USB
stick. (I can do so regularly with another machine, so the USB stick is ok and
so is the Debian netinst I burned onto it.) At the boot I press F9 and a menu
appears where I can choose to boot from USB stick; but then it d
Claudio Kuenzler writes:
On Wed, Jun 30, 2021 at 9:51 AM Paul Wise wrote:
Claudio Kuenzler wrote:
> I currently suspect a Kernel bug in 5.10.
Thanks to everyone for hints and suggestions!
At the end it turned out to be an issue with the hpwdt module. After
blacklisting this module,
On Wed, Jun 30, 2021 at 9:51 AM Paul Wise wrote:
> Claudio Kuenzler wrote:
>
> > I currently suspect a Kernel bug in 5.10.
>
Thanks to everyone for hints and suggestions!
At the end it turned out to be an issue with the hpwdt module. After
blacklisting this module, no boot or stability issues wi
Issue: "No bootable devices found" after motherboard replaced
Background: previously functional Debian system where hardware quit
(so called "No POST").
I spent a few hours on a "No bootable devices found" issue:
The fix was in the Dell BIOS (got to by pressing 'F2'):
-> Boot Configuration
-->
Claudio Kuenzler wrote:
> I currently suspect a Kernel bug in 5.10.
You could try booting a bullseye install with the buster kernel,
if that works then it sounds like you need a kernel git bisect.
https://wiki.debian.org/DebianKernel/GitBisect
--
bye,
pabs
https://wiki.debian.org/PaulWise
s
I tend to suspect it's unrelated, but if you add "nomodeset nofb" to
> your boot command line it will turn off the graphics drivers.
>
Yes, I guess it is indeed unrelated. With buster I can see the same
messages during boot:
- *ERROR* Failed to load firmware! on drm
- pcc_cpufreq_init: Too many CP
On Tue, Jun 29, 2021 at 11:08:09AM +0200, Claudio Kuenzler wrote:
This line catches my attention:
[ 62.953082] systemd[1]: modprobe@drm.service: Succeeded.
This is missing (doesn't show) when the freeze happens.
I tend to suspect it's unrelated, but if you add "nomodeset nofb" to
your boot
>
> Trace dump suggests that crash occurs while executing cpuidle module.
> Try to boot with "intel_pstate=force" kernel parameter [1] to force
> different CPU driver (if CPU supports it) and\or "cpuidle.off=1" to disable
> cpuidle subsystem.
>
>
Thank you Alexander and Georgi (thanks for the link!
On 6/29/21 1:29 PM, Claudio Kuenzler wrote:
> Hi Georgi
>
> I noticed that kernel logs you posted are between 62nd - 64th second
> after kernel loading. Why is the boot process so slow?
>
>
> Due to a disabled SATA device in BIOS, the kernel tries to do an ERST
> and SRST and does this u
On 29.06.2021 15:29, Claudio Kuenzler wrote:
Hi Georgi
I noticed that kernel logs you posted are between 62nd - 64th second
after kernel loading. Why is the boot process so slow?
Due to a disabled SATA device in BIOS, the kernel tries to do an ERST
and SRST and does this until 60s aft
Hi Georgi
I noticed that kernel logs you posted are between 62nd - 64th second
> after kernel loading. Why is the boot process so slow?
>
Due to a disabled SATA device in BIOS, the kernel tries to do an ERST and
SRST and does this until 60s after boot.
That's OK, it's been the same on Buster, too
On 6/29/21 12:08 PM, Claudio Kuenzler wrote:
> Sorry for auto-responding all the time ;-)
> I was just able to catch a "freeze" followed by a successful boot
> afterwards.
>
> The successful boot continues with these lines:
>
> [ 62.922169] systemd[1]: Finished Create System Users.
> [ 62.923
Sorry for auto-responding all the time ;-)
I was just able to catch a "freeze" followed by a successful boot
afterwards.
The successful boot continues with these lines:
[ 62.922169] systemd[1]: Finished Create System Users.
[ 62.923633] systemd[1]: Starting Create Static Device Nodes in /dev.
Meanwhile I was able to identify more by removing "quiet" from the grub
loader.
The pcc_cpufreq_init does not seem to hurt the booting - these are just
warnings popping up.
The following messages appear on the console before the server freezes:
[ OK ] Finished Load Kernel Module fuse.
[ 62.887855
Hello!
Currently testing the new Bullseye release (using
firmware-bullseye-DI-rc2-amd64-netinst.iso) and see a strange phenomenon on
a HP Proliant DL380 G7 server.
During boot, the following messages show up in the console:
[63.063844] pcc_cpufreq_init: Too many CPUs, dynamic performance scaling
This is an Acer netbook, a year or two old, no legacy BIOS, bought with
Win10 installed. It has a hardwired SSD designated mmcblk0 and I
installed another SSD which is /dev/sda. Stretch installed with no
problem, and gives me a Windows entry in its menu. It's been OK for
about 18 months, so I tho
On 08/11/2017 01:45 AM, Fungi4All wrote:
From: field.engin...@gmail.com
To: debian-user@lists.debian.org
On 08/10/2017 12:00 PM, kelsang sherab wrote:
I run Debian stretch on MacBook Air
I did a restore backup from previous system[debian Jessie ]
I don"t know, but maybe I can help with
From: field.engin...@gmail.com
> To: debian-user@lists.debian.org
>
> On 08/10/2017 12:00 PM, kelsang sherab wrote:
>> I run Debian stretch on MacBook Air
>>
>> I did a restore backup from previous system[debian Jessie ]
>>
>> Now machine is not bootin
On 08/10/2017 12:00 PM, kelsang sherab wrote:
I run Debian stretch on MacBook Air
I did a restore backup from previous system[debian Jessie ]
Now machine is not booting
upon boot the machine gives the normal GRUB menu:
Debian GNU/Linux
Advanced options for Debian GNU/linux
Click the 1st one
I run Debian stretch on MacBook Air
I did a restore backup from previous system[debian Jessie ]
Now machine is not booting
upon boot the machine gives the normal GRUB menu:
Debian GNU/Linux
Advanced options for Debian GNU/linux
Click the 1st one
saying
Loading etc
Loading initial ram disk
>>
>>Thanks to him, a guy (kozaki) has done thorough research (see 1&2) to
>>solve this problem. It is caused by a failed attempt to restore the LCD
>>backlight at boot. Passing 'systemd.restore_state=0' kernel parameter at
>>boot is a solution.
>>
>>1) https://bugs.archlinux.org/task/47509
>>2) ht
Le 18/05/2017 à 02:30, bw a écrit :
>> I had exactly the same problem recently with almost the same laptop:
>> Dell Inspiron Mini 1012 that I had previously given to a friend. I
>> switched it back to Jessie.
>
> I can confirm this on Dell Mini 1012, installation is successful, first boot
> is ok
On Fri, May 19, 2017 at 12:29 PM, Luis Finotti
wrote:
[snip]
> Any suggestions would be appreciated...
>
>
>
Never mind. The screen just went red and opening up to check the video
cable I just broke the trackpad (which was secured only by tape). (And it
did not fix the screen.)
I will just f
Thanks for your continued help!
On Thu, May 18, 2017 at 6:46 AM, Brian wrote:
>
> GRUB does its job but it appears the problem occurs when control is
> handed over to the init system.
>
> At the GRUB menu edit the linux line to add systemd.unit=rescue.target
> or systemd.unit=emergency.target.
>
On Wed 17 May 2017 at 19:01:20 -0400, Luis Finotti wrote:
> > No. I get stuck again.
>
> > You were able to type these commands? What do you mean by "stuck"? After
> > pressing ENTER do you get anything on the screen? What do you see?
>
>
> Yes, I am able to type those and boot starts, but get
>I had exactly the same problem recently with almost the same laptop:
>Dell Inspiron Mini 1012 that I had previously given to a friend. I
>switched it back to Jessie.
I can confirm this on Dell Mini 1012, installation is successful, first boot is
okay. After reboot all boots fail at various plac
> No. I get stuck again.
>
> You were able to type these commands? What do you mean by "stuck"? After
> pressing ENTER do you get anything on the screen? What do you see?
Yes, I am able to type those and boot starts, but gets stuck in the
middle. No HD activity and Ctrl+Alt+Del (or any other c
On Wed 17 May 2017 at 15:07:54 -0400, Luis Finotti wrote:
> > Let me know if I can provide anymore info or if this gives you any idea of
>
> > > what is wrong...
> >
> > At the GRUB menu hit "c" and type
> >
> > set root=(hd0,msdos1)
> > linux /vmlinuz root=/dev/sda1
> > initrd /initrd.img
> >
> Let me know if I can provide anymore info or if this gives you any idea of
> > what is wrong...
>
> At the GRUB menu hit "c" and type
>
> set root=(hd0,msdos1)
> linux /vmlinuz root=/dev/sda1
> initrd /initrd.img
> boot
>
> and hit the ENTER key.
>
> Do you boot into the OS?
No. I get stu
On Wed 17 May 2017 at 14:22:47 -0400, Luis Finotti wrote:
> Thanks for the reply!
No problem. There are GRUB experts on this list who are keeping an eye
on this thread, I hope.
> On Wed, May 17, 2017 at 2:03 PM, Brian wrote:
>
> > On Wed 17 May 2017 at 13:41:03 -0400, Luis Finotti wrote:
> >
>
I had exactly the same problem recently with almost the same laptop:
Dell Inspiron Mini 1012 that I had previously given to a friend. I
switched it back to Jessie.
Thanks for the reply!
On Wed, May 17, 2017 at 2:03 PM, Brian wrote:
> On Wed 17 May 2017 at 13:41:03 -0400, Luis Finotti wrote:
>
> > I've installed stretch from a DI RC3 image (from here:
> > https://cdimage.debian.org/cdimage/unofficial/non-free/
> cd-including-firmware/)
> > a couple of weeks
On Wed 17 May 2017 at 13:41:03 -0400, Luis Finotti wrote:
> I've installed stretch from a DI RC3 image (from here:
> https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/)
> a couple of weeks back on an old Dell Inspiron Mini 1018.
Is this the only OS on the machine?
> Th
Dear all,
I've installed stretch from a DI RC3 image (from here:
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/)
a couple of weeks back on an old Dell Inspiron Mini 1018.
The install went without a problem and I could reboot just fine. I then
updated it, installed
Hello Jiri,
I have faced the same problem. I think there is something wrong with the
sssd-nss socket unit /lib/systemd/system/sssd-nss.socket
After I disabled it by
# systemctl disable sssd-nss.socket
the problem has disappeared and my system (Stretch) boots normally. SSSD
works. NSS throu
Hello Jiri,
I had the same problem and removing sssd solved the issue. Thank you
for the solution.
Do you know if there is already a bug report so the developers are
aware of the problem?
Greetings
Leo
signature.asc
Description: This is a digitally signed message part
Hi.So the whole problem was related to sssd packages. When I unistalled sssd packeges the issue disappeared. Still not sure what problem sssd caused exactly.- JiriOn 1 Feb. 2017 8:59 pm, j...@ganomi.com wrote:Hi.I rhink this issue is related to avahi not starting and therefore having impact on netw
Hi.I rhink this issue is related to avahi not starting and therefore having impact on network manager.I wish systemd can process these things faster. Its killing me to wait until the system boots up just because few servises failed.I will keep digging into why avahi fails.- JiriOn 1 Feb. 2017 8:21
Thanks Santiago,
Issue fixed, bad record in fstab
Thanks,
Peter Reid
Thanks,
Peter Reid
Web: http://reidweb.com
Mobile: +44 78 5281 8850
On 17 June 2015 at 21:49, Peter Reid wrote:
> Hi,
>
> Good suggestions, I will try those out.
>
> However point to note: when I attempt to SSH with any se
Hi,
Good suggestions, I will try those out.
However point to note: when I attempt to SSH with any set of credentials to
the server, connection is being refused. Nmap of the server also suggests
SSH is not running
To me this would suggest that the OpenSSH service isn't even running on my
server.
On Wed, Jun 17, 2015 at 02:56:46PM -0400, Gary Dale wrote:
> You can ping but not ssh. This suggests that services are not being started.
> dmesg confirms this as nothing is showing up after the network is brought
> up.
Hmm, no. My system has ssh running but there are no traces of ssh in
dmesg at
On 17/06/15 02:42 PM, Peter Reid wrote:
Hello,
I recently rebooted my Debian 8 (Jessie) system, which I upgraded from
Wheezy upon the release of Debian 8. I shutdown my system and
restarted it, and the system does not appear to be 'booting'.
*_Description:_*
The system boots and responds to
Hello,
I recently rebooted my Debian 8 (Jessie) system, which I upgraded from
Wheezy upon the release of Debian 8. I shutdown my system and restarted it,
and the system does not appear to be 'booting'.
*Description:*
The system boots and responds to ping on both IPv4 and IPv6 interfaces,
however
Gary Dale writes:
> On 25/11/14 02:14 PM, lee wrote:
>> Hi,
>>
>> what could be the problem with the backport kernels? They never finish
>> booting when the root fs is on an LVM volume.
>>
>> Do I need to take special precautions with the backports kernel to get
>> it to boot? I have a separate
On 25/11/14 02:14 PM, lee wrote:
Hi,
what could be the problem with the backport kernels? They never finish
booting when the root fs is on an LVM volume.
Do I need to take special precautions with the backports kernel to get
it to boot? I have a separate /boot partition not on LVM and a biosg
Hi,
what could be the problem with the backport kernels? They never finish
booting when the root fs is on an LVM volume.
Do I need to take special precautions with the backports kernel to get
it to boot? I have a separate /boot partition not on LVM and a biosgrub
partition with the root fs on a
On Fri, Nov 21, 2014 at 09:17:09PM -0700, john.tiger wrote:
> Have followed both guided partitioning as well as trying manual partitions
> with efi boot as first partition. Install works fine but after completion
> does not boot (get ? folder image) - tried to boot into rescue mode but
> target
Have followed both guided partitioning as well as trying manual
partitions with efi boot as first partition. Install works fine but
after completion does not boot (get ? folder image) - tried to boot
into rescue mode but target partition not found
partitions :
free space 1 gb
/efi
On Wed, Sep 03, 2014 at 10:43:50AM +0500, Muhammad Yousuf Khan wrote:
>i have a 2TB hard disk and installation went fine no errors. however i can
>not manage to boot it from hard disk.
What happens when you try? Any error messages? Do you just get a
blinking cursor? Does the PC ex
i have a 2TB hard disk and installation went fine no errors. however i can
not manage to boot it from hard disk. my partitions are like this.
1. /boot : Boot Flag ON.
1. Swap : Boot Flag Off.
1. / : Boot Flag off.
but the weird part is when i press "F10" and select harddrive to boot it
amaz
Am 2014-01-28 15:07, schrieb Selim T. Erdogan:
>> apt-get install --reinstall grub-efi-amd64
>
> If the machine wasn't booting, how did you get to a state where you
> could run that? Did you use a rescue usb/cd?
Booted the machine using the rescue feature from a debian netboot on usb
stick
On Tue, 2014-01-28 at 15:28 +0100, Ralf Mardorf wrote:
> On Tue, 2014-01-28 at 08:07 -0600, Selim T. Erdogan wrote:
> > Jogi Hofmüller, 28.01.2014:
> > > Dear all,
> > >
> > > Zenbook bootable again. The fix was actually really easy:
> > >
> > > apt-get install --reinstall grub-efi-amd64
> >
On Tue, 2014-01-28 at 08:07 -0600, Selim T. Erdogan wrote:
> Jogi Hofmüller, 28.01.2014:
> > Dear all,
> >
> > Zenbook bootable again. The fix was actually really easy:
> >
> > apt-get install --reinstall grub-efi-amd64
>
> If the machine wasn't booting, how did you get to a state where you
Jogi Hofmüller, 28.01.2014:
> Dear all,
>
> Zenbook bootable again. The fix was actually really easy:
>
> apt-get install --reinstall grub-efi-amd64
If the machine wasn't booting, how did you get to a state where you
could run that? Did you use a rescue usb/cd?
--
To UNSUBSCRIBE, email t
Dear all,
Zenbook bootable again. The fix was actually really easy:
apt-get install --reinstall grub-efi-amd64
The question remains what led to this error, but I guess I will never
find out ;)
Regards!
--
j.hofmüller
mur.sat -- a space art projecthttp://sat.mur.at/
Dear all,
First of all let me state that I believe that what I am experiencing is
not necessarily a Debian problem. I direct my questions to this list
because I expect the most relevant answers here and I have been using
Debian now for more than 10 years.
I have been using this ASUS Zenbook (UX3
Miles Fidelman wrote:
> So problem is solved but 2 questions remain:
> - what's going on?
> - why didn't the installer put things in the right places?
I read your posting but don't understand it.
> Basic setup:
> - PXEboot into installer
You have set up a PXEboot on your network? That is sophis
Miles Fidelman wrote:
Miles Fidelman wrote:
Miles Fidelman wrote:
Just did a new install of Wheezy on a server, but having problems
trying to boot.
Basic setup:
- PXEboot into installer
- a pretty standard install
- had to fiddle a little at the end to get the MBR into the right
places (RAID
Miles Fidelman wrote:
Miles Fidelman wrote:
Just did a new install of Wheezy on a server, but having problems
trying to boot.
Basic setup:
- PXEboot into installer
- a pretty standard install
- had to fiddle a little at the end to get the MBR into the right
places (RAIDed disks, USB stick mou
Miles Fidelman wrote:
Just did a new install of Wheezy on a server, but having problems
trying to boot.
Basic setup:
- PXEboot into installer
- a pretty standard install
- had to fiddle a little at the end to get the MBR into the right
places (RAIDed disks, USB stick mounts as /dev/sda)
- now
Hi Folks,
Just did a new install of Wheezy on a server, but having problems trying
to boot.
Basic setup:
- PXEboot into installer
- a pretty standard install
- had to fiddle a little at the end to get the MBR into the right places
(RAIDed disks, USB stick mounts as /dev/sda)
- now it boots,
Hi,
Got the problems solved. I couldn't solve the problem by using the rescue
disk, as it wouldn't let me stop the raid array.
What I did was drop into the maintenance mode:
mdadm --assemble /dev/md1 /dev/sdd1 /dev/sde1 //This should recreate the
array
mdadm --detail --scan >> /etc/mdadm/mdadm.co
Hello,
I've been too nervous to reboot, so I've left it in the rescue mode at the
point where I assembled the raid arrays and went into boot at the \
partition.
Tried to run:
mdadm --stop /dev/md127
but got a mdadm: failed to stop array /dev/md127: Device or resource busy.
Perhaps a running proce
James Allsopp wrote:
> I'd like to hear about the optimisations, but I think I'll wait till I get
> the system rebuilt!
Basically I had expected you to use either rescue mode of the d-i or a
livecd or other to assemble the arrays. You did. But neither array
came up completely correct. One came
Thanks Bob, like I say, very much appreciated and I'll let you know how it
goes!
I'd like to hear about the optimisations, but I think I'll wait till I get
the system rebuilt!
James
On 4 July 2013 00:47, Bob Proulx wrote:
> James Allsopp wrote:
> > Thanks Bob, really can't thank you enough. Jus
James Allsopp wrote:
> Thanks Bob, really can't thank you enough. Just to be clear about this, I'd
> do these commands from the rescue disk after I have assembled the arrays
> and gone to the bash shell?
Short answer: Yes. Go for it!
Longer answer: There are all kinds of things I want to say her
Thanks Bob, really can't thank you enough. Just to be clear about this, I'd
do these commands from the rescue disk after I have assembled the arrays
and gone to the bash shell?
Much appreciated,
James
On 2 July 2013 22:44, Bob Proulx wrote:
> James Allsopp wrote:
> > One other point sda isn't
James Allsopp wrote:
> One other point sda isn't the boot hard drive, that's the partitions /sdb1
> and sdc1, but these should be the same (I thought I'd mirrored them to be
> honest).
I don't see sda anywhere. It might be a dual booting Windows disk?
Or other. But the BIOS will boot the first d
1 - 100 of 204 matches
Mail list logo
