Partition not showing up after reboot (sometimes)

Hey,

So I this setup for partitions & HDD/SSD:

[fv ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 111.8G 0 disk
├─sda1 8:1 0 513M 0 part /boot/efi
├─sda2 8:2 0 50.3G 0 part /
└─sda3 8:3 0 61G 0 part /home
sdb 8:16 0 931.5G 0 disk
├─sdb1 8:17 0 491.8G 0 part /run/timeshift/backup
└─sdb2 8:18 0 439.7G 0 part /run/media/fv/hdd-2
sr0 11:0 1 1024M 0 rom
sr1 11:1 1 87.7M 0 rom

sdb1 is the partition not mounting (and actually not showing up under Devices at all). After a reboot, it sometimes just isn’t there at all. Other times it’s fine.

[fv ~]$ sudo hdparm -I /dev/sdb | less
/dev/sdb:

ATA device, with non-removable media
Model Number: WDC WD1002FAEX-00Y9A0
Serial Number: WD-WMAW31618079
Firmware Revision: 05.01D05
Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5,
SATA Rev 2.6
Standards:
Supported: 8 7 6 5
Likely used: 8
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63

CHS current addressable sectors: 16514064
LBA user addressable sectors: 268435455
LBA48 user addressable sectors: 1953525168
Logical/Physical Sector size: 512 bytes
device size with M = 10241024: 953869 MBytes
device size with M = 1000
1000: 1000204 MBytes (1000 GB)
cache/buffer size = unknown
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec’d by Standard, with device specific minimum
R/W multiple sector transfer: Max = 16 Current = 0
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* NOP cmd
* DOWNLOAD_MICROCODE
Power-Up In Standby feature set
* SET_FEATURES required to spinup after power up
SET_MAX security extension
* 48-bit Address feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
* 64-bit World wide name
* {READ,WRITE}_DMA_EXT_GPL commands
* Segmented DOWNLOAD_MICROCODE
* Gen1 signaling speed (1.5Gb/s)
* Gen2 signaling speed (3.0Gb/s)
* Gen3 signaling speed (6.0Gb/s)
* Native Command Queueing (NCQ)
* Host-initiated interface power management
* Phy event counters
* NCQ priority information
DMA Setup Auto-Activate optimization
* Software settings preservation
* SMART Command Transport (SCT) feature set
* SCT Write Same (AC2)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
supported: enhanced erase
174min for SECURITY ERASE UNIT. 174min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 50014ee25c75e4ca
NAA : 5
IEEE OUI : 0014ee
Unique ID : 25c75e4ca
Checksum: correct

It is the partition on which I put my timeshift backups (along with a few other things, like Vm images & such). I am not positive, but it may have started happening when I designed it as my timeshift backup partition. Although the timing may also be roughly the same as a kernel update.

All other partitions, drives & devices show up fine.

If I want it to show up, I can reboot, and usually the 2nd time it shows up fine…

Any ideas as to what is up?