I also got this Banner…(Disk Likely to Fail Soon), So I did a complete back-up and installed 2 new SSD’s, in place of the HDD’s. Which was a dual boot system with Fed. 42 and Windows 10. Now I’ve got the 1st. SSD with Fed. 42 installed, which seems to be okay,. and Nothing on the second SSD. I do have an iso of Windows 10 on a thumb-drive but don’t know how to get the new drive to install it… any good tips / ideas as to how I can go about getting the Windows 10 on the second SSD and also have it set up again as a dual boot system? If I have to go into the BIOS, what are / would be the correct settings? thanks
It’s easier to install Windows first, then install Fedora and during setup point Fedora to the ESP (mounted at /boot/efi) that Windows created. Make sure that Fedora won’t re-format the ESP.
This way Fedora will detect the existing Wlndows system and automatically add it to grub boot menu.
As for your BIOS setup, don’t touch it, just make sure it’s set to UEFI, and not „legacy BIOS“.
Normally an ESP of 100 MB is sufficient for dual booting, but if you don’t mind, set the ESP to 1GB as in the future Fedora will use UKI that will be stored on the ESP partition.
Windows should ALWAYS be installed first on an empty SSD because it wants to litter the SSD with partitions used only by windows.
It goes both ways; Windows will re-use EFI created by Linux, and Linux (all mainstreams) re-uses Windows EFI.
If you’re using separate disks, install any OS first, disconnect/hide the drive, then the next OS; both drives have separate EFI partitions, both drives can do their own efi vars independently, and with GRUB, you can set it primary and it’ll auto-detect Windows EFI allowing selecting either Linux or Windows.
Presently I’ve REINSTALLED both HDD’s… Mainly because I can not make a Windows 10 iso on a thumbdrive… because I can not find / download / install WoeUSB anywhere… I searched many suggestions and variations in the konsole and just get no WoeUSB. I don’t know if it is only for Fed42 ? Does anyone know anything about this? It seems, normally that that is the best way to go for getting a Windows iso on a thumbdrive on Fedora, to do a new install of Windows 10. on a new empty SSD. Anyone have any other ideas / tips / suggestions?
Also as soon as I started the PC with the old HDD, I immediately got the RED BANNER about Disk failing soon. So I did a DNF update and am presently running the Disk test to see what results come back…It looks like in my case, it did fail…
I will do a restart and run it again for certain results…So I ran a test again after a restart and get the same RED BANNER: DISK IS LIKELY TO FAIL SOON ! Is there any possibility that GNOME is still the problem, or is this DEFINITELY my DISK GOING DOWN ?
Please post the result of your smartctl -x /dev/<device> command (run as root) here, so we can examine what the disk is actually reporting.
Regarding the Windows 10 USB, to be honest, I’m not sure what options are available nowadays. I typically run a Windows VM and create the bootable USB using Rufus within the VM. However, there may be a better or native tool that someone can recommend.
What is the entry in the konsole, as root when I am already logged in as sudo ? I can’t reboot right now because I found a way to Run Windows 10 onto a thumbdrive, using Fedora Media Writer. it will be a little while before it’s finished…
This is the read out with your entry… 
~$ smartctl -x /dev/
bash: syntax error near unexpected token `newline’
Download their script and run it; works any distro even LiveUSB:
wget -O '/tmp/woeusb.bash' 'https://github.com/WoeUSB/WoeUSB/releases/download/v5.2.4/woeusb-5.2.4.bash' && chmod +x '/tmp/woeusb.bash'
sudo dnf install 'wimlib-utils'
sudo '/tmp/woeusb.bash' --device ~/'Downloads/en-us_windows_10.iso' '/dev/sda'
If you’re doing a Windows install in EFI, you can format USB as plain NTFS and copy extracted Windows ISO as-is to it. FAT32 works too with smaller install.wim (10’s fine; 11 24H2 exceeds 4GB)
Ok, I found the alternative… sudo -i for root…
So now I gave in : $ sudo -i smartctl-x/dev/sbd1 … and here is the read out: -bash: line 1: smartctl-x/dev/sbd1: No such file or directory.
So something is wrong or missing. What do you think?
And now I have another problem with the konsole… there are 323 packages downloaded, but not installed. Here is the read out from that: [323/323] Total 100% | 0.0 B/s | 0.0 B | 00m06s
Running transaction
Transaction failed: Rpm transaction failed.
- file /usr/lib64/vlc/plugins/codec/libfaad_plugin.so from install of vlc-plugins-base-1:3.0.21-24.fc42.x86_64 conflicts with file from package vlc-plugins-freeworld-3.0.21-4.fc42.x86_64
- So how do i resolve this problem, because it’s possible the fix for the Disk problem in in this bunch of packages…?
It should be smartctl -x /dev/sda or generally smartctl -x <device>—there’s a typo in your command. You can find your device name using lsblk.
For example, it could be /dev/sda or /dev/nvme0n1.
Hi Ngi, ok, finally got a test read out.
I don’t know what all the data says / means.
Hereis a copy paste:
=== START OF INFORMATION SECTION ===
Model Family: HGST Travelstar 7K1000
Device Model: HGST HTS721075A9E630
Serial Number: JR13006R008S8E
LU WWN Device Id: 5 000cca 7dac020d9
Firmware Version: JB2OA3J0
User Capacity: 750’156’374’016 bytes [750 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 2.5 inches
Device is: In smartctl database 7.5/5706
ATA Version is: ATA8-ACS T13/1699-D revision 6
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sun Jun 29 09:40:34 2025 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM level is: 128 (minimum power consumption without standby)
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, frozen [SEC2]
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 45) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 123) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate PO-R-- 100 100 062 - 0
2 Throughput_Performance P-S— 100 100 040 - 0
3 Spin_Up_Time POS— 124 124 033 - 2
4 Start_Stop_Count -O–C- 096 096 000 - 7747
5 Reallocated_Sector_Ct PO–CK 100 100 005 - 0
7 Seek_Error_Rate PO-R-- 100 100 067 - 0
8 Seek_Time_Performance P-S— 100 100 040 - 0
9 Power_On_Hours -O–C- 038 038 000 - 27518
10 Spin_Retry_Count PO–C- 100 100 060 - 0
12 Power_Cycle_Count -O–CK 096 096 000 - 6955
191 G-Sense_Error_Rate -O-R-- 100 100 000 - 0
192 Power-Off_Retract_Count -O–CK 100 100 000 - 181
193 Load_Cycle_Count -O–C- 001 001 000 - 3109507
194 Temperature_Celsius -O---- 157 157 000 - 38 (Min/Max 14/49)
196 Reallocated_Event_Count -O–CK 100 100 000 - 0
197 Current_Pending_Sector -O—K 100 100 000 - 8
198 Offline_Uncorrectable —R-- 100 100 000 - 0
199 UDMA_CRC_Error_Count -O-R-- 200 200 000 - 0
223 Load_Retry_Count -O-R-- 100 100 000 - 0
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning
General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 SL R/O 1 Summary SMART error log
0x02 SL R/O 1 Comprehensive SMART error log
0x03 GPL R/O 1 Ext. Comprehensive SMART error log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 1 Extended self-test log
0x09 SL R/W 1 Selective self-test log
0x10 GPL R/O 1 NCQ Command Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data Transfer
SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
No Errors Logged
SMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
1 Extended offline Completed: read failure 90% 27515 114185104
2 Short offline Completed without error 00% 27515 -
3 Extended offline Completed: read failure 90% 27514 114185104
4 Short offline Completed without error 00% 27512 -
5 Extended offline Completed: read failure 90% 27512 114185104
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
SCT Status Version: 3
SCT Version (vendor specific): 256 (0x0100)
Device State: Active (0)
Current Temperature: 38 Celsius
Power Cycle Min/Max Temperature: 29/38 Celsius
Lifetime Min/Max Temperature: 14/49 Celsius
Specified Max Operating Temperature: 32 Celsius
Under/Over Temperature Limit Count: 0/0
SCT Temperature History Version: 2
Temperature Sampling Period: 1 minute
Temperature Logging Interval: 1 minute
Min/Max recommended Temperature: 0/60 Celsius
Min/Max Temperature Limit: -40/65 Celsius
Temperature History Size (Index): 128 (30)
Index Estimated Time Temperature Celsius
31 2025-06-29 07:33 38 *******************
… ..( 21 skipped). .. *******************
53 2025-06-29 07:55 38 *******************
54 2025-06-29 07:56 37 ******************
55 2025-06-29 07:57 38 *******************
… ..( 6 skipped). .. *******************
62 2025-06-29 08:04 38 *******************
63 2025-06-29 08:05 39 ********************
… ..( 4 skipped). .. ********************
68 2025-06-29 08:10 39 ********************
69 2025-06-29 08:11 38 *******************
… ..( 3 skipped). .. *******************
73 2025-06-29 08:15 38 *******************
74 2025-06-29 08:16 39 ********************
75 2025-06-29 08:17 39 ********************
76 2025-06-29 08:18 39 ********************
77 2025-06-29 08:19 ? -
78 2025-06-29 08:20 39 ********************
79 2025-06-29 08:21 40 *********************
80 2025-06-29 08:22 40 *********************
81 2025-06-29 08:23 40 *********************
82 2025-06-29 08:24 41 **********************
… ..( 4 skipped). .. **********************
87 2025-06-29 08:29 41 **********************
88 2025-06-29 08:30 40 *********************
89 2025-06-29 08:31 40 *********************
90 2025-06-29 08:32 41 **********************
… ..( 3 skipped). .. **********************
94 2025-06-29 08:36 41 **********************
95 2025-06-29 08:37 40 *********************
… ..( 2 skipped). .. *********************
98 2025-06-29 08:40 40 *********************
99 2025-06-29 08:41 39 ********************
… ..( 4 skipped). .. ********************
104 2025-06-29 08:46 39 ********************
105 2025-06-29 08:47 ? -
106 2025-06-29 08:48 39 ********************
107 2025-06-29 08:49 40 *********************
108 2025-06-29 08:50 41 **********************
… ..( 5 skipped). .. **********************
114 2025-06-29 08:56 41 **********************
115 2025-06-29 08:57 40 *********************
… ..( 3 skipped). .. *********************
119 2025-06-29 09:01 40 *********************
120 2025-06-29 09:02 41 **********************
… ..( 2 skipped). .. **********************
123 2025-06-29 09:05 41 **********************
124 2025-06-29 09:06 40 *********************
… ..( 2 skipped). .. *********************
127 2025-06-29 09:09 40 *********************
0 2025-06-29 09:10 39 ********************
1 2025-06-29 09:11 39 ********************
2 2025-06-29 09:12 40 *********************
3 2025-06-29 09:13 39 ********************
… ..( 4 skipped). .. ********************
8 2025-06-29 09:18 39 ********************
9 2025-06-29 09:19 38 *******************
… ..( 9 skipped). .. *******************
19 2025-06-29 09:29 38 *******************
20 2025-06-29 09:30 ? -
21 2025-06-29 09:31 ? -
22 2025-06-29 09:32 ? -
23 2025-06-29 09:33 30 ***********
24 2025-06-29 09:34 31 ************
25 2025-06-29 09:35 32 *************
26 2025-06-29 09:36 34 ***************
27 2025-06-29 09:37 35 ****************
28 2025-06-29 09:38 36 *****************
29 2025-06-29 09:39 37 ******************
30 2025-06-29 09:40 38 *******************
SCT Error Recovery Control:
Read: Disabled
Write: Disabled
Device Statistics (GP/SMART Log 0x04) not supported
Pending Defects log (GP Log 0x0c) not supported
SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x0001 2 0 Command failed due to ICRC error
0x0002 2 0 R_ERR response for data FIS
0x0003 2 0 R_ERR response for device-to-host data FIS
0x0004 2 0 R_ERR response for host-to-device data FIS
0x0005 2 0 R_ERR response for non-data FIS
0x0006 2 0 R_ERR response for device-to-host non-data FIS
0x0007 2 0 R_ERR response for host-to-device non-data FIS
0x0009 2 29876 Transition from drive PhyRdy to drive PhyNRdy
0x000a 2 8 Device-to-host register FISes sent due to a COMRESET
0x000b 2 0 CRC errors within host-to-device FIS
0x000d 2 0 Non-CRC errors within host-to-device FIS
Maybe you can understand what it means and let me know if the Disk is actually bad or is it just a false reading with GNOME.
Once again, I tried a DNF update, and got the same readout as last time :
[361/361] Total 100% | 1.6 MiB/s | 32.6 MiB | 00m21s
Running transaction
Transaction failed: Rpm transaction failed.
- file /usr/lib64/vlc/plugins/codec/libfaad_plugin.so from install of vlc-plugins-base-1:3.0.21-24.fc42.x86_64 conflicts with file from package vlc-plugins-freeworld-3.0.21-4.fc42.x86_64
Does this mean that NONE of the packages were installed, or just the vlc-plugin package was not installed… My understanding is that NONE of them have been installed, which probably means that the GNOME “WARNING” is still the problem, and that the fix is in the un-installed packages.
Thanks for your time and patience…
Holy moly! Replace the drive ASAP; it is failing hard, and it will likely only get worse. You already have 8 sectors pending reallocation, and your SMART tests have failed. Additionally, the drive is somewhat old.
Next time, make sure to configure disk power management better. Your Load_Cycle_Count is extremely high (if I read that correctly), more than three times what the drive is rated for.
My recommendation is to keep this drive spinning without turning it off, as that causes most of the load on it, and back up everything as soon as possible.
Not related to the health of your disk, but -
Correct, none of them have been installed.
You can install all the non-VLC updates using sudo dnf update -x 'vlc*' - Is anyone else getting this VLC clash while updating to most recent bits? - #10 by vekruse
Hi, I have already backed everything up. I have also a new SSD with Fed42 installed and it works.
My next problem is how to install Windows 10 on the second SSD, which is completely blank. I have a USB Stick with a Windows 10 iso, but don’t know how to get it onto the new SSD. It was a dual boot sytem earlier and worked fine. I don’t know how to install the Windows onto the second SSD. I tried taking out the Fed. SSD but that didn’t work. The system just doesn’t seem to co-ordinate between the new SSD and the USB w/ the iso. I spent all kinds of time messing around with different settings in the BIOS and don’t know if I screwed things up. When I started the system today it started okay and says, Fed. 42 or Windows boot manager, so I tried clicking on Windows boot manager with the USB in a slot, but nothing happened. Presently I have the old HDD running, so that I could do the test. But I can change it out for the new SSD also with FED 42.
Do you have any ideas about solving this problem?
Also how can I get the update to work on the old HDD, before I retire it. The DNF updates on the New SSD do’t seem to be a problem. I did one a short while ago.
What are and how can I adjust the “DISK POWER MANAGEMENT” Settings ?
The updates are running now and have installed completely, except for vcl.
Interesting, since the new DNF updates, the RED BANNER warning about the HDD has disappeared…
I don’t think there is any GUI for it. You can disable it by installing the hdparm package and running hdparm -B 255 <device>. You can refer to hdparm - ArchWiki (though it’s not a Fedora wiki, it works for Fedora as well) for instructions on how to make that persistent.
You can (and should) also complain to the manufacturer for setting the disk’s power defaults this way, as that is the core issue. 
One question is, do I need the Power management with the new SDD’s or is it mainly useful for HDD’s ?
Still can not get Windos10 on the second SSD. I removed the SDD with Fedora42, but the system is still not recognizing the blank SDD nor the USB Stick. With the SDD w/ Fed, the system boots up normally, giving the choice of which OS to chose from, Fed, Fed rescue, Windows Boot, or UEFI, but when I click on it, the choice for Windows, it goes immediately to the BIOS window.
There must be a way to install Windows on the empty SDD. I was wondering if it could be done with an USB / SDD external adapter, using another Laptop ?
SSD Power Management: No, SSDs have very different power management. The issue with your HDD was improperly configured power management from the manufacturer, which probably lowered its lifespan as the disk was spinning down too often.
Windows 10: This operating system will soon be out of support, so you should consider upgrading to Windows 11.
Installing it on SSD: I am uncertain what issue you are experiencing, but if you are looking to see the USB in your GRUB, that’s not how it works. You need to create a bootable USB with Windows (for example, using another Windows machine or a VM with Rufus - you can use other tools, but this one has worked most reliably for me) and then enter the boot menu from your BIOS/UEFI (refer to your laptop or motherboard manual; it is often accessed by pressing F9, F10, F11, or F12) and choose the USB stick there.
I used Fed Media Writer to put the iso on the 8 GB memory stick. I will try Rufus later. Now I need some fresh air. Will let you know what happens.