主机参考:VPS测评参考推荐/专注分享VPS服务器优惠信息!若您是商家可以在本站进行投稿,查看详情!此外我们还提供软文收录、PayPal代付、广告赞助等服务,查看详情! |
我们发布的部分优惠活动文章可能存在时效性,购买时建议在本站搜索商家名称可查看相关文章充分了解该商家!若非中文页面可使用Edge浏览器同步翻译!PayPal代付/收录合作 |
raid硬盘数据损坏或故障后,可能会导致某个盘的文件数据不能使用,通常我们都会请一些专业的人事回来检查一下,但有时候是可以自己主动修复的,下面我给你们讲一个案例,看看是否可以帮助到大家。
After the data of raid hard disk is damaged or malfunctioned, the file data of a certain disk may not be used. Generally, we will ask some professional personnel to check it, but sometimes we can repair it on our own initiative. Let me tell you a case to see if it can help you.
raid故障简介:HP DL380服务器三块300GSAS硬盘,磁盘故障导致整个RAID组瘫痪,其中一块硬盘状态灯为红色。数据库存储在D分区,备份存储在E分区。存储故障,造成D分区不可识别,E分区可识别,但是拷贝备份文件报错,并重启服务器,导致先离线的硬盘上线,并同步了一段时间,在没有同步完成就直接强制关机了,之后就没有在动过服务器。<br/gt;服务器数据恢复方法:1.为了确保现存磁盘中数据的安全,先对磁盘做只读镜像备份,三块硬盘可以正常读取,没有发现坏道,只读镜像备份日志。图一: <br/gt;2.对备份的镜像文件进行详细分析,重组raid结构,并进行异或校验,部分校验通过,离线硬盘上线之后进行同步操作,会损坏数据,部分通过就是表示数据有损坏,图二: <br/gt;3.RAID分析过程,尝试多种硬盘离线状态下提取数据,每块盘离线所提取的数据都是一样的,图三:图四:图五:图六:<br/gt;4.首先针对E分区中的dat文件进行分析修复。发现两个备份文件都有损坏,图七:<br/gt;5.分析聚合dat碎片,验证dat数据完整性,底层结构显示有损坏。图八:<br/gt;6.同时进行D分区的数据文件的分析扫描,由于存储同步,数据文件目录不可见。7.对D分区自由空间数据页扫描,并对文件碎片进行分析和聚合。8.验证数据文件碎片的完整性和有效性。9.提取备份文件中的数据记录到新建的数据库中。10.通过上层应用连接数据库,验证数据可用性,数据库文件可以正常加载,上层应用软件中用户账号正常,可以进行正常数据查询。<br/gt;数据恢复结论:在恢复过程中,在E盘发现2个SealLib数据库的备份文件。但是备份文件数据中页结构有小部分损坏, 在D分区扫描的结果中数据碎片发现较连续的数据片段,碎片可用。通过对D分区碎片和E分区备份文件进行整合拼接。最终修复解析出的数据可以支撑整个应用的正常使用,上层应用可以正常查询数据库内容,
Brief introduction to raid failure: HP DL380 server has three 300gsas hard disks. The disk failure causes the whole raid group to be paralyzed, and the status light of one of the hard disks is red. The database is stored in partition D, and the backup is stored in partition E. The storage failure causes the D partition to be unrecognized and the e partition to be unrecognized, but the copy backup file reports an error and restarts the server. As a result, the offline hard disk goes online first and synchronizes for a period of time. If the synchronization is not completed, it will be forced to shut down directly, and then the server will not be moved. Lt; br / gt; server data recovery methods: 1. In order to ensure the security of the data in the existing disk, first make a read-only image backup to the disk. The three hard disks can be read normally without any bad path. Read-only image backup logs. Figure 1: lt; br / gt; 2. Analyze the backup image file in detail, reorganize the raid structure, and perform XOR verification. If some of the verification passes, and synchronize the offline hard disk online, the data will be damaged. If some passes, the data will be damaged. Figure 2: lt; br / gt; 3.RAID analysis process, try to extract data from a variety of hard disks offline. The data extracted from each disk offline is the same. Figure three: figure four: figure five: figure six: < br/gt; 4. first, analyze and repair the dat file in the E partition. It is found that both backup files are damaged. Figure 7: lt; br / gt; 5. Analyze the aggregated dat fragments, verify the integrity of DAT data, and the underlying structure shows that there is damage. Figure 8: lt; br / gt; 6. Analyze and scan the data files in the D-partition at the same time. Because of the storage synchronization, the data file directory is not visible. 7. Scan the free space data page of D partition, analyze and aggregate the file fragments. 8. Verify the integrity and validity of data file fragments. 9. Extract the data in the backup file and record it in the new database. 10. Connect to the database through the upper application to verify the data availability. The database file can be loaded normally, and the user account in the upper application software is normal, and normal data query can be performed. Lt; br / gt; data recovery conclusion: during the recovery process, two backup files of seallib database are found on disk E. However, a small part of the page structure in the backup file data is damaged. In the results of the D-partition scanning, the data fragments are found to be more continuous, and the fragments are available. Through the integration and splicing of D-partition fragments and e-partition backup files. Finally, the recovered data can support the normal use of the whole application, and the upper application can query the database content normally,
raid硬盘故障数据恢复方法介绍就到这了,不知道能不能帮助到大家,如果还是没修复好,可能就真的要请专业人士检查一下了。
This is the end of the introduction to the recovery method of raid hard disk fault data. I don't know if it can help you. If it still hasn't been repaired, it may really need to be checked by professionals.
--------------------------------------------------------------
主机参考,收集国内外VPS,VPS测评,主机测评,云服务器,虚拟主机,独立服务器,国内外服务器,高性价比建站主机相关优惠信息@zhujicankao.com
详细介绍和测评国外VPS主机,云服务器,国外服务器,国外主机的相关优惠信息,商家背景,网络带宽等等,也是目前国内最好的主机云服务器VPS参考测评资讯优惠信息分享平台
这几篇文章你可能也喜欢:
- CloudCone,美国Win系统VPS云服务器少量补货,美国洛杉矶MC机房,KVM虚拟架构,3核4G内存1Gbps带宽,17.49美元/月
- LOCVPS,双12特惠,香港免备案VPS云服务器终身65折,香港葵湾机房,CN2+BGP/CN2网络,KVM虚拟架构,1核2G内存2Mbps带宽不限流量,29.25元/月
- Linux系统VPS云服务器网络速度性能测试一键脚本分享,附详细VPS主机云服务器一键测评脚本
- 萤光云,香港VPS云服务器测评报告,回国优化线路,香港VPS测评,萤光云VPS好不好?萤光云香港VPS云服务器值得购买吗?
- 热网互联Hotiis,年底特惠活动,海外高质量免备案VPS云服务器5折,中国香港/美国/日本机房,1核1G内存15Mbps带宽,低至20元/月,默认赠送5G DDOS防御
本文由主机参考刊发,转载请注明:raid硬盘故障数据恢复方法介绍 https://zhujicankao.com/14198.html
评论前必须登录!
注册