Strona 3 z 4
Re: GRUB nie widzi dysku po aktualizacji jądra 5.10.0-8-amd64
: 04 października 2021, 11:14
autor: fnmirk
Przedstaw jeszcze wyniki:
Kod: Zaznacz cały
cat /etc/fstab
blkid
ls -la /etc/grub.d/
ls -la /etc/default/grub.d/
cat /etc/default/grub
Re: GRUB nie widzi dysku po aktualizacji jądra 5.10.0-8-amd64
: 04 października 2021, 11:45
autor: Tarna
Kod: Zaznacz cały
root@MIR-LAP:/home/tarna# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda2 during installation
UUID=76ad448d-b574-4398-84fc-10c22654f8e0 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p2 during installation
UUID=528F-9706 /boot/efi vfat umask=0077 0 1
# /home was on /dev/sda3 during installation
UUID=e8e81abe-9258-49ba-a5f8-421674b391f7 /home ext4 defaults 0 2
# swap was on /dev/nvme0n1p7 during installation
UUID=894208a1-9001-461e-aad6-b9b3461d07a3 none swap sw 0 0
Kod: Zaznacz cały
root@MIR-LAP:/home/tarna# /usr/sbin/blkid
/dev/nvme0n1p1: LABEL="Odzyskiwanie" BLOCK_SIZE="512" UUID="FA868F16868ED295" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="fa56802f-8a9d-4960-bb8f-7432c707e2b6"
/dev/nvme0n1p2: UUID="528F-9706" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="3c2b4095-1fd1-4797-8052-b24256f5e4f6"
/dev/nvme0n1p3: PARTLABEL="Microsoft reserved partition" PARTUUID="5c25ef46-3ffa-4652-a2d6-1c7b5421df0b"
/dev/nvme0n1p4: BLOCK_SIZE="512" UUID="B8A4893EA489005C" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="4a63f6dc-6720-480e-8c0f-66d0870266ed"
/dev/nvme0n1p5: BLOCK_SIZE="512" UUID="429862539862458F" TYPE="ntfs" PARTUUID="7c8577e7-9af5-429c-8eef-000b59b1e88f"
/dev/nvme0n1p6: BLOCK_SIZE="512" UUID="26C08548C0851EE5" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="274705fe-91a0-4d5e-aef2-1d443850139e"
/dev/nvme0n1p7: UUID="894208a1-9001-461e-aad6-b9b3461d07a3" TYPE="swap" PARTUUID="803206e3-f146-4c6c-a0e4-372578ed9b73"
/dev/nvme0n1p8: LABEL="DELLSUPPORT" BLOCK_SIZE="512" UUID="FE2296AE22966C01" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="54ccc38a-4121-49e9-db8d-f0c80acf9cd6"
/dev/sda1: PARTUUID="50b9ef63-b29c-4b26-acb4-f771139ef469"
/dev/sda2: UUID="76ad448d-b574-4398-84fc-10c22654f8e0" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="e36a4b1e-ed28-40c3-92ec-832f0c2be5f8"
/dev/sda3: UUID="e8e81abe-9258-49ba-a5f8-421674b391f7" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="115c4557-b246-4579-ba64-3f8c869387cd"
Kod: Zaznacz cały
root@MIR-LAP:/home/tarna# ls -la /etc/grub.d/
razem 96
drwxr-xr-x 2 root root 4096 10-01 07:48 .
drwxr-xr-x 134 root root 12288 10-04 11:20 ..
-rwxr-xr-x 1 root root 10046 07-11 01:37 00_header
-rwxr-xr-x 1 root root 6260 07-11 01:37 05_debian_theme
-rwxr-xr-x 1 root root 13664 07-11 01:37 10_linux
-rwxr-xr-x 1 root root 13726 07-11 01:37 20_linux_xen
-rwxr-xr-x 1 root root 12059 2020-07-30 30_os-prober
-rwxr-xr-x 1 root root 1416 07-11 01:37 30_uefi-firmware
-rwxr-xr-x 1 root root 214 2020-07-30 40_custom
-rwxr-xr-x 1 root root 216 2020-07-30 41_custom
-rw-r--r-- 1 root root 483 2020-07-30 README
Kod: Zaznacz cały
root@MIR-LAP:/home/tarna# ls -la /etc/default/grub.d/
razem 12
drwxr-xr-x 2 root root 4096 10-01 07:48 .
drwxr-xr-x 3 root root 4096 10-01 07:48 ..
-rw-r--r-- 1 root root 274 2020-07-30 init-select.cfg
Kod: Zaznacz cały
root@MIR-LAP:/home/tarna# cat /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
Re: GRUB nie widzi dysku po aktualizacji jądra 5.10.0-8-amd64
: 04 października 2021, 17:09
autor: fnmirk
Re: GRUB nie widzi dysku po aktualizacji jądra 5.10.0-8-amd64
: 06 października 2021, 19:59
autor: Tarna
Zrobiłem eksperyment tzn. zainstalowałem Windows 11 i Debiana 11 całkowicie przebudowując partycje (efi poszło na drugi dysk) i nic to nie pomogło. Najbardziej bym stawiał na coś z GRUB.
Re: GRUB nie widzi dysku po aktualizacji jądra 5.10.0-8-amd64
: 06 października 2021, 21:49
autor: fnmirk
Czy próbowałeś samego Debiana zainstalować?
Re: GRUB nie widzi dysku po aktualizacji jądra 5.10.0-8-amd64
: 07 października 2021, 05:23
autor: Tarna
Nie. Bardziej odpuszczę i poczekam na aktualizacje pakietów. Ewidentne widać, że coś nie dogaduje się z tą konfiguracja 2 inne komputery chodzą bez zarzutu, z czego jeden tez z Windows.
Re: GRUB nie widzi dysku po aktualizacji jądra 5.10.0-8-amd64
: 07 października 2021, 10:29
autor: fnmirk
Spróbujmy tego rozwiązania z forum angielskojęzycznego Debiana.
Zainstaluj:
Przedstaw wynik polecenia:
Re: GRUB nie widzi dysku po aktualizacji jądra 5.10.0-8-amd64
: 07 października 2021, 10:52
autor: Tarna
Tym razem będziesz musiał bardziej mnie poprowadzić
tzn. nie mam podlinkowanych ścieżek (i za bardzo nie wiem jak to zrobić - wiem, że od któregoś wydania już zmienne do su nie są automatycznie przypisywane) zatem otrzymuję komunikat:
Kod: Zaznacz cały
root@mirek:/home/mir# /usr/sbin/bootinfoscript
Boot Info Script 0.78 [09 October 2019]
"blkid" could not be found.
"fdisk" could not be found.
"filefrag" could not be found.
"losetup" could not be found.
Please install the missing program(s) and run Boot Info Script again.
root@mirek:/home/mir# /usr/sbin/blkid
/dev/nvme0n1p1: UUID="201B-CF8F" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="1f641a3d-cf0d-4bf0-a31a-6577c30eeb02"
/dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="983ac963-55b3-441b-bb6e-c6fe05ef8f41"
/dev/nvme0n1p3: BLOCK_SIZE="512" UUID="BADE1CC8DE1C7EB7" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="9ca645f5-7b3e-409b-adf5-1dbc9de81bff"
/dev/nvme0n1p4: UUID="3ee4e107-165a-4b1b-91c1-22dc4aef2f13" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="/" PARTUUID="69e9447e-5b3e-4abc-8a1f-dc5e8a35b7d9"
/dev/nvme0n1p5: BLOCK_SIZE="512" UUID="A6A069F3A069C9FF" TYPE="ntfs" PARTUUID="050c00f7-5af7-48c7-ac97-f81ef8200a86"
/dev/nvme0n1p6: UUID="54d712b4-d9b6-4eef-bf15-b62733036fad" TYPE="swap" PARTUUID="d61df083-ae26-4c42-bc3c-219d7854b1ca"
/dev/sda1: UUID="5a82ef3b-d381-467c-abda-38df9e5699c4" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="68d6c079-b9b3-4904-bb4d-2195509f27a4"
/dev/sda2: LABEL="Dane" BLOCK_SIZE="512" UUID="D48A1FF08A1FCE3C" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="3abd1608-b3af-4493-94f6-5bd7ec0d9863"
root@mirek:/home/mir# /usr/sbin/fdisk
fdisk: błędna składnia
'fdisk --help' wyświetli więcej informacji.
root@mirek:/home/mir# /usr/sbin/filefrag
Usage: /usr/sbin/filefrag [-b{blocksize}[KMG]] [-BeEksvxX] file ...
root@mirek:/home/mir# /usr/sbin/losetup
root@mirek:/home/mir#
Re: GRUB nie widzi dysku po aktualizacji jądra 5.10.0-8-amd64
: 07 października 2021, 11:00
autor: fnmirk
Musisz użyć:
W Debian-referens jest o tym.
Re: GRUB nie widzi dysku po aktualizacji jądra 5.10.0-8-amd64
: 07 października 2021, 11:07
autor: Tarna
Dziękuję:
Kod: Zaznacz cały
Boot Info Script 0.78 [09 October 2019]
============================= Boot Info Summary: ===============================
=> No boot loader is installed in the MBR of /dev/sda.
sda1: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:
sda2: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows 8/2012: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
============================ Drive/Partition Info: =============================
Drive: sda _____________________________________________________________________
Dysk /dev/sda: 465,76 GiB, bajtów: 500107862016, sektorów: 976773168
Model dysku: CT500MX500SSD1
Jednostki: sektorów, czyli 1 * 512 = 512 bajtów
Rozmiar sektora (logiczny/fizyczny) w bajtach: 512 / 512
Rozmiar we/wy (minimalny/optymalny) w bajtach: 512 / 512
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 1 976,773,167 976,773,167 ee GPT
GUID Partition Table detected.
Partition Attrs Start Sector End Sector # of Sectors System
/dev/sda1 2,048 488,384,511 488,382,464 Data partition (Linux)
/dev/sda2 488,384,512 976,771,071 488,386,560 Data partition (Windows/Linux)
Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/nvme0n1p1 201B-CF8F vfat
/dev/nvme0n1p2
/dev/nvme0n1p3 BADE1CC8DE1C7EB7 ntfs
/dev/nvme0n1p4 3ee4e107-165a-4b1b-91c1-22dc4aef2f13 ext4
/dev/nvme0n1p5 A6A069F3A069C9FF ntfs
/dev/nvme0n1p6 54d712b4-d9b6-4eef-bf15-b62733036fad swap
/dev/sda1 5a82ef3b-d381-467c-abda-38df9e5699c4 ext4
/dev/sda2 D48A1FF08A1FCE3C ntfs Dane
========================= "ls -l /dev/disk/by-id" output: ======================
razem 0
lrwxrwxrwx 1 root root 9 10-07 07:19 ata-CT500MX500SSD1_2003E282D83B -> ../../sda
lrwxrwxrwx 1 root root 10 10-07 07:19 ata-CT500MX500SSD1_2003E282D83B-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 10-07 07:19 ata-CT500MX500SSD1_2003E282D83B-part2 -> ../../sda2
lrwxrwxrwx 1 root root 13 10-07 07:19 nvme-BC511_NVMe_SK_hynix_256GB_SS9BN62141090BF5E -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 10-07 07:19 nvme-BC511_NVMe_SK_hynix_256GB_SS9BN62141090BF5E-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 10-07 07:19 nvme-BC511_NVMe_SK_hynix_256GB_SS9BN62141090BF5E-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 10-07 07:19 nvme-BC511_NVMe_SK_hynix_256GB_SS9BN62141090BF5E-part3 -> ../../nvme0n1p3
lrwxrwxrwx 1 root root 15 10-07 07:19 nvme-BC511_NVMe_SK_hynix_256GB_SS9BN62141090BF5E-part4 -> ../../nvme0n1p4
lrwxrwxrwx 1 root root 15 10-07 07:19 nvme-BC511_NVMe_SK_hynix_256GB_SS9BN62141090BF5E-part5 -> ../../nvme0n1p5
lrwxrwxrwx 1 root root 15 10-07 07:19 nvme-BC511_NVMe_SK_hynix_256GB_SS9BN62141090BF5E-part6 -> ../../nvme0n1p6
lrwxrwxrwx 1 root root 13 10-07 07:19 nvme-nvme.1c5c-535339424e363231343130393042463545-4243353131204e564d6520534b2068796e6978203235364742-00000001 -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 10-07 07:19 nvme-nvme.1c5c-535339424e363231343130393042463545-4243353131204e564d6520534b2068796e6978203235364742-00000001-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 10-07 07:19 nvme-nvme.1c5c-535339424e363231343130393042463545-4243353131204e564d6520534b2068796e6978203235364742-00000001-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 10-07 07:19 nvme-nvme.1c5c-535339424e363231343130393042463545-4243353131204e564d6520534b2068796e6978203235364742-00000001-part3 -> ../../nvme0n1p3
lrwxrwxrwx 1 root root 15 10-07 07:19 nvme-nvme.1c5c-535339424e363231343130393042463545-4243353131204e564d6520534b2068796e6978203235364742-00000001-part4 -> ../../nvme0n1p4
lrwxrwxrwx 1 root root 15 10-07 07:19 nvme-nvme.1c5c-535339424e363231343130393042463545-4243353131204e564d6520534b2068796e6978203235364742-00000001-part5 -> ../../nvme0n1p5
lrwxrwxrwx 1 root root 15 10-07 07:19 nvme-nvme.1c5c-535339424e363231343130393042463545-4243353131204e564d6520534b2068796e6978203235364742-00000001-part6 -> ../../nvme0n1p6
lrwxrwxrwx 1 root root 9 10-07 07:19 wwn-0x500a0751e282d83b -> ../../sda
lrwxrwxrwx 1 root root 10 10-07 07:19 wwn-0x500a0751e282d83b-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 10-07 07:19 wwn-0x500a0751e282d83b-part2 -> ../../sda2
================================ Mount points: =================================
Device Mount_Point Type Options
/dev/nvme0n1p1 /boot/efi vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
/dev/nvme0n1p4 / ext4 (rw,relatime,errors=remount-ro)
/dev/sda1 /home ext4 (rw,relatime)