NTFS-3G and bitlocker drive formats

[Ed_P]

I got a new Dell notebook for Christmas and while I can boot Porteus from a USB drive on it I can't access files on the SSD drive due to them being NTFS-3G and bitlocker formats!

Does Porteus support NTFS-3G and if so, how? How about bitlocker's function bd_crypto_bitlk_open?

Can GParted safely shrink a NTFS-3G or bitlocker drive?

[ncmprhnsbl]

um, NTFG-3G? is that a thing? afaia it's NTFS and ntfs-3g is the linux utility for accessing it ..(which mount calls upon)
accessing bitlocked partions seems to require special apps ... eg. this one claims to do the trick: https://www.easyuefi.com/bitlocker-for- ... linux.html
another: https://www.ceos3c.com/open-source/open ... ive-linux/ using dislocker: https://slackbuilds.org/repository/14.2 ... =dislocker

not sure what the consequences of just turning off the bitlocker from inside windows is... which would have to be done, at least temporarily, to shrink the partition..
this talks about doing that: https://www.ctrl.blog/entry/dual-boot-b ... evice.html

[Ed_P]

Oops. I misspelled the error. NTFS-3G not NTFG-3G.

This is what I see with Porteus when I try to access the drive with Nemo and GParted.


Thank you for the links ncmp, I will definitely check them out.

On all my other systems I've added a partition for Data and when possible 1 for Backups, with this system the drive is only 256 GB. My older Dell has a 1 TB SSD.

[beny]

hi Ed_P i think you have a nvme hard disk, this is a porteus kernel config:5.16-rc7

# NVME Support
#
CONFIG_NVME_CORE=y
CONFIG_BLK_DEV_NVME=y
# CONFIG_NVME_MULTIPATH is not set
CONFIG_NVME_HWMON=y
CONFIG_NVME_FABRICS=m
CONFIG_NVME_FC=m
# CONFIG_NVME_TCP is not set
CONFIG_NVME_TARGET=m
# CONFIG_NVME_TARGET_PASSTHRU is not set
CONFIG_NVME_TARGET_LOOP=m
CONFIG_NVME_TARGET_FC=m
CONFIG_NVME_TARGET_FCLOOP=m
# CONFIG_NVME_TARGET_TCP is not set
# end of NVME Support
and there is also a slackware nvme-tools cli,btw dislocker is ok,for more information see this link https://wiki.archlinux.org/title/Solid_state_drive/NVMe
i forget this, paragon ntfs driver are now part of the linux kernel:
DOS/FAT/EXFAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_FAT_DEFAULT_UTF8=y
CONFIG_EXFAT_FS=y
CONFIG_EXFAT_DEFAULT_IOCHARSET="utf8"
CONFIG_NTFS_FS=y
# CONFIG_NTFS_DEBUG is not set
CONFIG_NTFS_RW=y
CONFIG_NTFS3_FS=y
# CONFIG_NTFS3_64BIT_CLUSTER is not set
CONFIG_NTFS3_LZX_XPRESS=y
CONFIG_NTFS3_FS_POSIX_ACL=y
# end of DOS/FAT/EXFAT/NT Filesystems

[Ed_P]

Thank you Beny.

hi Ed_P i think you have a nvme hard disk, this is a porteus kernel config:5.16-rc7

I agree. I'm running a 5.15.1 kernel, when did Porteus add the nvme support?

I normally only upgrade to Blaze's kernels. And I don't have any problems with Porteus accessing the SSD I put in my older Dell notebook.

[Ed_P]

accessing bitlocked partions seems to require special apps ... eg. this one claims to do the trick: https://www.easyuefi.com/bitlocker-for- ... linux.html

Well I tried it, bitlocker-anywhere-linux.tar.gz, but didn't get far.

Code: Select all

guest@porteus:/mnt/sda1/My_Files/newpc/bitlocker-anywhere/bin$ ./run.sh
Password: 
This application failed to start because it could not find or load the Qt platform plugin "xcb"
in "".

Available platform plugins are: xcb.

Reinstalling the application may fix this problem.
/mnt/sda1/My_Files/newpc/bitlocker-anywhere/bin/setenv.sh: line 13:  1805 Aborted                 ${APPDIR}/BitLockerAnywhere
guest@porteus:/mnt/sda1/My_Files/newpc/bitlocker-anywhere/bin$ echo $BASH_SOURCE
 
guest@porteus:/mnt/sda1/My_Files/newpc/bitlocker-anywhere/bin$ echo $APPDIR

guest@porteus:/mnt/sda1/My_Files/newpc/bitlocker-anywhere/bin$ 

There is an xcb file in the bitlocker-anywhere/bin folder.

Code: Select all

