• 0 Posts
  • 48 Comments
Joined 19 days ago
cake
Cake day: December 20th, 2025

help-circle

  • The reason I asked that is 3.5” drives can’t operate from usb bus 5v like 2.5” ones can and you didnt specify.

    Have you tried hot plugging the drive into the dock while it’s plugged into the computer? If the usb sata controller is slow on the uptake it might miss the relatively narrow chance to report to the pc what’s going on.

    Don’t worry about damaging your drives doing that btw, it’s extremely unlikely that you have a disk whose firmware doesn’t support it and all sata ports support it electrically.

    As an addendum: is the drive even good? Do you have a known functional disk to test with?

    E: oh yeah, on the off chance that the disk is uninitialized get everything plugged up and do an lsblk to show the various block devices. Sometimes if I plug up a disk with no partition table or superblock or whatever gpt uses nothing happens but lsblk shows it and I can mess with it.










  • If it’s simply putting your money where your mouth is then that’s perfectly good.

    If you’re worried about being in the crosshairs of that intelligence apparatus it would be good to limit what information stays outside the encrypted vault of whatever password manager you choose no matter where the service is based or servers are located.

    The mullvad port forwarding takedown is a great example of legal denial of service if you’re wondering to what extent these different agencies collaborate across oceans and borders.



  • You need an sd card adapter that lets you read and write the sd card from your pc to put an image the pi can boot onto the sd card.

    You will need this anyway when you eventually run into the sd card having a bunch of of bad blocks or unreadable sectors.

    It will work ”fine” for what you’re describing but consider getting one of those sata/m2 adapter boards so your root filesystem isn’t based on the media explicitly designed for temporarily holding information until the user can get back to a computer.

    If you already have a computer, just set up a vm.



  • Since you dont know what’s happening you dont need to be fucking around with busybox. Boot back into your usb install environment (was it the live system or netinst?) and see how fstab looks. Pasting it would be silly but I bet you can take a picture with your phone and post it itt.

    What you’re looking for is drives mounted by dynamic device identifiers as opposed to uuids.

    Like the other user said, you never know how quick a drive will report itself to the uefi and drives with big cache like ssds can have hundreds of operations in their queue before “say hi to the nice motherboard”.

    If it turns out that your fstab is all fucked up, use ls -al /dev/disk/by-uuid to show you what th uuids are and fix your fstab on the system then reboot.