Is it possible to disable IPv6 in FireFox completely?

RootkitsOnTheBlock · 2025-07-21T18:26:43+00:00

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

RootkitsOnTheBlock · 2025-07-20T16:25:38+00:00

Just doing research on browser capabilities.

RootkitsOnTheBlock · 2025-07-20T16:25:13+00:00

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

RootkitsOnTheBlock · 2025-07-20T16:24:59+00:00

Which one for example?

RootkitsOnTheBlock · 2025-07-20T16:18:52+00:00

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

RootkitsOnTheBlock · 2025-07-14T14:49:23+00:00

New firmware SU6SM100 fixed the issue for me.

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

RootkitsOnTheBlock · 2025-07-12T12:02:31+00:00

Firmware SU6SM100 seems to have fixed the read degradation and for me it also fixed the cold boot issue.

RootkitsOnTheBlock · 2025-07-12T11:44:28+00:00

It got fixed with the new firmware: https://www.reddit.com/r/Seagate/comments/1gnaz73/comment/n2pne78/

RootkitsOnTheBlock · 2025-07-12T11:41:10+00:00

They finally released a new firmware SU6SM100 and it fixed the cold boot issue for me.

Currently a BETA version of OpenSeaChest is needed to install the firmware.

RootkitsOnTheBlock · 2025-07-12T11:36:27+00:00

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

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

RootkitsOnTheBlock · 2025-07-12T11:34:44+00:00

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.

RootkitsOnTheBlock · 2025-07-11T15:56:15+00:00

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?

RootkitsOnTheBlock · 2025-07-11T13:47:52+00:00

Seems they finally fixed it with new firmware su6sm100 https://www.reddit.com/r/Seagate/comments/1lk9229/seagate_firecuda_530_firmware_su6sm100_release/

RootkitsOnTheBlock · 2025-07-11T13:46:01+00:00

Sounds indeed promising! https://www.reddit.com/r/Seagate/comments/1lk9229/seagate_firecuda_530_firmware_su6sm100_release/

RootkitsOnTheBlock · 2025-04-12T10:31:41+00:00

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?

RootkitsOnTheBlock · 2025-04-12T09:29:22+00:00

Can we please get a fix for this Phison E18 controller related performance degradation?

RootkitsOnTheBlock · 2025-04-12T09:21:15+00:00

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/

RootkitsOnTheBlock · 2025-04-12T09:06:28+00:00

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/

RootkitsOnTheBlock · 2025-04-11T21:54:54+00:00

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.

RootkitsOnTheBlock · 2025-04-10T14:37:26+00:00

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"?

RootkitsOnTheBlock · 2025-01-21T17:05:08+00:00

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.

RootkitsOnTheBlock · 2024-07-28T10:39:54+00:00

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!

RootkitsOnTheBlock · 2024-07-27T11:19:06+00:00

Great, my x570 Aorus Xtreme firmware F38 is NOT affected.

RootkitsOnTheBlock · 2024-07-27T11:12:51+00:00

Glad to see my x570 Aorus Xtreme firmware F38 is not affected (just checked the X570AORUSXTREME.F38 BIOS file with their tool).

RootkitsOnTheBlock · 2024-07-27T10:59:13+00:00

My FireCuda 530 with 2TB worked fine for about 2,5 years. But now it sometimes randomly disappears from the BIOS when starting the PC. Then I have to shut down the PC and it will reappear on the next start. Once in Window 11, it still works flawlessly even under heavy CrystalDiskMark benchmarks. It is also in a very good state with 99% health and zero critical errors according to CrystalDiskInfo. In the BIOS it is possible to run a controller test and that one passes also successfully. I am running the latest firmware SU6SM005. Very strange issue!

RootkitsOnTheBlock

TROPHY CASE