Obsolete Releases > SME Server 7.x
Is this are problem - doesn't contain a valid partition tab
beeboob:
pfloor Thats was are very god answer. Now i understand.
I try the
mdadm /dev/md1 -a /dev/hdc1
mdadm: hot added /dev/hdc1
And
mdadm /dev/md2 -a /dev/hdc2
mdadm: hot added /dev/hdc2
And the run
cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 hdc2[2] hda2[0]
159975168 blocks [2/1] [U_]
[>....................] recovery = 0.2% (471808/159975168) finish=208.4min speed=12751K/sec
md1 : active raid1 hdc1[1] hda1[0]
104320 blocks [2/2] [UU]
Is it not ok now?
TrevorB:
--- Quote from: "beeboob" ---cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 hdc2[2] hda2[0]
159975168 blocks [2/1] [U_]
[>....................] recovery = 0.2% (471808/159975168) finish=208.4min speed=12751K/sec
md1 : active raid1 hdc1[1] hda1[0]
104320 blocks [2/2] [UU]
Is it not ok now?
--- End quote ---
Yes, it is now rebuilding your array, and will take a little over 3hrs to do it (ie. it has to make them look the same). :-)
/dev/md1 has already synced.
Trevor B
beeboob:
My
cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 hda2[0]
159975168 blocks [2/1] [U_]
md1 : active raid1 hdc1[2](F) hda1[0]
104320 blocks [2/1] [U_]
But i get are admin mail whit:
A Fail event had been detected on md device /dev/md1.
So do i have to replace md1????
And i am very unsure on who to see what raid there is faling
Or can i ""just""
1-Replace the IDE cables with NEW GOOD FLAT 80 wire cables. Don't use the fancy ones with the wrapping around them.
2-Make sure you have a GOOD power supply, not a $20 one.
3-Don't use IBM Deskstar drives (or Hitachi for that matter), they won't stay in sync. This has happened to me several times.
4-Check your memory - Boot with the CD and type memtest <enter>. This test can take a LONG time but let it run completely through at least once. Bad memory can cause your drives to go out of sync.
5-If you are not using the CDROM, unplug it from the cable and the power supply.
TrevorB:
--- Quote from: "beeboob" ---My
cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 hda2[0]
159975168 blocks [2/1] [U_]
md1 : active raid1 hdc1[2](F) hda1[0]
104320 blocks [2/1] [U_]
--- End quote ---
Your last one showed that it was rebuilding, so it has obviously failed again.
--- Quote from: "beeboob" ---But i get are admin mail whit:
A Fail event had been detected on md device /dev/md1.
So do i have to replace md1????
And i am very unsure on who to see what raid there is faling
--- End quote ---
A good place to start is /var/log/messages
--- Quote from: "beeboob" ---Or can i ""just""
1-Replace the IDE cables with NEW GOOD FLAT 80 wire cables. Don't use the fancy ones with the wrapping around them.
2-Make sure you have a GOOD power supply, not a $20 one.
3-Don't use IBM Deskstar drives (or Hitachi for that matter), they won't stay in sync. This has happened to me several times.
4-Check your memory - Boot with the CD and type memtest <enter>. This test can take a LONG time but let it run completely through at least once. Bad memory can cause your drives to go out of sync.
5-If you are not using the CDROM, unplug it from the cable and the power supply.
--- End quote ---
You can certainly try, but if it continues, I'd get a new drive (or stick with only one and put in a good backup regime).
Trevor B
beeboob:
Many thanks...
I will get are new harddrive.
And find out off, whit off the 2 hdd i have to replace. Whit are new one... But is ther are tips to find out off whit disk i have to change. Something like,, Is it the first on the cable og the second
And also get are better backup regime. Something that are better then the manuel backup to desktop.
from my /var/log/messages
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 0
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 0
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 8
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 1
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 16
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 2
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 24
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 3
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 32
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 4
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 40
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 5
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 48
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 6
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 56
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 7
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 64
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 8
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 72
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 9
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 80
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 10
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 88
Aug 12 17:25:23 server1 kernel: Buffer I/O error on device hdc, logical block 11
Aug 12 17:25:23 server1 kernel: end_request: I/O error, dev hdc, sector 96
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version