Jump to content

raid 5 восстановление даных

cubespace
 Share

Recommended Posts

cubespace

cubespace

Posted
Posted

Здравствуйте !

 

У меня проблема большая! Не знаю как решить (

 

Есть Power Vault MD 3000 там настроен raid 5!

Был збой света, упсы держали сколько могли, но нехватило и накрылась файлова система (до збоя была NTFS) , там была база даных MSSQL, размер базы 10 гиг!

 

Систему настраивал не я, а разгребать нужно уже мне!

А свежих бекапов нет!

 

Система:

4 винта по 500 Гиг!

 

Можно ли нормально восстановить базу ? И как ?

agabekov

agabekov

Posted
Posted

RAID Reconstructor тут не поможет(да и не умеет он скорее всего с СХД работать), массив-то в принципе не развалился - просто туда записался мусор. По идее, должна помочь любая софтина, которая умеет восстанавливать данные с порченых томов NTFS(тот же GetDataBack for NTFS).

Giga-Byte

Giga-Byte

Posted
Posted

такс, Power Vault не покупаем :)

 

а вообще, рейды рейдами а бэкапы рулят!

 

Apr 19 03:18:02 dlodb logger: Делаю резервную копию базы данных barsdb...

Apr 19 03:19:36 dlodb logger: Успешно завершено

Apr 19 16:54:11 dlodb kernel: sd 0:0:4:0: SCSI error: return code = 0x08000002

Apr 19 16:54:11 dlodb kernel: sde: Current: sense key: Hardware Error

Apr 19 16:54:11 dlodb kernel: ASC=0x42 ASCQ=0x0

Apr 19 16:54:11 dlodb kernel:

Apr 19 16:54:11 dlodb kernel: end_request: I/O error, dev sde, sector 24410335

Apr 19 16:54:11 dlodb kernel: raid5: Disk failure on sde1, disabling device. Operation continuing on 3 devices

Apr 19 16:54:11 dlodb kernel: RAID5 conf printout:

Apr 19 16:54:11 dlodb kernel: --- rd:4 wd:3 fd:1

Apr 19 16:54:11 dlodb kernel: disk 0, o:1, dev:sdb1

Apr 19 16:54:11 dlodb kernel: disk 1, o:1, dev:sdc1

Apr 19 16:54:11 dlodb kernel: disk 2, o:1, dev:sdd1

Apr 19 16:54:11 dlodb kernel: disk 3, o:0, dev:sde1

Apr 19 16:54:14 dlodb kernel: RAID5 conf printout:

Apr 19 16:54:14 dlodb kernel: --- rd:4 wd:3 fd:1

Apr 19 16:54:14 dlodb kernel: disk 0, o:1, dev:sdb1

Apr 19 16:54:14 dlodb kernel: disk 1, o:1, dev:sdc1

Apr 19 16:54:14 dlodb kernel: disk 2, o:1, dev:sdd1

Apr 19 16:54:14 dlodb kernel: disk 3, o:0, dev:sde1

Apr 19 16:54:14 dlodb kernel: RAID5 conf printout:

Apr 19 16:54:14 dlodb kernel: --- rd:4 wd:3 fd:1

Apr 19 16:54:14 dlodb kernel: disk 0, o:1, dev:sdb1

Apr 19 16:54:14 dlodb kernel: disk 1, o:1, dev:sdc1

Apr 19 16:54:14 dlodb kernel: disk 2, o:1, dev:sdd1

Apr 19 16:54:14 dlodb kernel: RAID5 conf printout:

Apr 19 16:54:14 dlodb kernel: --- rd:4 wd:3 fd:1

Apr 19 16:54:14 dlodb kernel: disk 0, o:1, dev:sdb1

Apr 19 16:54:14 dlodb kernel: disk 1, o:1, dev:sdc1

Apr 19 16:54:14 dlodb kernel: disk 2, o:1, dev:sdd1

Apr 19 16:54:14 dlodb kernel: disk 3, o:1, dev:sdf1

Apr 19 16:54:14 dlodb kernel: md: syncing RAID array md0

Apr 19 16:54:14 dlodb kernel: md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc.

Apr 19 16:54:14 dlodb kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction.

Apr 19 16:54:14 dlodb kernel: md: using 128k window, over a total of 143371776 blocks.

