Neil Brown wrote:
On Wednesday April 19, [EMAIL PROTECTED] wrote:
I have a raid5 configuration with 4 disks, of which all were active. My
system froze due to a separate issue (firewire), so I had to power cycle.
In the past, I've always been able to recover with fsck on /dev/md0, however
mdadm -S /dev/md0
mdadm -A /dev/md0 --force /dev/sd[abd]
mdadm /dev/md0 --add /dev/sdc
All the command line tricks in the world will not change the fact that
his IEEE1394 drive subsystem is presenting one or more of his drives as
read only devices..
Well, the command line tricks
All the command line tricks in the world will not change the fact that
his IEEE1394 drive subsystem is presenting one or more of his drives as
read only devices..
Well, this turns out to have been true. The IEEE1394 package I installed
included an eth1394 kernel module, which seems to have
I have a raid5 configuration with 4 disks, of which all were active. My
system froze due to a separate issue (firewire), so I had to power cycle.
In the past, I've always been able to recover with fsck on /dev/md0, however
this time I was not, and I am unable to re-assemble the array now.
I'm
On Wednesday April 19, [EMAIL PROTECTED] wrote:
I have a raid5 configuration with 4 disks, of which all were active. My
system froze due to a separate issue (firewire), so I had to power cycle.
In the past, I've always been able to recover with fsck on /dev/md0, however
this time I was not,
