#502: RAID array does not start -------------------------------+-------------------------------------------- Reporter: [email protected] | Owner: free Type: defect | Status: new Priority: normal | Milestone: Component: build | Version: Severity: normal | Keywords: -------------------------------+-------------------------------------------- I fixed my 32-bit install of 3.0 beta3 by replacing a defective installation DVD. Now all is fine except this one (and maybe something with the video card).
Shouldn't the kernel automatically create md* devices when it detects partitions which belong to a RAID? I keep data on a mirror of two IDE disks (which I connected after installation), and they are not detected. Moreover, when I issue "sudo dpkg-reconfigure mdadm" I get these errors (after the dialogs): Generating array device nodes... rm: cannot remove `md0-': Read-only file system mknod: `md0-': Read-only file system rm: cannot remove `md0-': Read-only file system rm: cannot remove `md1-': Read-only file system mknod: `md1-': Read-only file system rm: cannot remove `md1-': Read-only file system rm: cannot remove `md2-': Read-only file system mknod: `md2-': Read-only file system rm: cannot remove `md2-': Read-only file system [omissis...] rm: cannot remove `md31-': Read-only file system mknod: `md31-': Read-only file system rm: cannot remove `md31-': Read-only file system done. Removing any system startup links for /etc/init.d/mdadm-raid ... update-initramfs: Generating /boot/initrd.img-2.6.29-1-multimedia-686 Meanwhile, I created a file named /etc/init.d/startraid.sh and linked as /etc/rcS.d/S25startraid.sh: #!/bin/sh test -e /dev/md0 || /sbin/mdadm --assemble /dev/md0 /dev/sdb1 /dev/sdc1 -- Ticket URL: <http://trac.64studio.com/64studio/ticket/502> 64 Studio <http://trac.64studio.com/64studio> _______________________________________________ 64studio-devel mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-devel
