[opensuse-support] failing boot, apparently not reading EFI partitioin
toshiba satellite laptop S55-C5274 dualboot via grub Tumbleweed (primary) and win10 cannot boot into either system did have broken xfs on /dev/sda7 (home) backed up entire /home/<user> to an external disk correct brokenness with xfs_repair -L made partition mountable do not appear to have lost anything # efibootmgr RootCurrent: 0003 Timeout: 0 seconds BootOrder: 2001 2003 2002 Boot0000* Realtek PXE Boot0001* Realtek PXE Boot0003* EFI USB Device (ASIX AX88772 USB Fast Ethernet Controller) Boot2001* EFI USB Device Boot2002* EFI DVD/CDROM Boot2003* EFI Network grep efi /etc/fstab UUID=52B7-E591 /boot/efi vfat defaults 0 0 from "journalctl -xb" Mar 20 16:13:52 toshiba systemd[1]: dev-disk-by\x2duuid-52B7\x2dE591.device: Job dev-disk-by\x2duuid-52B7\x2dE591.device/start timed out. Mar 20 16:13:52 toshiba systemd[1]: Timed out waiting for device /dev/disk/by-uuid/52B7-E591. -- Subject: A start job for unit dev-disk-by\x2duuid-52B7\x2dE591.device -- has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit dev-disk-by\x2duuid-52B7\x2dE591.device has -- finished with a failure. full output from "journalctl -xb" is here http://wahoo.no-ip.org/~paka/journalctl.xb.txt machine is booted to kernel-default 4.20.12 using an openSUSE live disk but is in maintenence mode other information available but I don't know what else is relevant or necessary. help appreciated, tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 20/03/2019 22.13, Patrick Shanahan wrote:
toshiba satellite laptop S55-C5274 dualboot via grub Tumbleweed (primary) and win10 cannot boot into either system
did have broken xfs on /dev/sda7 (home) backed up entire /home/<user> to an external disk correct brokenness with xfs_repair -L made partition mountable do not appear to have lost anything
# efibootmgr RootCurrent: 0003 Timeout: 0 seconds BootOrder: 2001 2003 2002 Boot0000* Realtek PXE Boot0001* Realtek PXE Boot0003* EFI USB Device (ASIX AX88772 USB Fast Ethernet Controller) Boot2001* EFI USB Device Boot2002* EFI DVD/CDROM Boot2003* EFI Network
grep efi /etc/fstab UUID=52B7-E591 /boot/efi vfat defaults 0 0
from "journalctl -xb" Mar 20 16:13:52 toshiba systemd[1]: dev-disk-by\x2duuid-52B7\x2dE591.device: Job dev-disk-by\x2duuid-52B7\x2dE591.device/start timed out. Mar 20 16:13:52 toshiba systemd[1]: Timed out waiting for device /dev/disk/by-uuid/52B7-E591. -- Subject: A start job for unit dev-disk-by\x2duuid-52B7\x2dE591.device -- has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit dev-disk-by\x2duuid-52B7\x2dE591.device has -- finished with a failure.
full output from "journalctl -xb" is here http://wahoo.no-ip.org/~paka/journalctl.xb.txt
machine is booted to kernel-default 4.20.12 using an openSUSE live disk but is in maintenence mode
Run fsck on the efi partition. But keep reading first. Another possibility is that it is no longer "/dev/disk/by-uuid/52B7-E591". You also has a problem with /dev/sda, IO and bad sectors. Mar 20 16:12:40 toshiba kernel: ata1.00: failed command: READ FPDMA QUEUED Mar 20 16:12:40 toshiba kernel: ata1.00: cmd 60/08:50:00:08:00/00:00:00:00:00/40 tag 10 ncq dma 4096 in res 41/40:08:00:08:00/00:00:00:00:00/40 Emask 0x409 (media error) <F> Mar 20 16:12:40 toshiba kernel: ata1.00: status: { DRDY ERR } Mar 20 16:12:40 toshiba kernel: ata1.00: error: { UNC } Mar 20 16:12:40 toshiba kernel: ata1.00: configured for UDMA/100 Mar 20 16:12:40 toshiba kernel: sd 0:0:0:0: [sda] tag#10 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Mar 20 16:12:40 toshiba kernel: sd 0:0:0:0: [sda] tag#10 Sense Key : Medium Error [current] Mar 20 16:12:40 toshiba kernel: sd 0:0:0:0: [sda] tag#10 Add. Sense: Unrecovered read error - auto reallocate failed Mar 20 16:12:40 toshiba kernel: sd 0:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 00 00 08 00 00 00 08 00 Mar 20 16:12:40 toshiba kernel: print_req_error: I/O error, dev sda, sector 2048 Mar 20 16:12:40 toshiba kernel: Buffer I/O error on dev sda1, logical block 0, async page read I don't know if sda is the disk that holds the EFI partition, but I suspect it is, because I see that /home is sda7. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [03-20-19 17:29]:
On 20/03/2019 22.13, Patrick Shanahan wrote:
toshiba satellite laptop S55-C5274 dualboot via grub Tumbleweed (primary) and win10 cannot boot into either system
did have broken xfs on /dev/sda7 (home) backed up entire /home/<user> to an external disk correct brokenness with xfs_repair -L made partition mountable do not appear to have lost anything
# efibootmgr RootCurrent: 0003 Timeout: 0 seconds BootOrder: 2001 2003 2002 Boot0000* Realtek PXE Boot0001* Realtek PXE Boot0003* EFI USB Device (ASIX AX88772 USB Fast Ethernet Controller) Boot2001* EFI USB Device Boot2002* EFI DVD/CDROM Boot2003* EFI Network
grep efi /etc/fstab UUID=52B7-E591 /boot/efi vfat defaults 0 0
from "journalctl -xb" Mar 20 16:13:52 toshiba systemd[1]: dev-disk-by\x2duuid-52B7\x2dE591.device: Job dev-disk-by\x2duuid-52B7\x2dE591.device/start timed out. Mar 20 16:13:52 toshiba systemd[1]: Timed out waiting for device /dev/disk/by-uuid/52B7-E591. -- Subject: A start job for unit dev-disk-by\x2duuid-52B7\x2dE591.device -- has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit dev-disk-by\x2duuid-52B7\x2dE591.device has -- finished with a failure.
full output from "journalctl -xb" is here http://wahoo.no-ip.org/~paka/journalctl.xb.txt
machine is booted to kernel-default 4.20.12 using an openSUSE live disk but is in maintenence mode
Run fsck on the efi partition. But keep reading first.
Another possibility is that it is no longer "/dev/disk/by-uuid/52B7-E591".
You also has a problem with /dev/sda, IO and bad sectors.
Mar 20 16:12:40 toshiba kernel: ata1.00: failed command: READ FPDMA QUEUED Mar 20 16:12:40 toshiba kernel: ata1.00: cmd 60/08:50:00:08:00/00:00:00:00:00/40 tag 10 ncq dma 4096 in res 41/40:08:00:08:00/00:00:00:00:00/40 Emask 0x409 (media error) <F> Mar 20 16:12:40 toshiba kernel: ata1.00: status: { DRDY ERR } Mar 20 16:12:40 toshiba kernel: ata1.00: error: { UNC } Mar 20 16:12:40 toshiba kernel: ata1.00: configured for UDMA/100 Mar 20 16:12:40 toshiba kernel: sd 0:0:0:0: [sda] tag#10 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Mar 20 16:12:40 toshiba kernel: sd 0:0:0:0: [sda] tag#10 Sense Key : Medium Error [current] Mar 20 16:12:40 toshiba kernel: sd 0:0:0:0: [sda] tag#10 Add. Sense: Unrecovered read error - auto reallocate failed Mar 20 16:12:40 toshiba kernel: sd 0:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 00 00 08 00 00 00 08 00 Mar 20 16:12:40 toshiba kernel: print_req_error: I/O error, dev sda, sector 2048 Mar 20 16:12:40 toshiba kernel: Buffer I/O error on dev sda1, logical block 0, async page read
I don't know if sda is the disk that holds the EFI partition, but I suspect it is, because I see that /home is sda7.
EFI is /dev/sda1 and it is vfat ran fsck.vfat -r /dev/sda1 nothing repaired and cannot capture fsck screen output disk is bad? output from smartctl is http://wahoo.no-ip.org/~paka/smartctl.txt tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 20/03/2019 22.51, Patrick Shanahan wrote:
* Carlos E. R. <> [03-20-19 17:29]:
I don't know if sda is the disk that holds the EFI partition, but I suspect it is, because I see that /home is sda7.
EFI is /dev/sda1 and it is vfat
ran fsck.vfat -r /dev/sda1
nothing repaired and cannot capture fsck screen output
disk is bad?
output from smartctl is http://wahoo.no-ip.org/~paka/smartctl.txt
Yes, disk is bad. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 9 Power_On_Hours 0x0032 032 032 000 Old_age Always - 27335 Disk is old. 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 6 197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 4104 198 Offline_Uncorrectable 0x0030 001 001 000 Old_age Offline - 255 And those figures are bad. Notice that the "THRESH" is zero, and the values start at 100. When they drop down to threshold, replace fast. I would power off, get a replacement, then, if you wish, dd?rescue to clone it if you wish. With a backup, you may attempt recovery of the disk: I would try: dd if=/dev/zero of=/dev/FAULTY bs=16M oflag=direct status=progress then run smartctl test=long on it. Extract the results (-a), and repeat hours later. Maybe repeat the dd and the long test. Observe if the realloacated count increase from test to test, which would indicate that deterioration continues. If stable, you may use the disk for offline storage. At 27000 hours and 2.5 inches I have my doubts about using it in the laptop. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Patrick Shanahan composed on 2019-03-20 17:13 (UTC-0400):
toshiba satellite laptop S55-C5274 dualboot via grub Tumbleweed (primary) and win10 cannot boot into either system ... # efibootmgr RootCurrent: 0003 Timeout: 0 seconds BootOrder: 2001 2003 2002 Boot0000* Realtek PXE Boot0001* Realtek PXE Boot0003* EFI USB Device (ASIX AX88772 USB Fast Ethernet Controller) Boot2001* EFI USB Device Boot2002* EFI DVD/CDROM Boot2003* EFI Network
This smells like it could be related to a bug I filed last week, even though it happened to me in 15.1 rather than TW, and there is no Windows on my Asus: https://bugzilla.opensuse.org/show_bug.cgi?id=1129328 Yours looks to be only part of the bigger problem I reported. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Felix Miata <mrmazda@earthlink.net> [03-20-19 18:13]:
Patrick Shanahan composed on 2019-03-20 17:13 (UTC-0400):
toshiba satellite laptop S55-C5274 dualboot via grub Tumbleweed (primary) and win10 cannot boot into either system ... # efibootmgr RootCurrent: 0003 Timeout: 0 seconds BootOrder: 2001 2003 2002 Boot0000* Realtek PXE Boot0001* Realtek PXE Boot0003* EFI USB Device (ASIX AX88772 USB Fast Ethernet Controller) Boot2001* EFI USB Device Boot2002* EFI DVD/CDROM Boot2003* EFI Network
This smells like it could be related to a bug I filed last week, even though it happened to me in 15.1 rather than TW, and there is no Windows on my Asus: https://bugzilla.opensuse.org/show_bug.cgi?id=1129328
Yours looks to be only part of the bigger problem I reported.
I believe my problem relates to the EFI partition not being read at all. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 21/03/2019 00.10, Patrick Shanahan wrote:
* Felix Miata <mrmazda@earthlink.net> [03-20-19 18:13]:
Patrick Shanahan composed on 2019-03-20 17:13 (UTC-0400):
toshiba satellite laptop S55-C5274 dualboot via grub Tumbleweed (primary) and win10 cannot boot into either system ... # efibootmgr RootCurrent: 0003 Timeout: 0 seconds BootOrder: 2001 2003 2002 Boot0000* Realtek PXE Boot0001* Realtek PXE Boot0003* EFI USB Device (ASIX AX88772 USB Fast Ethernet Controller) Boot2001* EFI USB Device Boot2002* EFI DVD/CDROM Boot2003* EFI Network
This smells like it could be related to a bug I filed last week, even though it happened to me in 15.1 rather than TW, and there is no Windows on my Asus: https://bugzilla.opensuse.org/show_bug.cgi?id=1129328
Yours looks to be only part of the bigger problem I reported.
I believe my problem relates to the EFI partition not being read at all.
The system fails to find the UUID of that partition. Maybe the rest is readable, but it doesn't locate the partition because if fails to read the UUID. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Patrick Shanahan composed on 2019-03-20 19:10 (UTC-0400):
Felix Miata composed:
This smells like it could be related to a bug I filed last week, even though it happened to me in 15.1 rather than TW, and there is no Windows on my Asus: https://bugzilla.opensuse.org/show_bug.cgi?id=1129328
Yours looks to be only part of the bigger problem I reported.
I believe my problem relates to the EFI partition not being read at all.
Not, or mis-, I believe contributed to why my partition table got corrupted, and why the entries on my ESP (and yours?) disappeared from NVRAM - or vice versa. What name is attributed to your Toshiba's BIOS - AMI, Toshiba, Phoenix, Award, other? -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Felix Miata <mrmazda@earthlink.net> [03-20-19 19:28]:
Patrick Shanahan composed on 2019-03-20 19:10 (UTC-0400):
Felix Miata composed:
This smells like it could be related to a bug I filed last week, even though it happened to me in 15.1 rather than TW, and there is no Windows on my Asus: https://bugzilla.opensuse.org/show_bug.cgi?id=1129328
Yours looks to be only part of the bigger problem I reported.
I believe my problem relates to the EFI partition not being read at all.
Not, or mis-, I believe contributed to why my partition table got corrupted, and why the entries on my ESP (and yours?) disappeared from NVRAM - or vice versa.
What name is attributed to your Toshiba's BIOS - AMI, Toshiba, Phoenix, Award, other?
Vendor: "INSYDE Corp." -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 20/03/2019 23.12, Felix Miata wrote:
Patrick Shanahan composed on 2019-03-20 17:13 (UTC-0400):
toshiba satellite laptop S55-C5274 dualboot via grub Tumbleweed (primary) and win10 cannot boot into either system ... # efibootmgr RootCurrent: 0003 Timeout: 0 seconds BootOrder: 2001 2003 2002 Boot0000* Realtek PXE Boot0001* Realtek PXE Boot0003* EFI USB Device (ASIX AX88772 USB Fast Ethernet Controller) Boot2001* EFI USB Device Boot2002* EFI DVD/CDROM Boot2003* EFI Network
This smells like it could be related to a bug I filed last week, even though it happened to me in 15.1 rather than TW, and there is no Windows on my Asus: https://bugzilla.opensuse.org/show_bug.cgi?id=1129328
Yours looks to be only part of the bigger problem I reported.
In his case, it is a single partition that fails, the rest mount just fine. He also has a bunch of bad sectors, and the log shows problems reading the disk. Hardware problems. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
full output from "journalctl -xb" is here > http://wahoo.no-ip.org/~paka/journalctl.xb.txt > > machine is booted to kernel-default 4.20.12 using an openSUSE live > disk but is in
On 2019-03-20 03:13 PM, Patrick Shanahan wrote: maintenence mode > > other information available but I don't know what else is relevant > or necessary. > > help appreciated, tks > I have to agree with Carlos on this -- that drive is failing. One thing Carlos did not mention that I recall is this (from your journal extract): Mar 20 16:12:22 toshiba kernel: sd 0:0:0:0: [sda] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Mar 20 16:12:22 toshiba kernel: sd 0:0:0:0: [sda] tag#5 Sense Key : Medium Error [current] Mar 20 16:12:22 toshiba kernel: sd 0:0:0:0: [sda] tag#5 Add. Sense: Unrecovered read error - auto reallocate failed Mar 20 16:12:22 toshiba kernel: sd 0:0:0:0: [sda] tag#5 CDB: Read(10) 28 00 00 00 08 00 00 00 08 00 Mar 20 16:12:22 toshiba kernel: print_req_error: I/O error, dev sda, sector 2048 That is repeated in your later report of the smartctl output: Error 8904 occurred at disk power-on lifetime: 27335 hours (1138 days + 23 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 41 38 00 08 00 40 Error: UNC at LBA = 0x00000800 = 2048 There is an unrecoverable error at LBA 2048, which I believe puts it right in the middle of the MBR. That is likely the partition record for the partition in question; the system does not even seem to be able to find the partition. You need a new drive, without question. Once you have booted from the live disk, can you mount the partition in question? If so, you are lucky, and can just use dd to copy the entire drive onto a replacement; if not, you are going to have to use dd with an offset to copy just the partitions (not the MBR) onto the replacement drive. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Darryl Gregorash <strange.charmed.antiquark@gmail.com> [03-20-19 21:56]:
On 2019-03-20 03:13 PM, Patrick Shanahan wrote:
[...]
After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 41 38 00 08 00 40 Error: UNC at LBA = 0x00000800 = 2048
There is an unrecoverable error at LBA 2048, which I believe puts it right in the middle of the MBR. That is likely the partition record for the partition in question; the system does not even seem to be able to find the partition.
You need a new drive, without question. Once you have booted from the live disk, can you mount the partition in question? If so, you are lucky, and can just use dd to copy the entire drive onto a replacement; if not, you are going to have to use dd with an offset to copy just the partitions (not the MBR) onto the replacement drive.
no, the efi partition is unmountable but I can read it with efibootmgr which provides: # efibootmgr BootCurrent: 0002 Timeout: 0 seconds BootOrder: 2001,2003,2002 Boot0000* Realtek PXE Boot0001* Realtek PXE Boot0002* EFI USB Device (ASIX AX88772 USB Fast Ethernet Controller) Boot2001* EFI USB Device Boot2002* EFI DVD/CDROM Boot2003* EFI Network I began yesterday making a full disk copy that is just now 70% thru the first pass, gnu_ddrescue, showing 18 read errors in a 1Tb drive. can I not finish this and then write 00's to the efi partition, /dev/sda1, if it is not recovered and then use efibootmgr to write it anew instead of starting over? tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Le 21/03/2019 à 13:44, Patrick Shanahan a écrit :
no, the efi partition is unmountable but I can read it with efibootmgr which provides: # efibootmgr BootCurrent: 0002(...)
I guess efibootmgr reads nvram, not efi partition jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On Thu, Mar 21, 2019 at 3:45 PM Patrick Shanahan <paka@opensuse.org> wrote:
no, the efi partition is unmountable but I can read it with efibootmgr which provides: # efibootmgr BootCurrent: 0002 Timeout: 0 seconds BootOrder: 2001,2003,2002 Boot0000* Realtek PXE Boot0001* Realtek PXE Boot0002* EFI USB Device (ASIX AX88772 USB Fast Ethernet Controller) Boot2001* EFI USB Device Boot2002* EFI DVD/CDROM Boot2003* EFI Network
This command invocation does not touch ESP at all. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Andrei Borzenkov <arvidjaar@gmail.com> [03-21-19 08:52]:
On Thu, Mar 21, 2019 at 3:45 PM Patrick Shanahan <paka@opensuse.org> wrote:
no, the efi partition is unmountable but I can read it with efibootmgr which provides: # efibootmgr BootCurrent: 0002 Timeout: 0 seconds BootOrder: 2001,2003,2002 Boot0000* Realtek PXE Boot0001* Realtek PXE Boot0002* EFI USB Device (ASIX AX88772 USB Fast Ethernet Controller) Boot2001* EFI USB Device Boot2002* EFI DVD/CDROM Boot2003* EFI Network
This command invocation does not touch ESP at all.
then how does one repopulate the EFI partition, in my case /dev/sda1 ? tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On Thu, Mar 21, 2019 at 3:58 PM Patrick Shanahan <paka@opensuse.org> wrote:
* Andrei Borzenkov <arvidjaar@gmail.com> [03-21-19 08:52]:
On Thu, Mar 21, 2019 at 3:45 PM Patrick Shanahan <paka@opensuse.org> wrote:
no, the efi partition is unmountable but I can read it with efibootmgr which provides: # efibootmgr BootCurrent: 0002 Timeout: 0 seconds BootOrder: 2001,2003,2002 Boot0000* Realtek PXE Boot0001* Realtek PXE Boot0002* EFI USB Device (ASIX AX88772 USB Fast Ethernet Controller) Boot2001* EFI USB Device Boot2002* EFI DVD/CDROM Boot2003* EFI Network
This command invocation does not touch ESP at all.
then how does one repopulate the EFI partition, in my case /dev/sda1 ?
I do not understand what "repopulate EFI partition" means, sorry. In any case, if this disk area is damaged you probably cannot "repopulate" it anyway. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Andrei Borzenkov <arvidjaar@gmail.com> [03-21-19 09:03]:
On Thu, Mar 21, 2019 at 3:58 PM Patrick Shanahan <paka@opensuse.org> wrote:
* Andrei Borzenkov <arvidjaar@gmail.com> [03-21-19 08:52]:
On Thu, Mar 21, 2019 at 3:45 PM Patrick Shanahan <paka@opensuse.org> wrote:
no, the efi partition is unmountable but I can read it with efibootmgr which provides: # efibootmgr BootCurrent: 0002 Timeout: 0 seconds BootOrder: 2001,2003,2002 Boot0000* Realtek PXE Boot0001* Realtek PXE Boot0002* EFI USB Device (ASIX AX88772 USB Fast Ethernet Controller) Boot2001* EFI USB Device Boot2002* EFI DVD/CDROM Boot2003* EFI Network
This command invocation does not touch ESP at all.
then how does one repopulate the EFI partition, in my case /dev/sda1 ?
I do not understand what "repopulate EFI partition" means, sorry. In any case, if this disk area is damaged you probably cannot "repopulate" it anyway.
actually referring to the replacement. how does one create the efi partition and put/write there what is needed (repopulate). I have built many systems but none with efi/esp. I am still using my last home-built box as my main workstation and it has been quite a few years. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
21.03.19 14:18 - Patrick Shanahan:
* Andrei Borzenkov <arvidjaar@gmail.com> [03-21-19 09:03]:
On Thu, Mar 21, 2019 at 3:58 PM Patrick Shanahan <paka@opensuse.org> wrote:
* Andrei Borzenkov <arvidjaar@gmail.com> [03-21-19 08:52]:
On Thu, Mar 21, 2019 at 3:45 PM Patrick Shanahan <paka@opensuse.org> wrote:
no, the efi partition is unmountable but I can read it with efibootmgr which provides: # efibootmgr BootCurrent: 0002 Timeout: 0 seconds BootOrder: 2001,2003,2002 Boot0000* Realtek PXE Boot0001* Realtek PXE Boot0002* EFI USB Device (ASIX AX88772 USB Fast Ethernet Controller) Boot2001* EFI USB Device Boot2002* EFI DVD/CDROM Boot2003* EFI Network
This command invocation does not touch ESP at all.
then how does one repopulate the EFI partition, in my case /dev/sda1 ?
I do not understand what "repopulate EFI partition" means, sorry. In any case, if this disk area is damaged you probably cannot "repopulate" it anyway.
actually referring to the replacement. how does one create the efi partition
You can use "gdisk" or "YaST" to create an EFS.
and put/write there what is needed (repopulate).
grub2-install will "repopulate" the EFI-partition (mounted at "/boot/efi", however one can tell grub2-install explicitly which partition to use) and the UEFIs NVRAM.
I have built many systems but none with efi/esp. I am still using my last home-built box as my main workstation and it has been quite a few years.
Regards Hagen -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Le 21/03/2019 à 18:34, Hagen Buliwyf a écrit :
grub2-install will "repopulate" the EFI-partition (mounted at "/boot/efi", however one can tell grub2-install explicitly which partition to use) and the UEFIs NVRAM.
notice, there can be more than one efi partition, so you can create a new one in a free place jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
21.03.2019 20:34, Hagen Buliwyf пишет:
grub2-install will "repopulate" the EFI-partition (mounted at "/boot/efi", however one can tell grub2-install explicitly which partition to use) and the UEFIs NVRAM.
It won't work if Secure Boot is enabled. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
21.03.2019 16:18, Patrick Shanahan пишет:
* Andrei Borzenkov <arvidjaar@gmail.com> [03-21-19 09:03]:
On Thu, Mar 21, 2019 at 3:58 PM Patrick Shanahan <paka@opensuse.org> wrote:
* Andrei Borzenkov <arvidjaar@gmail.com> [03-21-19 08:52]:
On Thu, Mar 21, 2019 at 3:45 PM Patrick Shanahan <paka@opensuse.org> wrote:
no, the efi partition is unmountable but I can read it with efibootmgr which provides: # efibootmgr BootCurrent: 0002 Timeout: 0 seconds BootOrder: 2001,2003,2002 Boot0000* Realtek PXE Boot0001* Realtek PXE Boot0002* EFI USB Device (ASIX AX88772 USB Fast Ethernet Controller) Boot2001* EFI USB Device Boot2002* EFI DVD/CDROM Boot2003* EFI Network
This command invocation does not touch ESP at all.
then how does one repopulate the EFI partition, in my case /dev/sda1 ?
I do not understand what "repopulate EFI partition" means, sorry. In any case, if this disk area is damaged you probably cannot "repopulate" it anyway.
actually referring to the replacement. how does one create the efi partition and put/write there what is needed (repopulate). I have built many systems but none with efi/esp. I am still using my last home-built box as my main workstation and it has been quite a few years.
You can create ESP using any tool you are familiar with - fdisk, gdisk, (g)parted, YaST. All offer mnemonic names for partitions so you do not need to remember EFI System Partition ID or GUID. Format it as FAT32, mount as /boot/efi. Then make sure you boot rescue medium in EFI mode, chroot, make sure you have all btrfs subvolumes mounted (mount -a -t btrfs) besides usual /sys, /dev, /proc and do "update-bootloader --reinit". Assuming bootloader configuration was correct previously, this should copy whatever files are necessary onto ESP and create NVRAM boot entry. You can also use shim-install or grub2-install directly. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Andrei Borzenkov <arvidjaar@gmail.com> [03-21-19 14:08]:
21.03.2019 16:18, Patrick Shanahan пишет:
* Andrei Borzenkov <arvidjaar@gmail.com> [03-21-19 09:03]:
On Thu, Mar 21, 2019 at 3:58 PM Patrick Shanahan <paka@opensuse.org> wrote:
[...]
actually referring to the replacement. how does one create the efi partition and put/write there what is needed (repopulate). I have built many systems but none with efi/esp. I am still using my last home-built box as my main workstation and it has been quite a few years.
You can create ESP using any tool you are familiar with - fdisk, gdisk, (g)parted, YaST. All offer mnemonic names for partitions so you do not need to remember EFI System Partition ID or GUID. Format it as FAT32, mount as /boot/efi. Then make sure you boot rescue medium in EFI mode, chroot, make sure you have all btrfs subvolumes mounted (mount -a -t btrfs) besides usual /sys, /dev, /proc and do "update-bootloader --reinit". Assuming bootloader configuration was correct previously, this should copy whatever files are necessary onto ESP and create NVRAM boot entry.
You can also use shim-install or grub2-install directly.
thanks all. I have a complete recovery from the failing/failed disk. the only bad sector happed to be on /dev/sda1, the EFI partition. used ddrescue to recreate the seven partitions (win10 included) to an attached usb3.1 drive using live leap 15.0 to boot replaced rust with ssd used dd to rewrite all partitions. deleted sda1 and recreated it. used above instructions from Andrei to chroot and then rewrite the EFI partiition, including shim-install and grub2-install last. provided bootable Tw system but no windows (not really a bad thing). booted manually into a win 10 install disk and recreated windows EFI boot entry in /dev/sda1 left me w/o Tw access. booted again with live leap 15.0 and created chroot. used efibootmgr to set Tw in front of windows. booted back successfully to Tw and used os-prober/grub2-mkconfig -o /boot/grub2/grub.cfg to successfully add window back to grub menu repeated both boots successfully. success. full recovery unless I see something I have not yet noticed. thanks all for your help, understanding and patience. was a learning experience I hope will not be repeated. but things happen :) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Le 24/03/2019 à 17:32, Patrick Shanahan a écrit :
left me w/o Tw access. booted again with live leap 15.0 and created chroot. used efibootmgr to set Tw in front of windows.
with uefi, most of the time, the efi firmware (was called BIOS) allows the choosing between OSs jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* jdd@dodin.org <jdd@dodin.org> [03-24-19 13:43]:
Le 24/03/2019 à 17:32, Patrick Shanahan a écrit :
left me w/o Tw access. booted again with live leap 15.0 and created chroot. used efibootmgr to set Tw in front of windows.
with uefi, most of the time, the efi firmware (was called BIOS) allows the choosing between OSs
how does one access that? keystroke combination, ??? I seem to remember being able to do that at one time but I am aging and my recollection appears to be effected greatly by the number of empty brown bottles lying about. :) tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Le 24/03/2019 à 18:48, Patrick Shanahan a écrit :
* jdd@dodin.org <jdd@dodin.org> [03-24-19 13:43]:
Le 24/03/2019 à 17:32, Patrick Shanahan a écrit :
left me w/o Tw access. booted again with live leap 15.0 and created chroot. used efibootmgr to set Tw in front of windows.
with uefi, most of the time, the efi firmware (was called BIOS) allows the choosing between OSs
how does one access that? keystroke combination, ??? I seem to remember being able to do that at one time but I am aging and my recollection appears to be effected greatly by the number of empty brown bottles lying about. :)
tks,
depends of the computer. I use to put a sticker near the relevant key. often Esc, or F2 to know, it's sometime nevessary to slide the finger on the Fx keys during early boot jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 24/03/2019 18.48, Patrick Shanahan wrote:
* jdd@dodin.org <jdd@dodin.org> [03-24-19 13:43]:
Le 24/03/2019 à 17:32, Patrick Shanahan a écrit :
left me w/o Tw access. booted again with live leap 15.0 and created chroot. used efibootmgr to set Tw in front of windows.
with uefi, most of the time, the efi firmware (was called BIOS) allows the choosing between OSs
how does one access that? keystroke combination, ??? I seem to remember being able to do that at one time but I am aging and my recollection appears to be effected greatly by the number of empty brown bottles lying about. :)
:-) Yes, a key pressed at the exact right time and speed. Manufacturers do not precisely want people to install several oses into /their/ machines. Or, being politically correct, I should say they do not want the boot to waste few seconds waiting for user input, but want boot to happen as fast as possible. Far easier to see the grub menu and choose. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Le 24/03/2019 à 20:04, Carlos E. R. a écrit :
Far easier to see the grub menu and choose.
after windows install, you can't. Going through BIOS is far more simple than boo(ting rescue disk and going with efibootmgr jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 24/03/2019 20.39, jdd@dodin.org wrote:
Le 24/03/2019 à 20:04, Carlos E. R. a écrit :
Far easier to see the grub menu and choose.
after windows install, you can't. Going through BIOS is far more simple than boo(ting rescue disk and going with efibootmgr
Sure. You go to BIOS once to make Linux the default again :-) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [03-24-19 15:49]:
On 24/03/2019 20.39, jdd@dodin.org wrote:
Le 24/03/2019 à 20:04, Carlos E. R. a écrit :
Far easier to see the grub menu and choose.
after windows install, you can't. Going through BIOS is far more simple than boo(ting rescue disk and going with efibootmgr
Sure. You go to BIOS once to make Linux the default again :-)
machine bios does not provide any means I can see to boot one installed system over another past secure vs legacy. if you refer bios to EFI, how do you access w/o using efibootmgr? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Le 24/03/2019 à 21:11, Patrick Shanahan a écrit :
* Carlos E. R. <robin.listas@telefonica.net> [03-24-19 15:49]:
On 24/03/2019 20.39, jdd@dodin.org wrote:
Le 24/03/2019 à 20:04, Carlos E. R. a écrit :
Far easier to see the grub menu and choose.
after windows install, you can't. Going through BIOS is far more simple than boo(ting rescue disk and going with efibootmgr
Sure. You go to BIOS once to make Linux the default again :-)
machine bios does not provide any means I can see to boot one installed system over another past secure vs legacy. if you refer bios to EFI, how do you access w/o using efibootmgr?
neither in boot bios menu? jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* jdd@dodin.org <jdd@dodin.org> [03-24-19 16:16]:
Le 24/03/2019 à 21:11, Patrick Shanahan a écrit :
* Carlos E. R. <robin.listas@telefonica.net> [03-24-19 15:49]:
On 24/03/2019 20.39, jdd@dodin.org wrote:
Le 24/03/2019 à 20:04, Carlos E. R. a écrit :
Far easier to see the grub menu and choose.
after windows install, you can't. Going through BIOS is far more simple than boo(ting rescue disk and going with efibootmgr
Sure. You go to BIOS once to make Linux the default again :-)
machine bios does not provide any means I can see to boot one installed system over another past secure vs legacy. if you refer bios to EFI, how do you access w/o using efibootmgr?
neither in boot bios menu?
now maybe I am being dense, but what is "boot bios menu"? in the machine bios I can set which "dev" boot before others such as optical/dvd/usb/hard-drive/... but not which operating system, unless I actually plug in a device high in order. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 24/03/2019 21.22, Patrick Shanahan wrote:
* jdd@dodin.org <jdd@dodin.org> [03-24-19 16:16]:
Le 24/03/2019 à 21:11, Patrick Shanahan a écrit :
* Carlos E. R. <robin.listas@telefonica.net> [03-24-19 15:49]:
On 24/03/2019 20.39, jdd@dodin.org wrote:
Le 24/03/2019 à 20:04, Carlos E. R. a écrit :
Far easier to see the grub menu and choose.
after windows install, you can't. Going through BIOS is far more simple than boo(ting rescue disk and going with efibootmgr
Sure. You go to BIOS once to make Linux the default again :-)
machine bios does not provide any means I can see to boot one installed system over another past secure vs legacy. if you refer bios to EFI, how do you access w/o using efibootmgr?
neither in boot bios menu?
now maybe I am being dense, but what is "boot bios menu"?
in the machine bios I can set which "dev" boot before others such as optical/dvd/usb/hard-drive/... but not which operating system, unless I actually plug in a device high in order.
Well, both my UEFI machines, when booting, can offer a "bios aka uefi boot menu". It is a menu powered by UEFI, before any operating system. In one it is a keypress that I never remember, maybe F9. No, F11, I have a sticker on the machine. Del gives me the UEFI menu. In another it is a hidden button behind a hole that has to be pressed with a paper clip (I had to google to find it). I may have to press more keys to reach it, but in the end I get a menu that offers more or less the same entries as "efibootmgr". And somewhere there may be a configuration of that menu. There should be, at least. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Patrick Shanahan composed on 2019-03-24 16:22 (UTC-0400):
jdd@dodin.org composed:
machine bios does not provide any means I can see to boot one installed system over another past secure vs legacy. if you refer bios to EFI, how do you access w/o using efibootmgr?
neither in boot bios menu?
now maybe I am being dense, but what is "boot bios menu"?
I don't know if there is a universal name for what he's described, but surely this is it: https://www.disk-image.com/faq-bootmenu.htm boot menu column.
in the machine bios I can set which "dev" boot before others such as> optical/dvd/usb/hard-drive/... but not which operating system, unless I actually plug in a device high in order.
On my newest Asus, a UEFI Kaby Lake purchased 9 months ago, @POST screen: F8 = "Please select boot device:" DEL = enter BIOS setup Boot -> UEFI Hard drive priorities # set default boot "device" On my newest Gigabyte, a UEFI Kaby Lake purchased 15 months ago, @POST screen: F12 = "Please select boot device:" DEL = enter BIOS setup BIOS -> Boot Option Priorities -> Boot Option #1 # set default boot device In both, "Please select boot device" really means select UEFI boot entry corresponding to the head of the BootOrder in efibootmgr output. These correspond to selection of boot "device" in pre-UEFI PCs, which on my Dells is also F12. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Felix Miata <mrmazda@earthlink.net> [03-24-19 18:59]:
Patrick Shanahan composed on 2019-03-24 16:22 (UTC-0400):
jdd@dodin.org composed:
machine bios does not provide any means I can see to boot one installed system over another past secure vs legacy. if you refer bios to EFI, how do you access w/o using efibootmgr?
neither in boot bios menu?
now maybe I am being dense, but what is "boot bios menu"?
I don't know if there is a universal name for what he's described, but surely this is it: https://www.disk-image.com/faq-bootmenu.htm boot menu column.
in the machine bios I can set which "dev" boot before others such as> optical/dvd/usb/hard-drive/... but not which operating system, unless I actually plug in a device high in order.
On my newest Asus, a UEFI Kaby Lake purchased 9 months ago, @POST screen:
F8 = "Please select boot device:"
DEL = enter BIOS setup Boot -> UEFI Hard drive priorities # set default boot "device"
On my newest Gigabyte, a UEFI Kaby Lake purchased 15 months ago, @POST screen:
F12 = "Please select boot device:"
DEL = enter BIOS setup BIOS -> Boot Option Priorities -> Boot Option #1 # set default boot device
In both, "Please select boot device" really means select UEFI boot entry corresponding to the head of the BootOrder in efibootmgr output.
These correspond to selection of boot "device" in pre-UEFI PCs, which on my Dells is also F12.
cannot attempt atm, doing partition backup, but... f12 at boot presents "device" order menu, usb/optical/hdd/pxe. I recall no options for an operating system or UEFI menu entry for a particular system. my toshiba satellite is: Machine: Type: Laptop System: TOSHIBA product: Satellite S55-C v: PSPTNU-00E00M serial: XF169121C Mobo: FF50 model: 06F2 v: Type2 - Board Version serial: QC0B0Q8F4102846 UEFI: INSYDE v: 5.10 date: 09/11/2015 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 21/03/2019 13.58, Patrick Shanahan wrote:
* Andrei Borzenkov <> [03-21-19 08:52]:
On Thu, Mar 21, 2019 at 3:45 PM Patrick Shanahan <paka@opensuse.org> wrote:
no, the efi partition is unmountable but I can read it with efibootmgr which provides: # efibootmgr BootCurrent: 0002 Timeout: 0 seconds BootOrder: 2001,2003,2002 Boot0000* Realtek PXE Boot0001* Realtek PXE Boot0002* EFI USB Device (ASIX AX88772 USB Fast Ethernet Controller) Boot2001* EFI USB Device Boot2002* EFI DVD/CDROM Boot2003* EFI Network
This command invocation does not touch ESP at all.
then how does one repopulate the EFI partition, in my case /dev/sda1 ?
Just copy with dd?rescue the partition, as you are doing already :-) Now, if that fails, then yast boot module. Now if you ask about the table above, which lives in nvram or flash memory (I don't know which), then I'm unsure. Probably the efibootmgr can do it. Or the bios config menu. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [03-21-19 13:47]:
On 21/03/2019 13.58, Patrick Shanahan wrote:
* Andrei Borzenkov <> [03-21-19 08:52]:
On Thu, Mar 21, 2019 at 3:45 PM Patrick Shanahan <paka@opensuse.org> wrote:
no, the efi partition is unmountable but I can read it with efibootmgr which provides: # efibootmgr BootCurrent: 0002 Timeout: 0 seconds BootOrder: 2001,2003,2002 Boot0000* Realtek PXE Boot0001* Realtek PXE Boot0002* EFI USB Device (ASIX AX88772 USB Fast Ethernet Controller) Boot2001* EFI USB Device Boot2002* EFI DVD/CDROM Boot2003* EFI Network
This command invocation does not touch ESP at all.
then how does one repopulate the EFI partition, in my case /dev/sda1 ?
Just copy with dd?rescue the partition, as you are doing already :-) Now, if that fails, then yast boot module.
if that fails, the system does not boot and no yast ... ???
Now if you ask about the table above, which lives in nvram or flash memory (I don't know which), then I'm unsure. Probably the efibootmgr can do it. Or the bios config menu.
not there, yet tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 21/03/2019 21.23, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [03-21-19 13:47]:
On 21/03/2019 13.58, Patrick Shanahan wrote:
* Andrei Borzenkov <> [03-21-19 08:52]:
On Thu, Mar 21, 2019 at 3:45 PM Patrick Shanahan <paka@opensuse.org> wrote:
no, the efi partition is unmountable but I can read it with efibootmgr which provides: # efibootmgr BootCurrent: 0002 Timeout: 0 seconds BootOrder: 2001,2003,2002 Boot0000* Realtek PXE Boot0001* Realtek PXE Boot0002* EFI USB Device (ASIX AX88772 USB Fast Ethernet Controller) Boot2001* EFI USB Device Boot2002* EFI DVD/CDROM Boot2003* EFI Network
This command invocation does not touch ESP at all.
then how does one repopulate the EFI partition, in my case /dev/sda1 ?
Just copy with dd?rescue the partition, as you are doing already :-) Now, if that fails, then yast boot module.
if that fails, the system does not boot and no yast ... ???
Ah. Boot from rescue image, then mount the old partitions /somewhere, chroot to that, run yast there (text mode probably). Before doing the actual chroot you need to mount bind /proc, /sys, /dev, etc: mount --bind /proc /otros/test_a/proc mount --bind /sys /otros/test_a/sys mount --bind /dev /otros/test_a/dev -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [03-22-19 07:21]:
On 21/03/2019 21.23, Patrick Shanahan wrote: [...]
if that fails, the system does not boot and no yast ... ???
Ah.
Boot from rescue image, then mount the old partitions /somewhere, chroot to that, run yast there (text mode probably).
Before doing the actual chroot you need to mount bind /proc, /sys, /dev, etc:
mount --bind /proc /otros/test_a/proc mount --bind /sys /otros/test_a/sys mount --bind /dev /otros/test_a/dev
proc,sys,dev from the machine system, not the rescue image? and then, tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 22/03/2019 17.40, Patrick Shanahan wrote:
* Carlos E. R. <> [03-22-19 07:21]:
On 21/03/2019 21.23, Patrick Shanahan wrote: [...]
if that fails, the system does not boot and no yast ... ???
Ah.
Boot from rescue image, then mount the old partitions /somewhere, chroot to that, run yast there (text mode probably).
Before doing the actual chroot you need to mount bind /proc, /sys, /dev, etc:
mount --bind /proc /otros/test_a/proc mount --bind /sys /otros/test_a/sys mount --bind /dev /otros/test_a/dev
*** running system ********** system under repair
proc,sys,dev from the machine system, not the rescue image?
The "broken system" gets to see the rescue image directories as if they were its own, because they being virtual filesystem they will have nothing there. They will not match exactly what it expects to see, but usually it works. There are files that might confuse the chrooted system, like mtab or network settings. In that case you will see messages about some error or other. This trick can be used for other things, like running zypper dup on another partition that is not the actually running one :-)
and then,
tks,
-- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [03-22-19 14:33]:
On 22/03/2019 17.40, Patrick Shanahan wrote:
* Carlos E. R. <> [03-22-19 07:21]:
On 21/03/2019 21.23, Patrick Shanahan wrote: [...]
if that fails, the system does not boot and no yast ... ???
Ah.
Boot from rescue image, then mount the old partitions /somewhere, chroot to that, run yast there (text mode probably).
Before doing the actual chroot you need to mount bind /proc, /sys, /dev, etc:
mount --bind /proc /otros/test_a/proc mount --bind /sys /otros/test_a/sys mount --bind /dev /otros/test_a/dev
*** running system ********** system under repair
proc,sys,dev from the machine system, not the rescue image?
The "broken system" gets to see the rescue image directories as if they were its own, because they being virtual filesystem they will have nothing there. They will not match exactly what it expects to see, but usually it works.
There are files that might confuse the chrooted system, like mtab or network settings. In that case you will see messages about some error or other.
This trick can be used for other things, like running zypper dup on another partition that is not the actually running one :-)
ok, laptop will now boot but errs with: Boot failure : a proper digital signature was not found. One of the files on the selected boot device was rejected by the Secure Boot Feature. google has lots of answers but none that appear prudent. I don't want to disable secure boot as I want to restore the win10 partition(s). tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Patrick Shanahan <paka@opensuse.org> [03-22-19 15:12]:
* Carlos E. R. <robin.listas@telefonica.net> [03-22-19 14:33]:
On 22/03/2019 17.40, Patrick Shanahan wrote:
* Carlos E. R. <> [03-22-19 07:21]:
On 21/03/2019 21.23, Patrick Shanahan wrote: [...]
if that fails, the system does not boot and no yast ... ???
Ah.
Boot from rescue image, then mount the old partitions /somewhere, chroot to that, run yast there (text mode probably).
Before doing the actual chroot you need to mount bind /proc, /sys, /dev, etc:
mount --bind /proc /otros/test_a/proc mount --bind /sys /otros/test_a/sys mount --bind /dev /otros/test_a/dev
*** running system ********** system under repair
proc,sys,dev from the machine system, not the rescue image?
The "broken system" gets to see the rescue image directories as if they were its own, because they being virtual filesystem they will have nothing there. They will not match exactly what it expects to see, but usually it works.
There are files that might confuse the chrooted system, like mtab or network settings. In that case you will see messages about some error or other.
This trick can be used for other things, like running zypper dup on another partition that is not the actually running one :-)
ok, laptop will now boot but errs with: Boot failure : a proper digital signature was not found. One of the files on the selected boot device was rejected by the Secure Boot Feature.
google has lots of answers but none that appear prudent. I don't want to disable secure boot as I want to restore the win10 partition(s).
ps: I deleted the old EFI partition created a new one and ran grub-install from the chroot system. the grub-install reported success. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 22/03/2019 20.15, Patrick Shanahan wrote:
* Patrick Shanahan <paka@opensuse.org> [03-22-19 15:12]:
* Carlos E. R. <robin.listas@telefonica.net> [03-22-19 14:33]:
On 22/03/2019 17.40, Patrick Shanahan wrote:
* Carlos E. R. <> [03-22-19 07:21]:
On 21/03/2019 21.23, Patrick Shanahan wrote: [...]
if that fails, the system does not boot and no yast ... ???
Ah.
Boot from rescue image, then mount the old partitions /somewhere, chroot to that, run yast there (text mode probably).
Before doing the actual chroot you need to mount bind /proc, /sys, /dev, etc:
mount --bind /proc /otros/test_a/proc mount --bind /sys /otros/test_a/sys mount --bind /dev /otros/test_a/dev
*** running system ********** system under repair
proc,sys,dev from the machine system, not the rescue image?
The "broken system" gets to see the rescue image directories as if they were its own, because they being virtual filesystem they will have nothing there. They will not match exactly what it expects to see, but usually it works.
There are files that might confuse the chrooted system, like mtab or network settings. In that case you will see messages about some error or other.
This trick can be used for other things, like running zypper dup on another partition that is not the actually running one :-)
ok, laptop will now boot but errs with: Boot failure : a proper digital signature was not found. One of the files on the selected boot device was rejected by the Secure Boot Feature.
google has lots of answers but none that appear prudent. I don't want to disable secure boot as I want to restore the win10 partition(s).
ps: I deleted the old EFI partition created a new one and ran grub-install from the chroot system. the grub-install reported success.
EFI was not grub install, was something else... I'll search. [...] Andrei Borzenkov: AB> You can create ESP using any tool you are familiar with - fdisk, gdisk, AB> (g)parted, YaST. All offer mnemonic names for partitions so you do not AB> need to remember EFI System Partition ID or GUID. Format it as FAT32, AB> mount as /boot/efi. Then make sure you boot rescue medium in EFI mode, AB> chroot, make sure you have all btrfs subvolumes mounted (mount -a -t AB> btrfs) besides usual /sys, /dev, /proc and do "update-bootloader AB> --reinit". Assuming bootloader configuration was correct previously, AB> this should copy whatever files are necessary onto ESP and create NVRAM AB> boot entry. AB> AB> You can also use shim-install or grub2-install directly. 21.03.2019 20:34, Hagen Buliwyf пишет: HB>> HB>> grub2-install will "repopulate" the EFI-partition (mounted at HB>> "/boot/efi", however one can tell grub2-install explicitly which HB>> partition to use) and the UEFIs NVRAM. HB>> AB> It won't work if Secure Boot is enabled. That's precisely your problem... -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-03-21 06:44 AM, Patrick Shanahan wrote:
I began yesterday making a full disk copy that is just now 70% thru the first pass, gnu_ddrescue, showing 18 read errors in a 1Tb drive. can I not finish this and then write 00's to the efi partition, /dev/sda1, if it is not recovered and then use efibootmgr to write it anew instead of starting over?
tks, Are you thinking you will be able to do this on the existing drive? You will not; it is giving a non-recoverable, non-relocatable read error somewhere in the EFI partition. I do not think there is any chance you would be able to successfully write to that sector, and even if you could, you would not be able to read from it in the future anyway.
You will have to create a new one on a new drive, as described by others, and restore the data drives with the backup you are making. -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Darryl Gregorash <strange.charmed.antiquark@gmail.com> [03-21-19 14:41]:
On 2019-03-21 06:44 AM, Patrick Shanahan wrote:
I began yesterday making a full disk copy that is just now 70% thru the first pass, gnu_ddrescue, showing 18 read errors in a 1Tb drive. can I not finish this and then write 00's to the efi partition, /dev/sda1, if it is not recovered and then use efibootmgr to write it anew instead of starting over?
tks, Are you thinking you will be able to do this on the existing drive? You will not; it is giving a non-recoverable, non-relocatable read error somewhere in the EFI partition. I do not think there is any chance you would be able to successfully write to that sector, and even if you could, you would not be able to read from it in the future anyway.
no, on a new drive
You will have to create a new one on a new drive, as described by others, and restore the data drives with the backup you are making.
tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
participants (7)
-
Andrei Borzenkov -
Carlos E. R. -
Darryl Gregorash -
Felix Miata -
Hagen Buliwyf -
jdd＠dodin.org -
Patrick Shanahan