Data domain upgrade precheck fails with this message "Error in boot_fsck"
Summary: Data Domain upgrade precheck fails with this message: "Error in boot_fsck"
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
When you run the upgrade precheck, you will get this message:
Error in boot_fsck Check and replace bad head-unit diskIn the autosupport report, you will see it under System Upgrade Status:
System Upgrade Status
---------------------
Current Upgrade Status: DD OS precheck found 1 blocking issue(s)
Node Severity Issue Solution
---- -------- ------------------------------ --------
0 CRITICAL Error in boot_fsck Check and replace bad
head-unit disk Cause
A head unit spare disk has failed and it is not being used at the moment, so the DDOS does not report the issue thus not producing a clear alert.
Resolution
The logs under /ddvar/log/debug/messages.engineering will display this command:
boot_fsck: failed 1 head disksThe logs under /ddvar/log/debug/platform/infra.log will display this:
01/10 07:33:21: boot_fsck: failed to sync disk dm-11p1 01/10 07:43:24: boot_fsck: failed to sync disk dm-11p1
Now, we clearly know there is a failed disk. We need to identify it in order to replace it.
This file /ddvar/log/debug/platform/dm_map.sub contains a map of the disks to dms
Enclosure 1 DD6300 FXTCS214200059
Enclosure 2 ES30 CK210220317620
Disk UUID DM Dev Maj:Min SD Maj:Min SG HCTL Path State
--------------------------------------------------------------------------------------------------------------
1.1 HITACHI_5000CCA0BCCB4E48 dm-2 254:32 sdj 8:144 sg9 0:0:9:0 hu:Active ONLINE
1.2 HITACHI_5000CCA0BCCB4CF0 dm-8 254:128 sdf 8:80 sg5 0:0:5:0 hu:Active ONLINE
1.3 HITACHI_5000CCA0BCCB4F20 dm-5 254:80 sdk 8:160 sg10 0:0:10:0 hu:Active ONLINE
1.4 HITACHI_5000CCA000CB0000 dm-10 254:160 sdd 8:48 sg3 0:0:3:0 hu:Active ONLINE
1.5 HITACHI_5000CCA0BCCB4F0C dm-3 254:48 sdl 8:176 sg11 0:0:11:0 hu:Active ONLINE
1.6 HITACHI_5000CCA0BCCB1EA8 dm-11 254:176 sdc 8:32 sg2 0:0:2:0 hu:Active SPARE
1.7 HITACHI_5000CCA0BCCB4BF0 dm-4 254:64 sdi 8:128 sg8 0:0:8:0 hu:Active ONLINE
1.8 HITACHI_5000CCA0BCCB0348 dm-13 254:208 sdb 8:16 sg1 0:0:1:0 hu:Active ONLINE
1.9 HITACHI_5000CCA0BCCB4E20 dm-1 254:16 sdm 8:192 sg12 0:0:12:0 hu:Active ONLINE
1.10 HITACHI_5000CCA0BCCB4BE0 dm-9 254:144 sde 8:64 sg4 0:0:4:0 hu:Active ONLINE
1.11 HITACHI_5000CCA0BCCB4C1C dm-6 254:96 sdh 8:112 sg7 0:0:7:0 hu:Active ONLINE
1.12 HITACHI_5000CCA0BCCAADB4 dm-12 254:192 sda 8:0 sg0 0:0:0:0 hu:Active ONLINE
1.13 HITACHI_5000CCA052685EEC dm-7 254:112 sdg 8:96 sg6 0:0:6:0 hu:Active ONLINE
1.14 (absent)
2.1 SEAGATE_5000C500E1D16B9B dm-14 254:224 sdn 8:208 sg14 1:0:0:0 7a:Active ONLINE
sdan 66:112 sg41 1:0:27:0 7c:Enabled
2.2 SEAGATE_5000C500E1F31277 dm-18 254:288 sdr 65:16 sg18 1:0:4:0 7a:Active ONLINE
sdap 66:144 sg44 1:0:30:0 7c:Enabled
2.3 SEAGATE_5000C500E1F272AB dm-17 254:272 sdq 65:0 sg17 1:0:3:0 7a:Active ONLINE
sdaq 66:160 sg45 1:0:31:0 7c:Enabled
2.4 SEAGATE_5000C500E21E7C97 dm-16 254:256 sdo 8:224 sg15 1:0:1:0 7a:Active ONLINE
sdao 66:128 sg43 1:0:29:0 7c:Enabled
2.5 SEAGATE_5000C500E1F330FB dm-15 254:240 sdp 8:240 sg16 1:0:2:0 7a:Active ONLINE
sdam 66:96 sg40 1:0:26:0 7c:Enabled
2.6 SEAGATE_5000C500E1F2A197 dm-19 254:304 sds 65:32 sg19 1:0:5:0 7a:Active ONLINE
sdak 66:64 sg38 1:0:24:0 7c:Enabled
2.7 SEAGATE_5000C500E1F0E76B dm-23 254:368 sdy 65:128 sg25 1:0:11:0 7a:Active ONLINE
sdah 66:16 sg35 1:0:21:0 7c:Enabled
2.8 SEAGATE_5000C500E1F0EB03 dm-20 254:320 sdaj 66:48 sg37 1:0:23:0 7c:Active ONLINE
sdt 65:48 sg20 1:0:6:0 7a:Enabled
2.9 SEAGATE_5000C500E21E946B dm-21 254:336 sdal 66:80 sg39 1:0:25:0 7c:Active ONLINE
sdu 65:64 sg21 1:0:7:0 7a:Enabled
2.10 SEAGATE_5000C500E21E659B dm-22 254:352 sdai 66:32 sg36 1:0:22:0 7c:Active ONLINE
sdv 65:80 sg22 1:0:8:0 7a:Enabled
2.11 SEAGATE_5000C500E1F337D3 dm-24 254:384 sdag 66:0 sg34 1:0:20:0 7c:Active ONLINE
From the above file, we identified that our disk is 1.6 and now we need to replace it.
You can use these commands and search the log files (like searching in Vim) instead of obtaining the whole bundle:
log view debug/messages.engineering log view debug/platform/infra.log log view debug/platform/dm_map.sub
Affected Products
Data DomainArticle Properties
Article Number: 000221198
Article Type: Solution
Last Modified: 12 Dec 2025
Version: 4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.