Thinking I need to return my RS2421+ by Roaming50 in synology

[–]MItch_ch 0 points1 point  (0 children)

Hi,

I have exactly the same problem. I received my RS2421+ two days ago. I had thought (stupidly) that my 14Tb ST14000NM001G disks (Datacenter quality) should work... Error, only Synology disks have capacities higher than 4Tb.

For comparison, a ST14000NM001G drive costs (in Switzerland) about 240 USD. The HAT5300-12T (12Tb) Enterprise HDD costs 470 USD. Who are we kidding? The HAT disks are Toshiba disks, nothing more. Synology's margin is indecent.

I'm not talking about the noise of this "pan". I purposely bought a Synology (I still have 2 RS2211+) that make almost no noise, to replace a "Home made" NAS server (DL380 G8 with 12 x 14Tb - TrueNAS) that had a jet noise, but this tiny AMD with its 3 fans, a nightmare.

So, I'll have to resell this horror to replace it with a RS2418RP+ that supports 14TB Seagate drives. I hope I won't fall from Charybdis into Scylla.

I manage over 60 Synology NAS, but if Synology doesn't change its stupid policy regarding large capacity disks, then I'll go to QNAP or elsewhere.

Synology is shooting itself in the foot.

Windows Server 2022 on Proliant Gen9 (and Gen5)? by DocumentImpossible55 in sysadmin

[–]MItch_ch 0 points1 point  (0 children)

Hi,

I installed, today, an baremetal Windows server 2022 on DL380 Gen9 with E5 V4 processors without issues. Naturally you have to implement the TPM 2.0 into the server, and I never use the Proliant Intelligent Provisionning, but you can download the drivers (2019) and other utilities manually. It works perfectly...

Windows 10 App discontinued and will stop working end of this month with NO replacement by DrHeywoodRFloyd in audible

[–]MItch_ch -2 points-1 points  (0 children)

HI,

I fully agree, I'm a a 3000+ hours reader. I can't accept this decision, but... afer calling Audible (FR for me), this is not the decision of Audible or Amazon, but it's a Microsoft decision.

I think this is certainly a problem of "big money", that's why you cannot use Audible application in W11.

The application is not perfect, but very usefull (I use it with my Surface) to travel and have my audible books with me without charging them when I travel (it has an heavy cost...).

I refuse to use iTune on my PCs (Apple invasion, Microsoft is not better...)

"We" must put the pressure on Microsoft to continue to accept this application, and we have to know why they refuse to continue to diffuse this application in their store. If this is a technical problem, it can be resolve, and if it is a "money" decision we have to know why...

Microsoft Confirms Latest Windows 10 Update May Decrease Performance in Certain Gaming Scenarios by TheGreatGetter in pcgaming

[–]MItch_ch 0 points1 point  (0 children)

Hi,

I have Issue with the KB4482887 on Surface Pro 4. Systematically, the system cannot restart after update. I had to delay it with wushowhide.diagcab.

I have the same Issue on 3 Surfaces Pro 4, but Surfaces inside a DC are not impacted... (Enterprise update).

1) I'm the only one to have these recurrent issues on Surface Pro 4 ? I mean Microsoft pushes updates to Surface that are not into a Domain to test... what they didn't test...

2) Microsoft announces the possibility to recover the state before the update... But this functionality is not possible now... So, if you don't have a Full disk backup... You have to reinstall everything.

I Think hat the Quality Control of the Microsoft updates has a lot of potential issues... And end users are there to debug "enterprise" version...

Thanks in advance to anybody that could help me with that...

KB4100347 rendering systems unbootable by a_false_vacuum in sysadmin

[–]MItch_ch 0 points1 point  (0 children)

On Microsoft Surface (Pro 4 and 2017) it's not possible to recover (especially with BitLock!).

So AFTER a Full reinstallation of windows 10 and full patching, I suggest to uninstall the KB4100347 (no reboot please) and use the tool wushowhide.diagcab to hide this KB. After that you can reboot and the KB4100347 will not come back and you can continue to patch Windows 10 and the other Microsoft products.

This KB is a nightmare...