Partition formats that don’t work on antiX?

[Member Xecure]

Now that anticapitalista is fixing the issues with exfat partition formats, I think it is the best time to fix them all together, not only for exfat.

Did you experience problems with any USB or internal drive not mounting automatically? Do you need to mount these partitions from the terminal? DO they only mount as root?

Any experience will help. Please provide information so we can test and try figuring it out. We need:
– Device (if external or internal device, if USB, SD card or Sata/IDE connected, or if SSD through USB, if using a USB Hub, etc.).
– Partition format (exfat, fat32, ntfs, etc.). Size of partition.
– Kernel version you were using (you can see it with uname -r command).
– antiX version you were using (including flavor, example “antiX 19.2 32 bits – base”).
– Mounting method you tried (from file manager, if rox or spacefm, if expecting automount to work, terminal method, if you needed root permissions, etc.).
– If it is configured in /etc/fstab or not (very important).

Thanks for all those who can share their experience. Hopefully these issues can be fixed for the upcoming antiX 21 and maybe even for the current antiX 19.X release.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Moderator Brian Masinick]

Helpful

Up

0

::

Did you experience problems with any USB or internal drive not mounting automatically? Do you need to mount these partitions from the terminal? DO they only mount as root?

If I use a SanDisk Ultra Dual Drive 128 GB Type C USB drive, it works perfectly with my Dell Inspiron 5558. Therefore I do not suspect any USB drive issues, not with this hardware. I’ve also used other USB drives with this same hardware and they also work well.

I conclude that: 1) My system works fine with this release and so does my USB drive.

If, however, I take the exact same image and attempt to install it on some new hardware that I recently purchased, an Acer Aspire 5 Model A515-55 with a NVME SSD, I can’t get it to respond at the USB boot prompt. I find this odd because I’ve been able to install both Siduction 2021 and Debian Bullseye 11 on the Aspire with multiple different USB drives.

If it’s any consolation, I experience the exact same issue with MX Linux. I was able to install a fresh instance of the latest MX Linux 21 on my Dell Inspiron 5558 without any trouble, but both MX Linux and antiX won’t even show their boot menus on the Aspire. I have Debian, siduction, PCLinuxOS and Endeavor OS installed on it right now, and I was also able to get KDE Neon installed on the Aspire.

If you’d rather see this information elsewhere, let me know and I’ll copy the contents of this message, post it elsewhere and remove it here. For the moment, since you asked about it.

Details below:

Working system:

inxi -Fzx
System:    Host: mx-21 Kernel: 5.10.0-8-amd64 x86_64 bits: 64 compiler: N/A Desktop: Xfce 4.16.0 
           Distro: MX-21_beta1_x64 Wildflower July 27  2021 base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Dell product: Inspiron 5558 v: 01 serial: <filter> 
           Mobo: Dell model: 086DKN v: A00 serial: <filter> UEFI: Dell v: A04 date: 08/06/2015 
Battery:   ID-1: BAT0 charge: 33.9 Wh condition: 33.9/41.4 Wh (82%) 
           model: Samsung SDI DELL 07G07587587 status: Full 
CPU:       Topology: Dual Core model: Intel Core i7-5500U bits: 64 type: MT MCP arch: Broadwell 
           rev: 4 L2 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19153 
           Speed: 938 MHz min/max: 500/3000 MHz Core speeds (MHz): 1: 1273 2: 1296 3: 1288 
           4: 1251 
Graphics:  Device-1: Intel HD Graphics 5500 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 
           Device-2: NVIDIA GK208BM [GeForce 920M] vendor: Dell driver: N/A bus ID: 08:00.0 
           Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa Intel HD Graphics 5500 (BDW GT2) v: 4.6 Mesa 20.3.5 
           direct render: Yes 