guest@porteus:/mnt/sda1/My_Files/newpc/bitlocker-anywhere/bin$ ls *xcb*
libxcb-xinerama.so.0*
guest@porteus:/mnt/sda1/My_Files/newpc/bitlocker-anywhere/bin$ 

There's a SetupApp file in the bitlocker-anywhere/bin folder also but it didn't run when I tried it.

Code: Select all

guest@porteus:/mnt/sda1/My_Files/newpc/bitlocker-anywhere/bin$ ls S*
SetupApp*  SetupApp.log*
guest@porteus:/mnt/sda1/My_Files/newpc/bitlocker-anywhere/bin$ 

Code: Select all

guest@porteus:/mnt/sda1/My_Files/newpc/bitlocker-anywhere/bin$ SetupApp
bash: SetupApp: command not found
guest@porteus:/mnt/sda1/My_Files/newpc/bitlocker-anywhere/bin$ 

Added in 4 hours 39 minutes 19 seconds:
Tried another one.

using dislocker: https://slackbuilds.org/repository/14.2 ... =dislocker

Code: Select all

guest@porteus:~/Downloads/dislocker$ ls
README  dislocker.SlackBuild*  dislocker.info  slack-desc
guest@porteus:~/Downloads/dislocker$ ./dislocker.SlackBuild
tar: /home/guest/Downloads/dislocker/dislocker-0.7.1.tar.gz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
guest@porteus:~/Downloads/dislocker$  

Added in 20 minutes 26 seconds:
Finally

another: https://www.ceos3c.com/open-source/open ... ive-linux/

First, we need to install Dislocker. It doesn’t get any easier than that.

sudo apt-get install dislocker

Code: Select all

guest@porteus:~$ sudo apt-get dislocker
Password: 
sudo: apt-get: command not found
guest@porteus:~$ 

[ncmprhnsbl]

Tried another one.

ncmprhnsbl wrote: ↑
05 Jan 2022, 08:33
using dislocker: https://slackbuilds.org/repository/14.2 ... =dislocker

Code: Select all

guest@porteus:~/Downloads/dislocker$ ls
README  dislocker.SlackBuild*  dislocker.info  slack-desc
guest@porteus:~/Downloads/dislocker$ ./dislocker.SlackBuild
tar: /home/guest/Downloads/dislocker/dislocker-0.7.1.tar.gz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
guest@porteus:~/Downloads/dislocker$

to use a SlackBuild:
have a look at the dislocker.info file, there's a download link for the source,, so first:

Code: Select all

wget https://github.com/Aorimn/dislocker/archive/v0.7.1/dislocker-0.7.1.tar.gz

there' also a link on the SBO page if you want to download with your browser... the source archive should be put in the same directory as the slackbuild..
but first, it also says: REQUIRES="mbedtls"
so that will need to be built first https://slackbuilds.org/repository/14.2 ... s/mbedtls/ and install it before building dislocker..
also: activate 05-devel and run the slackbuild as root. and resulting package, if successful will be in /tmp

and yes apt-get is useless outside of the debian universe..

[Ed_P]

to use a SlackBuild:
have a look at the dislocker.info file, there's a download link for the source,, so first:

Thank you ncmp.

I had looked at the dislocker.info file but thought the SlackBuild file would download the DOWNLOAD file.

So I downloaded the dislocker-0.7.1.tar.gz file, and put it in the dislocker folder. I then downloaded the mbedtls file, mbedtls.tar.gz, and put it in the dislocker folder. I also extracted it to a mbedtls folder in the dislocker folder. It's info file had a DOWNLOAD for mbedtls-mbedtls-2.16.8.tar.gz so I downloaded it to the dislocker folder and extracted it to a mbedtls-mbedtls-2.16.8.tar folder in the dislocker folder.

Code: Select all

guest@porteus:/mnt/sda1/My_Files/newpc/dislocker$ ls
README*                         dislocker-0.7.1.tar.gz*
dislocker.SlackBuild*           dislocker.info*
mbedtls/                        mbedtls-mbedtls-2.16.8/
mbedtls-mbedtls-2.16.8.tar.gz*  mbedtls.tar.gz*
slack-desc*
guest@porteus:/mnt/sda1/My_Files/newpc/dislocker$ 

The USB install is lacking the 05-devel module so I have to remove the drive and put it in my old notebook and copy it from there.

When I get back I will try the mbedtls install. In that I don't think I've ever done an install in Porteus, I'm a module person, I will have more questions.

[beny]

hi Ed_P here you have dislocker and mbedtls: https://www.mediafire.com/folder/zyug3gvg7fhu5/dslocker

[Ed_P]

Thank you beny.

As for my storytale:

I activated 05-devel.xzm.
I attempted to build mbedtls in the /dislocker/mbedtls folder and got:

