Community
cancel
Showing results for 
Search instead for 
Did you mean: 
UUbIx
Novice
3,453 Views

STK1AW32SC BIOS v0030 missing Legacy mode and microSD Card not working

So my experience with STK1A32WFC and STK2m364CC was fine and Linux runs perfect, I buyed the STK1A(W)32SC, due to the out of the box supported WLAN/BT Chipset. See also my comments in this thread: /thread/106904 https://communities.intel.com/thread/106904

At first I updated the BIOS to the new v0030 for STK1A32SC and STK1AW32SC (marked as the same - which make sense due to the identical HW). But it is not possible with this version to access via Linux (e.g. openSUSE Tumbleweed build from 26.12.2016) the microSD Card. Also an in the STK1A32WFC installed mikroSD Card, which is working fine also with the STK2m364CC, won't be listed as boot device in the BIOS settings (F2) or the Boot Menu (F10). In the documentation I can't find any deviation, between the 3 Compute Sticks! So I expect this is a bug in the BIOS firmware.

Some additional issues I've detected in the BIOS:

  1. The PTT mode is not clear for me. The Help with switch on and off PTT gives also no idea what happens with this option!
  2. The BIOS can't be switch to Legacy mode - so no older OS can't be installed!
  3. What is the technical background for the selection of OS between Win64, Win32 and Android/Ubuntu? (So I remind well, with the older v0024 on STK1A32WFC it was no problem to select Linux and Windows, with still Linux or Windows selected in the BOOT-Menu, in STK1AW32CC I can use the installed Windows 32bit Home only with this OS selected, and 64bit Tumbleweed was not listed, with Win64 and Android selected Tumbleweed Boots fine, but Windows Home is not listed - all other new BIOS what I know - from ASUS, MSI and so on - have no truble with this)
  4. During reboot it is not possible to select one of the BOOT
  5. Remark If I switch Switch on and off of secure BOOT - have no impact to the issues above (Tumbleweed GRUB is per default MS signed).

Happy New Year

UbIx

0 Kudos
28 Replies
idata
Community Manager
218 Views

Hello UbIx ,

 

 

When the Intel® Platform Trust Technology (Intel® PTT) is switch on is a platform functionality for credential storage and key management used by Windows 8* and Windows® 10. Intel® PTT supports BitLocker* for hard drive encryption and supports all Microsoft requirements for firmware Trusted Platform Module (fTPM) 2.0.

 

 

The Intel Compute Stick STK1AW32SC has Windows 10 Home 32-bit pre-installed with all necessary drivers, 64bit is not supported. On this unit any other operating system, Linux*, OpenSUSE we don't support it, this is because it has not been validated by Intel, you will get better support for these distros from their forum support sites.

 

 

The unit has been build to work with Windows®10 so legacy mode will not be necessary for the unit because older Windows® version is not supported and Windows®10 works better with UEFI.

 

 

You can see supported operating system here:

 

http://www.intel.com/content/www/us/en/support/boards-and-kits/intel-compute-stick/000005899.html http://www.intel.com/content/www/us/en/support/boards-and-kits/intel-compute-stick/000005899.html

 

 

Now, if somebody else has been able to install and access the Micro SD, they are free to share that information with us.

 

 

If the Micro SD is not detected not even with Windows installed, this could be an issue either with the Micro SD Card Reader or with the Micro SD itself, but in this case you're mentioning that the card works with the other Intel® Compute sticks.

 

 

Do you have another Micro SD to try if it is possible if not that is understandable?

 

 

What is the size of the Micro SD Card? It is formatted in exFAT or FAT32? Either one should work but is just to try. What is the model of the card?

 

 

 

Regards,

 

 

 

Ivan.

 

UUbIx
Novice
218 Views

Hi intel_corp Ivan,

at first - thanks for your fast reply

Intel Corporation wrote:

 

Hello UbIx,

 

 

When the Intel® Platform Trust Technology (Intel® PTT) is switch on is a platform functionality for credential storage and key management used by Windows 8* and Windows® 10. Intel® PTT supports BitLocker* for hard drive encryption and supports all Microsoft requirements for firmware Trusted Platform Module (fTPM) 2.0.

Thanks for your information. In the future it can be helpful if this information is available in the BIOS itself if I press F1-key

The Intel Compute Stick STK1AW32SC has Windows 10 Home 32-bit pre-installed with all necessary drivers, 64bit is not supported. On this unit any other operating system, Linux*, OpenSUSE we don't support it, this is because it has not been validated by Intel, you will get better support for these distros from their forum support sites.

