Ah I missed a few details sorry about that.
- Offical Pi5 power adapter (I have heard about the problems using something less)
- 2.5 SSD
- Crucial BX500 (not sure why that would be a factor)
- Power rating of SSD unknown and I really don't want to pull the enclosure apart at this point
- Chipset of enclosure unknown, but it is a SansDigital usb 3.0 and esata 2.5 enclosure
- Yes the enclosure draws all of its power from the AC adapter. It has both USB 3.0 and esata ports and USB does not need to be plugged in for it to work. In fact if you have only USB and don't plug in the adapter, it won't power on.
- in its failed state lsusb only shows the bus:
lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
- I don't have anything else connected to the USB ports
- I didn't think to try a USB 2 port I will try that later (I thought Linux USB was less voodooish than on a windows box should have known better).
- As for what changed between working and not, just as I said: I was in Qbittorrent webclient and tried to add a torrent via magnetic link which I hadn't tried before in Qbittorrent. It kept saying "checking the files" or something like that. After a few minutes I tried to pause the torrent and nothing happened. And I found Qbittorrent was unresponsive. I SSHed into the Pi and that worked so I did a Sudo Reboot. Qbittorrent wasn't downloading or seeding at the time. But the reboot wasn't instant. It took 5-8 minutes or so maybe even 10 before the Pi did reboot. Which is very unusual. Normally it is instant. I was deciding on if I should pull the power when it did finally reboot. When it came back up the drive was no longer visible anywhere.
Nothing else changed between working and not.
-Why NTFS instead of ext4? Simple. I don't have another Linux box to test the drive on should something happen and I needed to pull files or even look at it. If I had it in ext4 I wouldn't know if the drive had been formatted or corrupted at this point. But NTFS I could plug into windows box and check it (which all is fine as I said).
- I have since found Jellyfin is not running at all and generating an error. I hadn't tried it figuring it would have problems since many of the directorys it is set to use are on the SSD. I have now disabled the service so it won't run until I can get the drive mounted again. Nothing else has been changed. I did a sudo reboot after but it still wont mount. But didn't think that would make a difference.
- Offical Pi5 power adapter (I have heard about the problems using something less)
- 2.5 SSD
- Crucial BX500 (not sure why that would be a factor)
- Power rating of SSD unknown and I really don't want to pull the enclosure apart at this point
- Chipset of enclosure unknown, but it is a SansDigital usb 3.0 and esata 2.5 enclosure
- Yes the enclosure draws all of its power from the AC adapter. It has both USB 3.0 and esata ports and USB does not need to be plugged in for it to work. In fact if you have only USB and don't plug in the adapter, it won't power on.
- in its failed state lsusb only shows the bus:
lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
- I don't have anything else connected to the USB ports
- I didn't think to try a USB 2 port I will try that later (I thought Linux USB was less voodooish than on a windows box should have known better).
- As for what changed between working and not, just as I said: I was in Qbittorrent webclient and tried to add a torrent via magnetic link which I hadn't tried before in Qbittorrent. It kept saying "checking the files" or something like that. After a few minutes I tried to pause the torrent and nothing happened. And I found Qbittorrent was unresponsive. I SSHed into the Pi and that worked so I did a Sudo Reboot. Qbittorrent wasn't downloading or seeding at the time. But the reboot wasn't instant. It took 5-8 minutes or so maybe even 10 before the Pi did reboot. Which is very unusual. Normally it is instant. I was deciding on if I should pull the power when it did finally reboot. When it came back up the drive was no longer visible anywhere.
Nothing else changed between working and not.
-Why NTFS instead of ext4? Simple. I don't have another Linux box to test the drive on should something happen and I needed to pull files or even look at it. If I had it in ext4 I wouldn't know if the drive had been formatted or corrupted at this point. But NTFS I could plug into windows box and check it (which all is fine as I said).
- I have since found Jellyfin is not running at all and generating an error. I hadn't tried it figuring it would have problems since many of the directorys it is set to use are on the SSD. I have now disabled the service so it won't run until I can get the drive mounted again. Nothing else has been changed. I did a sudo reboot after but it still wont mount. But didn't think that would make a difference.
Statistics: Posted by DBDigital — Sat Jun 28, 2025 2:50 am