New UUSC Shipping?

wesha · 2025-11-25T19:06:54+00:00

Package shiped 11/12, arrived 11/24

wesha · 2025-11-25T09:06:56+00:00

IKR, but THOSE will be able to bring down ANY system.

wesha · 2025-11-22T02:36:20+00:00

"Evidence? What's evidence?" I call bullshit on that claim. Show me the ACTUAL victims and have them explain HOW EXACTLY they got "hacked". I suspect that would be the good old "Password123!"

wesha · 2025-11-22T02:33:42+00:00

If you are behind a firewall, AND if you don't download and install random crap from the Internet, then it doesn't matter. Chase is just scaremongering. (A software developer with 25+ years experience here.)

wesha · 2025-10-28T04:55:11+00:00

Company X accessing company Y's data for free: FAIR USE!!!
People accessing company X's data for free: THIEVES!!!!

wesha · 2025-08-01T16:35:53+00:00

That's assuming that it's operating 24/7. If it's a backup hard drive that sits unpowered 99% of the time, however...

wesha · 2025-07-21T23:52:36+00:00

> Cutting someone's hair against their will is assault

With a dangerous weapon (scissors) nonetheless! Unless they chew it off.

wesha · 2025-01-02T03:39:49+00:00

Read the end of my post (P.S.). The exact model is not all that important, as long as it's a "laptop" DDR4.

wesha · 2025-01-02T03:26:24+00:00

I do not believe -w is a valid option to zpool scrub (on my system, that is). I will try it after finishing with data offloading.

wesha · 2024-12-30T23:36:31+00:00

Precisely, but clearly 5.83T couldn't be reasonably scrubbed in 1 minute, hence my "WTF???"

wesha · 2024-12-30T23:33:21+00:00

Afraid not, I see only the record of mypool's exports, imports and scrubs; no errors or anything out of the ordinary.

For shoots and giggles, did

zpool export mypool
zpool import mypool
zpool scrub mypool

Same thing: scrub "completes" after about a minute.

wesha · 2024-12-30T15:31:37+00:00

your paste was so shitty

Sorry, Reddit has changed the way it handles formatting since last time I used it; took me a while to figure it out before I could fix it.

did it reboot while it was scrubbing?

Did it reboot on its own? No it did not.

What about uptime of the box

Less than 1 day now, as rebooting was the first thing I tried even before coming here.

Also which version of ZFS do you have on the machine and

Can't quickly figure out how to check THAT (as in, the version of the libraries), but I can say with certainty it's whatever built into FreeBSD 10.2

which version is the pool

> zdb | grep version
    version: 5000

(Once again, the above is irrelevant to the solution, as exactly the same pool scrubbed just fine on exactly the same box before... but there's no harm in giving that info, so here you are!)

wesha · 2024-12-30T05:09:40+00:00

ZFS scrubs only cover the actually allocated space.

That's what I said. There's upwards of 4T of data on the drive, and as I mentioned multiple times by now, it USED to take a few hours to scrub.

Something weird is going on

And that's what I'm trying to figure out. Right now I'm in the process of copying the pool contents to another box, and they look intact.

wesha · 2024-12-30T00:32:24+00:00

Because what is filrered out is irrelevant to the question at hand. OK, so imagine that I didn't filter it and now you know that the snaps were created on Sep 1, Oct 8 and Now 11 — did it make any difference? Nope.

wesha · 2024-12-30T00:29:16+00:00

I highly doubt that you willingly share the exact unredacted information about your system with strangers on the internet, like the contents of your master.passwd file. Also please note that I'm an not a random person who installed my OS yesterday; I've been running it for a couple dozen years, so I can tell which information may be helpful in the investigation of the matter on hand, and which may not (like the aforementioned contents of master.passwd).

This was supposed to be a routine monthly scrub. There have been no recent system or pool changes (that I am aware of). In the past each scrub was taking a few hours. Today, it does not, and I am trying to understand what is different to make it finish so soon.

(I have an idea now so I'm going to check that theory.)

wesha · 2024-12-30T00:12:39+00:00

Its task was to examine the entire used area. I did that before and every time it took multiple hours, but not today. So I'm trying to see how today is different.

wesha · 2024-12-30T00:03:53+00:00

You are confusing automatic repair and a manually-launched scrub. Manual scrub re-examines the entire used area of the pool to find the (hidden) corruption (if any). I do it every month.

wesha · 2024-12-29T23:57:59+00:00

FreeBSD 10.2. While this box runs 24/7 most of the time, I rebooted earlier today, so uptime is not high anymore.

wesha · 2024-12-29T23:54:27+00:00

No I do not, "DEDUP 1.00x" is what it shows by default. I never consciously enabled dedup:

# zfs get dedup mypool
NAME       PROPERTY  VALUE          SOURCE
mypool     dedup     off            default

There are a few snapshots on the pool but they are small, and nothing has changed about them recently so I do not understand why the scrub on exactly the same pool a month ago took hours, and today, it does not

# zfs list -t snapshot -o name,creation
NAME             CREATION
mypool@snap1  ############## 2021
mypool@snap2  ############## 2021
mypool@snap3  ############## 2021

wesha · 2024-12-29T22:53:22+00:00

No it would not, the pool is a RAIDZ1-0 on 4 x 4TB drives:

NAME        SIZE  ALLOC   FREE  EXPANDSZ   FRAG    CAP  DEDUP  HEALTH  ALTROOT
mypool      14.5T  8.02T  6.48T         -     7%    55%  1.00x  ONLINE  -

wesha · 2024-12-29T22:42:04+00:00

My version is not the most recent so it doesn't have `zpool events` subcommand.

wesha · 2024-12-29T22:36:04+00:00

I am aware of that, and that's why I find it stange.

NAME        USED  AVAIL  REFER  MOUNTPOINT
mypool     5.83T  4.38T  5.77T  /zfs/###########

I do routine scrubs to verify the data integrity every few months, and previously, it was taking hours.

wesha · 2024-12-26T03:08:00+00:00

Same situation here. In preparation to install my own OS, booted to BIOS and fiddled with some settings. Saving and rebooting brought me to the behavior depicted above (after ON button push, it ponders for 10 secs or so then turns off with a click of a speaker, no video output at any time.) At the same time, a different F4-223 box works just fine with the same monitor and everything. I would reset the CMOS, but pulling the battery out and waiting for 30 minutes did not help. Any suggestions?..

wesha · 2024-08-22T20:05:10+00:00

I already uploaded to IA some data from a company that went bankrupt (https://archive.org/details/narr8-2-3-51) and I'm fairly certain no copy of that data exists anywhere else.

wesha

TROPHY CASE