[Solved] Windows partition not accessible after upgrade  [Solved]

Help for Current Versions of MX
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Forum rules
Post Reply
Message
Author
Hocksul
Posts: 65
Joined: Wed Jan 13, 2021 6:01 am

[Solved] Windows partition not accessible after upgrade

#1 Post by Hocksul »

Code: Select all

System:    Kernel: 6.1.0-22-amd64 [6.1.94-1] x86_64 bits: 64 compiler: gcc v: 12.2.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-22-amd64 root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.18.1 tk: Gtk 3.24.36 info: xfce4-panel wm: xfwm 4.18.0 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-23.3_x64 Libretto September 18  2022 
           base: Debian GNU/Linux 12 (bookworm) 
Machine:   Type: Desktop Mobo: N/A model: N/A serial: <filter> UEFI: American Megatrends v: 5.13 
           date: 06/10/2022 
Battery:   Device-1: hidpp_battery_0 model: Logitech M705 serial: <filter> charge: 10% 
           rechargeable: yes status: Discharging 
           Device-2: hidpp_battery_1 model: Logitech MK700 serial: <filter> 
           charge: 70% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Info: Quad Core model: Intel Core i7-8559U bits: 64 type: MT MCP arch: Kaby Lake 
           note: check family: 6 model-id: 8E (142) stepping: A (10) microcode: F4 cache: 
           L2: 8 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 43198 
           Speed: 2901 MHz min/max: 400/4500 MHz Core speeds (MHz): 1: 2902 2: 2961 3: 4295 
           4: 2973 5: 2901 6: 3691 7: 4115 8: 3024 
           Vulnerabilities: Type: gather_data_sampling mitigation: Microcode 
           Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable 
           Type: reg_file_data_sampling status: Not affected 
           Type: retbleed mitigation: IBRS 
           Type: spec_rstack_overflow status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: conditional; RSB filling; 
           PBRSB-eIBRS: Not affected; BHI: Not affected 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel CoffeeLake-U GT3e [Iris Plus Graphics 655] driver: i915 v: kernel 
           bus-ID: 00:02.0 chip-ID: 8086:3ea5 class-ID: 0300 
           Display: x11 server: X.Org 1.21.1.7 compositor: xfwm4 v: 4.18.0 driver: 
           loaded: modesetting unloaded: fbdev,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.7x15.0") 
           s-diag: 777mm (30.6") 
           Monitor-1: HDMI-2 res: 2560x1440 hz: 60 dpi: 109 size: 598x336mm (23.5x13.2") 
           diag: 686mm (27") 
           OpenGL: renderer: Mesa Intel Iris Plus Graphics 655 (CFL GT3) v: 4.6 Mesa 22.3.6 
           direct render: Yes 
Audio:     Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel v: kernel 
           alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:9dc8 
           class-ID: 0403 
           Device-2: Logitech Logitech Stereo H650e type: USB 
           driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-2.3:6 chip-ID: 046d:0a46 
           class-ID: 0300 serial: <filter> 
           Sound Server-1: ALSA v: k6.1.0-22-amd64 running: yes 
           Sound Server-2: PulseAudio v: 16.1 running: yes 
Network:   Device-1: Intel Ethernet I219-V driver: e1000e v: kernel port: efa0 bus-ID: 00:1f.6 
           chip-ID: 8086:15be class-ID: 0200 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Wireless 3165 driver: iwlwifi v: kernel modules: wl port: efa0 
           bus-ID: 01:00.0 chip-ID: 8086:3165 class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 
           bus-ID: 1-9:5 chip-ID: 8087:0a2a class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2 
           sub-v: 1000 hci-v: 4.2 rev: 1000 
           Info: acl-mtu: 1021:5 sco-mtu: 96:6 link-policy: rswitch hold sniff 
           link-mode: peripheral accept service-classes: rendering, capturing, audio, telephony 
Drives:    Local Storage: total: 491.26 GiB used: 225.21 GiB (45.8%) 
           ID-1: /dev/sda maj-min: 8:0 vendor: Hoodisk model: SSD size: 476.94 GiB block-size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: T1.3 
           scheme: GPT 
           SMART Message: Unknown smartctl error. Unable to generate data. 
           ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: Cruzer Fit 
           size: 14.32 GiB block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> 
           rev: 1.00 scheme: MBR 
           SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
Partition: ID-1: / raw-size: 244.14 GiB size: 239.25 GiB (98.00%) used: 127.36 GiB (53.2%) 
           fs: ext4 block-size: 4096 B dev: /dev/sda4 maj-min: 8:4 
           ID-2: /boot/efi raw-size: 200 MiB size: 196 MiB (98.00%) used: 31.2 MiB (15.9%) 
           fs: vfat block-size: 512 B dev: /dev/sda1 maj-min: 8:1 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 19.53 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/sda5 maj-min: 8:5 
Sensors:   System Temperatures: cpu: 35.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     Packages: 2742 note: see --pkg apt: 2726 lib: 1200 flatpak: 16 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/azure-cli.list 
           1: deb [arch=amd64 signed-by=/etc/apt/keyrings/microsoft.gpg] https://packages.microsoft.com/repos/azure-cli/ bookworm main
           Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list 
           1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
           2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
           1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
           Active apt repos in: /etc/apt/sources.list.d/microsoft-edge.list 
           1: deb [arch=amd64] https://packages.microsoft.com/repos/edge/ stable main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://ftp.acc.umu.se/mirror/mxlinux.org/packages/mx/repo/ bookworm main non-free
           Active apt repos in: /etc/apt/sources.list.d/oguzhaninan-ubuntu-stacer-kinetic.list 
           1: deb http://ppa.launchpad.net/oguzhaninan/stacer/ubuntu kinetic main
           2: deb http://ppa.launchpad.net/oguzhaninan/stacer/ubuntu kinetic main
           3: deb-src http://ppa.launchpad.net/oguzhaninan/stacer/ubuntu kinetic main
           Active apt repos in: /etc/apt/sources.list.d/signal-xenial-added-by-mxpi.list 
           1: deb [arch=amd64] https://updates.signal.org/desktop/apt xenial main
           Active apt repos in: /etc/apt/sources.list.d/spotify.list 
           1: deb http://repository.spotify.com stable non-free
           Active apt repos in: /etc/apt/sources.list.d/teams.list 
           1: deb [arch=amd64] https://packages.microsoft.com/repos/ms-teams stable main
           Active apt repos in: /etc/apt/sources.list.d/vscode.list 
           1: deb [arch=amd64] https://packages.microsoft.com/repos/vscode stable main
Info:      Processes: 267 Uptime: 5h 51m wakeups: 12 Memory: 31.24 GiB used: 2.92 GiB (9.3%) 
           Init: SysVinit v: 3.06 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 12.2.0 
           alt: 10/12 Client: shell wrapper v: 5.2.15-release inxi: 3.3.06 
Boot Mode: UEFI
I had a dual boot system (Windows + Mx-Linux). I upgraded from MX-21 to MX-23 based on the instructions given here.

Everything went smoothly, but after the upgrade, there is no option to boot into Windows after restarting the system. The Windows partition is however there and is readily visible from the file manager Thunar.

How can I get the options to boot into either OS (linux or windows) at the start up again?

TIA
Last edited by Hocksul on Thu Jul 11, 2024 8:06 am, edited 1 time in total.
Top
User avatar
j2mcgreg
Global Moderator
Posts: 6610
Joined: Tue Oct 23, 2007 12:04 pm

Re: Windows partition not accessible after upgrade

#2 Post by j2mcgreg »

I'd reinstall Grub using the Boot Repair utility in MX Tools.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.
Top
User avatar
Eadwine Rose
Administrator
Posts: 14463
Joined: Wed Jul 12, 2006 2:10 am

Re: Windows partition not accessible after upgrade

#3 Post by Eadwine Rose »

sudo update-grub in the terminal won't work?
MX-23.6_x64 July 31 2023 * 6.1.0-34amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.216.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Top
Hocksul
Posts: 65
Joined: Wed Jan 13, 2021 6:01 am

Re: Windows partition not accessible after upgrade

#4 Post by Hocksul »

Thanks for the quick response!
Just to be on the safe side: should I choose the Boot Method installed on MBR, root, or ESP? MX Boot Repair gives me these three options to choose from.
Top
Hocksul
Posts: 65
Joined: Wed Jan 13, 2021 6:01 am

Re: Windows partition not accessible after upgrade

#5 Post by Hocksul »

Eadwine Rose wrote: Tue Jul 09, 2024 1:49 pm sudo update-grub in the terminal won't work?
I tried it and it didn't work.
Top
User avatar
j2mcgreg
Global Moderator
Posts: 6610
Joined: Tue Oct 23, 2007 12:04 pm

Re: Windows partition not accessible after upgrade

#6 Post by j2mcgreg »

Hocksul wrote: Tue Jul 09, 2024 1:55 pm Thanks for the quick response!
Just to be on the safe side: should I choose the Boot Method installed on MBR, root, or ESP? MX Boot Repair gives me these three options to choose from.
Your QSI shows that UEFI is in use, so your choice should be ESP.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.
Top
Hocksul
Posts: 65
Joined: Wed Jan 13, 2021 6:01 am

Re: Windows partition not accessible after upgrade

#7 Post by Hocksul »

j2mcgreg wrote: Tue Jul 09, 2024 3:07 pm
Hocksul wrote: Tue Jul 09, 2024 1:55 pm Thanks for the quick response!
Just to be on the safe side: should I choose the Boot Method installed on MBR, root, or ESP? MX Boot Repair gives me these three options to choose from.
Your QSI shows that UEFI is in use, so your choice should be ESP.
I tried that but it didn't work. I have attached what was chosen by default for "Location" (sda1) and "Set root location" (sda4 ). Should I have chosen a different partition?

Image
Top
User avatar
siamhie
Global Moderator
Posts: 3224
Joined: Fri Aug 20, 2021 5:45 pm

Re: Windows partition not accessible after upgrade

#8 Post by siamhie »

What's the output of this in a terminal?

Code: Select all

efibootmgr -v
This is my Fluxbox . There are many others like it, but this one is mine. My Fluxbox is my best friend. It is my life.
I must master it as I must master my life. Without me, my Fluxbox is useless. Without my Fluxbox, I am useless.
Top
Hocksul
Posts: 65
Joined: Wed Jan 13, 2021 6:01 am

Re: Windows partition not accessible after upgrade

#9 Post by Hocksul »

siamhie wrote: Tue Jul 09, 2024 5:46 pm What's the output of this in a terminal?

Code: Select all

efibootmgr -v

The output is

Code: Select all

BootCurrent: 0008
Timeout: 1 seconds
BootOrder: 0008,0003,0006,0002,0007,0000
Boot0000* Windows Boot Manager	HD(1,GPT,81850095-190b-41ad-8c21-bbece1a89b21,0x800,0x64000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...,................
Boot0002* MX21	HD(1,GPT,81850095-190b-41ad-8c21-bbece1a89b21,0x800,0x64000)/File(\EFI\MX21\GRUBX64.EFI)
Boot0003* MX21.2.1	HD(1,GPT,81850095-190b-41ad-8c21-bbece1a89b21,0x800,0x64000)/File(\EFI\MX21.2.1\GRUBX64.EFI)
Boot0006* ubuntu	HD(1,GPT,81850095-190b-41ad-8c21-bbece1a89b21,0x800,0x64000)/File(\EFI\UBUNTU\SHIMX64.EFI)
Boot0007* UEFI: SanDisk'Cruzer Fit, Partition 1	PciRoot(0x0)/Pci(0x14,0x0)/USB(2,0)/HD(1,MBR,0x6b503434,0x800,0x1ca3800)..BO
Boot0008* MX23	HD(1,GPT,81850095-190b-41ad-8c21-bbece1a89b21,0x800,0x64000)/File(\EFI\MX23\GRUBX64.EFI)
Top
User avatar
siamhie
Global Moderator
Posts: 3224
Joined: Fri Aug 20, 2021 5:45 pm

Re: Windows partition not accessible after upgrade

#10 Post by siamhie »

Where did you install grub?

Your screenshot (post #7) shows an efi boot partition (sda1) but the efi boot manager shows MX23 (sda4) as the default boot partition.

Code: Select all

Partition: ID-1: / raw-size: 244.14 GiB size: 239.25 GiB (98.00%) used: 127.36 GiB (53.2%) 
           fs: ext4 block-size: 4096 B dev: /dev/sda4 maj-min: 8:4 
           
           ID-2: /boot/efi raw-size: 200 MiB size: 196 MiB (98.00%) used: 31.2 MiB (15.9%) 
           fs: vfat block-size: 512 B dev: /dev/sda1 maj-min: 8:1
This is my Fluxbox . There are many others like it, but this one is mine. My Fluxbox is my best friend. It is my life.
I must master it as I must master my life. Without me, my Fluxbox is useless. Without my Fluxbox, I am useless.
Top
Post Reply

Return to “MX Help”