usb storage always getting unmounted each time i power on the pc

C

corporal_Canada

Member
Joined
Jun 8, 2021
Messages
102
Reaction score
16
Credits
717
hi, im Chris from the french part of Canada... but i currently reside in the Philippines for many reasons, primarily to be close to my amazing daughter, please forgive my imperfect englishg and lack of punctuation.

i have a mini pc... hp t620 i think, came with windows 10.. but only a tiny storage.. like 128gb.. kinda looks like an nvme.. i installed Pop!OS because im fond of how easy and comfortable it is to use.. i have 3 small hdd or ssd all connected via usb with stuff on it... NOTHING illegal.. im Canadian after all, so.. each time i reboot.. 1 or 2 usb storage is no longer mounted... is it becaue it was NTFS to begin with ? and linux is slowly edging me to go towards ext4 ??? when i try to mount it sais unable to mount and i think it once had the word "quark"... welp.. formatting my 512gb ssd now to copy some tiny things so that i "might" carry over to windows 10.. which im downloading now

i understand electricity is "different" here but i did plop down 300$cad for a beefy UPS and a good one, usually these things have a good AVR

the mini pc is a AMD dual core apu, came withg 4gb of laptop ram, im crazy glued in 16 gb for fun
 


corporal_Canada said:
1 or 2 usb storage is no longer mounted... is it becaue it was NTFS to begin with ?
Click to expand...
Hi, please reboot system with external storage medias plugged in to reproduce the problem, then upon reboot run:
Bash: 
sudo dmesg | grep -e mount -e ERROR
and share output here.

Please also post output of each of:
Bash: 
cat /etc/fstab
sudo blkid
lsblk
 
CaffeineAddict said:
Hi, please reboot system with external storage medias plugged in to reproduce the problem, then upon reboot run:
Bash: 
sudo dmesg | grep -e mount -e ERROR
and share output here.

Please also post output of each of:
Bash: 
cat /etc/fstab
sudo blkid
lsblk
Click to expand...
okay, will do.. but im kinda formatting my 512gb ssd into fat, it says 7 hours remaining, i guess quickformat is not a thing in linux... please be patient
 
I routinely format TB and 2TB disks in a few seconds.
I personally wouldn't use FAT on 512GB, I would use exFat as Fat32 has partition and file size limitations.
 
currently 1800 on this side of the world.. 5 minutes remaining and i will type out those commands in the terminal with all 3 usb storage's plugged in
 
dos2unix said:
I routinely format TB and 2TB disks in a few seconds.
I personally wouldn't use FAT on 512GB, I would use exFat as Fat32 has partition and file size limitations.
Click to expand...
good idea, i only saw ext4, ntfs and fat as format options...

maybe it was fat32, tbh im not entirely sober at all times, but im somewhat functional
 
chris@pop-os:~/Desktop$ sudo dmesg | grep -e mount -e ERROR
[ 43.488214] EXT4-fs (dm-1): mounted filesystem 181a87d7-62a7-48ec-8f6d-fbfd9ec5f100 ro with ordered data mode. Quota mode: none.
[ 44.831858] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 45.026391] systemd[1]: Starting Remount Root and Kernel File Systems...
[ 45.123696] EXT4-fs (dm-1): re-mounted 181a87d7-62a7-48ec-8f6d-fbfd9ec5f100 r/w. Quota mode: none.
[ 45.152929] systemd[1]: Finished Remount Root and Kernel File Systems.
[ 47.899360] FAT-fs (sdc2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 47.965462] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 130.087107] EXT4-fs (sdb1): mounted filesystem aabe7686-6522-4571-9237-8f55e5902daf r/w with ordered data mode. Quota mode: none.

