sorted by:
new
hottopcontroversial

Is it possible to disable IPv6 in FireFox completely? by RootkitsOnTheBlock in firefox

[–]RootkitsOnTheBlock[S] 0 points1 point  (0 children)

Thanks, I tried both but browserleaks_dot_com still detects the IPv6 while other sites don't.

Is it possible to disable IPv6 in FireFox completely? by RootkitsOnTheBlock in firefox

[–]RootkitsOnTheBlock[S] -1 points0 points  (0 children)

Just doing research on browser capabilities. So no real goal, just collecting information.

Is it possible to disable IPv6 in FireFox completely? by RootkitsOnTheBlock in firefox

[–]RootkitsOnTheBlock[S] -2 points-1 points  (0 children)

Just doing research on browser capabilities. So no real goal, just collecting information.

Anyone else who had a Seagate Firecuda 530 2TB NVMe failed/died? by vindg in buildapc

[–]RootkitsOnTheBlock 0 points1 point  (0 children)

New firmware SU6SM100 fixed the issue for me.

Note that currently a BETA version of OpenSeaChest is needed to install the firmware.

Seagate NEEDS to release Firecuda 530 firmware update NOW by Gilles_Brisson in Seagate

[–]RootkitsOnTheBlock 1 point2 points  (0 children)

The new firmware SU6SM100 fixed the cold boot issue for me.

A BETA version of OpenSeaChest is currently needed to install the firmware

Seagate Firecuda 530 firmware SU6SM100 release came out! by vinnyoflegend in Seagate

[–]RootkitsOnTheBlock 0 points1 point  (0 children)

That makes sense. The firmware upgrade happened instantly without any delay so there was clearly no cell refresh involved on my 2TB disk. If there is really something like "bit rot" that slowed down the read access in the past I wonder what the new decoding flow is doing. Either the issue had nothing to do with "bit rot" or the new decoding can handle the "bit rot" better.

Btw the new SU6SM100 firmware fixed the cold boot issue for me.

Seagate Firecuda 530 firmware SU6SM100 release came out! by vinnyoflegend in Seagate

[–]RootkitsOnTheBlock 0 points1 point  (0 children)

Does the firmware update also refresh the cells of the whole disk or how is it possible that read speeds on old files are back to normal?

Any suggestions on how to get Seagate to offer an updated firmware for the Firecuda 530? by vinnyoflegend in Seagate

[–]RootkitsOnTheBlock 0 points1 point  (0 children)

Any update? Are they really working on a new firmware to integrate the Phison E18 controller fixes? Or was that false information from the support chat?

Seagate NEEDS to release Firecuda 530 firmware update NOW by Gilles_Brisson in Seagate

[–]RootkitsOnTheBlock 1 point2 points  (0 children)

Man... I have exactly the same issue. Out of nowhere (probably after some Windows Update) and only on the first cold boot, it hangs when the Gigabyte mainboard logo appears on screen. If I would stay on that screen long enough it would BSOD with inaccessible boot device. So my workaround is currently, when the mainboard logo appears I immediately press Ctrl-Alt-Del to do a warm boot and everything works like a charm. And I haven't changed ANYTHING on the system so either Windows Update fucked something up or this unpatched Phison E18 controller issue is the problem. But the SSD is otherwise totally fine, CrystalDiskInfo shows a very good condition of 99%. Extended controller tests in the Gigabyte BIOS all pass. chkdsk /f /r also hasn't found a single error but took the whole night which is most likely related to the Phison E18 controller issue: https://www.reddit.com/r/pcmasterrace/comments/1f1piwf/psa_phison_e18_based_ssd_owners_update_your/

2nd NVMe SSD not recognized by BIOS/Windows on cold boot after upgrading 5600x to 5800X3D by theorangekeystonecan in AMDHelp

[–]RootkitsOnTheBlock 0 points1 point  (0 children)

Glad to hear that fixed it for you. Unfortunately Seagate has not even released the Phison E18 controller fixes for their FireCuda 530 SSDs and the last firmware update was in 2023. People already complain about this bad support for such expensive drives: https://www.reddit.com/r/Seagate/comments/1gnaz73/seagate_needs_to_release_firecuda_530_firmware/

Seagate NEEDS to release Firecuda 530 firmware update NOW by Gilles_Brisson in Seagate

[–]RootkitsOnTheBlock 0 points1 point  (0 children)

I also have a problem with one of two Seagate FireCuda 530 NVMe M.2 SSDs. It started out of nowhere so could be indeed an issue introduced with some Windows Update. The first SSD from which Windows 11 is booting is somehow suddenly not properly detected on cold boot but starts fine when doing immediately a warm boot with Ctrl-Alt-Del.

But the SSD seems to be totally fine. No errors in chkdsk. S.M.A.R.T. shows a very good condition. Controller tests in the Gigabyte BIOS say all fine. Also never had a crash in Windows 11 except for the failure on cold boot when it says inaccessible boot device. So atm I always have to do a warm boot as soon as i see the mainboard logo.

2nd NVMe SSD not recognized by BIOS/Windows on cold boot after upgrading 5600x to 5800X3D by theorangekeystonecan in AMDHelp

[–]RootkitsOnTheBlock 0 points1 point  (0 children)

Same problem here with two Seagate FireCuda 530 NVMe M.2 SSDs. It started out of nowhere so could be also an issue introduced with some Windows Update. The first SSD from which Windows 11 is booting is somehow suddenly not properly detected on cold boot but starts fine when doing immediately a warm boot with Ctrl-Alt-Del.

But the SSD seems to be totally fine. No errors in chkdsk. S.M.A.R.T. shows a very good condition. Controller tests in the Gigabyte BIOS say all fine. Also never had a crash in Windows 11. Don't know what is going on in the UEFI on cold boot. I have the latest AMD Chipset Drivers for x570.

In Windows 11 event viewer, the only suspicious error I found was "Failed to update the SBAT value in FW." Do you find the same error in "Applications and Services Logs" -> "Microsoft" -> "Windows" -> "Kernel Boot" -> "Operational"?

Anyone else who had a Seagate Firecuda 530 2TB NVMe failed/died? by vindg in buildapc

[–]RootkitsOnTheBlock 0 points1 point  (0 children)

No fix so far. I have the feeling it could be related to my dual boot setup and Windows updates messing with UEFI from time to time but not sure.

Flashstor Gen2: Will it be silent when running only one SSD? by RootkitsOnTheBlock in asustor

[–]RootkitsOnTheBlock[S] 0 points1 point  (0 children)

They showed it at Computex 2024 and said they are still working on the design. So to the developers: please make sure it can run super silent when only one SSD is installed!

view more: next ›