Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #232405 > unrolled thread

cannot boot into Debian after transferring hard drive to another desktop computer

Back to article view | Back to linux.debian.user

Contents

  cannot boot into Debian after transferring hard drive to another  desktop computer kaye n <guikaye@gmail.com> - 2021-03-05 16:20 +0100
    Re: cannot boot into Debian after transferring hard drive to another  desktop computer kaye n <guikaye@gmail.com> - 2021-03-05 16:30 +0100
      Re: cannot boot into Debian after transferring hard drive to  another desktop computer Joe <joe@jretrading.com> - 2021-03-05 21:10 +0100
    Re: cannot boot into Debian after transferring hard drive to  another desktop computer Charles Curley <charlescurley@charlescurley.com> - 2021-03-05 20:50 +0100
    Re: cannot boot into Debian after transferring hard drive to another  desktop computer IL Ka <kazakevichilya@gmail.com> - 2021-03-05 21:20 +0100
    Re: cannot boot into Debian after transferring hard drive to another  desktop computer "Andrew M.A. Cater" <amacater@einval.com> - 2021-03-05 22:00 +0100
    Re: cannot boot into Debian after transferring hard drive to another  desktop computer Felix Miata <mrmazda@earthlink.net> - 2021-03-05 23:40 +0100
    Re: cannot boot into Debian after transferring hard drive to another  desktop computer David Christensen <dpchrist@holgerdanske.com> - 2021-03-06 04:50 +0100

#232405 — cannot boot into Debian after transferring hard drive to another desktop computer

[Multipart message — attachments visible in raw view] — view raw

Hello Friends!

Desktop Computer One has a hard drive that is multiboot:  Windows 7,
Debian, and another linux operating system which I will call linux-x.

