Waster wrote: >I have a completely different setup, but the same problem. > >Resync gets to about 75% of 300Gb in RAID1 on two SATA disks. The crash brings >down the whole machine with no logging.
Waster wrote: >This is not good, as it now hangs the machine completely between 60% and 80% >resync. I'm now running a second resync using 'watch', so I'll see if it is at >exactly the same spot that it crashes. I'm having the same problem using Ubuntu 7.04 while rebuilding a 4-disk Raid 5 array. The array originally became out of sync after a system crash about two months ago (due to some previous bug that has since been fixed in Ubuntu), and I have not been able to rebuild the array since. I was able to start it in degraded mode with 3 drives, and backup my data (thankfully), but any attempts to resync leads to what you described above. I can leave the machine on with "watch" polling the output of "/proc/mdstat", and I noticed that it crashes in the 70% range. No logging is generated. After backing up my data, I decided to wipe the md superblocks from the drives and start fresh by creating a new raid 5 array. Unfortunately, I'm experiencing the same problem when constructing the array as it does the initial sync. I'm lead to believe this is a software problem, as tests from smartctl and Western Digital's own boot disk show no problems with the drives (250gb SATA's - WD2500KS-00MJB0). -- Boot hang, apparently blocking on SW RAID rebuild https://bugs.launchpad.net/bugs/22673 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
