Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
mdadm fails to add a spare to a raid1 array
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2  
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43383
Location: 56N 3W

PostPosted: Thu Jan 22, 2015 7:08 pm    Post subject: Reply with quote

sinanqapudan,

Is the pause repeatable or was the system doing something like a rootfsck?

What do you have in dmesg once it boots?
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
sinanqapudan
Apprentice
Apprentice


Joined: 26 Oct 2004
Posts: 208
Location: Milan

PostPosted: Thu Jan 22, 2015 7:48 pm    Post subject: Reply with quote

NeddySeagoon,

Quote:
Is the pause repeatable or was the system doing something like a rootfsck?


I'm not sure of what you mean. Could you please expand a bit on the matter?

Dmesg output is in my previous post.

Regards[/code]
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43383
Location: 56N 3W

PostPosted: Thu Jan 22, 2015 8:27 pm    Post subject: Reply with quote

sinanqapudan,

Does the pause happen every boot or was it just the first time, when some process lixe a fsck happened that does not happen every time?

If you have timestamps on dmesg, can you see what caused the delay?
If timestamps are off, read about printk.time= in /usr/src/linux/Documentation/kernel-parameters.txt
You can also set it on by rebuilding your kernel.

-- edit ---

I must be having a senior moment ...
Code:
[   19.477807] Sense Key : Medium Error [current] [descriptor]
[   19.477812] Descriptor sense data with sense descriptors (in hex):
[   19.477813]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[   19.477823]         13 15 70 25
[   19.477828] sd 4:0:0:0: [sdb]
[   19.477832] Add. Sense: Unrecovered read error - auto reallocate failed
[   19.477835] sd 4:0:0:0: [sdb] CDB:
[   19.477836] Read(10): 28 00 13 15 70 20 00 00 08 00
[   19.477845] end_request: I/O error, dev sdb, sector 320172069
[   19.477849] Buffer I/O error on device sdb, logical block 40021508
[   19.477867] ata5: EH complete
will be delaying things.
You still have the old raid connected. The controller still has several goes at reading the faulty sector on sdb, which is a bit odd as you should be boot and using root from the recovered degraded set.
Ahhh... but its a different block, its now sector 320172069
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
sinanqapudan
Apprentice
Apprentice


Joined: 26 Oct 2004
Posts: 208
Location: Milan

PostPosted: Thu Jan 22, 2015 8:44 pm    Post subject: Reply with quote

NeddySeagoon.

I booted two times and the pause happened both times. One thing worth noting is that i forgot to:

Code:
# mdadm --detail --scan >> /etc/mdadm.conf


in the /etc/mdadm.conf of the new array.

I have timestamps in dmesg but they do not represent correctly what I experienced, or at least what was the output visible on the screen.

The system (or rather the screen output) hung at:

Code:
[   11.408166] init-early.sh (901) used greatest stack depth: 6256 bytes left


what follows in dmesg is:

Code:
[   12.786777] systemd-udevd[1050]: starting version 208
[   13.130736] systemd-udevd[1069]: Error calling EVIOCSKEYCODE: Invalid argument
[   13.130749] systemd-udevd[1069]: Error calling EVIOCSKEYCODE: Invalid argument
[   13.130759] systemd-udevd[1069]: Error calling EVIOCSKEYCODE: Invalid argument
[   13.130768] systemd-udevd[1069]: Error calling EVIOCSKEYCODE: Invalid argument
[   13.130777] systemd-udevd[1069]: Error calling EVIOCSKEYCODE: Invalid argument
[   13.130786] systemd-udevd[1069]: Error calling EVIOCSKEYCODE: Invalid argument
[   13.130795] systemd-udevd[1069]: Error calling EVIOCSKEYCODE: Invalid argument
[   13.130804] systemd-udevd[1069]: Error calling EVIOCSKEYCODE: Invalid argument
[   13.130813] systemd-udevd[1069]: Error calling EVIOCSKEYCODE: Invalid argument
[   13.130822] systemd-udevd[1069]: Error calling EVIOCSKEYCODE: Invalid argument
[   13.130831] systemd-udevd[1069]: Error calling EVIOCSKEYCODE: Invalid argument
[   13.130839] systemd-udevd[1069]: Error calling EVIOCSKEYCODE: Invalid argument
[   13.130848] systemd-udevd[1069]: Error calling EVIOCSKEYCODE: Invalid argument
[   13.168332] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[   13.168913] r8169 0000:01:00.0 eth0: RTL8168d/8111d at 0xf807a000, 00:25:22:c2:a6:e4, XID 081000c0 IRQ 10
[   13.168916] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[   13.168932] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[   13.169136] ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 5