chris@pop-os:~/Desktop$ cat /etc/fstab
sudo blkid
lsblk
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
PARTUUID=acb1724e-f403-400e-b4a2-043757b42167 /boot/efi vfat umask=0077 0 0
PARTUUID=8583e168-30af-421e-b513-67cf0eee90d2 /recovery vfat umask=0077 0 0
/dev/mapper/cryptswap none swap defaults 0 0
UUID=181a87d7-62a7-48ec-8f6d-fbfd9ec5f100 / ext4 noatime,errors=remount-ro 0 1
/dev/mapper/cryptdata: UUID="E0PCu2-U22t-FZYZ-hsYF-v9Y4-Hi7g-Qvk0WD" TYPE="LVM2_member"
/dev/mapper/data-root: UUID="181a87d7-62a7-48ec-8f6d-fbfd9ec5f100" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdd1: LABEL_FATBOOT="512gb" LABEL="512gb" UUID="AB92-C418" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="0ca8d95f-01"
/dev/sdb1: LABEL="240gb ssd" UUID="aabe7686-6522-4571-9237-8f55e5902daf" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="64a330a3-01"
/dev/mapper/cryptswap: LABEL="cryptswap" UUID="3abc6fdf-eb98-46fe-85f6-2a974650a238" TYPE="swap"
/dev/sdc2: UUID="63D5-3029" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="recovery" PARTUUID="8583e168-30af-421e-b513-67cf0eee90d2"
/dev/sdc3: UUID="5687fac5-84fd-4e7e-aa5e-70da7af29c3c" TYPE="crypto_LUKS" PARTUUID="19564cf1-f030-4c34-bc78-895fb2469aeb"
/dev/sdc1: UUID="63D4-1DDD" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="acb1724e-f403-400e-b4a2-043757b42167"
/dev/sdc4: UUID="e5a02609-7896-40f3-ade5-7e9e21596892" TYPE="swap" PARTUUID="5735d0ee-b106-4c3a-b756-fccd6cfe321b"
/dev/sda2: LABEL="D:\\" BLOCK_SIZE="512" UUID="50741ED5741EBE22" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="985a2056-ecb1-4be3-beb2-634d8b8bb4ea"
/dev/sda1: UUID="E3DD-14E8" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="4a863ae1-b254-46eb-bf3e-dd65f941d5b3"
/dev/zram0: UUID="df84f823-e173-45d6-a11f-2c6bd4d6bc5b" TYPE="swap"
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 298.1G 0 disk
├─sda1 8:1 0 1022M 0 part
└─sda2 8:2 0 297.1G 0 part
sdb 8:16 0 223.6G 0 disk
└─sdb1 8:17 0 223.6G 0 part /media/chris/240gb ssd
sdc 8:32 0 119.2G 0 disk
├─sdc1 8:33 0 1022M 0 part /boot/efi
├─sdc2 8:34 0 4G 0 part /recovery
├─sdc3 8:35 0 110.2G 0 part
│ └─cryptdata 252:0 0 110.2G 0 crypt
│ └─data-root 252:1 0 110.2G 0 lvm /
└─sdc4 8:36 0 4G 0 part
└─cryptswap 252:2 0 4G 0 crypt [SWAP]
sdd 8:48 0 476.9G 0 disk
└─sdd1 8:49 0 476.9G 0 part /media/chris/512gb
zram0 251:0 0 15.1G 0 disk [SWAP]
 
Your output of cat /etc/fstab and sudo blkid is mixed up and hard to read because you didn't run then one by one but all at once.

D:\ can't be automounted because it needs to be set in fstab
blkid says it's /dev/sda2 first but then system reports it as /dev/sde2 because device names are not persistent across reboots, therefore it needs to be set by UUID in fstab

Example:
Run commands one by one:
Bash: 
sudo mkdir /media/chris/Ddrive
sudo nano /etc/fstab

Paste the following at the end of nano editor in terminal that opens:
UUID=50741ED5741EBE22 /media/chris/Ddrive ntfs auto,user,noexec,async,rw,nofail 0 2

Press CTRL+O followed by CTRL+X to save.

Run one by one:
Bash: 
sudo systemctl daemon-reload
mount -a

And the drive should be accessible from file explorer (mounted at /media/chris/Ddrive)
It should also auto mount on boot.
 
corporal_Canada said:
[ 47.899360] FAT-fs (sdc2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 47.965462] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Click to expand...
Two FAT filesystems (likely on USB drives) were not properly unmounted..

You need to first unmount them:
Bash: 
sudo umount /dev/sdc1
sudo umount /dev/sdc2

Then run fsck for each (with -y flag to say yes for each prompt to fix the filesystem):
Bash: 
sudo fsck -y /dev/sdc1
sudo fsck -y /dev/sdc2

...Remember, while ext4 is generally preferred for Linux systems, NTFS is still perfectly usable. The mounting issues you're experiencing are likely not related to the filesystem type but rather to how the system is handling USB devices on boot.

You can use udisks2 and udiskie for automatic usb drive mounting:
How To: Easy USB Mounting On Linux With Udisks2 And Udiskie
 
Freepoorman said:
Two FAT filesystems (likely on USB drives) were not properly unmounted..

You need to first unmount them:
Bash: 
sudo umount /dev/sdc1
sudo umount /dev/sdc2

Then run fsck for each (with -y flag to say yes for each prompt to fix the filesystem):
Bash: 
sudo fsck -y /dev/sdc1
sudo fsck -y /dev/sdc2
Click to expand...
Please disregard the above... Sorry I just read all the way to the bottom of your post:

corporal_Canada said:
media/chris/240gb ssd
sdc 8:32 0 119.2G 0 disk
├─sdc1 8:33 0 1022M 0 part /boot/efi
├─sdc2 8:34 0 4G 0 part /recovery
Click to expand...
These are your boot and recovery drives. You cannot unmount them...

FAT filesystem is a very strange choice indeed for this...
 
You must log in or register to reply here.


Members online

Total: 1,057 (members: 9, guests: 1,048)

Latest posts

Top