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


Groups > linux.debian.user > #200304

Re: Yet another UEFI/BIOS question

From steve <dlist@bluewin.ch>
Newsgroups linux.debian.user
Subject Re: Yet another UEFI/BIOS question
Date 2018-09-19 18:00 +0200
Message-ID <wzN3r-pg-3@gated-at.bofh.it> (permalink)
References <wzM7n-8j8-3@gated-at.bofh.it> <wzMAp-fQ-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Hi Darac,

Thanks answering me.

Le 19-09-2018, à 16:28:51 +0100, Darac Marjal a écrit :

>On Wed, Sep 19, 2018 at 04:50:14PM +0200, steve wrote:
>>Hi there,
>>
>>Just bought a new Mother Board and transfered all of my sdd's from my
>>old box to the new one. New box boots almost normally (I'll come back
>>there later). I then installed Win10 on a new sdd, which boots also
>>correctly.
>
>I'm not familiar with the acronym "sdd". Did You Mean™
>	SSDs - Solid State Disks
>	SDDs - SCSI Disk Drives (I'm making something up here)
>	/dev/sd* - Disks using the SCSI driver

Sorry, Solid State Disks.

>>
>>Now when booting Debian Stretch, I get the following messages, and the
>>system takes ages too continue the process:
>>
>>[    0.185353] Error parsing PCC subspaces from PCCT
>>[    0.275838] ACPI Error: [INTS] Namespace lookup failure, AE_ALREADY_EXISTS (20170831/dswload-378)
>>[    0.319628] ACPI Error: [SDS0] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
>>[    0.319685] ACPI Error: Method parse/execution failed \SHAD._STA, AE_NOT_FOUND (20170831/psparse-550)
>>[    0.319749] ACPI Error: [SDS0] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
>>[    0.319804] ACPI Error: Method parse/execution failed \SHAD._STA, AE_NOT_FOUND (20170831/psparse-550)
>>[   33.170504] ACPI Error: [SDS0] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
>>[   33.170575] ACPI Error: Method parse/execution failed \SHAD._STA, AE_NOT_FOUND (20170831/psparse-550)
>>[   33.195221] ACPI Error: [SDS0] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
>>[   33.195279] ACPI Error: Method parse/execution failed \SHAD._STA, AE_NOT_FOUND (20170831/psparse-550)
>>[   33.977492] ACPI Error: [SDS0] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)
>>[   33.977584] ACPI Error: Method parse/execution failed \SHAD._STA, AE_NOT_FOUND (20170831/psparse-550)
>>
>
>I don't believe this is a problem.

Well it is at boot time. System waits for more than 30 secondes before
going on.


> ACPI is a complex beast and 
>sometimes the ACPI driver is overly strict about working with ACPI and
>sometimes ACPI is overly strict about working with Linux (actually, I
>think Linux nowadays defaults to pretending to be Windows). The general
>advice is "Do you notice any other issues other than error messages?"
>If not, don't worry about it.


Haven't noticed other issues yet.



>>
>>Googling around, I suspect that these errors come from the fact that the
>>BIOS is configured to but in Legacy mode (aka Bios mode) rather than in
>>the more modern UEFI mode. Just an hypothesis.
>>
>>But the problem is that my old sdd's have all (except /dev/sdd, which I just
>>noticed) a msdos partition table:
>
>Changing Motherboard shouldn't have altered the partition table on 
>your disks.

It hasn't. The fact that sdd has a gpt one is a happy coincidence :) 
This device holds my virtual machines so no real problems.


