USB NAND Drive Bricked x2 #4642
Labels
Comments
Logfile attached. Click to expand! |
|
Looks like the NAND disk is detected as |
|
I did see that, but on a rasbian no drive comes up nor on a Windows device... It also does nothing when the microSD card is removed and the device is started up (only the power LED comes on, no blinking LED). Any idea how to fix? Thanks |
|
Strange that fdisk -l
[[ -b /dev/sda ]] && echo 'Block device is there'Also:
Would be interesting what these 30 lines are. Kernel message rate limiting can be disabled until reboot with: echo 0 > /proc/sys/kernel/printk_ratelimit
echo 0 > /proc/sys/kernel/printk_ratelimit_burstAnd: vcgencmd get_throttled |
Logfile attached. Click to expand! |
|
|
Can you run these: partprobe /dev/sda
partx -u /dev/sda
parted /dev/sda printThe device file is there, but if no tool is able to detect it as block device, then I cannot imagine the drive content being the issue, but the hardware/device/firmware itself. I mean the tools are not even able to format the drive. If you flashed the image from Windows, obviously Windows is able to detect it as drive. Does it detect the /boot FAT partition as well, else what does the Windows disk management show? |
From Windows Device Manager: From Windows Drive Manager: |
|
I guess you attached it to a USB3 port, right? Could you try (with a fresh image) to use a USB2 port? Another idea I have is that UAS causes issues with that stick. It is a small USB stick, no 2.5" SSD, right? |
|
The pi is a 3 b+, so there are no USB 3. My Laptop has no USB 2 ports and
I don't have a USB 2 hub.
Not to mention I'm out of USB drives (no, they're not 2.5" drives).
|
|
Ah right, then also UAS is not a topic.
You mean also on Windows you are unable to format that drives? |
|
That's correct. It's like the partition info is lost and not recoverable. |
|
Well the partition info is not required for being able to format the drive. Re-creating the partition table is a common task. But the problem on Linux is that even the tools which are there for creating partition tables do not detect the drive as accessible block device. Here are similar cases:
But I cannot imagine that the RPi really broke the USB stick, as this must mean serious overvoltage on the USB port, or so. dd if=/dev/zero of=/dev/sda bs=8M |
|
|
So indeed it seems to be broken then. Were these known brands, probably some warranty on them, or very old ones? As said, I cannot really imagine that the RPi killed them, without them being close to dead already, but risky/expensive to really debug the case. Also strange that it worked exactly until reboot, without starting to get I/O errors earlier. Always good to keep an eye on RPi repositories and forum, just in case someone had a similar issue, like if is something with the newest kernel/firmware release: |
|
These were cheap amazon bulk purchases, but I've not had any issues in other applications with these drives. I'm not sure what to think. I was going to try a name brand 16gb, but I'm a little worried it may brick it too... |
Understandable. Probably try it first with Raspberry Pi OS Lite, update all packages and kernel, and see ich that works stable. If it bricks again, it is an issue with the RPi and at least it's worth trying to contact the RPi support about it. Not sure if monitoring voltage on the port of some time would give any hint... |
|
I don't think it's likely that it was an over voltage issue because I tried it with 2 separate RPi 3's. The likelyhood that 2 Pi's had over voltage on a USB is extremely unlikely... |
|
I decided to try the Sandisk 16gb thumb drive. I installed the Pi OS from their website and was able to install everything I needed and it worked properly. I then decided to wipe the drive and re-downloaded the DietPi image from your website and try it again, this time doing installations one at a time and rebooting between each. Basically I installed DietPi with no added software, then rebooted, installed Fail2Ban, rebooted, PiHole, rebooted, PiVPN, rebooted. Everything seems to be working fine. I guess the cheap memory had issues.... I really don't have a clue what could have been different about them. I really appreciate your help with troubleshooting this!! Thanks |
|
Okay, I'm glad the new thumb drive was not toasted as well. Then indeed it seems the other two were too cheap, although still strange that both died to close after another, like with a self-destruction timer included 😄. |
|
if they are still in warranty, try to return them 😃 Personally I'm using a SanDisk Ultra Fit 16Gb. It's small and thin USB stick but working quite well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here is the result of
lsblkafter booting from the microSD with the USB drive installed.The USB is not listed, only the 16gb microSD.
Should we move the conversation to a different thread?
Thanks
The USB drive is not listed, only the 16gb microSD.
Should we move the conversation to a different thread?
Thanks
Originally posted by @Fireman1224 in #3708 (comment)
The text was updated successfully, but these errors were encountered: