Hi all!
I’m stuck with a problem on my TrueNAS server. I suspect the boot drive is dead, but I don’t know how to proceed to get it back up and running.
My setup:
-HP Compaq 8000 Elite SFF with 8gig ddr3
-TrueNAS-24.04.2.5
-Boot drive: Kingston SSD A400 240GB
-Data drives: 2 X Kingston SSD DC600M 960GB
Today i noticed that my Truenas was offline and I couldn’t ssh into it. The nic lights were not showing any activity. After a few boot attempts I hooked it to a monitor and keyboard. No boot media detected. Then checked in the bios and the data drives are detected but not the 240GB boot drive. So I pull the boot drive out and hook it to my Thinkpad running mxLinux. I have a USB to SATA cable, that I’ve used before to troubleshoot drives. The drive is not showing up in Disk Manager. Output of dmesg -w when hooking up the drive is following:
[ 2369.520731] usb 2-1: new SuperSpeed USB device number 9 using xhci_hcd
[ 2369.547175] usb 2-1: New USB device found, idVendor=2109, idProduct=0711, bcdDevice= 1.44
[ 2369.547194] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2369.547202] usb 2-1: Product: VLI Product String
[ 2369.547208] usb 2-1: Manufacturer: VLI manufacture String
[ 2369.547213] usb 2-1: SerialNumber: 000000123AFF
[ 2369.549433] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 2369.549917] usb-storage 2-1:1.0: Quirks match for vid 2109 pid 0711: 2000000
[ 2369.550061] scsi host3: usb-storage 2-1:1.0
Been trying to resolve this for hours with google but to no avail. Any help appreciated where to go from here.
Thanks 🙏
You must log in or # to comment.
Not sure what Disk Manager is, but if it says
USB Mass Storage device detected
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:
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_hcdThis 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.)
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.
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 👍
