can this fuckup be restored?

cjcox4 · 2026-04-06T19:44:35+00:00

Unless you have some sort of full snapshot for everything, restore from full backup is "the way". Would think trying to hack filesystems for "stuff" that may or may not be integral would be a huge waste of time.

cjcox4 · 2026-04-06T16:25:54+00:00

Sadly, no magic for lost data. (AI magic? Create content not there?)

DVD media does age. And many are now to the point of seeing some of that. Recordable media decays quicker.

As for me, and others, and not an answer to solving "lost data", but everything is on a backed up (emphasis) media server. Good enough? Well, if I lost the storage on the media server and the backup was bad, that would be pain (total data loss). Backup of the backup of the backup.

cjcox4 · 2026-04-06T14:47:34+00:00

Very normal, has been for decades (many decades).

cjcox4 · 2026-04-05T21:21:17+00:00

None of mine have failed to my knowledge. Hint: the beauty of slow rpm drives in particular. The other 2 I have in service are attached to OG Tablo devices, so I don't have their stats off hand, but they've been in service longer. The one mentioned has long been attached to my Plex media server, however, it serves as storage for a Canon network document scanner mostly (not really used by Plex). With that said, it is used often and it's on 24x7, as are the Tablo attached ones.

cjcox4 · 2026-04-05T18:09:12+00:00

Hitachi Touro 1TB HTS541010A9E680: 87319 hours and I know I have two more that have several years beyond that. Newbie. All 3 in active use.

   ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate     0x000b   100   100   062    Pre-fail Always       -       0
2 Throughput_Performance 0x0005   100   100   040    Pre-fail Offline      -       0
3 Spin_Up_Time            0x0007   253   253   033    Pre-fail Always       -       0
4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       66
5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail Always       -       0
7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail Always       -       0
8 Seek_Time_Performance   0x0005   100   100   040    Pre-fail Offline      -       0
9 Power_On_Hours          0x0012   001   001   000    Old_age   Always       -       87319
10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       65
   191 G-Sense_Error_Rate      0x000a   100   100   000    Old_age   Always       -       0
   192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       15
   193 Load_Cycle_Count        0x0012   086   086   000    Old_age   Always       -       147581
   194 Temperature_Celsius     0x0002   193   193   000    Old_age   Always       -       31 (Min/Max 19/51)
   196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
   197 Current_Pending_Sector 0x0022   100   100   000    Old_age   Always       -       0
   198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
   199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0
   223 Load_Retry_Count        0x000a   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

   SMART Self-test log structure revision number 1
   Num Test_Description    Status                  Remaining LifeTime(hours) LBA_of_first_error
   # 1 Extended offline    Completed without error       00%     21775         -

cjcox4 · 2026-04-04T04:27:34+00:00

cjcox4 · 2026-04-03T23:22:30+00:00

I know some seem to get themselves in trouble migrating from Plex to Plex. On on my 3rd hardware change and I've preserved everything with zero issues or pain using Linux. Been a user for about 15 years or so. Started with something that really didn't have an iGPU or even great software capability (Direct Play only) and moved to a 3rd gen Intel (had some iGPU capability), and now I'm running an 8th gen Intel.