Sure, that's clear - that I do this with my own risk (like always if I need Linux). Normally I would by the STK1A32SC - but this is not in all shops available and the price deviation is sometimes only some Euro - so that I used a shop which I do anyway a buy - so the price deviation was covered by the transportation fee. But on this - there is now remark that I lost the warranty, if I play Linux on it . So for me it is not forbidden (hopefully).

The unit has been build to work with Windows®10 so legacy mode will not be necessary for the unit because older Windows® version is not supported and Windows®10 works better with UEFI.

 

 

You can see supported operating system here:

 

http://www.intel.com/content/www/us/en/support/boards-and-kits/intel-compute-stick/000005899.html http://www.intel.com/content/www/us/en/support/boards-and-kits/intel-compute-stick/000005899.html

Sure - this is always the situation at all companies

Now, if somebody else has been able to install and access the Micro SD, they are free to share that information with us.

Hopefully - someone can help

If the Micro SD is not detected not even with Windows installed, this could be an issue either with the Micro SD Card Reader or with the Micro SD itself, but in this case you're mentioning that the card works with the other Intel® Compute sticks.

Yes, I can read the card on the preinstalled Windows (for sure only the FAT-UEFI part of the card). But at boot time and also later after boot, I can't see the bootable source. I use the quality cards from SanDisk Ultra (32GB and 64GB) or Samsung Pro (32GB), both shows the same effect on STK1AW32SC (but all works fine in the other both Compute Sticks STK1A32WFC and STK2m364CC). So for me es electronic Engineer, it looks like an error on the BIOS of the STK1A(W)32SC. So the BIOS have many additional bugs like written above (much more than the other both C-Sticks)

Do you have another Micro SD to try if it is possible if not that is understandable?

Like written above, I tested two different Suppliers (SanDisk and Samsung) and two different Card-Sizes (32GB and 64GB). All I can read with the preinstalled Windows fine (for sure only the supported File Systems). But doesn't be detected in the internal slot.

What is the size of the Micro SD Card? It is formatted in exFAT or FAT32? Either one should work but is just to try. What is the model of the card?

One partition is formatted with the EFI-FAT

The Installation partitioning with the Linux

Device Boot Begin End Sectors Size Kn Typ

/dev/sdh1 3840 11399 7560 3,7M ef EFI (FAT-12/16/32)

/dev/sdh2 * 11400 9091071 9079672 4,3G 17 Hidden HPFS/NTFS

And the later generated one (32GB => 29GB) which was generated on STK1A32WFC and works fine on this one:

/dev/sdi1 2048 321535 319488 156M EFI-System

/dev/sdi2 321536 643071 321536 157M Linux-Filesystem

/dev/sdi3 643072 4868095 4225024 2G Linux-Filesystem

/dev/sdi4 4868096 62519295 57651200 27,5G Linux-Filesystem

The EFI partition is the relevant part for the BIOS - which includes the bootloader of the Linux system.

Summary: for me it looks like, the enabling of the SD-Card interface don't work really in v0030!

Regards

UbIx

EDIT: It seems that the Editor here can't handle multiple quotes in one answer correctly (in the Editor view it looks perfect).

idata
Community Manager
218 Views

I really appreciate your feedback about the F1-key and thank you for all the information.

 

 

Does this SD-card work on previous BIOS version with the Intel® STK1AW32SC?

 

 

Perhaps you would like to try version https://downloadcenter.intel.com/download/26317/BIOS-Update-SCCHTAX5-86A-?product=91065 0029 and see how it goes.

 

 

Also, I would suggest to post your issue at the Linux*community to see if somebody else can be able to help somehow.

We are always working to make better our products so any feedback is appreciated, hopefully new BIOS versions will be released to add features and fix issues.

 

 

 

Ivan.

 

UUbIx
Novice
218 Views

Hi Ivan (intel_corp ),

thanks for your reply.

I will test the roll back of the Firmware tomorrow. For some minutes I've tested to disable/enable the internal SD-Card support in BIOS - but no effect.

Regards

UbIx

UUbIx
Novice
218 Views

Hi Ivan,

Intel Corporation wrote:

I really appreciate your feedback about the F1-key and thank you for all the information.

 

 

Does this SD-card work on previous BIOS version with the Intel® STK1AW32SC?

 

 