Apr 19 17:23:38 dlodb kernel: sd 0:0:1:0: SCSI error: return code = 0x08000002

Apr 19 17:23:38 dlodb kernel: sdb: Current: sense key: Medium Error

Apr 19 17:23:38 dlodb kernel: Add. Sense: Unrecovered read error

Apr 19 17:23:38 dlodb kernel:

Apr 19 17:23:38 dlodb kernel: Info fld=0x620b710

Apr 19 17:23:38 dlodb kernel: end_request: I/O error, dev sdb, sector 102807312

Apr 19 17:23:38 dlodb kernel: raid5:md0: read error not correctable (sector 102807248 on sdb1).

Apr 19 17:23:38 dlodb kernel: raid5: Disk failure on sdb1, disabling device. Operation continuing on 2 devices

Apr 19 17:23:38 dlodb kernel: raid5:md0: read error not correctable (sector 102807256 on sdb1).

Apr 19 17:23:38 dlodb kernel: Buffer I/O error on device dm-1, logical block 39921586

Apr 19 17:23:38 dlodb kernel: lost page write due to I/O error on dm-1

Apr 19 17:23:38 dlodb kernel: Buffer I/O error on device dm-1, logical block 49884600

Apr 19 17:23:38 dlodb kernel: lost page write due to I/O error on dm-1

Apr 19 17:23:38 dlodb kernel: Buffer I/O error on device dm-1, logical block 4403076

Apr 19 17:23:38 dlodb kernel: lost page write due to I/O error on dm-1

Apr 19 17:23:38 dlodb kernel: Buffer I/O error on device dm-1, logical block 10324671

Apr 19 17:23:38 dlodb kernel: lost page write due to I/O error on dm-1

Apr 19 17:23:38 dlodb kernel: Buffer I/O error on device dm-1, logical block 39921587

Apr 19 17:23:38 dlodb kernel: lost page write due to I/O error on dm-1

Apr 19 17:23:38 dlodb kernel: Buffer I/O error on device dm-1, logical block 39921585

Apr 19 17:23:38 dlodb kernel: lost page write due to I/O error on dm-1

Apr 19 17:23:38 dlodb kernel: Buffer I/O error on device dm-1, logical block 4403077

Apr 19 17:23:38 dlodb kernel: lost page write due to I/O error on dm-1

Apr 19 17:23:38 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #50725150 offset 0

Apr 19 17:23:38 dlodb kernel: Aborting journal on device dm-1.

Apr 19 17:23:38 dlodb kernel: Buffer I/O error on device dm-1, logical block 39921588

Apr 19 17:23:38 dlodb kernel: lost page write due to I/O error on dm-1

Apr 19 17:23:38 dlodb kernel: EXT3-fs error (device dm-1) in ext3_ordered_writepage: IO failure

Apr 19 17:23:38 dlodb kernel: md: md0: sync done.

Apr 19 17:23:39 dlodb kernel: Buffer I/O error on device dm-1, logical block 4403078

Apr 19 17:23:39 dlodb kernel: Buffer I/O error on device dm-1, logical block 49884601

Apr 19 17:23:39 dlodb kernel: lost page write due to I/O error on dm-1

Apr 19 17:23:39 dlodb kernel: lost page write due to I/O error on dm-1

Apr 19 17:23:39 dlodb kernel: EXT3-fs error (device dm-1) in ext3_ordered_writepage: IO failure

Apr 19 17:23:39 dlodb kernel: EXT3-fs error (device dm-1) in ext3_ordered_writepage: IO failure

Apr 19 17:23:39 dlodb kernel: ext3_abort called.

Apr 19 17:23:39 dlodb kernel: EXT3-fs error (device dm-1): ext3_journal_start_sb: Detected aborted journal

Apr 19 17:23:39 dlodb kernel: Remounting filesystem read-only

Apr 19 17:23:39 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #49872897 offset 0

Apr 19 17:23:39 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #50987014 offset 0

Apr 19 17:23:40 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #50725151 offset 0

Apr 19 17:23:40 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #50725151 offset 0

Apr 19 17:23:40 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #50725150 offset 0

Apr 19 17:23:40 dlodb kernel: __journal_remove_journal_head: freeing b_committed_data

Apr 19 17:23:40 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #50725151 offset 0

Apr 19 17:23:41 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #50725150 offset 0

Apr 19 17:23:41 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #21758476 offset 0

Apr 19 17:23:41 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #21758471 offset 0

Apr 19 17:23:41 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #21758481 offset 0

Apr 19 17:23:41 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #21758481 offset 0

Apr 19 17:23:47 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #22251780 offset 0

Apr 19 17:23:47 dlodb last message repeated 4 times

Apr 19 17:23:47 dlodb kernel: EXT3-fs error (device dm-1): ext3_get_inode_loc: unable to read inode block - inode=21773995, block=21758455

Apr 19 17:23:47 dlodb kernel: EXT3-fs error (device dm-1): ext3_get_inode_loc: unable to read inode block - inode=21774231, block=21758462

Apr 19 17:23:47 dlodb kernel: EXT3-fs error (device dm-1): ext3_get_inode_loc: unable to read inode block - inode=21773995, block=21758455

Apr 19 17:23:47 dlodb kernel: EXT3-fs error (device dm-1): ext3_get_inode_loc: unable to read inode block - inode=21774231, block=21758462

Apr 19 17:23:47 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #22251780 offset 0

Apr 19 17:23:47 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #22251780 offset 0

Apr 19 17:23:49 dlodb kernel: sd 0:0:1:0: SCSI error: return code = 0x08000002

Apr 19 17:23:49 dlodb kernel: sdb: Current: sense key: Medium Error

Apr 19 17:23:49 dlodb kernel: Add. Sense: Unrecovered read error

Apr 19 17:23:49 dlodb kernel:

Apr 19 17:23:49 dlodb kernel: Info fld=0x620bf12

Apr 19 17:23:49 dlodb kernel: end_request: I/O error, dev sdb, sector 102809362

Apr 19 17:23:49 dlodb kernel: raid5:md0: read error not correctable (sector 102809296 on sdb1).

Apr 19 17:23:49 dlodb kernel: raid5:md0: read error not correctable (sector 102809304 on sdb1).

Apr 19 17:23:49 dlodb kernel: raid5:md0: read error not correctable (sector 102809312 on sdb1).

Apr 19 17:23:49 dlodb kernel: raid5:md0: read error not correctable (sector 102809320 on sdb1).

Apr 19 17:23:49 dlodb kernel: raid5:md0: read error not correctable (sector 102809328 on sdb1).

Apr 19 17:23:49 dlodb kernel: raid5:md0: read error not correctable (sector 102809336 on sdb1).

Apr 19 17:23:49 dlodb kernel: raid5:md0: read error not correctable (sector 102809344 on sdb1).

Apr 19 17:23:49 dlodb kernel: raid5:md0: read error not correctable (sector 102809352 on sdb1).

Apr 19 17:23:49 dlodb kernel: raid5:md0: read error not correctable (sector 102809360 on sdb1).

Apr 19 17:23:49 dlodb kernel: raid5:md0: read error not correctable (sector 102809368 on sdb1).

Apr 19 17:23:49 dlodb kernel: raid5:md0: read error not correctable (sector 102809376 on sdb1).

Apr 19 17:23:49 dlodb kernel: raid5:md0: read error not correctable (sector 102809384 on sdb1).

Apr 19 17:23:49 dlodb kernel: raid5:md0: read error not correctable (sector 102809392 on sdb1).

Apr 19 17:23:49 dlodb kernel: raid5:md0: read error not correctable (sector 102809400 on sdb1).

Apr 19 17:23:49 dlodb kernel: raid5:md0: read error not correctable (sector 102809408 on sdb1).

Apr 19 17:23:49 dlodb kernel: raid5:md0: read error not correctable (sector 102809416 on sdb1).

Apr 19 17:23:49 dlodb kernel: raid5:md0: read error not correctable (sector 102809424 on sdb1).

Apr 19 17:23:49 dlodb kernel: raid5:md0: read error not correctable (sector 102809432 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809440 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809448 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809456 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809464 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809472 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809480 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809488 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809496 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809504 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809512 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809520 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809528 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809536 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809544 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809552 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809560 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809568 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809576 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809584 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809592 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809600 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809608 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809616 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809624 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809632 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809640 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809648 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809656 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809664 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809672 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809680 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809688 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809696 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809704 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809712 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809720 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809728 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809736 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809744 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809752 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809760 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809768 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809776 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809784 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809792 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809800 on sdb1).

Apr 19 17:23:50 dlodb kernel: raid5:md0: read error not correctable (sector 102809808 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809816 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809824 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809832 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809840 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809848 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809856 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809864 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809872 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809880 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809888 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809896 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809904 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809912 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809920 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809928 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809936 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809944 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809952 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809960 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809968 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809976 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809984 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102809992 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102810000 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102810008 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102810016 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102810024 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102810032 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102810040 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102810048 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102810056 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102810064 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102810072 on sdb1).

Apr 19 17:23:51 dlodb kernel: raid5:md0: read error not correctable (sector 102810080 on sdb1).

Apr 19 17:23:51 dlodb kernel: printk: 25 messages suppressed.

Apr 19 17:23:51 dlodb kernel: Buffer I/O error on device dm-1, logical block 12845059

Apr 19 17:23:51 dlodb kernel: lost page write due to I/O error on dm-1

Apr 19 17:23:51 dlodb kernel: Buffer I/O error on device dm-1, logical block 21463052

Apr 19 17:23:51 dlodb kernel: lost page write due to I/O error on dm-1

Apr 19 17:23:55 dlodb kernel: sd 0:0:1:0: SCSI error: return code = 0x08000002

Apr 19 17:23:55 dlodb kernel: sdb: Current: sense key: Medium Error

Apr 19 17:23:55 dlodb kernel: Add. Sense: Unrecovered read error

Apr 19 17:23:55 dlodb kernel:

Apr 19 17:23:55 dlodb kernel: Info fld=0x620c6ac

Apr 19 17:23:55 dlodb kernel: end_request: I/O error, dev sdb, sector 102811308

Apr 19 17:23:55 dlodb kernel: raid5:md0: read error not correctable (sector 102811240 on sdb1).

Apr 19 17:23:55 dlodb kernel: raid5:md0: read error not correctable (sector 102811248 on sdb1).

Apr 19 17:23:55 dlodb kernel: raid5:md0: read error not correctable (sector 102811256 on sdb1).

Apr 19 17:23:55 dlodb kernel: raid5:md0: read error not correctable (sector 102811264 on sdb1).

Apr 19 17:23:55 dlodb kernel: raid5:md0: read error not correctable (sector 102811272 on sdb1).

Apr 19 17:23:55 dlodb kernel: raid5:md0: read error not correctable (sector 102811280 on sdb1).

Apr 19 17:23:55 dlodb kernel: raid5:md0: read error not correctable (sector 102811288 on sdb1).

Apr 19 17:23:55 dlodb kernel: raid5:md0: read error not correctable (sector 102811296 on sdb1).

Apr 19 17:23:55 dlodb kernel: RAID5 conf printout:

Apr 19 17:23:55 dlodb kernel: --- rd:4 wd:2 fd:2

Apr 19 17:23:55 dlodb kernel: disk 0, o:0, dev:sdb1

Apr 19 17:23:55 dlodb kernel: disk 1, o:1, dev:sdc1

Apr 19 17:23:55 dlodb kernel: disk 2, o:1, dev:sdd1

Apr 19 17:23:55 dlodb kernel: disk 3, o:1, dev:sdf1

Apr 19 17:23:55 dlodb kernel: RAID5 conf printout:

Apr 19 17:23:55 dlodb kernel: --- rd:4 wd:2 fd:2

Apr 19 17:23:55 dlodb kernel: disk 0, o:0, dev:sdb1

Apr 19 17:23:55 dlodb kernel: disk 1, o:1, dev:sdc1

Apr 19 17:23:55 dlodb kernel: disk 2, o:1, dev:sdd1

Apr 19 17:23:55 dlodb kernel: RAID5 conf printout:

Apr 19 17:23:55 dlodb kernel: --- rd:4 wd:2 fd:2

Apr 19 17:23:55 dlodb kernel: disk 0, o:0, dev:sdb1

Apr 19 17:23:55 dlodb kernel: disk 1, o:1, dev:sdc1

Apr 19 17:23:55 dlodb kernel: disk 2, o:1, dev:sdd1

Apr 19 17:23:55 dlodb kernel: RAID5 conf printout:

