Debian bootloader problems

G'day all :)

BACKGROUND

Peer, you can tell me anything I have wrong here, with the usual "quote and answer" :D

Member @Peer has a relatively new laptop he got for his birthday at end of July last.

Before that he had another laptop and had begun his journey in Linux (he also has a Raspberry Pi), starting with Ubuntu, which he still uses.

Since that time, he has also started exploring Debian, another good choice, IMO.


THE PROBLEM

As Peer's Thread Title suggests, he has a problem with the bootloading on his Debian install.

I always have to use the grub on my other Ubuntu installation to bot Debian.

Peer has Windows on, I think, both laptops, the old and the new ... Is that Windows 10 on each machine, Peer?

With his Ubuntu, he gets a Grub Menu, which features Ubuntu, Debian and Windows. He can boot the Debian from there, and there only.

...and debian has a grub,

Well, yes it does, that was a part of the install, but does it have a Grub Menu by itself, now?

It is important to note the difference here -

GRUB is the GRand Universal Bootloader, and is installed with most Linux.

But the Grub Menu is what we see to choose what to boot into - Linux, Windows or other.


WHAT WE HAVE LEARNED ABOVE


Through questions, we have established that neither the Ubuntu nor the Debian is a full install to Peer's hard drive.

Windows is still the only OS installed on his laptop.

Peer has performed a full install of Ubuntu, but only to a USB stick, not to his HDD.

He has performed a full install of his Debian, but only to a USB stick, not to his HDD.


MY THOUGHTS


Ubuntu and other Debian-based Distros have been actively churning out updates in the last few weeks, involving:
  • New Kernel updates
  • New efi-signed packages
  • New Grub 2 updates
  • New firmware updates
  • other, can include shim and shim-signed updates
... all of which, when installed, can cause Linux to run a "generating or updating grub bootloader configuration" protocol, which you may or may not see, depending on how you perform your updates.

Debian itself, which Peer is also using, not so busy.

Peer has had both sticks inserted on his computer when one of these "events" has occurred, and Ubuntu has been in charge of the Grub Menu, or it has been affected when he ran updates from it.

Because Ubuntu is a full install on a stick, when Grub is updated, Peer's computer will treat it a bit like a full install, to the point of recognising it in the BIOS.

If his Debian has not been treated in the same way, it will not get its own Grub Menu, and the BIOS will not recognise it as a full install, that can be booted through his Setup Utility.


OPTIONS


  1. Peer can get his Debian running through his Ubuntu install, and then run
    Code:
    sudo update-grub
    as @tchakatak has mentioned above, and see if this affects things
  2. He can overwrite the Debian stick and reinstall the Debian again (without the Ubuntu stick in place), and once that is completed and running successfully, he can update grub with Ubuntu in place, and reboot, and he should get a new Debian-controlled Grub Menu also featuring Ubuntu and Windows. *Not Desirable, see below
  3. Alternative
*Not Desirable

Can be done, but the first time he boots from the Ubuntu stick, it will show the Debian entry, but not boot to it, as he will have to change the UUID in /etc/fstab to reflect the UUID of the new Debian install.

3. ALTERNATIVE


Peer, are you aware that you will not ever get the performance and speed that Ubuntu and Debian can deliver with your current setup?

Doesn't matter if they are USB 3.0 or 3.1 sticks to USB 3 ports or whatever?

You can only get that if each of Ubuntu and Debian is fully installed to your HDD alongside Windows.

Which prompts me to ask -

Do you want to do that? Are you aware that it can be done?

And of course - do you need to check it with Mutter und Vater?

Think about it and let us know. :)

And don't be afraid to tell me I have made a colossal "booboo" in my understanding, here. Just set me straight.

Wizard has crashed and burned ...

8MEAGEj.jpg


... more times than you have had hot dinners :D

That's how you become a Wizard ... CRASH, BURN ...AND LEARN

Cheers all

Wizard
 


