#Help accessing other drives

27 messages · Page 1 of 1 (latest)

ocean canyon
#
mount: /mnt/ssd250: unknown filesystem type 'ntfs'.
       dmesg(1) may have more information after failed mount system call.```
spice surge
#

I realized I have the ntfs-3g package and that was needed in the past, but apparently now there is a newer way supported in more recent kernels.

#

mount -t ntfs3 /dev/sda1 /mnt/ssd250
It seems specifying the type as ntfs3 is enough. There's further troubleshooting in the link.

steep ice
ocean canyon
#

ty, i ended up using the ntfs package. 1 more question though, now i'm trying to set it up in fstab but after rebooting, it went into emergency mode and said soemthing about disk dependencies not being met

#

i commented out the 2 lines where i was trying to mount my other drives. not sure if i have to change defaults to something to include support for ntfs?

steep ice
#

the ones you commented out should say ntfs3 instead of NTFS I believe

ocean canyon
#

i'd have to reboot agin

#

lemme try changing the filesystem first

sick kettle
#

U format it properly, check ur fstab

ocean canyon
#

hmm ok it mounted one of my disks, not the other though lol

sick kettle
#

Lsblk blkid and fstab plz

ocean canyon
#

UUID=2CFA503CFA50050C should correspond to sda1, right?

#

sry let me send it as text

#
[rin@summit ~]$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0 223.6G  0 disk 
└─sda1        8:1    0 223.6G  0 part /mnt/SSD250
sdb           8:16   0 931.5G  0 disk 
├─sdb1        8:17   0    16M  0 part 
└─sdb2        8:18   0 931.5G  0 part /mnt/HDD
zram0       254:0    0     4G  0 disk [SWAP]
nvme0n1     259:0    0 465.8G  0 disk 
├─nvme0n1p1 259:1    0   511M  0 part /boot
└─nvme0n1p2 259:2    0 465.3G  0 part /
[rin@summit ~]$ sudo blkid
[sudo] password for rin: 
/dev/nvme0n1p1: UUID="ACBA-7F55" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="primary" PARTUUID="82227b10-51eb-4870-a5c1-0dec32594f38"
/dev/nvme0n1p2: UUID="2abb4df0-84c1-4046-9187-419bb28ed0c9" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="primary" PARTUUID="bf7f6cbe-12ce-4337-a64c-b296ea703e9d"
/dev/sdb2: LABEL="New Volume" BLOCK_SIZE="512" UUID="AA4EF07E4EF0449B" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="810d78da-3590-4ea7-91d3-d59d231145df"
/dev/sdb1: PARTLABEL="Microsoft reserved partition" PARTUUID="140135a1-a7a5-4557-8e1a-c677afcc68d1"
/dev/sda1: LABEL="SSD" BLOCK_SIZE="512" UUID="2CFA503CFA50050C" TYPE="ntfs" PARTUUID="b133db2b-01"
/dev/zram0: LABEL="zram0" UUID="05e86427-b382-4e0f-8227-a2426df48657" TYPE="swap"
[rin@summit ~]$ cat /etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/nvme0n1p2
UUID=2abb4df0-84c1-4046-9187-419bb28ed0c9    /             ext4          rw,relatime    0 1

# /dev/nvme0n1p1
UUID=ACBA-7F55          /boot         vfat          rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro    0 2

UUID=2CFA503CFA50050C   /mnt/SSD250    ntfs-3g        permissions,locale=en_US.utf8        0 2

UUID=AA4EF07E4EF0449B   /mnt/HDD       ntfs-3g        permissions,locale=en_US.utf8        0 2
sick kettle
#

blkid as well

ocean canyon
#

it's there in the middle

#
/dev/nvme0n1p1: UUID="ACBA-7F55" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="primary" PARTUUID="82227b10-51eb-4870-a5c1-0dec32594f38"
/dev/nvme0n1p2: UUID="2abb4df0-84c1-4046-9187-419bb28ed0c9" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="primary" PARTUUID="bf7f6cbe-12ce-4337-a64c-b296ea703e9d"
/dev/sdb2: LABEL="New Volume" BLOCK_SIZE="512" UUID="AA4EF07E4EF0449B" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="810d78da-3590-4ea7-91d3-d59d231145df"
/dev/sda1: LABEL="SSD" BLOCK_SIZE="512" UUID="2CFA503CFA50050C" TYPE="ntfs" PARTUUID="b133db2b-01"
/dev/zram0: LABEL="zram0" UUID="05e86427-b382-4e0f-8227-a2426df48657" TYPE="swap"
#

OH i'm sorry it did work, i had a leftover dir from earlier called ssd250 and i was checking that facepalm

#

the capilization was off, mb

sick kettle
#

im outside on phone, but I’m sure there’s sth misconfigured on ur fstab or somewhere else

#

U might wanna regen ur fstab and reimplement ur idk I’m assuming it’s auto mount following aw

#

.aw fstab