General NAS-Central Forums

Welcome to the NAS community
It is currently Fri Nov 24, 2017 5:33 am

All times are UTC




Post new topic Reply to topic  [ 44 posts ]  Go to page 1, 2, 3  Next
Author Message
PostPosted: Wed Jan 01, 2014 12:19 pm 
Offline

Joined: Thu Aug 09, 2012 11:15 am
Posts: 44
Hi, after an electric shutdown the NAS had the drives unmounted or at least I couldn't access the data. The red light was blinking.
I shutteddown the NAS with the front power button, then started it again and after some time the drives worked right again. I can access all my data (Music, Videos, etc), but the front red light still is blinking.

When I go to the web interface on the 'System Status' option I get this warnings:

Quote:
- 1 drive with existing data on your Iomega StorCenter ix2-200.
- Storage is degraded and data protection is at risk.


I have no idea about what to do to get the red light turn off. If I write in the cli the command:

Code:
cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid6] [raid5] [raid4]
md1 : active raid1 sda2[0]
      1932533488 blocks super 1.0 [2/1] [U_]

md0 : active raid1 sda1[0] sdb1[1]
      20980800 blocks [2/2] [UU]

unused devices: <none>


So everything seems to be fine. Any ideas? My firmware is 3.2.6.21659 and the disks are set on RAID 1.


Top
 Profile  
 
PostPosted: Thu Jan 02, 2014 9:14 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6075
The data raid array is degraded:
Code:
md1 : active raid1 sda2[0]
There is no sdb2, while it should. The system array is fine:
Code:
md0 : active raid1 sda1[0] sdb1[1]
So the disk is not dead.

Maybe a
Code:
mdadm --examine /dev/sd[ab]2
can tell what is going on. This will show the raid headers of the 2 data partitions.


Top
 Profile  
 
PostPosted: Thu Jan 02, 2014 1:43 pm 
Offline

Joined: Thu Aug 09, 2012 11:15 am
Posts: 44
Thanks, although I don't understand well what's happening. After mdadm --examine:

Quote:
mdadm --examine /dev/sda2
/dev/sda2:
Magic : a92b4efc
Version : 1.0
Feature Map : 0x0
Array UUID : cba54300:251e4d89:9dbf101c:f04b7735
Name : ix2-200-D8S0EN:1 (local to host ix2-200-D8S0EN)
Creation Time : Fri Jun 8 03:34:59 2012
Raid Level : raid1
Raid Devices : 2

Avail Dev Size : 3865066976 (1843.01 GiB 1978.91 GB)
Array Size : 3865066976 (1843.01 GiB 1978.91 GB)
Super Offset : 3865067232 sectors
State : clean
Device UUID : 6c2a7f2c:7c29e513:b6a4e8ed:13fc606b

Update Time : Thu Jan 2 14:40:13 2014
Checksum : 2fadeb58 - correct
Events : 1255903


Array Slot : 0 (0, 1)
Array State : Uu