There is just one question: why is the grub menu shown when I want to boot Debian on my older Computer and JUST the Debian USB-stick is connected to the older computer.
 
Just dropping by, i must say that your posts Wizard containing all links and info is so awesome :)
love seeing this, used to be a moderator @ a swedish Ubuntu forum (no longer online)
I know i did some back then, starting to itch in my fingers to get in to it again =D
Spend so much time online and alone so.
 
Is that Windows 10 on each machine, Peer?
One with Windows 10 and one with Windows xp
Peer can get his Debian running through his Ubuntu install, and then run
Code:
sudo update-grub
That doesn’t work.
Do you want to do that? Are you aware that it can be done?

And of course - do you need to check it with Mutter und Vater?

Think about it and let us know. :)
I can not install a Linux distro on the HDD on the older one because it’s an old work Computer of my father with many domane stuff and data on it. And I can not install a Linux on my newer one because on the SSD are a full office package and a Kaspersky.
 
why is the grub menu shown when I want to boot Debian on my older Computer and JUST the Debian USB-stick is connected to the older computer.

Which computer was the Debian stick inserted into when you ran

Code:
sudo update-grub

? Is an entry for the Ubuntu stick (even though it is not in place) showing on that Menu?

As a separate exercise, place the Debian stick into the old laptop and boot into it, then type in this command

Code:
sudo cat /boot/grub/grub.cfg | grep -i ubuntu

and show us the output.


I can not install a Linux distro on the HDD on the older one because it’s an old work Computer of my father with many domane stuff and data on it. And I can not install a Linux on my newer one because on the SSD are a full office package and a Kaspersky.

I understand. :(

On the new laptop, can you give us the output for

Code:
inxi -Fxz

#if inxi is not installed, run

sudo apt install inxi

#then repeat the command
?

See if you can copy and paste the output or put it into a text file, rather than show me the Terminal screen - with text output it makes it easier for us to quote some back to you, with or without changes.

inxi -Fxz is basically the same as inxi -Fxs but -Fxz filters out the MAC address and I know you are learning about that at school. Try both to see the difference.

Thanks Peer

@friTTe

i must say that your posts Wizard containing all links and info is so awesome :)

