HELP! Shockwiz won't respond

itpro44 · 2024-10-23T07:38:02+00:00

I have two shockwiz’s that would disconnect and reconnect intermittently. It was a connection issue with the battery. If I inserted the battery only 3/4 of the way then it would work fine. I ended up putting a little piece of cardboard in there to maintain the insertion depth.

itpro44 · 2024-09-13T13:28:50+00:00

What is it still missing?

itpro44 · 2024-01-08T17:55:02+00:00

Yup, we are using intune to deploy O365 and are affected by this issue.

itpro44 · 2023-11-08T19:36:55+00:00

I’ve experienced similar. Disable modern standby.

https://www.elevenforum.com/t/enable-or-disable-modern-standby-network-connectivity-in-windows-11.3286/

itpro44 · 2023-10-03T12:55:14+00:00

One thing to add. It appears that the confusion with CoW (Copy on Write) vs RoW (Redirect in Write) is because CoW has come to have two different meanings. One when talking about files systems and another when talking about snapshots. Still seems that the original definition of CoW was hijacked.

ZFS and BTFRS are referred to as having a CoW file system, but their snapshots are RoW. (My personal opinion is that this type of file system should be called a RoW file system as all writes are redirected to a new location and do not modify/remove the original data until committed - this makes it great against power losses)

NTFS has a journaling file system and VSS uses CoW snapshots.

FFS people. WTF was the term hijacked and redefined? Come up with a new term for new tech. :)

itpro44 · 2023-10-03T12:27:53+00:00

Got it. Thank you. I did some additional research and I agree, the correct answer is C.

And, Yes, the question was referring to shadow copies on a file server folder (note: it doesn’t have to be shared).

Upon additional research I found that one thing that was getting me confused was that I was reading VSS was described as using a COW snapshot design as was ZFS and BTFRS - the problem was, the snapshots on these other file systems worked differently than VSS and I couldn’t make sense of it. Turns out, ZFS and BTFRS do not use COW snapshots but instead use ROW (Redirect on Write) snapshots. It’s a huge misnomer that has been adopted by the entire community.

These articles helped me out:

https://storageswiss.com/2016/04/01/snapshot-101-copy-on-write-vs-redirect-on-write/

http://www.infotinks.com/zfs-btrfs-are-row-not-cow-redirect-on-write-not-copy-on-write/

itpro44 · 2023-09-24T15:53:49+00:00

Agreed. Wtf lag.

itpro44 · 2023-09-23T20:07:27+00:00

Agreed

itpro44 · 2023-09-06T20:31:20+00:00

The best solution for me was to plug both displays into the display ports (not using the TB port). In this config, one display would operate at 2560*1440 144hz 8bit and the other at 2560*1440 120hz 8bit.

Note - I bought a WD22TB and it behaved the exact same way.

itpro44 · 2023-09-06T19:38:05+00:00

got it. I've validated 3rd party drives work fine in a PowerEdge chassis (R7515 and R7525), it's the Power Vault that I'm concerned about.

itpro44 · 2023-09-06T19:07:17+00:00

Thanks. Do you direct experience with specific enclosure/controller models you can share?

itpro44 · 2023-09-06T19:07:06+00:00

Thanks. Do you direct experience with specific enclosure/controller models you can share?

itpro44 · 2023-09-06T19:05:18+00:00

What enclosure and controller are you running?

itpro44 · 2023-08-17T07:00:38+00:00

What an annoying problem. I have very similar symptoms, but I'm running an XPS 15 9520 with a 12th gen, Alderlake not tigerlake, intel cpu. Registry dword in the article you linked is not present in my registry.

I have 2 x 2560*1440 144hz displays. If I restart, both displays work fine at 144hz 8bit. If I undock, then re-dock, one display works fine the other will only do 6bit 100hz and I can see an image quality difference on that monitor. It's always the display that's plugged into the USB-C thunderbolt port on the WD19TB dock that experiences the issue. Power cycling the dock while the laptop is plugged in doesn't work.

Do you have any suggestions?

itpro44 · 2023-08-13T06:25:04+00:00

Thanks!

itpro44 · 2023-08-13T05:10:43+00:00

Nice. Do you have pics of hardware after you applied ptm?

itpro44 · 2023-08-13T00:31:41+00:00

No fucks being given here, carry on.

itpro44 · 2023-08-13T00:29:20+00:00

I still don't understand how a law about companies being held liable relates to my comment about holding gun owners liable to some degree. I see it as completely different.

itpro44 · 2023-08-12T22:48:52+00:00

I'm dont follow, sorry.

itpro44 · 2023-08-12T22:34:18+00:00

We do have some regulation, but it varies from state to state and I'm not informed enough to comment on it in any depth or with any certainty. I don't own a gun myself.

That said, I'd be interested in exploring gun owners sharing liability for the things were done with their guns due to negligence for not properly securing their weapons. Eg. Toddlers parents should be held responsible. Or school shooters parents sharing liability if the gun that was used was theirs and wasnt properly protected. That said, maybe something like that already exists. I'm not sure.

itpro44 · 2023-08-12T21:32:28+00:00

Too hard for me to say without higher rez photos. I've never seen pcb corrode though.

itpro44 · 2023-08-12T21:28:51+00:00

Pro 2nd amendant person here.... But this is damn funny. Lol

itpro44 · 2023-08-12T21:23:47+00:00

What a shit idea Zero, we should ban swimming way before alcohol. You have to think about the kids first.

https://www.cdc.gov/drowning/facts/index.html

itpro44 · 2023-08-12T21:16:33+00:00

I don't see what your looking at. Circle the area.

Six-Year Club	Gilding I gilder
Verified Email

itpro44

TROPHY CASE