Apr 19 17:23:55 dlodb kernel: --- rd:4 wd:2 fd:2

Apr 19 17:23:55 dlodb kernel: disk 1, o:1, dev:sdc1

Apr 19 17:23:55 dlodb kernel: disk 2, o:1, dev:sdd1

Apr 19 17:24:02 dlodb kernel: EXT3-fs error (device dm-1): ext3_get_inode_loc: unable to read inode block - inode=21774494, block=21758470

Apr 19 17:24:02 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #22251795 offset 0

Apr 19 17:24:02 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #22251780 offset 0

Apr 19 17:24:04 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #39256176 offset 0

Apr 19 17:24:04 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #39256176 offset 0

Apr 19 17:25:32 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #22251780 offset 0

Apr 19 17:25:32 dlodb kernel: EXT3-fs error (device dm-1): ext3_get_inode_loc: unable to read inode block - inode=21773995, block=21758455

Apr 19 17:25:32 dlodb kernel: EXT3-fs error (device dm-1): ext3_get_inode_loc: unable to read inode block - inode=21774231, block=21758462

Apr 19 17:25:32 dlodb kernel: EXT3-fs error (device dm-1): ext3_get_inode_loc: unable to read inode block - inode=21773995, block=21758455

Apr 19 17:25:32 dlodb kernel: EXT3-fs error (device dm-1): ext3_get_inode_loc: unable to read inode block - inode=21774231, block=21758462

Apr 19 17:25:34 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #39256176 offset 0

Apr 19 17:25:34 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #39224338 offset 0

Apr 19 17:25:35 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #22251780 offset 0

Apr 19 17:27:05 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #22251780 offset 0

Apr 19 17:35:36 dlodb kernel: EXT3-fs error (device dm-1): ext3_find_entry: reading directory #2 offset 0

 

по русски - MD raid5+hotspare, отказывает диск, hotspare подключается и начинается ребилд. тут натыкается на bad-block и тупой md выводит диск из рейда (сцуко, второй уже!)

а потом материться, дык ёптыть, я работать не буду, у меня уже двух дисков нет :))))

 

это сбой по питанию на IBM x366 2005-го года выпуска, в 2010 году признали брак платы PCI-X, там регулятор напруги питания плат греется и отрубает всю плату

 

ночь *** и к утру все данные были восстановлены (с этих дисков), бэкапы 10 часовой давности, тобишь из бэкапов всё не поднять, это рабочий день типа в ауте.

vitalyb

vitalyb

Posted
Posted

Giga-Byte

в соседней ветке уже писал, напишу еще раз. Для всех рейдов с избыточностью необходимо делать периодическую проверку, чтобы минимизировать вероятность такого вот развития событий.

Для линуха так: echo check > /sys/block/${DEV}/md/sync_action, для нормальных контроллеров - см. инструкцию.

dignity

dignity

Posted
Posted

Есть мнение, что RAID5 - зло и нередко не отличается какой-либо надежностью. Предпочтительнее использовать RAID6, хотя я на практике юзаю только MIRROR, STRIP и их комбинации RAID1,0,10, во все остальное не верю, диски не такие уж дорогие по сравнению с последствиями сбоя...

Ivan_83

Ivan_83

Posted
Posted

У меня был опыт копания в NTFS: два диска 500гб объединил в терабайтник для увеличения ёмкости, потом оно развалилось по моей неосторожности.

 

Закончилось тем, что я руками восстановил служебные записи до состояния что файлы были видны но родной чекдиск всё убивал, но альтернативная софтина всё вытащила. Пару файлов только закоцались - уже от моих плясок с восстановлением.

 

Юзал NTFS explorer и ихную же восстанавливалка: http://www.runtime.org/

 

лучше ничего не нашёл.

 

 

 

 

В вашем случае есть шанс что софтина найдёт MFT, если предварительно вы чекдиском виндовым сильно всё не загробили.

 

Рекомендую сделать имэджи дисков и тренироваться на них.

 

 

  • 7 months later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing
×
×
  • Create New...
На сайте используются файлы cookie и сервисы аналитики для корректной работы форума и улучшения качества обслуживания. Продолжая использовать сайт, вы соглашаетесь с использованием файлов cookie и с Политикой конфиденциальности.