It seems that the MOTHERBOARD of Desktop Computer One has finally given out
(wild guess only, as even a linux live USB can't function properly).  I
took out the multiboot hard drive and put it in another desktop computer
which I call Desktop Computer Two.

Now I can boot into linux-x just fine with Desktop Computer Two.  I'm using
linux-x to type and send this email.  I have not tried the windows 7 yet.

However I cannot boot into Debian (I believe it is Debian 10).  I get this
message:

-----------------
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or "exit"
to boot into default mode.

Cannot open access to console, the root account is locked.
See sulogin(8) man page for more details.

Press Enter to continue.
-------------------

If I press enter, I reach the Debian logo with the circling animation but
after a while I get the above message again.

If it matters, the UUID of both / and /home partitions of the Debian system
remain the same; I compared the info provided by Gparted and the /etc/fstab
in the Debian system.

Thank you for your time.
kaye

[toc] | [next] | [standalone]

#232407

[Multipart message — attachments visible in raw view] — view raw

UPDATE:
I also cannot boot into Windows 7.  I get the start normally or safe mode
window.


On Fri, Mar 5, 2021 at 11:12 PM kaye n <guikaye@gmail.com> wrote:

> Hello Friends!
>
> Desktop Computer One has a hard drive that is multiboot:  Windows 7,
> Debian, and another linux operating system which I will call linux-x.
>
> It seems that the MOTHERBOARD of Desktop Computer One has finally given
> out (wild guess only, as even a linux live USB can't function properly).  I
> took out the multiboot hard drive and put it in another desktop computer
> which I call Desktop Computer Two.
>
> Now I can boot into linux-x just fine with Desktop Computer Two.  I'm
> using linux-x to type and send this email.  I have not tried the windows 7
> yet.
>
> However I cannot boot into Debian (I believe it is Debian 10).  I get this
> message:
>
> -----------------
> You are in emergency mode. After logging in, type "journalctl -xb" to view
> system logs, "systemctl reboot" to reboot, "systemctl default" or "exit"
> to boot into default mode.
>
> Cannot open access to console, the root account is locked.
> See sulogin(8) man page for more details.
>
> Press Enter to continue.
> -------------------
>
> If I press enter, I reach the Debian logo with the circling animation but
> after a while I get the above message again.
>
> If it matters, the UUID of both / and /home partitions of the Debian
> system remain the same; I compared the info provided by Gparted and the
> /etc/fstab in the Debian system.
>
> Thank you for your time.
> kaye
>
>

[toc] | [prev] | [next] | [standalone]

#232429 — Re: cannot boot into Debian after transferring hard drive to another desktop computer

On Fri, 5 Mar 2021 23:25:30 +0800
kaye n <guikaye@gmail.com> wrote:

> UPDATE:
> I also cannot boot into Windows 7.  I get the start normally or safe
> mode window.
> 
That's deliberate. You'll probably have to reactivate Windows, possibly
by phone.

-- 
Joe

[toc] | [prev] | [next] | [standalone]

#232427 — Re: cannot boot into Debian after transferring hard drive to another desktop computer

On Fri, 5 Mar 2021 23:12:35 +0800
kaye n <guikaye@gmail.com> wrote:

> Desktop Computer One has a hard drive that is multiboot:  Windows 7,
> Debian, and another linux operating system which I will call linux-x.
> 
> It seems that the MOTHERBOARD of Desktop Computer One has finally
> given out (wild guess only, as even a linux live USB can't function
> properly).

How far do you get booting? Do you get the grub2 menu?

If you have memtest86 (assuming it's an Intel processor or similar) on
either of your linuxes, what does that report?

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#232430

[Multipart message — attachments visible in raw view] — view raw

Hi.

A couple of questions.

* Do you use EFI or MBR/BIOS mode?
* You have a SATA disk, right? Does your controller set to the AHCI mode?
Was it set to AHCI in the previous motherboard?


On Fri, Mar 5, 2021 at 6:13 PM kaye n <guikaye@gmail.com> wrote:

> Hello Friends!
>
> Desktop Computer One has a hard drive that is multiboot:  Windows 7,
> Debian, and another linux operating system which I will call linux-x.
>
> It seems that the MOTHERBOARD of Desktop Computer One has finally given
> out (wild guess only, as even a linux live USB can't function properly).  I
> took out the multiboot hard drive and put it in another desktop computer
> which I call Desktop Computer Two.
>
> Now I can boot into linux-x just fine with Desktop Computer Two.  I'm
> using linux-x to type and send this email.  I have not tried the windows 7
> yet.
>
> However I cannot boot into Debian (I believe it is Debian 10).  I get this
> message:
>
> -----------------
> You are in emergency mode. After logging in, type "journalctl -xb" to view
> system logs, "systemctl reboot" to reboot, "systemctl default" or "exit"
> to boot into default mode.
>
> Cannot open access to console, the root account is locked.
> See sulogin(8) man page for more details.
>
> Press Enter to continue.
> -------------------
>
> If I press enter, I reach the Debian logo with the circling animation but
> after a while I get the above message again.
>
> If it matters, the UUID of both / and /home partitions of the Debian
> system remain the same; I compared the info provided by Gparted and the
> /etc/fstab in the Debian system.
>
> Thank you for your time.
> kaye
>
>

[toc] | [prev] | [next] | [standalone]

#232433

On Fri, Mar 05, 2021 at 11:12:35PM +0800, kaye n wrote:
> Hello Friends!
> 
> Desktop Computer One has a hard drive that is multiboot:  Windows 7,
> Debian, and another linux operating system which I will call linux-x.
> 
> It seems that the MOTHERBOARD of Desktop Computer One has finally given out
> (wild guess only, as even a linux live USB can't function properly).  I
> took out the multiboot hard drive and put it in another desktop computer
> which I call Desktop Computer Two.
> 
> Now I can boot into linux-x just fine with Desktop Computer Two.  I'm using
> linux-x to type and send this email.  I have not tried the windows 7 yet.
> 
> However I cannot boot into Debian (I believe it is Debian 10).  I get this
> message:
> 
> -----------------
> You are in emergency mode. After logging in, type "journalctl -xb" to view
> system logs, "systemctl reboot" to reboot, "systemctl default" or "exit"
> to boot into default mode.
> 
> Cannot open access to console, the root account is locked.
> See sulogin(8) man page for more details.
> 
> Press Enter to continue.
> -------------------
> 
> If I press enter, I reach the Debian logo with the circling animation but
> after a while I get the above message again.
> 
> If it matters, the UUID of both / and /home partitions of the Debian system
> remain the same; I compared the info provided by Gparted and the /etc/fstab
> in the Debian system.
> 
> Thank you for your time.
> kaye

OK. 

* In what order did you install Debian / Linux-x / Windows on the original
  machine?

* Are the two motherboards booting the same way - was one booting legacy/MBR 
  and is the other booting using UEFI?

* What happens if you boot into rescue mode for the Debian / boot using boot
  media and use rescue mode?

If you can boot using rescue media, say, and chroot into the Debian partition,
you can use the option to re-install GRUB

Windows 7

If you can't boot into Windows 7 - use the original install media to boot and 
boot from the DVD

One suggestion online is to use System Recovery Options and use Startup Repair
or a more complex route via Windows Commmand Prompt.

Ideally, you should not now be using Windows 7 (and, in fact, should not be 
using Windows at all - but that's another rant :-) )

All the very best, as ever,

Andy C.

[toc] | [prev] | [next] | [standalone]

#232437

kaye n composed on 2021-03-05 23:12 (UTC+0800):

> It seems that the MOTHERBOARD of Desktop Computer One has finally given out
> (wild guess only										
High probability that what went bad was the power supply. High probably you can
open the power supply and spot bad electrolytic capacitors. Generally these can be
successfully replaced using only modest soldering/desoldering skills. The forums
at http://badcaps.net/ has all the HOWTOs for DIY. More often than not, a dead PS
does not kill the motherboard, but it is certainly a significant possibility. How
old is yours? What model? Power supply brand?
-- 
Evolution as taught in public schools, like religion,
	is based on faith, not on science.

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

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

[toc] | [prev] | [next] | [standalone]

#232445

On 3/5/21 7:12 AM, kaye n wrote:
> Hello Friends!
> 
> Desktop Computer One has a hard drive that is multiboot:  Windows 7,
> Debian, and another linux operating system which I will call linux-x.
> 
> It seems that the MOTHERBOARD of Desktop Computer One has finally given out
> (wild guess only, as even a linux live USB can't function properly).  I
> took out the multiboot hard drive and put it in another desktop computer
> which I call Desktop Computer Two.
> 
> Now I can boot into linux-x just fine with Desktop Computer Two.  I'm using
> linux-x to type and send this email.  I have not tried the windows 7 yet.
> 
> However I cannot boot into Debian (I believe it is Debian 10).  I get this
> message:
> 
> -----------------
> You are in emergency mode. After logging in, type "journalctl -xb" to view
> system logs, "systemctl reboot" to reboot, "systemctl default" or "exit"
> to boot into default mode.
> 
> Cannot open access to console, the root account is locked.
> See sulogin(8) man page for more details.
> 
> Press Enter to continue.
> -------------------
> 
> If I press enter, I reach the Debian logo with the circling animation but
> after a while I get the above message again.
> 
> If it matters, the UUID of both / and /home partitions of the Debian system
> remain the same; I compared the info provided by Gparted and the /etc/fstab
> in the Debian system.

On 3/5/21 7:25 AM, kaye n wrote:
 > I also cannot boot into Windows 7.  I get the start normally or safe
 > mode window.


I attempted multi-boot years ago.  Even when I got it working (and kept 
it working), I found that I wanted to use the multiple OS's at the same 
time.  My solution was to get another computer, put drive racks in my 
computers, dedicate one drive to each OS, and then boot a given drive in 
an available computer.  I now have a half dozen computers and a dozen OS 
drives.  The key is to install each OS so that its boot loader finds the 
right partitions regardless of the BIOS device enumeration.  This works 
great for FOSS OS's, but Windows is tied to the computer it was 
activated on.


I would use a power supply tester and test all of your power supplies.


Can you fix One (or do you want to?), such as by installing a new power 
supply or an identical motherboard?


Alternatively, install a blank drive in Two and install Debian.  Put the 
salvaged HDD into a USB enclosure and back up the Debian stuff.  Restore 
to the new Debian drive.  Similarly, get two more drives and do install/ 
backup/ restore cycles for Windows 7 and linux-x.


David

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web