For future reference...
The output of dmesg, with working drive and usb-sata cable:
undefined
[21697.558147] usb 2-2: new SuperSpeed USB device number 18 using xhci_hcd [21697.587491] usb 2-2: New USB device found, idVendor=2109, idProduct=0711, bcdDevice= 1.44 [21697.587509] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [21697.587518] usb 2-2: Product: VLI Product String [21697.587525] usb 2-2: Manufacturer: VLI manufacture String [21697.587531] usb 2-2: SerialNumber: 000000123AFF [21697.590092] usb-storage 2-2:1.0: USB Mass Storage device detected [21697.590736] usb-storage 2-2:1.0: Quirks match for vid 2109 pid 0711: 2000000 [21697.590984] scsi host3: usb-storage 2-2:1.0 [21699.441247] scsi 3:0:0:0: Direct-Access USB3.0 high speed 2210 PQ: 0 ANSI: 6 [21699.441988] sd 3:0:0:0: Attached scsi generic sg2 type 0 [21699.442809] sd 3:0:0:0: [sdc] 468862124 512-byte logical blocks: (240 GB/224 GiB) [21699.443369] sd 3:0:0:0: [sdc] Write Protect is off [21699.443382] sd 3:0:0:0: [sdc] Mode Sense: 2f 00 00 00 [21699.443975] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [21699.447303] sdc: sdc1 sdc2 < sdc5 > [21699.447882] sd 3:0:0:0: [sdc] Attached SCSI disk [21704.928734] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Quota mode: none.
The issue is now resolved.
- Replaced boot ssd for a new one.
- Installed Truenas on said ssd.
- Imported config/db.
- Unlocked encrypted datasets on data drives.
Really straightforward with Truenas. Thanks to those who took the time to reply 👍
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. 🤷♂️
Output of journalctl is almost same as dmesg:
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.)
Why was he in prison again...?
Dipping my toes into this as well. Would you care to share the contents of your .mount unit file?
If I understand it correctly systemd generates unit files at boot using fstab 🤔. Probably not possible to specify the network dependency in fstab.
Glad someone said it out loud 😁 I've been running the snap for almost three years now 24/7. I works really well!
A bit of a sidenote and definitely an unpopular opinion coming up... The nextcloud snap is perhaps the easiest and among the most stable ways to run NC. And I base this on my own experience, having installed and tested NC on numerous devices in several ways. You loose some tinkerability and the performance is nothing to write home about. And yes I know - snap no good - Canonical evil. That having been said, If stability and easy setup is what you want, it's worth considering.
I just have a shell-script running daily that runs the smartctl short test and checks certain S.M.A.R.T. values and pings healthchecks.io when successful. Easy and seems to do the job.