rune@runescomp:~/Desktop$ sudo dpkg -i mdadm_3.0.3-2_i386.deb
Selecting previously deselected package mdadm.
(Reading database ... 197151 files and directories currently installed.)
Unpacking mdadm (from mdadm_3.0.3-2_i386.deb) ...
Setting up mdadm (3.0.3-2) ...
Generating array device nodes... /var/lib/dpkg/info/mdadm.postinst: 158: /dev/MAKEDEV: not found
failed.
Generating mdadm.conf... done.
update-initramfs: deferring update (trigger activated)
* Starting MD monitoring service mdadm --monitor [ OK ]
* Assembling MD arrays... [ OK ]
Processing triggers for ureadahead ...
Processing triggers for man-db ...
Processing triggers for doc-base ...
Processing 6 added doc-base file(s)...
Registering documents with scrollkeeper...
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.32-22-generic
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
W: mdadm: no arrays defined in configuration file.
Is this insanely dangerous to do? Or just somewhat dangerous?
I haven't had time to test it yet, but I will when I finish copying some files over to my new HDD.
Would it be completely crazy to try to install mdadm 3.0.3-2 from Debian squeeze in Lucid?: packages. debian. org/squeeze/ mdadm
http://
Well I just tried it. It did spit out an error:
rune@ runescomp: ~/Desktop$ sudo dpkg -i mdadm_3. 0.3-2_i386. deb 0.3-2_i386. deb) ... dpkg/info/ mdadm.postinst: 158: /dev/MAKEDEV: not found initramfs: deferring update (trigger activated)
Selecting previously deselected package mdadm.
(Reading database ... 197151 files and directories currently installed.)
Unpacking mdadm (from mdadm_3.
Setting up mdadm (3.0.3-2) ...
Generating array device nodes... /var/lib/
failed.
Generating mdadm.conf... done.
update-
* Starting MD monitoring service mdadm --monitor [ OK ]
* Assembling MD arrays... [ OK ]
Processing triggers for ureadahead ... initramfs: Generating /boot/initrd. img-2.6. 32-22-generic mdadm.conf defines no arrays.
Processing triggers for man-db ...
Processing triggers for doc-base ...
Processing 6 added doc-base file(s)...
Registering documents with scrollkeeper...
Processing triggers for initramfs-tools ...
update-
W: mdadm: /etc/mdadm/
W: mdadm: no arrays defined in configuration file.
Is this insanely dangerous to do? Or just somewhat dangerous?
I haven't had time to test it yet, but I will when I finish copying some files over to my new HDD.