Bad blocks in raid5 disk
On Thu, 23 Feb 2006 14:07:49 -0300, Ney AndrŽ de Mello Zunino staggered into the Black Sun and said: One of the filesystems inetc-fstab failed to mount at boot. The...
I have the following situation:
3 harddisks, 2 P-ATA, 1 SATA. All 160 GB disks, not relevant I think)dev-hda, dev-hdb,dev-sda
On each disk a 20GB parbreastion (type fd) that is used in a software raid5 arraydev-md0. (-dev-hda5,dev-hdb3,dev-sda2)
My is mounted on this raid volume.
Suddenly I got swamped in messages indicating disk problems ondev-sda2 (Driveseek, Read errors)
(Temporarily stopped mdmonitor and auditd, as my system became almost totally unresponsive, as each error produces another message.)
Failed thedev-sda2 device (mdadmdev-md0 --faildev-sda2 --remove dev-sda2)
Tried to fsck the parbreastion but can't. There seems to be no fstype suited for checking a 'raid auto' parbreastion.
Hi: I am trying to burn Verbatim Datalife 4x DVD+RW media using a Panasonic SW-9573 drive on Suse 9.1 Linux 2.6.5. Using dvd+rw-tools-5.17.4.8.6-17.5.5 and mkisofs-2.01a27-21. I created an...
Ran badblocks on the device and found bad blocks. I'll buy a new disk asap.
For the time being : (how) Can I use fsck on this fd- parbreastion to map out the bad sectors ? Since the SATA-device is treated 'as scsi', does the driver itself take care of the bad block relocation? How can I best proceed, given the fact the drive cannot be replaced until next week or so ? I found some wish-list for mdadm, so I buttume this driver isn't fully developed yet. I'd rather have tools to 'repair' the thing from within the raid array. Is that possible ??
Thanks Sh.
Linux groups from Newsgroups