Perhaps you would like to try version https://downloadcenter.intel.com/download/26317/BIOS-Update-SCCHTAX5-86A-%3Fproduct%3D91065 0029 and see how it goes.

 

 

Also, I would suggest to post your issue at the Linux*community to see if somebody else can be able to help somehow.

We are always working to make better our products so any feedback is appreciated, hopefully new BIOS versions will be released to add features and fix issues.

 

 

I tested the recovery via F4 and the reflashing with the v0029, both don't work.

Is it possible that the recovery don't work if the update was done via Windows?

Additional I made some many other tests - it is not possible to access the SD-Card without Windows drivers

Per default the event logging is on and some crazy entries are in - do you think this was OK:

CMOS Checksum Error ( 2) 3/27/2048 0: 0: 0

CMOS Time Not Set ( 2) 1/ 1/2015 0: 0: 0

Flash Update Failed ( 8) 10/27/2025 20:12:42

The entry with the BIOS update is missing and also the time was from beginning on OK (I think due to the Time Server in my local network - which is also included in the DHCP entry). Also I've connected an Digitus USB 3.0 3-Port HUB & Gigabit LAN Adapter DA-70250:

http://www.digitus.info/en/products/computer-accessories-and-components/computer-accessories/usb-hub... http://www.digitus.info/en/products/computer-accessories-and-components/computer-accessories/usb-hub...

Which works fine with all compute sticks with Windows 10 and Linux (out of the box without driver installation).

What is confusing for me, is the fast reboot without any text output, if I start the Recovery with F4 - on the STK1A32WFC there was an dialog which ask me if I was sure - to do this (I don't remind the correct wording anymore).

A totally confused

UbIx

idata
Community Manager
218 Views

Maybe I posted the incorrect BIOS version, please try this version for the Intel® Compute Stick STCK1A32WFC

 

 

https://downloadcenter.intel.com/download/26502/BIOS-Update-FCBYT10H-86A- https://downloadcenter.intel.com/download/26502/BIOS-Update-FCBYT10H-86A-

This version is latest one that Intel has released

 

 

 

Ivan.

 

UUbIx
Novice
218 Views

Hi Ivan,

thanks for the replay. But I don't need an update on STCK1A32WFC - which is running fine with Linux on the SD-Card.

I need to update the STK1AW32SC, which the newest BIOS is there:

https://downloadcenter.intel.com/download/26448/BIOS-Update-SCCHTAX5-86A-?v=t https://downloadcenter.intel.com/download/26448/BIOS-Update-SCCHTAX5-86A-?v=t

But anyway, I flashed now 0029 and again 0030, but still the SD card won't be listed, also not with the FAT FS which includes the firmware files. With a stick and also with a sd card reader which includes this SD card, it is possible to read!

idata
Community Manager
218 Views

Thanks for this information, if you are able to read the SD card from a SD card reader then it seems that the Intel® Compute Stick card reader is defective, at least this is what it seems to be for me.

 

 

At this point, I suggest getting a replacement for the unit.

 

 

I have sent you a private message.

 

 

Regards,

 

 

 

Ivan.

 

UUbIx
Novice
218 Views

Hi Ivan,

thanks again for answer. I've received your eMail, but I prefere to send it back to my supplier (so I'm in the 14 days extended warranty (in Germany you can send in this time each more expencive device back - also without any reason) and for sure in the half year warranty for full functionality).

But I fill the Email and send it back. If it is better - for error analysis reason, than I also accept to send it to Intel.

Please let me know your preferred solution.

Regards

UbIx

idata
Community Manager
218 Views

In this case, we just replace the unit but we don't do any analyze unless there is several report about the same issue.

 

 

At this point if you have the option to send it to your supplier in Germany I suggest you to get in contact with them and get the replacement.

 

 

Best wishes,

 

 

 

Ivan.

 

UUbIx
Novice
218 Views

Hi Ivan,

OK, than I will send it back to supplier. Please ignore my private answer for some minutes.

Thanks for support and nice Day

UbIx

idata
Community Manager
218 Views

You are more than welcome!

 

 

 

Best wishes,

 

 

Ivan.
UUbIx
Novice
218 Views

Hi Ivan,

today arrived the new STK1AW32SC - but still the same issue (in the moment BIOS v0029).

Seems for me more an BIOS issue than a HW topic.

Regards

Ulf

JVanB
Valued Contributor II
218 Views

Does the output you get from

dmesg | grep mmc1

provide any insights into the problem?

