SMART error (CurrentPendingSector) detected on host

crisman · 9. Januar 2015

Hi Guys,

I've one HD that is on Raid5/LVM volume that is failing according to the Short Smart Test, what is the best procedure for replace it?

Thanks.

WastlJ · 9. Januar 2015

Depending if your SATA is capable of HotPlug, detach your drive or shutdown your NAS and then detach your drive. Plug a new drive in, and start your NAS. Then you can add it to your RAID and it will start a rebuild.

ryecoaaron · 9. Januar 2015

mdadm --fail /dev/mdX /dev/sdY
mdadm --remove /dev/mdX /dev/sdY
mdadm --add /dev/mdX /dev/sdZ

If you post cat /proc/mdstat and fdisk -l, I can help more.

crisman · 9. Januar 2015

Zitat

root@server-nas:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md126 : active raid5 sdb[0] sde[2] sdd[1]
1953262592 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]

md127 : active raid5 sdc[0] sdi[4] sdg[3] sdf[2] sdh[1]
7813531648 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/5] [UUUUU]

unused devices: <none>

Alles anzeigen

Zitat

root@server-nas:~# fdisk -l

Disk /dev/sda: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders, total 117231408 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00098c7c

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 112383999 56190976 83 Linux
/dev/sda2 112386046 117229567 2421761 5 Extended
/dev/sda5 112386048 117229567 2421760 82 Linux swap / Solaris

Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x81ac81ac

Disk /dev/sdc doesn't contain a valid partition table

Disk /dev/sdg: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x81ac81ad

Disk /dev/sdg doesn't contain a valid partition table

Disk /dev/sdi: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Disk /dev/sdi doesn't contain a valid partition table

Disk /dev/sdh: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Disk /dev/sdh doesn't contain a valid partition table

Disk /dev/sdf: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Disk /dev/sdf doesn't contain a valid partition table

Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/sdd doesn't contain a valid partition table

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/sdb doesn't contain a valid partition table

Disk /dev/sde: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/sde doesn't contain a valid partition table

WARNING: GPT (GUID Partition Table) detected on '/dev/md127'! The util fdisk doesn't support GPT. Use GNU Parted.

Disk /dev/md127: 8001.1 GB, 8001056407552 bytes
2 heads, 4 sectors/track, 1953382912 cylinders, total 15627063296 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 2097152 bytes
Disk identifier: 0x00000000

Disk /dev/md127 doesn't contain a valid partition table

Disk /dev/md126: 2000.1 GB, 2000140894208 bytes
2 heads, 4 sectors/track, 488315648 cylinders, total 3906525184 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Disk identifier: 0x00000000

Disk /dev/md126 doesn't contain a valid partition table

WARNING: GPT (GUID Partition Table) detected on '/dev/mapper/vg01-lv01'! The util fdisk doesn't support GPT. Use GNU Parted.

Disk /dev/mapper/vg01-lv01: 8001.1 GB, 8001054310400 bytes
256 heads, 63 sectors/track, 968939 cylinders, total 15627059200 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 2097152 bytes
Disk identifier: 0x05e4e67f

Device Boot Start End Blocks Id System
/dev/mapper/vg01-lv01p1 1 4294967295 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.

Disk /dev/mapper/vg00-lv00: 2000.1 GB, 2000137748480 bytes
255 heads, 63 sectors/track, 243169 cylinders, total 3906519040 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/vg00-lv00 doesn't contain a valid partition table
root@server-nas:~#

Alles anzeigen

ryecoaaron · 9. Januar 2015

Which drive is failing?

crisman · 9. Januar 2015

The drive failing is /dev/sdg.

I'm also worried about the messages "Drive xxx doesn't contain a valid partition table"

ryecoaaron · 9. Januar 2015

OMV raid doesn't use partition tables. Not a problem

mdadm --fail /dev/md127 /dev/sdg
mdadm --remove /dev/md127 /dev/sdg

turn system off and replace drive

mdadm --add /dev/md127 /dev/sdZ

Still need to change Z in last line to new drive. Should be g if you replace other drive.

crisman · 9. Januar 2015

Ok! Will do it after lunch and then back with news when possible.

Thanks Guys!

WastlJ · 9. Januar 2015

The command line guy This is also possible via GUI if you like to do it more user friendly.

ryecoaaron · 9. Januar 2015

You can't remove the drive properly from the GUI

crisman · 9. Januar 2015

OK! drive added and rebuild in progress!
The new drive appears has /dev/sde.

Don't understand why, after each reboot the drive identification most of the times changes, what could cause this?

@WastlJ The only option I was able to see on the GUI was "adding" a drive to the degraded raid, the other options "Mark has failed and Remove" could not see them.

ryecoaaron · 9. Januar 2015

OMV uses the uuid of the drive. So, the drive letter doesn't matter. They may change because of initialization sequence at boot. Nothing to worry about Glad it is rebuilding.

WastlJ · 9. Januar 2015

Thought removing is possible since OMV 1.X?

crisman · 9. Januar 2015

Zitat von WastlJ

Thought removing is possible since OMV 1.X?

Apparently not, at least I couldn't found it!

ryecoaaron · 9. Januar 2015

You can remove a missing drive but not from raid.

crisman · 9. Januar 2015

Honestly I think this 3 steps should be possible trough the GUI, this would simplify the user who has no skills in command line (linux).

ryecoaaron · 9. Januar 2015

Zitat von crisman

Honestly I think this 3 steps should be possible trough the GUI, this would simplify the user who has no skills in command line (linux).

Bug filed here.

crisman · 9. Januar 2015

Great!

Jetzt mitmachen!