(memo to self - put this man on Wizard's Christmas Card List)

Kind words, much appreciated.

Enjoy your Linux, all

Wiz
 
Which computer was the Debian stick inserted into when you ran
the old one
Is an entry for the Ubuntu stick (even though it is not in place) showing on that Menu?
yes
sudo cat /boot/grub/grub.cfg | grep -i ubuntu
Code:
debian@unknowne0ca9470007a:~$ sudo cat /boot/grub/grub.cfg | grep -i ubuntu
[sudo] Passwort für debian:
menuentry 'Ubuntu 18.04.1 LTS (18.04) (auf /dev/sdc2)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-c1a3f09d-6239-45d7-9a81-3df860077479' {
submenu 'Erweiterte Optionen für Ubuntu 18.04.1 LTS (18.04) (auf /dev/sdc2)' $menuentry_id_option 'osprober-gnulinux-advanced-c1a3f09d-6239-45d7-9a81-3df860077479' {
    menuentry 'Ubuntu (auf /dev/sdc2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.15.0-39-generic--c1a3f09d-6239-45d7-9a81-3df860077479' {
    menuentry 'Ubuntu, mit Linux 4.15.0-39-generic (auf /dev/sdc2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.15.0-39-generic--c1a3f09d-6239-45d7-9a81-3df860077479' {
    menuentry 'Ubuntu, mit Linux 4.15.0-39-generic (recovery mode) (auf /dev/sdc2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.15.0-39-generic-root=UUID=c1a3f09d-6239-45d7-9a81-3df860077479 ro recovery nomodeset-c1a3f09d-6239-45d7-9a81-3df860077479' {
    menuentry 'Ubuntu, mit Linux 4.15.0-38-generic (auf /dev/sdc2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.15.0-38-generic--c1a3f09d-6239-45d7-9a81-3df860077479' {
    menuentry 'Ubuntu, mit Linux 4.15.0-38-generic (recovery mode) (auf /dev/sdc2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.15.0-38-generic-root=UUID=c1a3f09d-6239-45d7-9a81-3df860077479 ro recovery nomodeset-c1a3f09d-6239-45d7-9a81-3df860077479' {
    menuentry 'Ubuntu, mit Linux 4.15.0-34-generic (auf /dev/sdc2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.15.0-34-generic--c1a3f09d-6239-45d7-9a81-3df860077479' {
    menuentry 'Ubuntu, mit Linux 4.15.0-34-generic (recovery mode) (auf /dev/sdc2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.15.0-34-generic-root=UUID=c1a3f09d-6239-45d7-9a81-3df860077479 ro recovery nomodeset-c1a3f09d-6239-45d7-9a81-3df860077479' {
 
inxi -Fxz
Code:
System:    Host: unknowne0ca9470007a Kernel: 4.9.0-8-amd64 x86_64 (64 bit gcc: 6.3.0)
           Desktop: Gnome 3.22.3 (Gtk 3.22.11-1)
           Distro: Debian GNU/Linux 9 (stretch)
Machine:   Device: laptop System: HP product: HP Laptop 15-bs1xx v: Type1ProductConfigId
           Mobo: HP model: 832B v: 23.47 UEFI: Insyde v: F.34 date: 01/25/2018
Battery    BAT1: charge: 27.9 Wh 98.8% condition: 28.2/28.5 Wh (99%)
           model: Hewlett-Packard PABAS0241231 status: Charging
CPU:       Quad core Intel Core i5-8250U (-HT-MCP-) cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 14400
           clock speeds: max: 3400 MHz 1: 713 MHz 2: 699 MHz 3: 708 MHz
           4: 707 MHz 5: 730 MHz 6: 848 MHz 7: 735 MHz 8: 704 MHz
Graphics:  Card-1: Intel Device 5917 bus-ID: 00:02.0
           Card-2: Advanced Micro Devices [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430]
           bus-ID: 01:00.0
           Display Server: X.Org 1.19.2 driver: N/A
           Resolution: [email protected]
           GLX Renderer: Mesa DRI Intel Kabylake GT1.5
           GLX Version: 3.0 Mesa 13.0.6 Direct Rendering: Yes
Audio:     Card Intel Device 9d71 driver: snd_hda_intel bus-ID: 00:1f.3
           Sound: Advanced Linux Sound Architecture v: k4.9.0-8-amd64
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: 3000 bus-ID: 02:00.0
           IF: eno1 state: down mac: <filter>
           Card-2: Intel Device 24fb driver: iwlwifi bus-ID: 03:00.0
           IF: wlo1 state: up speed: N/A duplex: N/A mac: <filter>
Drives:    HDD Total Size: 350.7GB (17.5% used)
           ID-1: /dev/sda model: SanDisk_SD9SN8W size: 256.1GB temp: 21C
           ID-2: USB /dev/sdb model: Ultra_Fit size: 30.8GB temp: 0C
           ID-3: USB /dev/sdd model: SD/MMC/MS_PRO size: 63.9GB temp: 0C
Partition: ID-1: / size: 25G used: 19G (83%) fs: ext4 dev: /dev/sdb1
           ID-2: swap-1 size: 4.20GB used: 0.00GB (0%) fs: swap dev: /dev/sdb5
Sensors:   System Temperatures: cpu: 34.0C mobo: 29.8C gpu: 28.0
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 253 Uptime: 2 min Memory: 1304.3/7904.4MB
           Init: systemd runlevel: 5 Gcc sys: 6.3.0
           Client: Shell (bash 4.4.121) inxi: 2.3.5
 
Thanks Peer :)

...the old one

Try it with the new one, now.

1. Have both sticks inserted so that Ubuntu is in charge. It has Debian on its Grub Menu, yes?

Choose Debian and boot into Debian.

Then run from Debian's Terminal

Code:
sudo update-grub

2. Reboot and report any changes.

3. Get back into Ubuntu on the new computer, with both sticks in and give us the outputs for both

Code:
sudo update-grub

# and, wait until finished, then

sudo cat /boot/grub/grub.cfg | grep -i debian

I know this is a lot of work, and frustrating, and with no guaranteed good result, but only through this can I get a clear picture of what is involved. Thanks for being patient :)

Wizard
 
On a separate train of thought, ask yourself "Would I like to be able to have both Debian and Ubuntu as full installs on my SSD ... still keeping Windows, MS Office and Kaspersky?"

If the answer is Yes, I expect we have a way.

If Yes, I will need some information from Windows 10.

Cheers

Wizard
 
sudo update-grub
Code:
[sudo] Passwort für linuxgamer21:
GRUB-Konfigurationsdatei wird erstellt …
Linux-Abbild gefunden: /boot/vmlinuz-4.15.0-39-generic
initrd-Abbild gefunden: /boot/initrd.img-4.15.0-39-generic
Linux-Abbild gefunden: /boot/vmlinuz-4.15.0-38-generic
initrd-Abbild gefunden: /boot/initrd.img-4.15.0-38-generic
Linux-Abbild gefunden: /boot/vmlinuz-4.15.0-34-generic
initrd-Abbild gefunden: /boot/initrd.img-4.15.0-34-generic
Windows Boot Manager auf /dev/sda1@/efi/Microsoft/Boot/bootmgfw.efi gefunden
Debian GNU/Linux 9 (stretch) auf /dev/sdb1 gefunden
Hinzufügen des Boot-Menü Eintrages für die EFI Firmware Konfiguration
erledigt
sudo cat /boot/grub/grub.cfg | grep -i debian
Code:
### BEGIN /etc/grub.d/05_debian_theme ###
### END /etc/grub.d/05_debian_theme ###
menuentry 'Debian GNU/Linux 9 (stretch) (auf /dev/sdb1)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-d3c0bde4-b8c5-4ce9-addf-1a1040a1c67d' {
submenu 'Erweiterte Optionen für Debian GNU/Linux 9 (stretch) (auf /dev/sdb1)' $menuentry_id_option 'osprober-gnulinux-advanced-d3c0bde4-b8c5-4ce9-addf-1a1040a1c67d' {
    menuentry 'Debian GNU/Linux (auf /dev/sdb1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.9.0-8-amd64--d3c0bde4-b8c5-4ce9-addf-1a1040a1c67d' {
    menuentry 'Debian GNU/Linux, mit Linux 4.9.0-8-amd64 (auf /dev/sdb1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.9.0-8-amd64--d3c0bde4-b8c5-4ce9-addf-1a1040a1c67d' {
    menuentry 'Debian GNU/Linux, with Linux 4.9.0-8-amd64 (recovery mode) (auf /dev/sdb1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.9.0-8-amd64-root=UUID=d3c0bde4-b8c5-4ce9-addf-1a1040a1c67d ro single-d3c0bde4-b8c5-4ce9-addf-1a1040a1c67d' {
    menuentry 'Debian GNU/Linux, mit Linux 4.9.0-6-amd64 (auf /dev/sdb1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.9.0-6-amd64--d3c0bde4-b8c5-4ce9-addf-1a1040a1c67d' {
    menuentry 'Debian GNU/Linux, with Linux 4.9.0-6-amd64 (recovery mode) (auf /dev/sdb1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.9.0-6-amd64-root=UUID=d3c0bde4-b8c5-4ce9-addf-1a1040a1c67d ro single-d3c0bde4-b8c5-4ce9-addf-1a1040a1c67d' {
 
OK, thanks for that :)

When you get the chance next, can you give us the output for (with both sticks inserted in the new laptop)

Code:
sudo fdisk -l

# that's a lowercase L
?

I'm going to try a couple of things with my old laptop and a couple of sticks. The Toshiba Satellite has Insyde BIOS Setup Utility, but some years older than yours.

Do think about what I said at #30 above, and if you do, I would like to see something from your Windows Disk Management utility similar to what I show you below in a minute.

Wizard
 
When you get the chance next, can you give us the output for (with both sticks inserted in the new laptop)

Code:
sudo fdisk -l
Festplatte /dev/sda: 238,5 GiB, 256060514304 Bytes, 500118192 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 4096 Bytes
E/A-Größe (minimal/optimal): 4096 Bytes / 4096 Bytes
Festplattenbezeichnungstyp: gpt
Festplattenbezeichner: 5D6E80DB-9FF7-4BFF-AF01-04683CCBE81E

Gerät Anfang Ende Sektoren Größe Typ
/dev/sda1 2048 534527 532480 260M EFI-System
/dev/sda2 534528 567295 32768 16M Microsoft reserviert
/dev/sda3 567296 463101951 462534656 220,6G Microsoft Basisdaten
/dev/sda4 463101952 465108991 2007040 980M Windows-Wiederherstellungsumgebu
/dev/sda5 465108992 500105215 34996224 16,7G Microsoft Basisdaten




Festplatte /dev/sdb: 28,7 GiB, 30752636928 Bytes, 60063744 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: dos
Festplattenbezeichner: 0x908253d0

Gerät Boot Anfang Ende Sektoren Größe Kn Typ
/dev/sdb1 * 2048 51857407 51855360 24,7G 83 Linux
/dev/sdb2 51859454 60061695 8202242 3,9G 5 Erweiterte
/dev/sdb5 51859456 60061695 8202240 3,9G 82 Linux Swap / Solaris


Festplatte /dev/sdc: 28,7 GiB, 30752636928 Bytes, 60063744 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: gpt
Festplattenbezeichner: EB81F135-2E18-46F0-AECA-0E9EE381D0A2

Gerät Anfang Ende Sektoren Größe Typ
/dev/sdc1 2048 1050623 1048576 512M EFI-System
/dev/sdc2 1050624 60061695 59011072 28,1G Linux-Dateisystem


Festplatte /dev/sdd: 59,5 GiB, 63864569856 Bytes, 124735488 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: dos
Festplattenbezeichner: 0x2e435a91

Gerät Boot Anfang Ende Sektoren Größe Kn Typ
/dev/sdd1 32768 124735487 124702720 59,5G c W95 FAT32 (LBA)
 
For you non German speaking types: ;)

Hard disk / dev / sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical / physical): 512 bytes / 4096 bytes
I / O size (minimum / optimal): 4096 bytes / 4096 bytes
Disk Type: gpt
Hard disk identifier: 5D6E80DB-9FF7-4BFF-AF01-04683CCBE81E

Device Start End Sectors Size Type
/ dev / sda1 2048 534527 532480 260M EFI system
/ dev / sda2 534528 567295 32768 16M Microsoft reserved
/ dev / sda3 567296 463101951 462534656 220.6G Microsoft Basic Data
/ dev / sda4 463101952 465108991 2007040 980M Windows Recovery Rebuild
/ dev / sda5 465108992 500105215 34996224 16.7G Microsoft Basic Data




Hard disk / dev / sdb: 28.7 GiB, 30752636928 bytes, 60063744 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical / physical): 512 bytes / 512 bytes
I / O size (minimum / optimal): 512 bytes / 512 bytes
Disk Type: dos
Hard disk identifier: 0x908253d0

Device Boot Start End Sectors Size Kn Type
/ dev / sdb1 * 2048 51857407 51855360 24,7G 83 Linux
/ dev / sdb2 51859454 60061695 8202242 3,9G 5 Advanced
/ dev / sdb5 51859456 60061695 8202240 3.9G 82 Linux Swap / Solaris


Hard disk / dev / sdc: 28.7 GiB, 30752636928 bytes, 60063744 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical / physical): 512 bytes / 512 bytes
I / O size (minimum / optimal): 512 bytes / 512 bytes
Disk Type: gpt
Hard disk identifier: EB81F135-2E18-46F0-AECA-0E9EE381D0A2

Device Start End Sectors Size Type
/ dev / sdc1 2048 1050623 1048576 512M EFI system
/ dev / sdc2 1050624 60061695 59011072 28.1G Linux file system


Disk / dev / sdd: 59.5 GiB, 63864569856 bytes, 124735488 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical / physical): 512 bytes / 512 bytes
I / O size (minimum / optimal): 512 bytes / 512 bytes
Disk Type: dos
Hard disk identifier: 0x2e435a91

Device Boot Start End Sectors Size Kn Type
/ dev / sdd1 32768 124735487 124702720 59.5G c W95 FAT32 (LBA)
 
Oh, BB you are such a smart arse, but I luv yer :D

I was working through that output and guessing (correctly) what it all meant, but now you've translated it is much easier.:p:confused::cool:

Peer, this is a significant indicator, your USB sticks are set up differently !

One is formatted to MS-DOS, the other is set to GPT. The GPT one is friendly to the UEFI on your new computer, the MSDOS one not so friendly.

The GPT stick (/dev/sdc) is also having its own ESP (EFI (Extensible Firmware Interface) System Partition). It is 512MB in size, which is not untypical.

Your Windows also has one of these on /dev/sda1 and is set to 260MB.

Can you identify for us which of the two sticks is which? That is which Distro on /dev/sdb and which on /dev/sdc.

I am betting I know but I need confirmation, to be sure.

I want to install Debian 9 on the SSD and keep WIndows.
But not now first I want to fix this: https://www.linux.org/threads/debian-wifi-problems.20957/

Noted, and quite understand :D

More commands, both sticks plugged into the new laptop again:

Code:
df -h

and

Code:
sudo lsblk --fs

Thanks, Peer and Avagudweegend

Wiz
 
Datasystem Size used Verf. Verw% mounted on
udev 3,9G 0 3,9G 0% /dev
tmpfs 791M 9,6M 781M 2% /run
/dev/sdb1 25G 19G 4,4G 82% /
tmpfs 3,9G 6,4M 3,9G 1% /dev/shm
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 3,9G 0 3,9G 0% /sys/fs/cgroup
tmpfs 791M 16K 791M 1% /run/user/117
tmpfs 791M 32K 791M 1% /run/user/1000
/dev/sdd1 60G 35G 26G 58% /media/debian/SD_Card
/dev/sdc2 28G 20G 7,1G 74% /media/debian/c1a3f09d-6239-45d7-9a81-3
sudo lsblk --fs
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 vfat F870-EE1F
├─sda2
├─sda3 ntfs Windows 147698437698278E
├─sda4 ntfs Windows RE tools 6E24C18E24C159AB
└─sda5 ntfs RECOVERY B08875128874D874
sdb
├─sdb1 ext4 d3c0bde4-b8c5-4ce9-addf-1a1040a1c67d /
├─sdb2
└─sdb5 swap 02aec05f-faa7-4479-9ac1-05d30db66901 [SWAP]
sdc
├─sdc1 vfat D673-4E16
└─sdc2 ext4 c1a3f09d-6239-45d7-9a81-3df860077479 /media/debia
sdd
└─sdd1 vfat SD_Card 4FF2-21B3 /media/debia
sr0
 
Thanks Peer - one small booboo on my part :( - can you open a File Manager and click on the partition that holds your Windows OS. Mine looks like this and yours will be similar but not exactly the same.

kBQHDIK.png


See at the bottom where mine says "21 items, Free space: 10.8 GB"?

I want that figure. If you do that, and then repeat the "df -h" command, Windows will also show up.

Cheers

Chris
 

Members online


Top