Code: Select all

tar: /mnt/sdb1/My_Files/newpc/dislocker/mbedtls/mbedtls-mbedtls-2.16.8.tar.gz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now

So I moved the /dislocker/mbedtls-mbedtls-2.16.8.tar.gz file to the /dislocker/mbedtls folder and got:

Code: Select all

chown: changing ownership of './visualc/VS2010/zeroize.vcxproj': Operation not permitted
chown: changing ownership of './visualc/VS2010/udp_proxy.vcxproj': Operation not permitted
chown: changing ownership of './visualc/VS2010/strerror.vcxproj': Operation not permitted
chown: changing ownership of './visualc/VS2010/ssl_server2.vcxproj': Operation not permitted
chown: changing ownership of './visualc/VS2010/ssl_server.vcxproj': Operation not permitted
chown: changing ownership of './visualc/VS2010/ssl_mail_client.vcxproj': Operation not permitted
chown: changing ownership of
  :
  :
  :
chown: changing ownership of './.github/issue_template.md': Operation not permitted
chown: changing ownership of './.github': Operation not permitted
chown: changing ownership of '.': Operation not permitted

I determined my error and attempted to build mbedtls again and got:

Code: Select all

guest@porteus:/mnt/sdb1/My_Files/newpc/dislocker/mbedtls$ su
Password: 
root@porteus:/mnt/sdb1/My_Files/newpc/dislocker/mbedtls# ./*.SlackBuild
mbedtls-mbedtls-2.16.8/
mbedtls-mbedtls-2.16.8/.github/
mbedtls-mbedtls-2.16.8/.github/issue_template.md
  :
  :
  :
    Building C object CMakeFiles/cmTC_244bb.dir/testCCompiler.c.o
    /usr/bin/cc   -O2 -fPIC  -o CMakeFiles/cmTC_244bb.dir/testCCompiler.c.o -c /tmp/SBo/mbedtls-mbedtls-2.16.8/build/CMakeFiles/CMakeTmp/testCCompiler.c
    as: error while loading shared libraries: libbfd-2.33.1-slack15.so: cannot open shared object file: No such file or directory
    gmake[1]: *** [CMakeFiles/cmTC_244bb.dir/build.make:85: CMakeFiles/cmTC_244bb.dir/testCCompiler.c.o] Error 1
    gmake[1]: Leaving directory '/tmp/SBo/mbedtls-mbedtls-2.16.8/build/CMakeFiles/CMakeTmp'
    gmake: *** [Makefile:140: cmTC_244bb/fast] Error 2
    
    

  

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:5 (project)


-- Configuring incomplete, errors occurred!
See also "/tmp/SBo/mbedtls-mbedtls-2.16.8/build/CMakeFiles/CMakeOutput.log".
See also "/tmp/SBo/mbedtls-mbedtls-2.16.8/build/CMakeFiles/CMakeError.log".
root@porteus:/mnt/sdb1/My_Files/newpc/dislocker/mbedtls# 

CMakeOutput.log

Code: Select all

The system is: Linux - 5.15.1-porteus - x86_64

CMakeError.log

Code: Select all

Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
Compiler: /usr/bin/cc 
Build flags: -O2;-fPIC
Id flags:  

The output was:
1
as: error while loading shared libraries: libbfd-2.33.1-slack15.so: cannot open shared object file: No such file or directory


Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
Compiler: /usr/bin/cc 
Build flags: -O2;-fPIC
Id flags: -c 

The output was:
1
as: error while loading shared libraries: libbfd-2.33.1-slack15.so: cannot open shared object file: No such file or directory


Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
Compiler: /usr/bin/cc 
Build flags: -O2;-fPIC
Id flags: -Aa 
  :
  :
  :
Checking whether the C compiler is IAR using "" did not match "IAR .+ Compiler":
cc: fatal error: no input files
compilation terminated.
Detecting C compiler ABI info failed to compile with the following output:
Change Dir: /tmp/SBo/mbedtls-mbedtls-2.16.8/build/CMakeFiles/CMakeTmp

Run Build Command(s):/usr/bin/gmake cmTC_b2538/fast && /usr/bin/gmake  -f CMakeFiles/cmTC_b2538.dir/build.make CMakeFiles/cmTC_b2538.dir/build
gmake[1]: Entering directory '/tmp/SBo/mbedtls-mbedtls-2.16.8/build/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_b2538.dir/CMakeCCompilerABI.c.o
/usr/bin/cc   -O2 -fPIC  -o CMakeFiles/cmTC_b2538.dir/CMakeCCompilerABI.c.o -c /usr/share/cmake-3.18/Modules/CMakeCCompilerABI.c
as: error while loading shared libraries: libbfd-2.33.1-slack15.so: cannot open shared object file: No such file or directory
gmake[1]: *** [CMakeFiles/cmTC_b2538.dir/build.make:85: CMakeFiles/cmTC_b2538.dir/CMakeCCompilerABI.c.o] Error 1
gmake[1]: Leaving directory '/tmp/SBo/mbedtls-mbedtls-2.16.8/build/CMakeFiles/CMakeTmp'
gmake: *** [Makefile:140: cmTC_b2538/fast] Error 2