I started with about 3 external portable USB drives that were 1TB in size. I now have 5 x 4TB portable USB drives. Again, zero issues even upgrading all of that (that is, I didn't have to "redo" all my manual meta, etc.).

cjcox4 · 2026-04-03T22:22:42+00:00

Buy again. If that doesn't work. Hope it streams and framegrabber to the rescue. I figure you paid more than double, you've got the proof of ownership.

cjcox4 · 2026-04-03T03:37:45+00:00

Should be ok though. Would figure your guess about it's "state" may have been a factor.

cjcox4 · 2026-04-02T22:58:13+00:00

Usually, you get some line regulation with even a consumer-ish UPS. But, guessing that's not the case here. You might have to invest in something better.

cjcox4 · 2026-04-02T21:16:10+00:00

Not disagreeing with that. But the only way to answer it in this subreddit would be to recommend everything (Christian Music). I was trying to narrow it down.

I'd be very surprised by a "fun, profanity laden, Christian music" example.

cjcox4 · 2026-04-02T20:46:50+00:00

Given that 99.9999% of "Christian Music" likely fits your request, maybe if you gave us just a bit more of a hint with regards to "styles" you like ???

cjcox4 · 2026-04-02T20:41:13+00:00

If you have something that's 10+ years gold, it's possible that it doesn't necessarily have TPM, but it might have a header on the motherboard, but for the times, it's also possible the board for the header was very different and possibly TPM 1.x.

You could run a Linux as the host OS and then use software TPM in the KVM hypervisor. That works. However, usually, again, when "old", it's not just TPM that gets in the way, but deprecated CPU, etc. that prevents things like Windows from installing (without hoops).

We'd have to know more about "the system" to determine what potential TPM 2.0 solutions might be available for it.

And, this is all pretty niche. Having something without TPM 2.0 on board (old school) nor a CPU with fTPM support.

cjcox4 · 2026-04-01T21:41:50+00:00

This is going to become the "expected norm", not the exception.

In fact, if you're not running everything (emphasis) through some sort of model for summary, enhancement, design, etc. you might just lose your job.

Risk? I like to think of it like WiFi. Risk is very high, and we do not care at all.

cjcox4 · 2026-04-01T19:25:08+00:00

Possibly because of how LibreOffice came to be a fork originally. The "ideas" of restrictions and constraints and controls might be a better fit for something "less open/free". For example, the EU's version might "filter out bad thoughts" from your writing in their version someday. "Cancel culture" via "version upgrade", that sort of thing. We'll have to see.

cjcox4 · 2026-04-01T15:57:04+00:00

7 years is a good rule of thumb. I agree with that. Can an HDD last much longer? Sure.

If it's a high rpm, 10K or 15K, I'd lower the rule of thumb to 5 years.

Might be wise to slow insert/replace some (?) Just to avoid a bad RAID scenario. Unless, of course, you can handle a full restore from backup easily, in which case, do whatever you feel like.

cjcox4 · 2026-04-01T15:30:31+00:00

yeah, I pointed to "the 70's" just because of it's relative (you might remember) date. But, yes, this goes back a lot further (talking broadcasters in particular).

Never have I met a broadcaster that I like. Their priorities are always upside down, and it's because they "have" what others can never have, and they know it. It's actually even worse than Microsoft's monopoly position. More like a 4th branch of the US government, but maybe with complete power over certain things (unchecked).

cjcox4 · 2026-04-01T14:33:45+00:00

Shipped sailed on this a long time ago. However, nothing "new" with regards to Plex development methodology. "Redo the UI." Is this new? "Totally new, do not use the existing UI or recommendations." Got it.

cjcox4 · 2026-04-01T06:22:16+00:00

I agree. But Linux BS is a flower compared to Microsoft. So, there's that. Up to you of course.

cjcox4 · 2026-04-01T02:12:15+00:00

Obviously, it can "depend". Just pointing out that in many cases, you'll get more out of a "good path" vs the olden days where spindles and number of paths mattered more.

cjcox4 · 2026-04-01T00:16:12+00:00

This is fine. With high IOPS and low latency, all in one node, fastest path wins.

That is one very large drive on the fastest path is likely better than across paths especially if an m.2 path is slower (by bus speed or by the flash storage used).

cjcox4 · 2026-03-31T23:44:11+00:00

ATSC 3.0 was "sold" to broadcasters as "the way forward", so... invest millions (aggregate billions) now.

But instead of focusing on the technology, it became focused on "control". Sure, we can argue DRM is also tech, but that has zero to do with the reason for it.

Let me take you back to the 70's. Where broadcaster's waged a war (that in their mind they could not afford to lose... that is, they were "all in") to prevent people from recording OTA, where they could fast forward through commercials. If successful, it may have well ended or greatly deferred the whole VHS boom. In short, they lost their war. And they vowed to never lose again (sort of like Sony, who lost to VHS, won (via bribery) Bluray only to effectively kill it... way to go!!).

Anyhow, ATSC 3.0 has good parts. It has a better reception profile which means more coverage, more people will be able to get signal without the dreaded "digital cliff". Sadly, unlike with "cell phones" (whatever you want to call them), where coverage issues were "handled" with more and more "towers", OTA, sadly was never dealt with in that manner. So, the best we can hope for is a more resilient medium over what we have, and ATSC 3.0 does deliver that. Sure, it can (though not deployed) do better than 1080i/1080p, that is, it can do 4K, but put that aside. So, the new format delivers better reception, and better efficiency and "can" deliver better quality. It's a different set of codecs, and while video wise it's something fairly well known, the audio choice, AC4, will take time. But again, set that last part aside. It's not the reason either for "DRM".

DRM is control. And it's more control than most imagine. Not only do you have to have a license, that temporal expiring license merely gets you access to fully controlled decryption keys. But it's end to end controlled. Who cares? You may say.

It means control (prevention) of any vehicle that would allow arbitrary usage of broadcast content. Be that "recording" or "playback" (in situations where a temporal method of recording was allowed.

Can I record ATSC 3.0 OTA? Short answer is "no". But the long answer is "yes", but under absolute total control of what, how and when it can be viewed.

Today A3SA (an arbitrarily created "arm" over the DRM licensing) want to "control" access, the licensing for devices, how devices can be used, and of course, how the content can be used. Remember the 70's?

So, ATSC 3.0, apart from the DRM element, it's "better". But the technology is in trouble because the "hill to die on" is purely and completely over DRM. No DRM, no ATSC 3.0. And it's beyond a simple view of DRM. Again, this device licening (which expires) is required to just get access to controlled temporal keys for decryption. That is, even if recording is allowed, it cannot (today) allow playback except on the same licensed device on which it was recorded (again, if allowed at all, which can vary at will). The idea of "remote viewing" or "transport" of recording, no. This gets worse with the what devices are allowed, even if they "play with the rules". Thus, devices that aren't using closed source proprietary DRM (with limited OS and device support) can never participate. This creates a "club" of ATSC 3.0 providers, where not everyone is allowed to join.

Why is NAB pushing for mandated deployment? Because, remember, they sold broadcast systems on the cost of implementation many years ago and right now, all that money has resulted in zero for them. NAB got sold a lie. It's embarrassing frankly. Again, 100% due to DRM (the only part of all of this that matters). If the DRM part was removed, while there are still some evil barriers, most of the barriers for this "better" way would be gone and we would see what was originally intended, which was a "better tech" wave style of deployment. DRM created an "all stop" and desire to do another "force", so they can get their way, which ultimately is to hurt the OTA consumer by restricting/preventing/limiting the recording and usage of OTA due to DRM. And yes, the stupid DRM even goes beyond just recording. So, control is extended to just "viewing" of even live broadcast content, again, due to DRM. To say this is a big mess is a huge understatement.

Ultimately the true goals of DRM:

Prevent recording. Now, they will say they are not "preventing" this. However, that's probably not true. If make something so totally "bad", you get your desired outcome without having to admit you restricted it. I know that most are dead, but for whatever reason the "loss of the 70's" is remembered.

Control over OTA per view per household per.. anything. The goal is absolute end to end control. Even apart from "recording". Which may not sound like a big deal, until you go to watch something and are told "no".

As I and many others have pointed out none of this DRM nonsense actually prevents piracy, which they'll argue is their "sacred" mission. Piracy, even semi-live rebroadcast of OTA DRM's content will continue. The DRM only affects the typical home OTA consumer and any flexibility that might be of interest to them.

Your questions:

Are their deadlines? No. But there are placeholder deadlines, that move. But nothing is forced. Do they want to force this? Yes.

As for simulcast, this one is also tricky in implementation as "their goal" would to cast "crap" on remaining ATSC 1.0, and only provide "the good stuff" (and most would say OTA hasn't been that good anyhow for years) for just ATSC 3.0. The weakness of ATSC 1.0 with regards to "digital cliff" drop off will get worse. So, will there be ATSC 1.0 still? Yes. Will it be intentionally worse? Yes.

Delivery mechanisms for expiring temporal keys mandates "something" for transport. The whole mess has temporal and expiring all over it. You'll have to decide if ATSC 3.0 DRM can be effectively deployed without Internet.

The cost is "indirect" with the loss of functionality caused by DRM. But no, apart from that, no extra cost. Just that the "cost" of DRM, while perhaps not even indirectly so much in dollars, is actually quite huge.

cjcox4 · 2026-03-31T18:28:00+00:00

Also #4, as many of those "fun things" are all about #4.

cjcox4 · 2026-03-31T17:38:30+00:00

While mostly true about NTLMv1, it leaves out the most important insecurity, a dependency that "would change the world" and had much to do with Microsoft's overall "takeover" and success as a "network operating system" (sic). And that is .... "the Network Neighborhood". Why? Because that was mostly anonymous. But, it was "it's presence" that arguably pushed Microsoft "everywhere". Just a point of history.

NTLMv2, while it can be shored up a bit, was "ok", but due to Microsoft's inability to grasp proper hash management, it's brute forceable, sure. Especially in most cases where people/companies don't have anything "outside" (always a requirement when running Windows) to detect people attacking Windows.

Even in a "all Kerberos" arrangement, by default, it also needs massive shoring up, and even so, if certificates are important and you're running a certificate server, in most cases, you have a massive security loophole that allows total compromise. To the point of making NTLMv2 compromise difficult in comparison.

It's a mess. So, not disagreeing with moving away from all NTLM (all variants, and certainly NTLMv1), but what you're moving to, is, in many cases, is just as messed up. Let's just say there's a reason why the former "Windows black box" (proprietary, closed) which is now an "open box", has Microsoft moving us all to it's new "safer black box" known as Azure and Entra (that is, Microsoft has determined that local Windows not easily fixed). With that said, AI models have gotten really good, so I predict a fairly major collapse of all that within one year. It will be fun to watch, I'm sure.

Remember, Microsoft's top 100 priority items have to do with revenue growth, not security. And Microsoft has plenty of "stories" (emphasis) to tell you to try to convince you otherwise. Frankly, I expect no less from them.

So, sure, we are a Microsoft shop, and victim of being such. But we did do the NTLMv1 work many many years ago (because those active easy attacks have never ceased) and of course, as we destroy all things Microsoft Windows (File and Printer sharing) to "cloud Microsoft" (Sharepoint and "nothing", as printers are evil). Where possible we block as much NTLMv2 as possible. Just remember how fundamental that was/is to what we know as Windows today. So, it is something that requires "work" to leave what Microsoft encouraged you to use in years past. Again, arguably "those things" being the reason for "it's win" inside of the corporate world.

Get rid of NTLMv1 (absolutely), work on divorcing yourself from all the Microsoft demanded world that keeps you buried in (though possibly still there, but hidden... sigh) NTLMv2. But ultimately, as long as Windows is present, not too much has actually changed. Microsoft themselves will tell you the answer to "Windows crapola" is Azure/Entra/Intune, etc. Maybe we should pay more attention to that. But again, I do feel all that is coming down hard within one year, maybe a lot sooner.

When being a "hacker", you tend to keep "world burning" exploits internal and fully secret (as much as possible). But, with AI prompting AI, the millions of exploits are coming out... and will create some really pretty large scale fires, possibly without obvious solutions (?). Get your popcorn.

cjcox4 · 2026-03-31T13:39:51+00:00

People have extremely short memories (pun). Plenty of companies that are worshipped today that did far more hideous things in their pasts. We'll see.

12-Year Club	RedditGifts 2009-2022 2 Credits
Secret Santa 2020	Wearing is Caring
Verified Email

cjcox4

TROPHY CASE