Help! im lost, finaly have found the new howto on ftp.fi.kernel.org after days
of dispair and old documentation... tried the new tools ... nada ... tried
kernel patches ... busted kernel 2.2.5 ...
My problem is this ... i created the /etc/raidtools (modified example raid1
raidtab) with 3 scsi dis
On Thu, 8 Apr 1999, Ricardo Kleemann wrote:
> Hi everyone,
>
> I created a raid-0 device as follows:
>
> 1. partitioned 4 disks
> 2. configured /etc/raidtab
> 3. ran mkraid /dev/md0 -> everything reported fine
> 4. ran mke2fs /dev/md0 -> everything went well
> 5. mounted /dev/md0 to verify thin
Hi everyone,
I created a raid-0 device as follows:
1. partitioned 4 disks
2. configured /etc/raidtab
3. ran mkraid /dev/md0 -> everything reported fine
4. ran mke2fs /dev/md0 -> everything went well
5. mounted /dev/md0 to verify things were ok - it mounted fine.
6. added /dev/md0 mountpoint to /
Hi Alex
I have tested with raidtools 0.90 also and had a similar problem. Also
there were a lot of similar questions on the list in the past.
Try to make a new ext2-fs on the disk (maybe on another system) and connect
it again; as far as I remember, the raidtools mark a bad disk and recognize
it
> Could the information be stuck in the master boot record?
Any LILO gurus out there who know about "spare" space in the MBR ??
> Anyhow, as far as I can see the real issue is how to replace a failed drive
> in the array..
No -- that's easy -- raidhotadd ...
> In a RAID setup, you'd like to be
Hello group,
I am trying to understand software RAID-1. In order to learn
a bit I am experimenting with Software RAID on a Linux box.
The hardware I use is a PII 300 MMX with 64 MB memory.
Two identical IDE Hard drives Fujitsu MPC3043AT 4.3 GB
The OS is RedHat5.2 And the kernel is 2.2.3 patched
Hi,
> The only place I would even imagine this would be possible would be in
> the mode pages, but my recollection of the SCSI standard says that all
> of these modes pages are read only. :(
IIRC there are some writable fields in some drives to allow you to set
caching/writeback behaviour, for e
