Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
status of the components for raid /dev/md1
1) sda2 = State (Clean) / Events 2141670
2) sdb2 = State (Clean) / Events 2141670
3) sdc2 = State (Clean) / Events 2141670
4) sdd2 = State (Clean) / Events 2141506
I saw a post online to try to force assembly the raid /dev/md1. Question is based on the info above, is it safe to do so?
The command suggested was 'mdadm --assemble --force /dev/md1 /dev/sd[a-d]2'
Last edited by TobiSGD; 04-16-2014 at 06:59 PM.
Reason: Moderator: added code-tags
Please use code-tags to preserve formatting when posting output of commands, this improves the readability of your posts significantly. I fixed that in your previous posts already. If you need more information on code-tags have a look at the link in my signature.
sorry dimonic for the late reply. see below output
Code:
root@IomegaNAS:/# mount
rootfs on / type rootfs (rw)
/dev/root.old on /initrd type ext2 (rw)
none on / type tmpfs (rw)
/dev/md0 on /boot type ext2 (rw)
/dev/loop0 on /mnt/apps type cramfs (ro)
/dev/loop1 on /etc type ext2 (rw)
/dev/loop2 on /oem type cramfs (ro)
proc on /proc type proc (rw)
none on /proc/bus/usb type usbfs (rw)
none on /proc/fs/nfsd type nfsd (rw)
none on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw)
tmpfs on /mnt/apps/lib/init/rw type tmpfs (rw,nosuid)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
Code:
root@IomegaNAS:/# fdisk -l /dev/sdd
Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x490e5aa7
Device Boot Start End Blocks Id System
/dev/sdd1 1 127 1020096 83 Linux
/dev/sdd2 128 121602 975742455+ 83 Linux
root@IomegaNAS:/# mdadm /dev/md1 -f /dev/sdb2
mdadm: metadata format 00.90 unknown, ignored.
mdadm: metadata format 01.00 unknown, ignored.
mdadm: set device faulty failed for /dev/sdb2: No such device
root@IomegaNAS:/# mdadm /dev/md1 -r /dev/sdb2
mdadm: metadata format 00.90 unknown, ignored.
mdadm: metadata format 01.00 unknown, ignored.
mdadm: hot remove failed for /dev/sdb2: No such device
root@IomegaNAS:/# mdadm /dev/md1 -a /dev/sdb2
mdadm: metadata format 00.90 unknown, ignored.
mdadm: metadata format 01.00 unknown, ignored.
mdadm: Cannot open /dev/sdb2: Device or resource busy
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.