and so on.

Now the system **appears** to be working fine.

Regards
Back to top
View user's profile Send private message
sinanqapudan
Apprentice
Apprentice


Joined: 26 Oct 2004
Posts: 208
Location: Milan

PostPosted: Thu Feb 05, 2015 12:17 pm    Post subject: Reply with quote

Ok, I'm back from my holidays.

I changed my kernel .config to

Code:
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y


previously it was
Code:
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=n



and now the system boot using md0 as root in readonly mode.

I have to say that I'm a bit perplexed by this. Why on earth should the same system be able to boot readonly from one disk and require read&write from another it's a mistery to me. One could argue that the two sytems are not *exactly* the same, but I think that it is not to the point.

Anyway thanks a lot for your support, NeddySeagoon.
Back to top
View user's profile Send private message
sinanqapudan
Apprentice
Apprentice


Joined: 26 Oct 2004
Posts: 208
Location: Milan

PostPosted: Thu Feb 05, 2015 3:02 pm    Post subject: Reply with quote

Hi there,

I've added dev/sdb3 to the raid array and the syncing is now completed:

The output of

Code:
smartctl -s /dev/sdb3


is:

Code:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  3 Spin_Up_Time            0x0027   213   203   063    Pre-fail  Always       -       12041
  4 Start_Stop_Count        0x0032   253   253   000    Old_age   Always       -       1823
  5 Reallocated_Sector_Ct   0x0033   252   240   063    Pre-fail  Always       -       15
  6 Read_Channel_Margin     0x0001   253   253   100    Pre-fail  Offline      -       0
  7 Seek_Error_Rate         0x000a   253   252   000    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0027   239   226   187    Pre-fail  Always       -       53855
  9 Power_On_Minutes        0x0032   176   176   000    Old_age   Always       -       783h+10m
 10 Spin_Retry_Count        0x002b   253   252   157    Pre-fail  Always       -       0
 11 Calibration_Retry_Count 0x002b   253   252   223    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   247   247   000    Old_age   Always       -       2577
192 Power-Off_Retract_Count 0x0032   253   253   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   253   253   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0032   044   253   000    Old_age   Always       -       49
195 Hardware_ECC_Recovered  0x000a   253   252   000    Old_age   Always       -       13484
196 Reallocated_Event_Count 0x0008   124   124   000    Old_age   Offline      -       129
197 Current_Pending_Sector  0x0008   253   241   000    Old_age   Offline      -       0
198 Offline_Uncorrectable   0x0008   124   124   000    Old_age   Offline      -       129
199 UDMA_CRC_Error_Count    0x0008   199   199   000    Old_age   Offline      -       0
200 Multi_Zone_Error_Rate   0x000a   253   252   000    Old_age   Always       -       0
201 Soft_Read_Error_Rate    0x000a   253   252   000    Old_age   Always       -       0
202 Data_Address_Mark_Errs  0x000a   253   247   000    Old_age   Always       -       0
203 Run_Out_Cancel          0x000b   253   252   180    Pre-fail  Always       -       2
204 Soft_ECC_Correction     0x000a   253   252   000    Old_age   Always       -       0
205 Thermal_Asperity_Rate   0x000a   253   252   000    Old_age   Always       -       0
207 Spin_High_Current       0x002a   253   252   000    Old_age   Always       -       0
208 Spin_Buzz               0x002a   253   252   000    Old_age   Always       -       0
209 Offline_Seek_Performnce 0x0024   239   239   000    Old_age   Offline      -       168
210 Unknown_Attribute       0x0032   253   252   000    Old_age   Always       -       0
211 Unknown_Attribute       0x0032   253   252   000    Old_age   Always       -       0
212 Unknown_Attribute       0x0032   253   253   000    Old_age   Always       -       0


So everything appears to be fine, as Current_Pending_Sector is 0.

Regards
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Goto page Previous  1, 2
Page 2 of 2

 
Jump to:  
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 vote in polls in this forum