>>
>>root@box:~# parted /dev/sda print | grep -i partition
>>Partition Table: msdos
>>root@box:~# parted /dev/sdb print | grep -i partition
>>Partition Table: msdos
>>root@box:~# parted /dev/sdc print | grep -i partition
>>Partition Table: msdos
>>root@box:~# parted /dev/sdd print | grep -i partition
>>Partition Table: gpt
>>root@box:~# parted /dev/sde print | grep -i partition
>>Partition Table: msdos
>>root@box:~# parted /dev/sdf print | grep -i partition
>>Partition Table: msdos
>>root@box:~# parted /dev/sdg print | grep -i partition
>>Partition Table: gpt
>>1      1049kB  524MB  523MB   ntfs         Basic data partition          hidden, diag
>>2      524MB   629MB  105MB   fat32        EFI system partition          boot, esp
>>3      629MB   646MB  16.8MB               Microsoft reserved partition  msftres
>>4      646MB   250GB  249GB   ntfs         Basic data partition          msftdata
>>
>>
>>Grub-pc is currently installed on /dev/sda1 (/boot) and /dev/sda.
>>
>>Disks sdb, sdc and sdf are raid1:
>>
>>cat /proc/mdstat Personalities : [linear] [multipath] [raid0] 
>>[raid1] [raid6] [raid5] [raid4] [raid10] md1 : active raid1 
>>sdb5[2](S) sdf5[3] sdc5[1]
>>    117120896 blocks super 1.2 [2/2] [UU]
>>md2 : active raid1 sdf6[3] sdb6[2](S) sdc6[1]
>>    97589120 blocks super 1.2 [2/2] [UU]
>>md0 : active raid1 sdf1[3] sdb1[2](S) sdc1[1]
>>    19514240 blocks super 1.2 [2/2] [UU]
>>
>>
>>My questions are rather simple. Is it conceivable to convert the sdd's to gpt
>>partition table without reformatting/reinstalling the whole disks? Or maybe
>>only sda (which contains /, /usr, /boot and /tmp) so I can switch my BIOS to
>>UEFI? Am I stuck with those msdos partition tables?
>
>Yes. Here's a good write-up on the subject from Rod Smith, the author 
>of gdisk, a GPT-only equivalent to fdisk.
>
>http://www.rodsbooks.com/gdisk/mbr2gpt.html

I'll read. Thanks for the link.

Steve

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Yet another UEFI/BIOS question steve <dlist@bluewin.ch> - 2018-09-19 17:00 +0200
  Re: Yet another UEFI/BIOS question Darac Marjal <mailinglist@darac.org.uk> - 2018-09-19 17:30 +0200
    Re: Yet another UEFI/BIOS question steve <dlist@bluewin.ch> - 2018-09-19 18:00 +0200
  Re: Yet another UEFI/BIOS question Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-09-19 23:40 +0200
    Re: Yet another UEFI/BIOS question steve <dlist@bluewin.ch> - 2018-09-20 09:00 +0200
      Re: Yet another UEFI/BIOS question Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-09-20 20:30 +0200
        [SOLVED] Re: Yet another UEFI/BIOS question steve <dlist@bluewin.ch> - 2018-09-21 08:40 +0200
          Re: [SOLVED] Re: Yet another UEFI/BIOS question Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-09-21 20:30 +0200
            Re: [SOLVED] Re: Yet another UEFI/BIOS question steve <dlist@bluewin.ch> - 2018-09-22 07:00 +0200
              Re: [SOLVED] Re: Yet another UEFI/BIOS question Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-09-22 10:10 +0200
                Re: [SOLVED] Re: Yet another UEFI/BIOS question steve <dlist@bluewin.ch> - 2018-09-22 10:50 +0200
            And yet another UEFI/BIOS question: Work on both. Wayne Sallee <Wayne@WayneSallee.com> - 2018-09-23 17:00 +0200
              Re: And yet another UEFI/BIOS question: Work on both. Patrick Bartek <nemommxiv@gmail.com> - 2018-09-23 18:20 +0200
                Re: And yet another UEFI/BIOS question: Work on both. Wayne Sallee <Wayne@WayneSallee.com> - 2018-09-23 23:30 +0200
                Re: And yet another UEFI/BIOS question: Work on both. Patrick Bartek <nemommxiv@gmail.com> - 2018-09-24 03:00 +0200
                Re: And yet another UEFI/BIOS question: Work on both. David Wright <deblis@lionunicorn.co.uk> - 2018-09-24 21:20 +0200
                Re: And yet another UEFI/BIOS question: Work on both. Michael Stone <mstone@debian.org> - 2018-09-24 21:30 +0200
                Re: And yet another UEFI/BIOS question: Work on both. Pascal Hambourg <pascal@plouf.fr.eu.org> - 2018-09-27 15:10 +0200
              Re: And yet another UEFI/BIOS question: Work on both. David Wright <deblis@lionunicorn.co.uk> - 2018-09-23 20:40 +0200

csiph-web