On 11/21/07, Andrea Righi <[EMAIL PROTECTED]> wrote:
> In some distro the mdadm.conf file is not needed at all. You could try to
> auto-generate it with "mdadm --detail --scan > /etc/mdadm/mdadm.conf". If this
> resolves you can add this command in a post-install script to create the
> configuratio
Tory M Blue wrote:
> If I umount /dev/md7 and stop the raid array, I can fsck both sda7 and
> sdb7 (tells me that one disk is in the raid array).. Also tryihg to
> use normal commads such as
> "/sbin/mdadm --assemble --verbose --run /dev/md7" fails with no config
> file found. I'm really wondering
Update:
Due to some typo's things were not working, now I can image just fine,
no issue on timing, however when the system first comes up it wants to
go into single user mode.
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda7
fsck.ext3: Device or resource busy while try
Tory M Blue wrote:
> On 11/9/07, Andrea Righi <[EMAIL PROTECTED]> wrote:
>> Tory M Blue wrote:
>>
>> Maybe you could try to set both speed_limit_max and speed_limit_min to 0, to
>> totally disable the disks synchronization. Theoretically in this case
>> md_do_sync() should simply sleep and quit.
>
On 11/9/07, Andrea Righi <[EMAIL PROTECTED]> wrote:
> Tory M Blue wrote:
>
> Maybe you could try to set both speed_limit_max and speed_limit_min to 0, to
> totally disable the disks synchronization. Theoretically in this case
> md_do_sync() should simply sleep and quit.
Tried and it's been running
Tory M Blue wrote:
> Imaging is still taking forever. the last couple of folks I've talked
> to said their images attempt to sync after the boot, not during the
> rsync (image creation process).
>
> I've modified the speed_limit files to have 1000 or so for min and max
> (took forever), I then cha
> what I'm waiting for now, it's laying down the image (rsync and I get
> these messages every X (once a md device finishes sync'n I guess)
> (note i have tried 1000/1000 on speed and it took the same amount of
> time as this appears to be taking).
>
> md: minimum _guaranteed_ reconstruction speed:
Imaging is still taking forever. the last couple of folks I've talked
to said their images attempt to sync after the boot, not during the
rsync (image creation process).
I've modified the speed_limit files to have 1000 or so for min and max
(took forever), I then changed it to 5000 and 10 and
Tory M Blue wrote:
> On 11/6/07, Tory M Blue <[EMAIL PROTECTED]> wrote:
>> Greetings,
>>
>> So I've created my own autoinstallscript.conf file and ran a
>> si_mkautoinstallscript against it and my image appears to create all
>> the various MD devices and syncs them up (this process takes about 3
>
On 11/6/07, Tory M Blue <[EMAIL PROTECTED]> wrote:
> Greetings,
>
> So I've created my own autoinstallscript.conf file and ran a
> si_mkautoinstallscript against it and my image appears to create all
> the various MD devices and syncs them up (this process takes about 3
> hours+ to lay down the im
Tory M Blue wrote:
> So I've created my own autoinstallscript.conf file and ran a
> si_mkautoinstallscript against it and my image appears to create all
> the various MD devices and syncs them up (this process takes about 3
> hours+ to lay down the image due to all the sync'n that's going on).
I
Greetings,
So I've created my own autoinstallscript.conf file and ran a
si_mkautoinstallscript against it and my image appears to create all
the various MD devices and syncs them up (this process takes about 3
hours+ to lay down the image due to all the sync'n that's going on).
But I'm running i
12 matches
Mail list logo
