It appears to be something. If you do a sudo journalctl -f before you plug it in, does it tell you what device name it is given? If it is sata-to-usb you are using it is probably /dev/sd[a-z] or so, does anyone show up when you plug it in?
dec 04 05:22:58 mx kernel: usb 2-1: new SuperSpeed USB device number 17 using xhci_hcd
dec 04 05:22:58 mx kernel: usb 2-1: New USB device found, idVendor=2109, idProduct=0711, bcdDevice= 1.44
dec 04 05:22:58 mx kernel: usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
dec 04 05:22:58 mx kernel: usb 2-1: Product: VLI Product String
dec 04 05:22:58 mx kernel: usb 2-1: Manufacturer: VLI manufacture String
dec 04 05:22:58 mx kernel: usb 2-1: SerialNumber: 000000123AFF
dec 04 05:22:58 mx kernel: usb-storage 2-1:1.0: USB Mass Storage device detected
dec 04 05:22:58 mx kernel: usb-storage 2-1:1.0: Quirks match for vid 2109 pid 0711: 2000000
dec 04 05:22:58 mx kernel: scsi host3: usb-storage 2-1:1.0
dec 04 05:22:58 mx mtp-probe[31054]: checking bus 2, device 17: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
dec 04 05:22:58 mx mtp-probe[31054]: bus: 2, device: 17 was not an MTP device
dec 04 05:22:59 mx mtp-probe[31084]: checking bus 2, device 17: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
dec 04 05:22:59 mx mtp-probe[31084]: bus: 2, device: 17 was not an MTP device
dec 04 05:23:20 mx kernel: usb 2-1: reset SuperSpeed USB device number 17 using xhci_hcd
This cable has connected fine to previous ssd’s.
Maybe the drive just had a typical ssd reactive failure 🤔
(Disk Manager is just a gui mount tool shipped with mx.)
As for backups…
The disks containing the important stuff are higher spec SSD’s.
The data is backed up on 3 different drives - one offsite. So not really worried about dataloss at this point. And I have a fairly recent backup of the Truenas config/db.
The choice to not backup the boot drive, was made to save some money.
Just trying to figure out if a reinstall of Truenas on a new drive is the only option left. 🤷♂️
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Not sure what Disk Manager is, but if it says
It appears to be something. If you do a
sudo journalctl -fbefore you plug it in, does it tell you what device name it is given? If it is sata-to-usb you are using it is probably /dev/sd[a-z] or so, does anyone show up when you plug it in?Output of journalctl is almost same as dmesg:
This cable has connected fine to previous ssd’s.
Maybe the drive just had a typical ssd reactive failure 🤔
(Disk Manager is just a gui mount tool shipped with mx.)
For future reference…
The output of dmesg, with working drive and usb-sata cable:
The issue is now resolved.
Really straightforward with Truenas. Thanks to those who took the time to reply 👍
Sure seems dead if you can’t get it to detect via two different routes.
This is what I think is most likely as well. The capacity on the drive makes me think it’s a SSD and they can just spontaneously fail.
This is why you always need backups. It’s never a question of if, but rather when a drive will fail.
Well, I did mention it was a SSD in the post.
As for backups…
The disks containing the important stuff are higher spec SSD’s.
The data is backed up on 3 different drives - one offsite. So not really worried about dataloss at this point. And I have a fairly recent backup of the Truenas config/db.
The choice to not backup the boot drive, was made to save some money.
Just trying to figure out if a reinstall of Truenas on a new drive is the only option left. 🤷♂️