Quote:
mdadm --examine /dev/sda1
/dev/sda1:
Magic : a92b4efc
Version : 00.90.00
UUID : bb7db4dd:fdee1f62:a266f1a9:a2250747
Creation Time : Fri Jun 8 03:23:38 2012
Raid Level : raid1
Used Dev Size : 20980800 (20.01 GiB 21.48 GB)
Array Size : 20980800 (20.01 GiB 21.48 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0

Update Time : Thu Jan 2 14:48:02 2014
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : 4bae57d0 - correct
Events : 5909065


Number Major Minor RaidDevice State
this 0 8 1 0 active sync /dev/sda1

0 0 8 1 0 active sync /dev/sda1
1 1 8 17 1 active sync /dev/sdb1


For sdb2, as it doesn't exists, the result is obvious:

Quote:
mdadm --examine /dev/sdb2
mdadm: No md superblock detected on /dev/sdb2.


Quote:
mdadm --examine /dev/sdb1
/dev/sdb1:
Magic : a92b4efc
Version : 00.90.00
UUID : bb7db4dd:fdee1f62:a266f1a9:a2250747
Creation Time : Fri Jun 8 03:23:38 2012
Raid Level : raid1
Used Dev Size : 20980800 (20.01 GiB 21.48 GB)
Array Size : 20980800 (20.01 GiB 21.48 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0

Update Time : Thu Jan 2 14:48:43 2014
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : 4bae581f - correct
Events : 5909075


Number Major Minor RaidDevice State
this 1 8 17 1 active sync /dev/sdb1

0 0 8 1 0 active sync /dev/sda1
1 1 8 17 1 active sync /dev/sdb1

Everything looks to be ok, isn't it?

Why should it be a sdb2 device?


Top
 Profile  
 
PostPosted: Thu Jan 02, 2014 8:24 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6075
eyp wrote:
Everything looks to be ok, isn't it?
No. Your NAS contains two raid arrays, a 'small' one, 20 GB, containing firmware stuff, and a big one, 2TB, containing userdata. Both should be assembled from 2 partitions, so 4 partitions in total.
The small array has sda1 and sdb1 (the first partition of both harddisks)
The big array should have sda2 and sdb2 (the 2nd partition of both harddisks).

But somehow sdb2 lost it's raid header
Quote:
mdadm --examine /dev/sdb2
mdadm: No md superblock detected on /dev/sdb2.
This result should have been almost a duplicate of /dev/sda2. You have a degraded array, using only one disk.

The question is, what happened? The raid header is at the end of the partition, which in this case means the end of the disk. Somehow it got damaged. The disk itself is still working, as the small array still uses a partition from it.

You can try to resync the array:
Code:
mdadm /dev/md1 --add /dev/sdb2
The box should immediately start rebuilding. That will take a day, or something like that. If it fails rebuilding, than the 2nd disk has hardware problems. Bad sectors or something like that.


Top
 Profile  
 
PostPosted: Thu Jan 02, 2014 10:01 pm 
Offline

Joined: Thu Aug 09, 2012 11:15 am
Posts: 44
Thanks a lot, I'll try it just now. I'm really a noob about RAID disks, it's absolutely new to me and related utilities are very confusing for now.

Well, there something wrong or I've missed something:

Quote:
mdadm /dev/md1 --add /dev/sdb2
mdadm: add new device failed for /dev/sdb2 as 2: Invalid argument


Top
 Profile  
 
PostPosted: Fri Jan 03, 2014 8:47 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6075
Sorry, my mistake. The command should be
Code:
mdadm --manage /dev/md1 --add /dev/sdb2
After having executed this command, you can see the rebuild process in
Code:
cat /proc/mdstat


Top
 Profile  
 
PostPosted: Fri Jan 03, 2014 4:08 pm 
Offline

Joined: Thu Aug 09, 2012 11:15 am
Posts: 44
You don't need to apologize.

The command wasn't wrong, I've been reading a little bit about RAID management and both syntax are valid and it's a shame that with the same result:

Quote:
mdadm --manage /dev/md1 --add /dev/sdb2
mdadm: add new device failed for /dev/sdb2 as 2: Invalid argument


:( It seems that /dev/sbd2 has been removed from the array (not by me) before tagging it as a fault drive, so now it can't be added again. I don't know what to do, I don't now if the array can be created again (--create) without deleting the data. Any ideas?


Top
 Profile  
 
PostPosted: Fri Jan 03, 2014 6:30 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6075
I wonder if the partition is somehow too small. Can you post the output of
Code:
cat /proc/partitions
?


Top
 Profile  
 
PostPosted: Fri Jan 03, 2014 6:36 pm 
Offline

Joined: Thu Aug 09, 2012 11:15 am
Posts: 44
Well, the disks were working well a week ago, also the space used is not much, only 600GB. I've never modified the default partitions:

Quote:
cat /proc/partitions
major minor #blocks name

7 0 604505 loop0
7 1 8192 loop1
7 2 204 loop2
8 0 1953514584 sda
8 1 20980888 sda1
8 2 1932533625 sda2
8 16 1953514584 sdb
8 17 20980888 sdb1
8 18 1932533625 sdb2
31 0 768 mtdblock0
31 1 16 mtdblock1
31 2 3072 mtdblock2
31 3 3072 mtdblock3
31 4 32768 mtdblock4
9 0 20980800 md0
253 0 4194304 dm-0
253 1 16785408 dm-1
9 1 1932533488 md1
253 2 1932529664 dm-2


Besides that, I'm trying to stop the array but I can't, it always says the device is busy. I'm trying to stop it because I want to try to reassemble it:

Quote:
mdadm --stop /dev/md1
mdadm: fail to stop array /dev/md1: Device or resource busy


Top
 Profile  
 
PostPosted: Fri Jan 03, 2014 6:58 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6075
sdb2 is exact the same size as sda2. So that is not the problem. I wonder if it could be a bad sector on the place where the header should be. Can you post the output of
Code:
dmesg -c >/dev/null
mdadm --manage /dev/md1 --add /dev/sdb2
dmesg
?

You can't stop the array because there is an active Logical Volume on it.


Top
 Profile  
 
PostPosted: Fri Jan 03, 2014 7:07 pm 
Offline

Joined: Thu Aug 09, 2012 11:15 am
Posts: 44
Quote:
(ERROR) Status : 0041
Core Driver (ERROR) 0 1: handlePortError: Finished All erring ports
sd 1:0:0:0: [sdb] Unhandled sense code
sd 1:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08
sd 1:0:0:0: [sdb] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
72 03 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
e8 e0 88 62
sd 1:0:0:0: [sdb] ASC=0x0 ASCQ=0x0
end_request: I/O error, dev sdb, sector 3907029090
Buffer I/O error on device sdb2, logical block 3865067234
Buffer I/O error on device sdb2, logical block 3865067235
Buffer I/O error on device sdb2, logical block 3865067236
Buffer I/O error on device sdb2, logical block 3865067237
Core Driver (ERROR) 0 1: Edma Error Reg 0x2000004
Core Driver (ERROR) 0 1: EDMA device error in NCQ mode
Core Driver (ERROR) 0 1: First error
Core Driver (ERROR) 0 1: updatePortsWithErrors: old val 0x0000, new 0x0001
Core Driver (ERROR) 0 1: command (host tag 0x02)(device tag 0x02) not expected, port 0x00.
Core Driver (ERROR) 0 1: isGoodCompletionsExpected: No commands expected to be completed. PortrNumDevError 0x0001
Core Driver (ERROR) 0 1: enterRequestSenseState: PortsWithErrors 0x0001
Core Driver (ERROR) 0 1: handlePortError: Device Error found on Port 0x00
Core Driver (ERROR) 0 1: insertReadLogExtCmnd: Port 0x00
Linux IAL (ERROR) [0 1] device error occured
Core Driver (ERROR) 0 1: ReadLogExtCompletionCB: Normal completion. Port 0x00
Core Driver (ERROR) ReadLogExt: 0x02 0x00 0x41 0x40 0x62 0x88
Core Driver (ERROR) ReadLogExt: 0xe0 0x00 0xe8 0x00 0x00 0x00
Core Driver (ERROR) ReadLogExt: 0x08 0x00 0x00 0x00 0x00 0x00
Core Driver (ERROR) 0 1 0: _getHostTagByDeviceTag, command entry found, host tag = 0x02, deviceTag(0x02)
Core Driver (ERROR) 0 1: parseReadLogExtOutPut: command tag (0x02)
Core Driver (ERROR) ATA Drive Registers:
Core Driver (ERROR) Error : 0040
Core Driver (ERROR) SectorCount : 0008
Core Driver (ERROR) LBA Low : e862
Core Driver (ERROR) LBA Mid : 0088
Core Driver (ERROR) LBA High : 00e0
Core Driver (ERROR) Device : 0000
Core Driver (ERROR) Status : 0041
SAL (ERROR) COMPLETION ERROR , adapter =0, channel=1, flags=4
SAL (ERROR) Failed command Cdb: 28 00 e8 e0 88 60 00 00 08 00
SAL (ERROR) UDMA READ command failed
SAL (ERROR) DMA Read failed on UNC at sector 00 00 e8 e0 88 62
SAL (ERROR) 0 1 0 :Scsi command completed. pScb c27da240, ScsiStatus 2 completionStatus MV_SCSI_COMPLETION_ATA_FAILED
SAL (ERROR) CDB:28 0 e8 e0 88 60 0 0 8 0
SAL (ERROR) Sense Data:72 3 0 0 0 0 0 c 0 a 80 0 0 0 0 0 e8 e0 88 62
SAL (ERROR) ATA Drive Registers:
SAL (ERROR) Error : 0040
SAL (ERROR) SectorCount : 0008
SAL (ERROR) LBA Low : e862
SAL (ERROR) LBA Mid : 0088
SAL (ERROR) LBA High : 00e0
SAL (ERROR) Device : 0000
SAL (ERROR) Status : 0041
Core Driver (ERROR) 0 1: handlePortError: Finished All erring ports
Linux IAL (ERROR) : retry command host=1, bus=1 SCpnt = c44d83a0
Core Driver (ERROR) 0 1: Edma Error Reg 0x4
Core Driver (ERROR) 0 1: EDMA device error in NCQ mode
Core Driver (ERROR) 0 1: First error
Core Driver (ERROR) 0 1: updatePortsWithErrors: old val 0x0000, new 0x0001
Core Driver (ERROR) 0 1: command (host tag 0x02)(device tag 0x02) not expected, port 0x00.
Core Driver (ERROR) 0 1: isGoodCompletionsExpected: No commands expected to be completed. PortrNumDevError 0x0001
Core Driver (ERROR) 0 1: enterRequestSenseState: PortsWithErrors 0x0001
Core Driver (ERROR) 0 1: handlePortError: Device Error found on Port 0x00
Core Driver (ERROR) 0 1: insertReadLogExtCmnd: Port 0x00
Linux IAL (ERROR) [0 1] device error occured
Core Driver (ERROR) 0 1: ReadLogExtCompletionCB: Normal completion. Port 0x00
Core Driver (ERROR) ReadLogExt: 0x02 0x00 0x41 0x40 0x62 0x88
Core Driver (ERROR) ReadLogExt: 0xe0 0x00 0xe8 0x00 0x00 0x00
Core Driver (ERROR) ReadLogExt: 0x08 0x00 0x00 0x00 0x00 0x00
Core Driver (ERROR) 0 1 0: _getHostTagByDeviceTag, command entry found, host tag = 0x02, deviceTag(0x02)
Core Driver (ERROR) 0 1: parseReadLogExtOutPut: command tag (0x02)
Core Driver (ERROR) ATA Drive Registers:
Core Driver (ERROR) Error : 0040
Core Driver (ERROR) SectorCount : 0008
Core Driver (ERROR) LBA Low : e862
Core Driver (ERROR) LBA Mid : 0088
Core Driver (ERROR) LBA High : 00e0
Core Driver (ERROR) Device : 0000
Core Driver (ERROR) Status : 0041
SAL (ERROR) COMPLETION ERROR , adapter =0, channel=1, flags=4
SAL (ERROR) Failed command Cdb: 28 00 e8 e0 88 60 00 00 08 00
SAL (ERROR) UDMA READ command failed
SAL (ERROR) DMA Read failed on UNC at sector 00 00 e8 e0 88 62
SAL (ERROR) 0 1 0 :Scsi command completed. pScb c27da240, ScsiStatus 2 completionStatus MV_SCSI_COMPLETION_ATA_FAILED
SAL (ERROR) CDB:28 0 e8 e0 88 60 0 0 8 0
SAL (ERROR) Sense Data:72 3 0 0 0 0 0 c 0 a 80 0 0 0 0 0 e8 e0 88 62
SAL (ERROR) ATA Drive Registers:
SAL (ERROR) Error : 0040
SAL (ERROR) SectorCount : 0008
SAL (ERROR) LBA Low : e862
SAL (ERROR) LBA Mid : 0088
SAL (ERROR) LBA High : 00e0
SAL (ERROR) Device : 0000
SAL (ERROR) Status : 0041
Core Driver (ERROR) 0 1: handlePortError: Finished All erring ports
Linux IAL (ERROR) : retry command host=1, bus=1 SCpnt = c44d83a0
Core Driver (ERROR) 0 1: Edma Error Reg 0x4
Core Driver (ERROR) 0 1: EDMA device error in NCQ mode
Core Driver (ERROR) 0 1: First error
Core Driver (ERROR) 0 1: updatePortsWithErrors: old val 0x0000, new 0x0001
Core Driver (ERROR) 0 1: command (host tag 0x02)(device tag 0x02) not expected, port 0x00.
Core Driver (ERROR) 0 1: isGoodCompletionsExpected: No commands expected to be completed. PortrNumDevError 0x0001
Core Driver (ERROR) 0 1: enterRequestSenseState: PortsWithErrors 0x0001
Core Driver (ERROR) 0 1: handlePortError: Device Error found on Port 0x00
Core Driver (ERROR) 0 1: insertReadLogExtCmnd: Port 0x00
Linux IAL (ERROR) [0 1] device error occured
Core Driver (ERROR) 0 1: ReadLogExtCompletionCB: Normal completion. Port 0x00
Core Driver (ERROR) ReadLogExt: 0x02 0x00 0x41 0x40 0x62 0x88
Core Driver (ERROR) ReadLogExt: 0xe0 0x00 0xe8 0x00 0x00 0x00
Core Driver (ERROR) ReadLogExt: 0x08 0x00 0x00 0x00 0x00 0x00
Core Driver (ERROR) 0 1 0: _getHostTagByDeviceTag, command entry found, host tag = 0x02, deviceTag(0x02)
Core Driver (ERROR) 0 1: parseReadLogExtOutPut: command tag (0x02)
Core Driver (ERROR) ATA Drive Registers:
Core Driver (ERROR) Error : 0040
Core Driver (ERROR) SectorCount : 0008
Core Driver (ERROR) LBA Low : e862
Core Driver (ERROR) LBA Mid : 0088
Core Driver (ERROR) LBA High : 00e0
Core Driver (ERROR) Device : 0000
Core Driver (ERROR) Status : 0041
SAL (ERROR) COMPLETION ERROR , adapter =0, channel=1, flags=4
SAL (ERROR) Failed command Cdb: 28 00 e8 e0 88 60 00 00 08 00
SAL (ERROR) UDMA READ command failed
SAL (ERROR) DMA Read failed on UNC at sector 00 00 e8 e0 88 62
SAL (ERROR) 0 1 0 :Scsi command completed. pScb c27da240, ScsiStatus 2 completionStatus MV_SCSI_COMPLETION_ATA_FAILED
SAL (ERROR) CDB:28 0 e8 e0 88 60 0 0 8 0
SAL (ERROR) Sense Data:72 3 0 0 0 0 0 c 0 a 80 0 0 0 0 0 e8 e0 88 62
SAL (ERROR) ATA Drive Registers:
SAL (ERROR) Error : 0040
SAL (ERROR) SectorCount : 0008
SAL (ERROR) LBA Low : e862
SAL (ERROR) LBA Mid : 0088
SAL (ERROR) LBA High : 00e0
SAL (ERROR) Device : 0000
SAL (ERROR) Status : 0041
Core Driver (ERROR) 0 1: handlePortError: Finished All erring ports
Linux IAL (ERROR) : retry command host=1, bus=1 SCpnt = c44d83a0
Core Driver (ERROR) 0 1: Edma Error Reg 0x4
Core Driver (ERROR) 0 1: EDMA device error in NCQ mode
Core Driver (ERROR) 0 1: First error
Core Driver (ERROR) 0 1: updatePortsWithErrors: old val 0x0000, new 0x0001
Core Driver (ERROR) 0 1: command (host tag 0x02)(device tag 0x02) not expected, port 0x00.
Core Driver (ERROR) 0 1: isGoodCompletionsExpected: No commands expected to be completed. PortrNumDevError 0x0001
Core Driver (ERROR) 0 1: enterRequestSenseState: PortsWithErrors 0x0001
Core Driver (ERROR) 0 1: handlePortError: Device Error found on Port 0x00
Core Driver (ERROR) 0 1: insertReadLogExtCmnd: Port 0x00
Linux IAL (ERROR) [0 1] device error occured
Core Driver (ERROR) 0 1: ReadLogExtCompletionCB: Normal completion. Port 0x00
Core Driver (ERROR) ReadLogExt: 0x02 0x00 0x41 0x40 0x62 0x88
Core Driver (ERROR) ReadLogExt: 0xe0 0x00 0xe8 0x00 0x00 0x00
Core Driver (ERROR) ReadLogExt: 0x08 0x00 0x00 0x00 0x00 0x00
Core Driver (ERROR) 0 1 0: _getHostTagByDeviceTag, command entry found, host tag = 0x02, deviceTag(0x02)
Core Driver (ERROR) 0 1: parseReadLogExtOutPut: command tag (0x02)
Core Driver (ERROR) ATA Drive Registers:
Core Driver (ERROR) Error : 0040
Core Driver (ERROR) SectorCount : 0008
Core Driver (ERROR) LBA Low : e862
Core Driver (ERROR) LBA Mid : 0088
Core Driver (ERROR) LBA High : 00e0
Core Driver (ERROR) Device : 0000
Core Driver (ERROR) Status : 0041
SAL (ERROR) COMPLETION ERROR , adapter =0, channel=1, flags=4
SAL (ERROR) Failed command Cdb: 28 00 e8 e0 88 60 00 00 08 00
SAL (ERROR) UDMA READ command failed
SAL (ERROR) DMA Read failed on UNC at sector 00 00 e8 e0 88 62
SAL (ERROR) 0 1 0 :Scsi command completed. pScb c27da240, ScsiStatus 2 completionStatus MV_SCSI_COMPLETION_ATA_FAILED
SAL (ERROR) CDB:28 0 e8 e0 88 60 0 0 8 0
SAL (ERROR) Sense Data:72 3 0 0 0 0 0 c 0 a 80 0 0 0 0 0 e8 e0 88 62
SAL (ERROR) ATA Drive Registers:
SAL (ERROR) Error : 0040
SAL (ERROR) SectorCount : 0008
SAL (ERROR) LBA Low : e862
SAL (ERROR) LBA Mid : 0088
SAL (ERROR) LBA High : 00e0
SAL (ERROR) Device : 0000
SAL (ERROR) Status : 0041
Core Driver (ERROR) 0 1: handlePortError: Finished All erring ports
Linux IAL (ERROR) : retry command host=1, bus=1 SCpnt = c44d83a0
Core Driver (ERROR) 0 1: Edma Error Reg 0x4
Core Driver (ERROR) 0 1: EDMA device error in NCQ mode
Core Driver (ERROR) 0 1: First error
Core Driver (ERROR) 0 1: updatePortsWithErrors: old val 0x0000, new 0x0001
Core Driver (ERROR) 0 1: command (host tag 0x02)(device tag 0x02) not expected, port 0x00.
Core Driver (ERROR) 0 1: isGoodCompletionsExpected: No commands expected to be completed. PortrNumDevError 0x0001
Core Driver (ERROR) 0 1: enterRequestSenseState: PortsWithErrors 0x0001
Core Driver (ERROR) 0 1: handlePortError: Device Error found on Port 0x00
Core Driver (ERROR) 0 1: insertReadLogExtCmnd: Port 0x00
Linux IAL (ERROR) [0 1] device error occured
Core Driver (ERROR) 0 1: ReadLogExtCompletionCB: Normal completion. Port 0x00
Core Driver (ERROR) ReadLogExt: 0x02 0x00 0x41 0x40 0x62 0x88
Core Driver (ERROR) ReadLogExt: 0xe0 0x00 0xe8 0x00 0x00 0x00
Core Driver (ERROR) ReadLogExt: 0x08 0x00 0x00 0x00 0x00 0x00
Core Driver (ERROR) 0 1 0: _getHostTagByDeviceTag, command entry found, host tag = 0x02, deviceTag(0x02)
Core Driver (ERROR) 0 1: parseReadLogExtOutPut: command tag (0x02)
Core Driver (ERROR) ATA Drive Registers:
Core Driver (ERROR) Error : 0040
Core Driver (ERROR) SectorCount : 0008
Core Driver (ERROR) LBA Low : e862
Core Driver (ERROR) LBA Mid : 0088
Core Driver (ERROR) LBA High : 00e0
Core Driver (ERROR) Device : 0000
Core Driver (ERROR) Status : 0041
SAL (ERROR) COMPLETION ERROR , adapter =0, channel=1, flags=4
SAL (ERROR) Failed command Cdb: 28 00 e8 e0 88 60 00 00 08 00
SAL (ERROR) UDMA READ command failed
SAL (ERROR) DMA Read failed on UNC at sector 00 00 e8 e0 88 62
SAL (ERROR) 0 1 0 :Scsi command completed. pScb c27da240, ScsiStatus 2 completionStatus MV_SCSI_COMPLETION_ATA_FAILED
SAL (ERROR) CDB:28 0 e8 e0 88 60 0 0 8 0
SAL (ERROR) Sense Data:72 3 0 0 0 0 0 c 0 a 80 0 0 0 0 0 e8 e0 88 62
SAL (ERROR) ATA Drive Registers:
SAL (ERROR) Error : 0040
SAL (ERROR) SectorCount : 0008
SAL (ERROR) LBA Low : e862
SAL (ERROR) LBA Mid : 0088
SAL (ERROR) LBA High : 00e0
SAL (ERROR) Device : 0000
SAL (ERROR) Status : 0041
Core Driver (ERROR) 0 1: handlePortError: Finished All erring ports
Linux IAL (ERROR) : retry command host=1, bus=1 SCpnt = c44d83a0
Core Driver (ERROR) 0 1: Edma Error Reg 0x4
Core Driver (ERROR) 0 1: EDMA device error in NCQ mode
Core Driver (ERROR) 0 1: First error
Core Driver (ERROR) 0 1: updatePortsWithErrors: old val 0x0000, new 0x0001
Core Driver (ERROR) 0 1: command (host tag 0x02)(device tag 0x02) not expected, port 0x00.
Core Driver (ERROR) 0 1: isGoodCompletionsExpected: No commands expected to be completed. PortrNumDevError 0x0001
Core Driver (ERROR) 0 1: enterRequestSenseState: PortsWithErrors 0x0001
Core Driver (ERROR) 0 1: handlePortError: Device Error found on Port 0x00
Core Driver (ERROR) 0 1: insertReadLogExtCmnd: Port 0x00
Linux IAL (ERROR) [0 1] device error occured
Core Driver (ERROR) 0 1: ReadLogExtCompletionCB: Normal completion. Port 0x00
Core Driver (ERROR) ReadLogExt: 0x02 0x00 0x41 0x40 0x62 0x88
Core Driver (ERROR) ReadLogExt: 0xe0 0x00 0xe8 0x00 0x00 0x00
Core Driver (ERROR) ReadLogExt: 0x08 0x00 0x00 0x00 0x00 0x00
Core Driver (ERROR) 0 1 0: _getHostTagByDeviceTag, command entry found, host tag = 0x02, deviceTag(0x02)
Core Driver (ERROR) 0 1: parseReadLogExtOutPut: command tag (0x02)
Core Driver (ERROR) ATA Drive Registers:
Core Driver (ERROR) Error : 0040
Core Driver (ERROR) SectorCount : 0008
Core Driver (ERROR) LBA Low : e862
Core Driver (ERROR) LBA Mid : 0088
Core Driver (ERROR) LBA High : 00e0
Core Driver (ERROR) Device : 0000
Core Driver (ERROR) Status : 0041
SAL (ERROR) COMPLETION ERROR , adapter =0, channel=1, flags=4
SAL (ERROR) Failed command Cdb: 28 00 e8 e0 88 60 00 00 08 00
SAL (ERROR) UDMA READ command failed
SAL (ERROR) DMA Read failed on UNC at sector 00 00 e8 e0 88 62
SAL (ERROR) 0 1 0 :Scsi command completed. pScb c27da240, ScsiStatus 2 completionStatus MV_SCSI_COMPLETION_ATA_FAILED
SAL (ERROR) CDB:28 0 e8 e0 88 60 0 0 8 0
SAL (ERROR) Sense Data:72 3 0 0 0 0 0 c 0 a 80 0 0 0 0 0 e8 e0 88 62
SAL (ERROR) ATA Drive Registers:
SAL (ERROR) Error : 0040
SAL (ERROR) SectorCount : 0008
SAL (ERROR) LBA Low : e862
SAL (ERROR) LBA Mid : 0088
SAL (ERROR) LBA High : 00e0
SAL (ERROR) Device : 0000
SAL (ERROR) Status : 0041
Core Driver (ERROR) 0 1: handlePortError: Finished All erring ports
sd 1:0:0:0: [sdb] Unhandled sense code
sd 1:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08
sd 1:0:0:0: [sdb] Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
72 03 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
e8 e0 88 62
sd 1:0:0:0: [sdb] ASC=0x0 ASCQ=0x0
end_request: I/O error, dev sdb, sector 3907029090
md: disabled device sdb2, could not read superblock.
md: sdb2 does not have a valid v1.0 superblock, not importing!
md: md_import_device returned -22


Top
 Profile  
 
PostPosted: Fri Jan 03, 2014 7:14 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6075
And there it is:
Code:
Buffer I/O error on device sdb2, logical block 3865067234
Buffer I/O error on device sdb2, logical block 3865067235
Buffer I/O error on device sdb2, logical block 3865067236
Buffer I/O error on device sdb2, logical block 3865067237
The disk has I/O errors. It's basically dead.

Strange effect for a power failure. But maybe the disk was already dying, and was the boot after the power fail just the first time this sectors had to be read.


Top
 Profile  
 
PostPosted: Fri Jan 03, 2014 7:23 pm 
Offline

Joined: Thu Aug 09, 2012 11:15 am
Posts: 44
So there isn't any solution?, can't be formatted or something else?


Top
 Profile  
 
PostPosted: Sat Jan 04, 2014 8:47 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6075
Maybe. A modern harddisk has a bunch of spare sectors, which are used when a 'normal' sector gets unusable. This is completely transparant, you won't notice it. (Apart from difficult timing measurements. The spare sector is on a different place, so the head has to move to it, which takes (measurable) time).
But of course it can only do so if you write a bad sector. If you only read it, it doesn't know which data it should deliver. Although I wouldn't expect an I/O error in that case, but a checksum error. (Each sector has a checksum, so that the controller knows if the data is valid).

But *if* this are replaceable bad sectors, *and* the disk has still spares, yes, then you can write that sectors and 'repair' them that way.
According to your logs the sectors 3865067234-..37 of sdb2 are bad. Don't know if the first sector is 0 or 1, so lets just write zero's to 3865067200-..300.
Code:
dd if=/dev/zero of=/dev/sdb2 seek=3865067200 count=100

After that you can try to re-add the partition. If dmesg doesn't show any I/O errors in that range, the disk is 'repaired'.

Using smartctl you can read the SMART data of the disk. If also contains a counter of remaining spare sectors. Don't know if the box has that tool.


Top
 Profile  
 
PostPosted: Sat Jan 04, 2014 2:21 pm 
Offline

Joined: Thu Aug 09, 2012 11:15 am
Posts: 44
Hey!, It seems that has worked...

Quote:
d if=/dev/zero of=/dev/sdb2 seek=3865067200 count=100
dd: writing to `/dev/sdb2': No space left on device
52+0 records in
51+0 records out
26112 bytes (26 kB) copied, 0.265411 s, 98.4 kB/s
dmesg -c >/dev/null
mdadm --manage /dev/md1 --add /dev/sdb2
mdadm: added /dev/sdb2
dmesg
md: bind<sdb2>
RAID1 conf printout:
--- wd:1 rd:2
disk 0, wo:0, o:1, dev:sda2
disk 1, wo:1, o:1, dev:sdb2
md: recovery of RAID array md1
md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
md: using 128k window, over a total of 1932533488 blocks.


Quote:
cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid6] [raid5] [raid4]
md1 : active raid1 sdb2[2] sda2[0]
1932533488 blocks super 1.0 [2/1] [U_]
[>....................] recovery = 0.7% (13851840/1932533488) finish=199.3min speed=160429K/sec

md0 : active raid1 sda1[0] sdb1[1]
20980800 blocks [2/2] [UU]

unused devices: <none>


You saved me! :D


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 44 posts ]  Go to page 1, 2, 3  Next

All times are UTC


Who is online

Users browsing this forum: No registered users and 46 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group