Selfhosted

40493 readers

727 users here now

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
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

TrueNAS boot drive dead? - resolved (self.selfhosted)

submitted 1 day ago* (last edited 9 hours ago) by steel_moose to c/selfhosted

7 comments fedilink hide all child comments

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 🙏

top 7 comments

sorted by: hot top controversial new old

[–] steel_moose 1 points 9 hours ago

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 👍

[–] mumblerfish 4 points 1 day ago (1 children)

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 -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?

[–] steel_moose 2 points 20 hours ago (1 children)

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.)

[–] steel_moose 1 points 9 hours ago

For future reference...

The output of dmesg, with working drive and usb-sata cable:

[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.

[–] just_another_person 4 points 1 day ago (1 children)

Sure seems dead if you can't get it to detect via two different routes.

[–] BluescreenOfDeath 3 points 1 day ago (1 children)

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.

[–] steel_moose 1 points 20 hours ago

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. 🤷‍♂️