Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)IN
Posts
1
Comments
2,508
Joined
2 yr. ago

  • Np, good luck.

    I miss my old Walkman from when I was young (actually think the one I used most was a Toshiba). Favorite was a Panasonic fm radio though, still love that thing, might have it in storage actually.

    They were awesome for the time, best of luck with yours, ask if you have other questions!

  • If the speeds are right, that's almost a smoking gun for a weak autoreverse spring.

    You might be able to jury-rig it temporarily, I don't know this unit's design, but either remove the spring and replace it with string or wire so the autoreverse sensor can't trigger, or fix the spring itself.

    Pull it and see what kind of tension it has.

    Heat treating is the proper method to fix it, here's the directions from chatgpt, it's not wrong, usually I've just seen it kept relaxed and heated with a lighter for 10 seconds, then left to cool.

    Heat the spring to ~400–600°F (204–316°C) depending on material (e.g., music wire, stainless).

    Hold for 30 minutes.

    Let it cool slowly in air.

  • Sorry, also one of the capstans or rollers could be sticking, increasing the resistance which also signals that the tape has reached its end.

    Interesting way to confirm: Does it autoreverse both ways equally? If so it is more likely to be the spring, if not then one of the capstans or rollers or the reversed lug is sticky.

  • The mechanism for detecting autoreverse needs attention.

    Usually there's a tension spindle that detects if the tape has ended, becauaw the pulling lug pulls and theres no more tape to feed.

    Maybe the spring lost tension?

    You need more info, probably an expert, but you can retension it by removing it and twisting it while heating in a fire (doesn't work great but might be enough).

  • It's interesting, however, if you mkfs.ext4 without -E ssd, or through some weirdness in your driver chain the filsystem doesn't know it can discard, then everything everywhere sucks for everyone, a cow fs is worse because no blocks are ever overwritten till the end, and the block map becomes a disaster while performance goes down the drain.

    Nowadays this rarely happens outside of very broken USB mass storage chips.

    This is why we used to have the fstrim command.

  • The fs does cow then releases the old block if appropriate.

    The ssd has a tracking map for all blocks, it's cow relies on a block being overwritten to free the old block.

    Basically it works out the same either way.

  • 4 is bad because parity is on one drive so no matter what happens that drive is the write bottleneck. Raid5 is basically raid4 + raid0.

    5 is just fine but low safety, I run 6 always and it has basically never let me down.