idata
Community Manager
218 Views

Make sure fast boot is off in the BIOS.

 

 

Other than that I'm not sure what could've be, is not detected in BIOS either?

 

 

Is your SD model on the Intel® compatibility list, this could be also a compatibility problem with the Intel® Compute stick.

 

http://www.intel.com/content/www/us/en/support/boards-and-kits/intel-compute-stick/000017555.html Tested Peripherals for Intel® Compute Stick STK1AW32SC and STK1A32SC

 

 

 

Ivan.

 

UUbIx
Novice
218 Views

Hi Repeat%20Offender,

on the STK1AW32SC only mmc0 is listed in

fdisk -l

and

dmesg | grep mmc

has no return

On my STK2m364CC (which the same Samsung Ultra Card boots - see my description above), the output of the same:

fdisk -l

and

dmesg | grep mmc

returns only an BTRFS message from installed Tumbleweed partition on the internal memory

Hopefully on weekend I can check the output on EVI console.

JVanB
Valued Contributor II
218 Views

Here is a procedure that doesn't require installing an OS to reproduce the problem.

1. Get one of linuxium 's Zesty images, e.g. https://goo.gl/8MScR9 zesty-ubuntu-desktop-alpha-010117-linuxium.iso - Google Drive

2. Get rufus https://rufus.akeo.ie/ Rufus - Create bootable USB drives the easy way

3. Burn zesty image to 8+ GB USB stick using rufus.

4. Insert USB stick into Compute Stick (Power connected but turned off)

5. Hold power button for 3.5 sec (time with watch) and release

6. At menu, hit for boot menu

7. Select USB (make it white), hit

8. At GRUB menu, accept default of Try Ubuntu without installing

9. After ubuntu boots, hit ++T to start Terminal

10. Hit so numeric keypad works

11. I always have to type

xrandr --output HDMI-2 --mode 3840x2160 --rate 30

at this point becaues ubuntu wants to start me out in 4096x2160 so I can't see the edges of my logical display.

12. Connect to network using icon @ upper right

Here is the content of my Terminal session

[code]

To run a command as administrator (user "root"), use "sudo ".

See "man sudo_root" for details.

ubuntu@ubuntu:~$ xrandr --output HDMI-2 --mode 3840x2160 --rate 30

ubuntu@ubuntu:~$ df -h

Filesystem Size Used Avail Use% Mounted on

udev 930M 0 930M 0% /dev

tmpfs 193M 9.2M 184M 5% /run

/dev/sda1 30G 2.0G 28G 7% /cdrom

/dev/loop0 1.5G 1.5G 0 100% /rofs

/cow 964M 68M 897M 7% /

tmpfs 964M 133M 832M 14% /dev/shm

tmpfs 5.0M 4.0K 5.0M 1% /run/lock

tmpfs 964M 0 964M 0% /sys/fs/cgroup

tmpfs 964M 4.2M 960M 1% /tmp

tmpfs 193M 160K 193M 1% /run/user/999

/dev/mmcblk0p5 9.6G 5.8G 3.4G 64% /media/ubuntu/2a8cc165-d07a-4feb-939b-a626131a24e0

/dev/mmcblk0p4 19G 17G 2.0G 90% /media/ubuntu/5C1E95661E9539CA

ubuntu@ubuntu:~$ blkid

/dev/mmcblk0p1: LABEL="Recovery" UUID="A6EC846DEC843A17" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="8831a3b4-a894-4ee4-92cf-3522cdeaf1d3"

/dev/mmcblk0p2: UUID="EC88-4951" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="250078dc-fd3a-4854-b23b-d89af6d21368"

/dev/mmcblk0p4: UUID="5C1E95661E9539CA" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="9e2e5047-8209-4a2b-a3be-d4325bff0d66"

/dev/mmcblk0p5: UUID="2a8cc165-d07a-4feb-939b-a626131a24e0" TYPE="ext4" PARTUUID="56e100b8-bb61-4b4a-86ea-5bff51ed1b36"

/dev/sda1: LABEL="UBUNTU 17_0" UUID="7C28-B64F" TYPE="vfat" PARTUUID="01aaa8ca-01"

ubuntu@ubuntu:~$ dmesg | grep mmc1

[ 40.573283] mmc1: SDHCI controller on ACPI [80860F14:02] using ADMA

[ 40.953164] mmc1: Skipping voltage switch

[ 43.120918] mmc1: card never left busy state

[ 43.121003] mmc1: error -110 whilst initialising SD card