Audio:     Device-1: Intel Broadwell-U Audio vendor: Dell driver: snd_hda_intel v: kernel 
           bus ID: 00:03.0 
           Device-2: Intel Wildcat Point-LP High Definition Audio vendor: Dell 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
           Device-3: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel v: kernel bus ID: 08:00.1 
           Sound Server: ALSA v: k5.10.0-8-amd64 
Network:   Device-1: Intel Wireless 3160 driver: iwlwifi v: kernel port: f040 bus ID: 06:00.0 
           IF: wlan0 state: up mac: <filter> 
           Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 
           v: kernel port: e000 bus ID: 07:00.0 
           IF: eth0 state: down mac: <filter> 
Drives:    Local Storage: total: 931.51 GiB used: 8.36 GiB (0.9%) 
           ID-1: /dev/sda vendor: Seagate model: ST1000LM024 HN-M101MBB size: 931.51 GiB 
Partition: ID-1: / size: 97.87 GiB used: 8.35 GiB (8.5%) fs: ext4 dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 54.0 C mobo: N/A sodimm: 38.0 C 
           Fan Speeds (RPM): cpu: 2200 
Info:      Processes: 195 Uptime: 24m Memory: 7.68 GiB used: 1.37 GiB (17.9%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 10.2.1 Shell: bash v: 5.1.4 inxi: 3.0.36 

Same information on the Aspire 5:

inxi -Fxz
System:    Kernel: 5.12.0-19.3-liquorix-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: Xfce 4.16.0 
           Distro: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Laptop System: Acer product: Aspire A515-55 v: V1.12 serial: <filter> 
           Mobo: IL model: Doc_IL v: V1.12 serial: <filter> UEFI: Insyde v: 1.12 date: 09/07/2020 
Battery:   ID-1: BAT1 charge: 50.1 Wh condition: 50.1/47.8 Wh (105%) model: LGC AP18C8K status: Full 
CPU:       Info: Dual Core model: Intel Core i3-1005G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 L2 cache: 4 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 9523 
           Speed: 1087 MHz min/max: 400/1201 MHz boost: enabled Core speeds (MHz): 1: 1087 2: 1160 3: 1196 4: 1199 
Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Acer Incorporated ALI driver: i915 v: kernel bus ID: 00:02.0 
           Device-2: Quanta HD User Facing type: USB driver: uvcvideo bus ID: 1-5:3 
           Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel 
           bus ID: 00:1f.3 
           Sound Server: ALSA v: k5.12.0-19.3-liquorix-amd64 
Network:   Device-1: Intel Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter driver: iwlwifi v: kernel port: 4000 
           bus ID: 00:14.3 
           IF: wlp0s20f3 state: up mac: <filter> 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Acer Incorporated ALI driver: r8169 
           v: kernel port: 3000 bus ID: 01:00.0 
           IF: enp1s0 state: down mac: <filter> 
Bluetooth: Device-1: Intel type: USB driver: btusb v: 0.8 bus ID: 1-10:5 
           Report: ID: hci0 state: up running bt-v: 3.0 lmp-v: 5.2 address: <filter> 
Drives:    Local Storage: total: 119.24 GiB used: 19.53 GiB (16.4%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLQ128HBHQ-00000 size: 119.24 GiB 
Partition: ID-1: / size: 28.7 GiB used: 19.52 GiB (68.0%) fs: ext4 dev: /dev/nvme0n1p4 
           ID-2: /boot/efi size: 97.5 MiB used: 4.2 MiB (4.3%) fs: vfat dev: /dev/nvme0n1p1 
Swap:      ID-1: swap-1 type: partition size: 2.93 GiB used: 0 KiB (0.0%) dev: /dev/nvme0n1p2 
Sensors:   System Temperatures: cpu: 46.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 194 Uptime: 5m Memory: 3.63 GiB used: 1.62 GiB (44.6%) Init: systemd runlevel: 5 Compilers: gcc: 10.2.1 
           Packages: 2193 Shell: Bash v: 5.1.8 inxi: 3.3.01 

• This reply was modified 1 year, 9 months ago by Brian Masinick. Reason: Adding information on system that won't boot antiX

--
Brian Masinick

[Member felipecardope]

Helpful

Up

0

::

Hello

ntfs-3g partition format, previously there was a Windows 7 installed.
Partition Size 149GB + 100MB
Kernel 4.9.235-antix.1-amd64-smp
version of antiX “antiX-19.3_x64-full”
The Hard Disk is mounted with Rox Filer as root.
Hard Disk is not mounted with SpaceFM as root.
Hard Disk is mounted with Disk Manager.
Mounted 149 GB on /media/923851C03851A3CF
Mounted 100 MB on /media/06344EFE344EF06B

Drives:
ID-1: /dev/sda vendor: Samsung model: HD161HJ 41R0186LEN size: 149.05 GiB

Olá

Formato de partição ntfs-3g, anteriormente havia um Windows 7 instalado.
Tamanho da partição 149 GB + 100 MB
Kernel 4.9.235-antix.1-amd64-smp
Versão do antiX “antiX-19.3_x64-full”
O Disco rígido é montado com o Rox Filer como root.
O Disco rígido não é montado com o SpaceFM como root.
O Disco rígido é montado com o Gerenciador de Disco.
Montado 149 GB em /media/923851C03851A3CF
Montado 100 MB em /media/06344EFE344EF06B

Drives:
ID-1: /dev/sda vendor: Samsung model: HD161HJ 41R0186LEN size: 149.05 GiB

felipecardope

[Member Xecure]

Helpful

Up

0

::

Thanks, felipe. I will be exploring ntfs during the day.
I think there is a missing allowed_options_ntfs option in the current configuration of udevil that makes it impossible to mount ntfs.

If you don’t mind, could you edit /etc/udevil/udevil.conf
sudo geany /etc/udevil/udevil.conf
Search for allowed_options_exfat, and just below it add this line:
allowed_options_ntfs = nosuid, noexec, nodev, noatime, fmask=0133, dmask=0022, uid=$UID, gid=$GID, umask=0077, namecase=*, ro, rw, sync, flush, utf8, remount, nonempty
Save and wait a second. Then, try to mount the internal ntfs partition as root on spacefm again.

Another thing you can do (it is not the recommended way, but it can easy users suffering) is to allow any user to mount internal drives (non-root). If you edit the same udevil file as before, search for # allowed_internal_devices, un-comment it and leave it looking like this:
allowed_internal_devices = *

This will let you mount all internal devices as your usual user without the need of root. This is OK on your personal configuration, but it is not recommended, as any users on your system would be able to mount your internal devices without any permissions and have access to your files.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member ex_Koo]

Helpful

Up

0

::

I install 19.4 on an Nvme drive from usb which I made with DD on ArchLabs. After partitioning the drive with gparted
Had no trouble at all booting from the usb to the desktop installer or installing.
After booting to the desktop had no internet needed to do the below to fix it.

There is a bug in the runit editions of antiX-19.4 (full and base) after installation via the gui installer.
Fix: As root user, remove all /etc/sv/* folders EXCEPT /etc/sv/getty-*   <<<<now I see errors on the tty boot screen but it works..

Had an update for connman which killed the internet. But your fix got it working again. (connman is an app name for this program, been painful right from the start.) Love you Ceni

Also updated the kernel to Linux antix19 5.10.52-antix.1-amd64-smp which fixed hardware issues.

So far have install a bunch from source code.
i3-gaps
rofi
mpd
ncmpcpp running as ncmpcpp-ueberzug
kitty

pip install
ueberzug

Can’t remember more.

System:    Kernel: 5.10.52-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: i3 4.19.1-138-g01a45d28 
           Distro: antiX-19.4-runit_x64-base Grup Yorum 21 May 2021 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop Mobo: ASUSTeK model: ROG STRIX B450-I GAMING v: Rev 1.xx serial: <filter> UEFI: American Megatrends 
           v: 4502 date: 07/13/2021 
CPU:       Info: 6-Core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2 rev: 0 cache: L2: 3 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 86405 
           Speed: 3598 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 3598 2: 3593 3: 3594 4: 3602 5: 3600 
           6: 3600 7: 3590 8: 3597 9: 3595 10: 3596 11: 3598 12: 3597 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5700 / 5700 XT] vendor: Sapphire Limited 
           driver: amdgpu v: kernel bus-ID: 09:00.0 
           Display: x11 server: X.Org 1.20.4 driver: loaded: amdgpu unloaded: fbdev resolution: 2560x1440~60Hz 
           OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio driver: snd_hda_intel v: kernel bus-ID: 09:00.1 
           Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus-ID: 0b:00.4 
           Device-3: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid bus-ID: 3-3:3 
           Sound Server-1: ALSA v: k5.10.52-antix.1-amd64-smp running: yes 
Network:   Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel port: d000 bus-ID: 04:00.0 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Realtek RTL8822BE 802.11a/b/g/n/ac WiFi adapter vendor: ASUSTeK driver: rtw_8822be v: N/A port: c000 
           bus-ID: 05:00.0 
           IF: wlan0 state: down mac: <filter> 
Bluetooth: Device-1: ASUSTek type: USB driver: btusb v: 0.8 bus-ID: 1-8:5 
           Report: rfkill ID: hci0 rfk-id: 1 state: down bt-service: not found rfk-block: hardware: no software: yes 
           address: see --recommends 
Drives:    Local Storage: total: 3.87 TiB used: 1.49 TiB (38.5%) 
           ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS500G3X0C-00SJG0 size: 465.76 GiB temp: 45.9 C 
           ID-2: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB 
           ID-3: /dev/sdb vendor: Seagate model: ST3000DM001-1CH166 size: 2.73 TiB 
           ID-4: /dev/sdc vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB 
Partition: ID-1: / size: 30.24 GiB used: 4.35 GiB (14.4%) fs: ext4 dev: /dev/nvme0n1p8 
           ID-2: /boot/efi size: 96 MiB used: 88.8 MiB (92.5%) fs: vfat dev: /dev/nvme0n1p1 
           ID-3: /home size: 78.3 GiB used: 1.69 GiB (2.2%) fs: ext4 dev: /dev/nvme0n1p3 
Swap:      ID-1: swap-1 type: partition size: 16 MiB used: 0 KiB (0.0%) dev: /dev/nvme0n1p2 
           ID-2: swap-2 type: partition size: 16.37 GiB used: 0 KiB (0.0%) dev: /dev/nvme0n1p11 
Sensors:   System Temperatures: cpu: 45.0 C mobo: 38.0 C gpu: amdgpu temp: 45.0 C 
           Fan Speeds (RPM): cpu: 1025 case-1: 712 gpu: amdgpu fan: 0 
           Power: 12v: 10.14 5v: N/A 3.3v: N/A vbat: 3.23 
Info:      Processes: 255 Uptime: 15m Memory: 31.34 GiB used: 1.27 GiB (4.1%) Init: runit runlevel: 2 Compilers: gcc: 8.3.0 
           Packages: 1589 Shell: Bash v: 5.0.3 inxi: 3.3.06 

• This reply was modified 1 year, 9 months ago by ex_Koo.

[Member felipecardope]

Helpful

Up

0

::

Obrigado Xecure, funcionaram muito bem as suas explicações.

Thanks Xecure, your explanations worked very well.

felipecardope

[Member Xecure]

Helpful

Up

0

::

Thanks for the feedback, @felipecardope. I will suggest adding this line for ntfs to the next udevil package build.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member marcelocripe]

Helpful

Up

0

::

Hello Xecure.

In one of the antiX hard drive installations, the antiX-19.4_x64-full.iso ISO with kernel 4.9.0.264 failed to detect the Seagate Barracuda 1TB hard drive (described below). At the time, I didn’t have the antiX-19.4_x64-full.iso ISO with kernel 4.19.184 on my USB device prepared with Ventoy in order to test whether kernel 4.19.184 would detect the hard drive or not. However, I had one of your builds, the pseudo-antiX-19.3_x64.iso ISO with kernel 5.8.16 managed to detect the hard drive and so I managed to install antiX. As I do not know this information may or may not be related to the topic of this topic, when in doubt, I decided to share this experience anyway.

Asus H61M-A/BR Rev X.0x motherboard, with Seagate Barracuda 1TB hard drive, only “pseudo-antiX-19.3_x64.iso” ISO with 5.8.16 kernel could detect the hard drive:

HD Seagate Barracuda 1TB
ST 1000DM010
SN: Z9AE77WR
PN: 2EP102-300
FW: CC43
WWN: 5000C500A3346FEC
PSID: ZT33HH84WHJYYYP4NN5F7RTCLE8SMCJ3
DOM: 28JUN2017

marcos@antix1:~
$ inxi -Fnz

Drives:
Local Storage: total: 946.16 GiB used: 28.3 MiB (0.0%)
ID-1: /dev/sda vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB
ID-2: /dev/sdb type: USB model: N/A size: 14.65 GiB

marcelocripe

– – – – –

Olá Xecure.

Em uma das instalações do antiX em disco rígido, a ISO antiX-19.4_x64-full.iso com kernel 4.9.0.264 não conseguiu detectar o disco rígido Seagate Barracuda 1TB (descrito abaixo do texto em idioma Inglês). Na ocasião, eu não tinha a ISO antiX-19.4_x64-full.iso com kernel 4.19.184 no meu dispositivo USB preparado com o Ventoy para poder testar se com o kernel 4.19.184 iria detectar ou não o disco rígido. Contudo, eu estava com uma das suas construções, a ISO pseudo-antiX-19.3_x64.iso com kernel 5.8.16 conseguiu detectar o disco rígido e assim eu consegui instalar o antiX. Como eu não sei esta informação pode estar relacionada ou não ao tema deste tópico, na dúvida, eu resolvi compartilhar mesmo assim esta experiência.

Placa-mãe Asus H61M-A/BR Rev X.0x, com disco rígido Seagate Barracuda 1TB, somente a ISO “pseudo-antiX-19.3_x64.iso” com kernel 5.8.16 conseguiu detectar o disco rígido:

marcelocripe

[Member Xecure]

Helpful

Up

0

::

It is not exactly related to partition formats. You are saying that the installer didn’t recognize the Hard drive. Is this in Gparted? Or the installer itself?
These kind of events are way over my head. Device detection vs partition detection and mounting are very different topics, so I cannot suggest anything here.
If gparted couldn’t see it either then it is possibly related to a boot parameter (like failsafe) or a HD setting in BIOS (AHCI vs SATA).
I don’t think we can figure this out here, unfortunately.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member marcelocripe]

Helpful

Up

0

::

It is not necessary to Xecure any kind of work in this case, as the computer is working fine with the pseudo-antiX-19.3_x64.iso ISO with the 5.8.16 kernel you built. The installer really didn’t detect the hard drive, as well as it wasn’t detected by Gparted, SpaceFM, Rox Filer and Disk Manager. Sorry for bringing a case that is unrelated to the topic of the topic.

– – – – –

Não é necessário Xecure qualquer tipo de trabalho neste caso, pois o computador está funcionando muito bem com a ISO pseudo-antiX-19.3_x64.iso com kernel 5.8.16 que você construiu. Realmente o instalador não detectou o disco rígido, bem como não foi detectado pelo Gparted, SpaceFM, Rox Filer e o Gerenciador de Disco. Desculpe-me por trazer um caso que não está relacionado com o tema do tópico.

marcelocripe

[Author]

Posts