Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
When I go to rescue mode and delete /dev/md0 from fstab, I can restart, but I get this when I try to mount it again:
Code:
mount: you must specify the filesystem type
So I try to make it to a ext3
Code:
# mkfs.ext3 /dev/md0
mke2fs 1.39 (29-May-2006)
mkfs.ext3: Device size reported to be zero. Invalid partition specified, or
partition table wasn't reread after running fdisk, due to
a modified partition being busy and in use. You may need to reboot
to re-read your partition table.
#fdisk /dev/md0
Unable to read /dev/md0
mdadm --detail /dev/md0
mdadm: md device /dev/md0 does not appear to be active.
*note: This is after a reboot and deletion of /dev/md0 /vz ext3 defaults 0 0 from fstab.
Code:
#fdisk -l
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 * 14 2703 21600666 83 Linux
Partition 2 does not end on cylinder boundary.
/dev/sda3 2703 119301 936580194 83 Linux
/dev/sda4 119302 121601 18474750 5 Extended
/dev/sda5 119302 121601 18474718+ 82 Linux swap / Solaris
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 1 121601 976760001 83 Linux
Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdc1 1 121601 976760001 83 Linux
Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdd1 121601 121601 8032+ 83 Linux
mdadm --detail /dev/md0 suppose to equal /dev/sda3, /dev/sdb1, /dev/sdc1, /dev/sdd1
It seemed that Raid stop working after reboot. So I recreated it:
Code:
# mdadm --create /dev/md0 --chunk=4 --level=0 --raid-devices=4 /dev/sda3 /dev/sdb1 /dev/sdc1 /dev/sdd1
mdadm: /dev/sda3 appears to contain an ext2fs file system
size=-1404859392K mtime=Thu May 5 15:38:17 2011
mdadm: /dev/sda3 appears to be part of a raid array:
level=raid0 devices=4 ctime=Thu May 5 07:13:38 2011
mdadm: /dev/sdb1 appears to be part of a raid array:
level=raid0 devices=4 ctime=Thu May 5 07:13:38 2011
mdadm: /dev/sdc1 appears to be part of a raid array:
level=raid0 devices=4 ctime=Thu May 5 07:13:38 2011
mdadm: /dev/sdd1 appears to be part of a raid array:
level=raid0 devices=4 ctime=Thu May 5 07:13:38 2011
Continue creating array? yes
mdadm: array /dev/md0 started.
and made it ext3
Code:
# mkfs.ext3 /dev/md0
mke2fs 1.39 (29-May-2006)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
361267200 inodes, 722526976 blocks
36126348 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
22050 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544
Writing inode tables: 10728/22050
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.