Problem with HDD not detected on your latest computer build.
Problem with HDD not detected on your latest computer build.
Started assembling a new PC yesterday with LinuxMint 21. I have an SSD drive and an HDD drive; the HDD isn’t recognized, showing up in the disk section as not mounted. The command `sudo fdisk -l` lists it as `/dev/sda`. Someone can help mount it, please! Thanks ahead of time.
To prepare a new drive for use, begin by formatting it from the Mints start menu. Locate your new HDD in the left column, choose it, and select the format or partition option. Ensure the file system matches your needs—ext4 for Linux-only use, ntfs if sharing between Windows and Linux. After formatting, the disk should mount automatically; if not, add it to the fstab file via the provided link.
You need to create your own setup. A "mount point" is simply an empty folder, then you can attach the storage device manually (directly or via automation). On a brand new machine, it's wise to start with solid guidelines so you're set from the beginning. Some users place their slower HDDs in /home, which keeps system and user files separate, but using an SSD as the main drive means many files—like settings and caches—live in the user folder, gaining the speed benefits they deserve. Removable drives are usually placed under /media/something, though /mnt is better for fixed static storage. Make a directory in /mnt for your drive, for example: sudo su || sudo -i || su mkdir /mnt/storage_1 chown :users /mnt/storage_1 chmod g+w /mnt/storage_1. This process raises your privileges, creates the folder, sets the group ownership, and ensures only you can write to it. Linux doesn’t require a partition table for basic use, but from a recovery standpoint it’s less ideal since you don’t know which drive you’ll need later. We’ll use `lsblk` to inspect your disks: lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 1.8T 0 disk └─sda1 8:1 0 1.8T 0 part nvme0n1 259:0 0 894.3G 0 disk ├─nvme0n1p1 259:1 0 2M 0 part ├─nvme0n1p2 259:2 0 128M 0 part /boot ├─nvme0n1p3 259:3 0 32G 0 part [SWAP] └─nvme0n1p4 259:4 0 207.4G 0 part / So here, sda1 is the target partition. Before locking it in fstab, we’ll mount it manually to verify: mount /dev/sda1 /mnt/storage_1 if successful then run blkid to confirm details: blkid | grep "/dev/sda1" /dev/sda1: UUID="72966c46-e4b1-4ca6-a5f9-7881e16966cd" We’ll use the UUID for fstab, not the PARTUUID, since it remains consistent regardless of where you connect the drive. It’s safer to reference the UUID for reliability across different motherboards or extra drives. Now, we can add the entry to fstab: /etc/fstab # Storage HDD UUID=72966c46-e4b1-4ca6-a5f9-7881e16966cd /mnt/storage_1 ext4 rw,noatime 0 2 This will ensure automatic mounting at boot. Optional Enhancement: set up symbolic links in your home folder so the drive appears automatically for certain apps. First, change ownership and permissions: chown :users /mnt/storage_1 chmod g+w /mnt/storage_1 Then create symlinks to place files where you want them: ln -s /mnt/storage_1/LadyDragon/Documents ~/Documents ln -s /mnt/storage_1/LadyDragon/Music ~/Music ln -s /mnt/storage_1/LadyDragon/Videos ~/Videos ln -s /mnt/storage_1/Downloads ~/Downloads This way, your files will end up on the HDD rather than the SSD. *If mounting fails, share the error and I’ll suggest fixes.* You can open any file manager to manage this if you prefer. ***If these directories already exist in your home folder, just transfer their contents to /mnt/storage_1/LadyDragon/[appropriate type] and remove the original files.***
You're making good progress with Linux! It sounds like you've set up the storage folder and are trying to mount it, but you're encountering an error. Let's try to clarify what might be going on.
The message suggests a problem with the file system type or missing configuration. You might want to verify the mount command and ensure your filesystem is correctly recognized. If you're unsure, double-check the path and permissions. Tkx is helpful—keep sharing updates!
lsblk output shows disk partitions with details like name, size, and mount points. It lists the sda drive at 8:0 with 9.1Gb available, followed by nvme0n1p1 and nvme0n1p2 under the same partition. Each entry specifies block size, usage, and location on the disk.
You should set up a filesystem on the storage device. Mint likely includes a GUI tool named "disks" for this purpose, or you can install gparted for better control. It’s better to create a partition rather than formatting the entire disk raw, especially if you plan to recover data later. To handle both tasks via the command line: use sudo fdisk /dev/sda followed by your partition number, then w to exit, and finally sudo mkfs.ext4 on the desired partition. If you need a raw format, replace /dev/sda1 with /dev/sda in the command. The mkfs command formats the partition as ext4, which is widely supported in Windows for third-party tools. For specific needs, research suitable filesystems like BTRFS, XFS, or NTFS based on your requirements. After formatting, proceed with the mount command that triggered the error, and share any further issues for assistance.
You need to reformat the entire drive if you want a clean partition layout. If you're sure, proceed with the full partition process. The current setup isn't suitable for standard use. Let me know if you'd like guidance on the next steps.
Answer: ladydragon@ladydragon-System-Product-Name:~$ sudo fdisk /dev/sda
I understand you've tried it before and it's still not functioning properly. Please let me know what you did, so I can help further. Kindly send an email with the details: ladydragon@ladydragon-System-Product-Name