[ 43.218881] mmc1: Skipping voltage switch

[ 43.677138] mmc1: Skipping voltage switch

[ 45.200171] mmc1: Skipping voltage switch

[ 47.584931] mmc1: card never left busy state

[ 47.584943] mmc1: error -110 whilst initialising SD card

[ 49.976616] mmc1: card never left busy state

[ 49.976629] mmc1: error -110 whilst initialising SD card

[ 52.439439] mmc1: Skipping voltage switch

[ 54.920977] mmc1: card never left busy state

[ 54.920989] mmc1: error -110 whilst initialising SD card

ubuntu@ubuntu:~$ mkdir /stuff

mkdir: cannot create directory '/stuff': Permission denied

ubuntu@ubuntu:~$ sudo mkdir /stuff

ubuntu@ubuntu:~$ sudo mount /dev/sda1 /stuff

mount: /dev/sda1 is already mounted or /stuff busy

/dev/sda1 is already mounted on /cdrom

ubuntu@ubuntu:~$ gedit /dev/sda1/output.txt

** (gedit:3750): WARNING **: Error when getting information for file "/dev/sda1/output.txt": Not a directory

ubuntu@ubuntu:~$ cd /dev/sda1

bash: cd: /dev/sda1: Not a directory

ubuntu@ubuntu:~$ cd /cdrom

ubuntu@ubuntu:/cdrom$ gedit output.txt

[/code]

So it can be seen what an ubuntu newbie I am, but at least some error messages seem to be showing regarding the sd card.

UUbIx
Novice
218 Views

Intel Corporation wrote:

Make sure fast boot is off in the BIOS.

 

 

Other than that I'm not sure what could've be, is not detected in BIOS either?

 

 

Is your SD model on the Intel® compatibility list, this could be also a compatibility problem with the Intel® Compute stick.

 

http://www.intel.com/content/www/us/en/support/boards-and-kits/intel-compute-stick/000017555.html Tested Peripherals for Intel® Compute Stick STK1AW32SC and STK1A32SC

 

 

 

Ivan.

 

Hi Ivan,

There is no fast boot option in BIOS v0029 (update to v0030 is planed next days)!

I Tested (Like described in this thread ):

  • SanDisk Extreme 32GB µSD (UHS-I)
  • SanDisk Ultra 64GB µSD (UHS-I)
  • SanDisk Ultra PLUS microSDXC UHS-1 64 GB
  • Samsung EVO Plus microSDXC UHS-1 64 GB

With all still the same - works stable in the STK1A32WFC and STK2m364CC (also will be listed in the Boot menu - F10 - if there is a EFI GDI System available).

Regards

UbIx

UUbIx
Novice
218 Views

Hi Repeat%20Offender,

thanks for your detailed reply. But I see no dedicated reason to use not 100% free Ubuntu instead off openSUSE Tumbleweed.

Now I've installed daily build from 2016-01-18

# uname -a

Linux linux-vt4t 4.9.3-1-default # 1 SMP PREEMPT Thu Jan 12 11:32:53 UTC 2017 (2c7dfab) x86_64 x86_64 x86_64 GNU/Linux

# dmesg | grep mmc1

[ 5.439850] mmc1: SDHCI controller on ACPI [80860F14:02] using ADMA

[ 46.398063] mmc1: card never left busy state

[ 46.398092] mmc1: error -110 whilst initialising SD card

Still the same as on yours.

If I insert an card with running

# journalctl -f

shows the following error

linux-vt4t kernel: mmc1: error -110 whilst initialising SD card

# df -h

Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf

devtmpfs 950M 0 950M 0% /dev

tmpfs 958M 0 958M 0% /dev/shm

tmpfs 958M 1,7M 956M 1% /run

tmpfs 958M 0 958M 0% /sys/fs/cgroup

/dev/mapper/system-root 20G 5,4G 14G 29% /

/dev/sdb2 400M 56M 232M 20% /boot

/dev/sdb1 148M 4,6M 144M 4% /boot/efi

tmpfs 192M 12K 192M 1% /run/user/1000

The inserted SanDisk 32GB was not listed - like also at

# fdisk -l

Festplatte /dev/mmcblk0: 29,1 GiB, 31268536320 Bytes, 61071360 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: CC66D8BE-2A4C-4B6D-833A-A3ACFA98A0FB

Gerät Anfang Ende Sektoren Größe Typ

