You are not logged in.
Pages: 1
I am attempting to add a second hard drive to a system for data storage only. You can see /dev/sdb1 below.
$ blkid
/dev/sda1: UUID="545C-B608" TYPE="vfat" PARTUUID="b8eb84a0-9b3d-46c9-ab5b-e07b2c86235d"
/dev/sda2: UUID="87d0cb74-974e-4faa-8185-cd23bc815f6d" TYPE="ext4" PARTUUID="9559d5f6-fdbf-44da-8383-8f88d216b3ad"
/dev/sdb1: UUID="956d3ed3-cc2b-4092-ba41-7e22efeb1942" TYPE="ext4" PARTUUID="49d30cfa-fb2a-bd4c-9950-3b41b6733be3"Here is my fstab file:
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda2
UUID=87d0cb74-974e-4faa-8185-cd23bc815f6d / ext4 $
# /dev/sda1
UUID=545C-B608 /boot vfat rw,relatime,fmask=0022,$
# /dev/sdb1 (/music)
#UUID=956d3ed3-ccb2-4092-ba41-7e22efeb1942 /music ext4 $
PARTUUID=49d30cfa-fb2a-bd4c-9950-3b41b6733be3 /music ext4 defaults,noatim$
#/dev/sdb1 /music ext4 defaults,noatime 0 1As you can see, I tried with both UUID and PARTUUID. Both work when I connect the drive via USB. But when I connect the same drive via SATA, not only does mounting fail, but networking as well. The system waits trying to mount the drive and this is the additional service tails:
systemd-networkd-wait-online.service enabledI tried disabling that service, but then I had no network connection. So a re-enabled it.
Here is the fdisk information on the drive in question:
$ fdisk /dev/sdb
Welcome to fdisk (util-linux 2.31.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/sdb: 4.6 TiB, 5000981073920 bytes, 1220942645 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 268431360 bytes
Disklabel type: gpt
Disk identifier: FE792804-0AC1-A54A-968F-4C7C4A3F4F2F
Device Start End Sectors Size Type
/dev/sdb1 65535 1220942639 1220877105 4.6T Linux filesystem
Command (m for help):Why does this work if the drive is connected via USB and not internally as a SATA drive?
- Jim
Offline
Secure the mount by adding "noauto,nofail" to the options and then boot with the SATA-attached disk and check dmesg & "lsblk -f" on whether the device exists at all.
If so attempt a manual mount and see the error messages. If not: #1 cause is a broken SATA cable.
Offline
Pages: 1