Determining if the C compiler works failed with the following output:
Change Dir: /tmp/SBo/mbedtls-mbedtls-2.16.8/build/CMakeFiles/CMakeTmp

Run Build Command(s):/usr/bin/gmake cmTC_244bb/fast && /usr/bin/gmake  -f CMakeFiles/cmTC_244bb.dir/build.make CMakeFiles/cmTC_244bb.dir/build
gmake[1]: Entering directory '/tmp/SBo/mbedtls-mbedtls-2.16.8/build/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_244bb.dir/testCCompiler.c.o
/usr/bin/cc   -O2 -fPIC  -o CMakeFiles/cmTC_244bb.dir/testCCompiler.c.o -c /tmp/SBo/mbedtls-mbedtls-2.16.8/build/CMakeFiles/CMakeTmp/testCCompiler.c
as: error while loading shared libraries: libbfd-2.33.1-slack15.so: cannot open shared object file: No such file or directory
gmake[1]: *** [CMakeFiles/cmTC_244bb.dir/build.make:85: CMakeFiles/cmTC_244bb.dir/testCCompiler.c.o] Error 1
gmake[1]: Leaving directory '/tmp/SBo/mbedtls-mbedtls-2.16.8/build/CMakeFiles/CMakeTmp'
gmake: *** [Makefile:140: cmTC_244bb/fast] Error 2

Development work is tedious. I don't know how you guys do it, but Thank You for doing it.

Now to see what beny sent me.

Added in 35 minutes 33 seconds:
I booted the new notebook, I activated the mbedtls and dislocker modules beny posted tried to access the bitlocker drive and got this:


Added in 8 minutes 28 seconds:
Tried a different approach.

Code: Select all

guest@porteus:~$ dislocker -V nvme0n1p3
Tue Jan 11 16:12:30 2022 [CRITICAL] Failed to open nvme0n1p3: No such file or directory
guest@porteus:~$ dislocker -V /dev/nvme0n1p3
Tue Jan 11 16:13:20 2022 [CRITICAL] Failed to open /dev/nvme0n1p3: Permission denied
guest@porteus:~$ dislocker -V /dev/nvme0n1p3 -u[Dell]
Tue Jan 11 16:14:43 2022 [CRITICAL] Failed to open /dev/nvme0n1p3: Permission denied
guest@porteus:~$ dislocker -V /dev/nvme0n1p3 -u=[Dell]
Tue Jan 11 16:15:39 2022 [CRITICAL] Failed to open /dev/nvme0n1p3: Permission denied
guest@porteus:~$ dislocker -V /dev/nvme0n1p3 -user-password=[Dell]
Tue Jan 11 16:16:07 2022 [CRITICAL] Failed to open /dev/nvme0n1p3: Permission denied
guest@porteus:~$ 

Maybe a different problem I need to resolve.

[beny]

hi Ed_P guest user with bitlocker? sudo dislocker -r -V /dev/nvme0n1p3 -uYourPassword -- /media/bitlocker well media bitlocker is a directory where you mount the encripted disk

[ncmprhnsbl]

ah yes, ponces repo to the rescue..
have a read of this: https://linux.die.net/man/1/dislocker (especially the examples section..provided it's up to date)
the whole bitlocker thing seems like a bit of a pain...

[beny]

yes ponce slackbuild sbo-git and yes bitlocker is a pain without gui.

[Ed_P]

Thanks guys.

the whole bitlocker thing seems like a bit of a pain...

No "seems" about it, it is a royal pain. Searching Google for how to disable it has me going through Windows menus in circles. I can't disable it for the same reason I can't connect to it with dislocker, I don't know the password. Writing to Dell for help made the problem even more annoying. They said software support would cost $99. Will never buy, or receive, another Dell.

Added in 1 hour 17 minutes 55 seconds:
Update
Finally figured out how to turn bitlocker off for the C: drive.

Porteus now has access to it.

Unable to access the other nvme0 drives though other than nvme0n1p1 which is the ESP drive.

Added in 9 hours 12 minutes 17 seconds:

[beny]

hi, glad that you have solved,and the software dislocker work well... seem that you have trouble with the ntfs3 driver take a look at the permission of the ntfs3 bin, only root can read and write, root group in slackware nothing, and also other group the same nothing.