/dev/mmcblk0p1 2048 206847 204800 100M EFI-System

/dev/mmcblk0p2 206848 468991 262144 128M Microsoft reserviert

/dev/mmcblk0p3 468992 58972159 58503168 27,9G Microsoft Basisdaten

/dev/mmcblk0p4 58972160 61069311 2097152 1G Windows-Wiederherstellungsumgebung

Festplatte /dev/mmcblk0boot1: 4 MiB, 4194304 Bytes, 8192 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

Festplatte /dev/mmcblk0boot0: 4 MiB, 4194304 Bytes, 8192 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

Festplatte /dev/sdb: 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: gpt

Festplattenbezeichner: 140E1B00-559F-465A-9E16-7D6C159CBB7A

Gerät Anfang Ende Sektoren Größe Typ

/dev/sdb1 2048 305151 303104 148M EFI-System

/dev/sdb2 305152 1124351 819200 400M Linux-Dateisystem

/dev/sdb3 4497408 124733439 120236032 57,3G Linux LVM

/dev/sdb4 1124352 4497407 3373056 1,6G Linux LVM

Partitionstabelleneinträge sind nicht in Festplatten-Reihenfolge.

Festplatte /dev/mapper/cr_usb-Generic-_USB3.0_CRW_-SD_201006010301-0:0-part3: 57,3 GiB, 61558751232 Bytes, 120231936 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

Festplatte /dev/mapper/system-swap: 2 GiB, 2147483648 Bytes, 4194304 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

Festplatte /dev/mapper/system-root: 20 GiB, 21474836480 Bytes, 41943040 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

Festplatte /dev/mapper/cr_usb-Generic-_USB3.0_CRW_-SD_201006010301-0:0-part4: 1,6 GiB, 1724907520 Bytes, 3368960 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

and

# blkid

/dev/mmcblk0: PTUUID="cc66d8be-2a4c-4b6d-833a-a3acfa98a0fb" PTTYPE="gpt"

/dev/mmcblk0p1: LABEL="SYSTEM" UUID="66F3-AA75" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="a3f99fdc-a920-4fdc-9935-f010f462b690"

/dev/mmcblk0p2: PARTLABEL="Microsoft reserved partition" PARTUUID="670f3fc0-3f48-4705-9eb8-a4d0a5ff6f0f"

/dev/mmcblk0p3: UUID="D278F8C378F8A6FF" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="c602457f-df61-421e-b2fd-cbf7a0095eab"

/dev/mmcblk0p4: LABEL="Recovery" UUID="98C0F9B0C0F994AA" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="4de36d87-aff0-4460-87c8-fe3e57e0cbc6"

/dev/sdb1: SEC_TYPE="msdos" UUID="CF78-84F1" TYPE="vfat" PARTLABEL="primary" PARTUUID="0a14f566-4f92-4fe0-b25f-3e8e779b3770"

/dev/sdb2: UUID="de925130-3362-4b97-bf3c-1ee16aaaef68" UUID_SUB="35411fdd-3685-4602-aedd-4fd900cf430f" TYPE="btrfs" PARTLABEL="primary" PARTUUID="55c48b33-be96-4497-a5dc-9109e986a8b9"

/dev/sdb3: UUID="d6d6e9a6-9689-4775-8a92-5b0cbcfc3ef2" TYPE="crypto_LUKS" PARTLABEL="primary" PARTUUID="19d271c5-b05c-4a72-b3db-9fc3374a97b6"

/dev/sdb4: UUID="1af13b6a-31f1-4956-9029-9808b575fd83" TYPE="crypto_LUKS" PARTLABEL="primary" PARTUUID="20e21a02-b2d8-4329-b573-a953820da813"

/dev/mapper/cr_usb-Generic-_USB3.0_CRW_-SD_201006010301-0:0-part3: UUID="L4TGG9-QIvI-D5ht-tDSN-GNsi-eT67-ZK3fAQ" TYPE="LVM2_member"

/dev/mapper/system-swap: UUID="86c90162-6935-47fd-8c0d-dac493754252" TYPE="swap"

/dev/mapper/system-root: UUID="a9a05197-2006-42fe-9373-1020ba1dcfb1" TYPE="ext4"

/dev/mapper/cr_usb-Generic-_USB3.0_CRW_-SD_201006010301-0:0-part4: UUID="c3uXhl-qGzA-bHpG-xxrZ-1xCR-ulur-yvCcF9" TYPE="LVM2_member"

Regards

Ulf