Moderator

 • 

4.1K Posts

March 13th, 2025 05:09

Hi,

 

This situation sound like RAID puncture: http://del.ly/612180OfNu which resides in the drive and VD array. 

 

 

Moderator

 • 

5.4K Posts

March 31st, 2022 18:00

Hi, thanks for choosing Dell. Best we take a look at your logs. Is your system still in warranty?

1 Rookie

 • 

3 Posts

April 1st, 2022 07:00

I believe it might not be since it is an older server. Do it need to be under warranty to get help with this issue?

Moderator

 • 

4K Posts

April 1st, 2022 09:00

No you can post here the logs and we can try to give you an help.

Thanks
Marco

1 Rookie

 • 

3 Posts

April 1st, 2022 10:00

Do I just copy and paste the logs? I attached them using the support portal.

Moderator

 • 

4.7K Posts

April 1st, 2022 11:00

Hello Cmiranda15,

 

It sounds like you may have a puncture.  You can search the log for "Puncture" see what shows up.

 

You can upload the PERC log [ here ] to the Service Tag of the server and Private message Young and myself the service tag number.

 

 

I'll supply some other reference information for you:

 

How to Fix a RAID Puncture

https://dell.to/3LvHvyE

 

Double Faults and Punctures in RAID Arrays

https://dell.to/3uLszWk

 

How to Handle Puncturing (Bad Blocks) on Virtual Disks for PowerEdge servers

https://dell.to/3uMkAse

 

 

 

Basic steps for virtual disk bad blocks:

 

1. Get file level, not block level, backup of the data

2. Update the firmware of the hard drives and RAID controller

3. Run a Consistency Check on the virtual disk (via OMSA)

4. Clear the bad block table for the virtual disk (via OMSA)

   (Then monitor for any new bad blocks or other issues)

 

 

Virtual Disk Bad Block process:

 

1 Run consistency check

Consistency check:

Expand Storage>expand controller. Select ‘Virtual Disk’. Choose ‘Check Consistency’ from dropdown and Execute.

 

 

2   Perform a backup of the virtual disk with the Verify option selected.  Do a full backup with system state, with Verify.

  

*  Backup operation fails on one or more files. In this case, restore the file from a previous backup. After restoring the file, proceed to step 3. 

 *  Backup operation completes without error. This indicates that there are no bad blocks on the written portion of your virtual disk.  If you still receive bad block warnings, the bad blocks are in a non-data area. Proceed to Step 3

 

3   Run Patrol Read and check the system event log to ensure that no new bad blocks are found. 

To run Patrol Read: Select H710 in left column under Storage. Click Information&Configuration hyper link at top of page. Go to Controller Task drop down. Select ‘Start Patrol Read’ and Execute.

 

If bad blocks still exist, proceed to step 4. If not, the condition is cleared without the need for step 4.

 

4   To clear these bad blocks, execute the Clear Virtual Disk Bad Blocks task. 

 To clear the virtual disk bad blocks: Select the ‘Virtual Disk’ link under the H710. In the drop down choose ‘Clear Virtual Disk Bad Block’ and Execute.

 

5 Once the above steps are complete, set the Patrol Read to Auto:

 Select H710 in left column under Storage. Click Information&Configuration hyper link at top of page. Go to Controller Task drop down. Select ‘Set Patrol Read Mode’, Execute.  Choose Auto and Apply Changes.

 

 

Moderator

 • 

5.4K Posts

April 3rd, 2022 23:00

Hi, we ran your service tag and yes the warranty was expired in 2017. I'm afraid we can't help you with log analysis but it seems like you tried replacing with a non-Dell disk.

Moderator

 • 

4.7K Posts

April 4th, 2022 05:00

Hello Cmiranda15,

 

I looked over the controller log. Below I outlined an action plan.  The other reference links I provided would be good to review over.

 

Action plan:

1. Get file level, not block level, backup of the data

2. Update the firmware of the hard drives  v. ES68 : https://dell.to/3LDWTsL

3. Run a Consistency Check on the virtual disk (via OMSA)

4. Clear the bad block table for the virtual disk (via OMSA)

   (Then monitor for any new bad blocks or other issues)

5. Run diagnositcs: Boot to  F11 on Dell Splash screen, selecting  Boot Manager -> System Utilities -> Launch Dell Diagnostics.  Note any messages and continue testing.

 

1 Rookie

 • 

2 Posts

March 13th, 2025 00:05

Hi,

I have same issue with these log

Unable to log block 0x277f673ff.Bad block table on Virtual Disk 1 on RAID Controller in Slot 6 is full.

I have replace disks with new but not all disk have replaced.

PERC ctrl has been replaced too.

then I have recreate New VD, but this issue still happen.

with 2 disk have predictive and 2 disk punctured and VD alert BAD BLOCK yes.

this issue happen again in state NO DATA in current VD and not mounted in to OS.

my data has been lost but this issue still facing again, I think this is must be replacing all DISK in the VD have issue with BAD BLOCK.

my environment is DELL R740XD using PERC H740P Adapter and SAS DISK 2.4TB.

(edited)

No Events found!

Top