My Oracle Support Banner

Bad Sectors found On A Hard Disk during Scrubbing Job (Doc ID 2861670.1)

Last updated on NOVEMBER 16, 2022

Applies to:

Exadata X7-2 Hardware - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

 Bad sectors were found in one of the cell disk as per the cell alert log and other supporting traces.

 

From alert_<cellnode01>.log

Read Error:Generic I/O error[201], on Grid Disk DATAC1_CD_05_<cellnode01> at grid disk offset 89158320128 bytes (device /dev/sdf sector 174235648) with size 1048576 bytes from disk scrub
2022-03-31T02:07:36.137135+02:00
Read Error on Cell Disk CD_05_<cellnode01> (/dev/sdf) at device offset 89435144192 bytes with size 1048576 bytes membuf 0x1cde600000, bioreq 0x23e92e3a4 (errno: No data available [61])
Read Error:Generic I/O error[201], on Grid Disk DATAC1_CD_05_<cellnode01> at grid disk offset 89384812544 bytes (device /dev/sdf sector 174678016) with size 1048576 bytes from disk scrub
2022-03-31T02:07:48.772073+02:00
Broadcast: 1 events ASM REPAIR diskgroup of opcode 10 for diskgroup DATAC1 to:
ClientHostName = exaalcdb02.bde.es, ClientPID = 66569
Broadcast: 1 events ASM REPAIR diskgroup of opcode 10 for diskgroup DATAC1 to:
ClientHostName = exaalcdb01.bde.es, ClientPID = 255207
2022-03-31T02:07:49.551343+02:00
The block starting from offset 89158320128 on grid disk DATAC1_CD_05_<cellnode01> (device /dev/sdf sector 174235648) with size 1M is being repaired>>>>>>>>>>>>>>>>>>>>>>
The block starting from offset 89159368704 on grid disk DATAC1_CD_05_<cellnode01> (device /dev/sdf sector 174237696) with size 1M is being repaired
The block starting from offset 89160417280 on grid disk DATAC1_CD_05_<cellnode01> (device /dev/sdf sector 174239744) with size 1M is being repaired

022-03-31T16:25:49.065972+02:00
Finished scrubbing CellDisk:CD_06_<cellnode01>, scrubbed blocks (1MB):9342144, found bad blocks:0
2022-03-31T16:27:57.966328+02:00
Finished scrubbing CellDisk:CD_10_<cellnode01>, scrubbed blocks (1MB):9342144, found bad blocks:0
2022-03-31T16:29:40.452104+02:00
Finished scrubbing CellDisk:CD_05_<cellnode01>, scrubbed blocks (1MB):9342144, found bad blocks:3>>>>>>>>>>>>>>>>>>
2022-03-31T16:32:20.817553+02:00
Finished scrubbing CellDisk:CD_01_<cellnode01>, scrubbed blocks (1MB):9342144, found bad blocks:0
2022-03-31T16:34:32.859191+02:00
Finished scrubbing CellDisk:CD_08_<cellnode01>, scrubbed blocks (1MB):9342144, found bad blocks:0
2022-03-31T16:37:13.817131+02:00
Finished scrubbing CellDisk:CD_04_<cellnode01>, scrubbed blocks (1MB):9342144, found bad blocks:0

he block starting from offset 89387958272 on grid disk DATAC1_CD_05_<cellnode01> (device /dev/sdf sector 174684160) with size 1M is being repaired
2022-03-31T02:07:49.553834+02:00
The following 1 blocks were discovered by scrubbing disk DATAC1_CD_05_<cellnode01> [e653d03b-5911-41ad-ab48-89a4b85c31ed] but not repaired because they are not allocated by ASM>>>>
The block starting from offset 89384812544 on grid disk DATAC1_CD_05_<cellnode01> (device /dev/sdf sector 174678016) is skipped

 

//Cell Image version

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.