Koozali.org: home of the SME Server
Obsolete Releases => SME 7.x Contribs => Topic started by: mgb on December 11, 2012, 12:17:12 PM
-
Trying to run the Mirror
Not a week has advanced 2.6%
SME 7.6
Installing the Mirror of SME
Half a year ago was successfully added Mirror
It is used as a backup after the Mirror
Disconnect the old disk
/raid.JPG (ftp://mail.makif.omer.k12.il/raid.JPG)
-
mgb, if you are having problem updating your server, check:
http://forums.contribs.org/index.php/topic,49361.0.html
Hope it helps.
-
Trying to run the Mirror
Not a week has advanced 2.6%
SME 7.6
Installing the Mirror of SME
Half a year ago was successfully added Mirror
It is used as a backup after the Mirror
Disconnect the old disk
/raid.JPG (ftp://mail.makif.omer.k12.il/raid.JPG)
I "think" this about a failed raid that is not syncing.
Then again..
-
I "think" this about a failed raid that is not syncing.
Then again..
Trex, you are correct. My bad, need a strong coffee...
mgb, ignore my post.
-
Thank you
I installed yum update
Work waiting for the end of the Mirror
Created a new problem
After the signal-event post-upgrade; signal-event reboot
stop is active
i login the alt + f2
Running ini3
the init 7
is begin to work
In any event
Activated waiting for the end of the Mirror
-
After Update
Mirror stops and starts again Cannot finish Mirror
Thanks for any idea to the
Solution
-
After Update
Mirror stops and starts again Cannot finish Mirror
Thanks for any idea to the
Solution
Have to say that you need to find somone to post for you in english or use one of the non-english forums because I am not sure what you are asking.
I "think" it is about a non syncing Raid, and if that is what it is, you need to be very very sure about what is being said to do or NOT to do.
-
mgb
That screen image data looks like something is wrong.
One of your disks may be faulty.
I suggest you remove the new disk you added and try another.
Also run a test on both disks before proceeding any further.
Boot up to the sme install CD in Rescue mode and run smartctl, refer
http://wiki.contribs.org/Monitor_Disk_Health
or boot up to the UBCD (Ultimate Boot CD) & run a test on both drives using the appropriate manufacturers drive diagnostic utility.
Search Google for UBCD
-
I thank the answer
I turned
Here are the results log
smartctl version 5.33 [i686-redhat-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/ (http://smartmontools.sourceforge.net/)
=== START OF INFORMATION SECTION ===
Device Model: SAMSUNG HD103SJ
Serial Number: S246JDWSB67512
Firmware Version: 1AJ100E4
User Capacity: 1,000,204,886,016 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: Not recognized. Minor revision code: 0x28
Local Time is: Tue Dec 18 08:59:22 2012 IST
==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details.
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
Drive failure expected in less than 24 hours. SAVE ALL DATA.
See vendor-specific Attribute list for failed Attributes.
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 137) Reserved.
Total time to complete Offline
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 137) Reserved.
Total time to complete Offline
data collection: (9240) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off sup$
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 154) minutes.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN$
1 Raw_Read_Error_Rate 0x002f 001 001 051 Pre-fail Always FAIL$
2 Throughput_Performance 0x0026 252 252 000 Old_age Always $
3 Spin_Up_Time 0x0023 074 073 025 Pre-fail Always $
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always $
5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always $
7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always $
8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline $
9 Power_On_Hours 0x0032 100 100 000 Old_age Always $
10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always $
11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always $
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always $
191 G-Sense_Error_Rate 0x0022 252 252 000 Old_age Always $
192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always $
194 Temperature_Celsius 0x0002 059 054 000 Old_age Always $
195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always $
196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always $
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always $
198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline $
199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always $
200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always $
223 Load_Retry_Count 0x0032 252 252 000 Old_age Always $
225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always $
SMART Error Log Version: 1
ATA Error Count: 9716 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 9716 occurred at disk power-on lifetime: 23001 hours (958 days + 9 hours)
When the command that caused the error occurred, the device was active or idl$
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 b8 4a 9c 2c ee Error: UNC 184 sectors at LBA = 0x0e2c9c4a = 237804618
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 d8 2a 9c 2c ee 08 00:22:56.417 READ DMA
ec 03 46 00 00 00 a0 08 00:22:56.417 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 08 00:22:56.417 SET FEATURES [Set transfer mode]
ec 00 b8 4a 9c 2c a0 08 00:22:56.417 IDENTIFY DEVICE
c8 00 e0 22 9c 2c ee 08 00:22:56.416 READ DMA
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LB$
# 1 Extended offline Completed: handling damage?? 90% 23003 -
# 2 Short offline Completed: handling damage?? 90% 23003 -
# 3 Extended offline Completed: handling damage?? 90% 22983 -
# 4 Short offline Completed: handling damage?? 90% 22983 -
SMART Selective Self-Test Log Data Structure Revision Number (0) should be 1
SMART Selective self-test log data structure revision number 0
Warning: ATA Specification requires selective self-test log data structure revi$
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Completed_handling_damage?? [10% left] (0-65535)
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
-
mgb
Drive failure expected in less than 24 hours. SAVE ALL DATA.
Like I said, change the faulty drive