search for: md9

...This isn't specifically a CentOS question, since it could apply for any distro but I hope someone can answer it anyway. I took the following steps but was puzzled by the outcome of the test at the end: 1. Create a RAID1 array called md3 with two 750GB drives 2. Create a RAID1 array called md9 with two 500GB drives 3. Initialise md3 then md9 as physical volumes (pvcreate) 4. Create a new volume group called "3ware" with md3 (helps me remember what controller the disks are on) 5. Use vgextend and add md9 to the 3ware volume group. 6. Add a logical volume filling the volume gro...

Hi, My workstation is running CentOS 7 on two disks (sda and sdb) in a software RAID 1 setup. It looks like I accidentally nuked it. I wanted to write an installation ISO file to a USB disk, and instead of typing dd if=install.iso of=/dev/sdc I typed /dev/sdb. As soon as I hit <Enter>, the screen froze. I tried a hard reset, but of course, the boot process would stop short very early in

...esystem Size Used Avail Use% Mounted on /dev/md5 939M 237M 654M 27% / /dev/md0 91M 22M 65M 25% /boot /dev/md6 277M 8.1M 254M 4% /tmp /dev/md7 1.8G 1.3G 595M 69% /usr /dev/md8 938M 761M 177M 82% /var /dev/md9 9.2G 2.6G 6.1G 30% /home /dev/md10 11G 2.1G 8.7G 19% /scratch /dev/md12 56G 43G 13G 77% /global The /usr and /var filesystems keep switching to ro mode following the detection of errors. This has been happening on a daily basis since switching to e...

...olGroup00 lvm2 [139.72 GB / 0 free] PV /dev/md5 VG VolGroup00 lvm2 [139.72 GB / 0 free] PV /dev/md6 VG VolGroup00 lvm2 [139.72 GB / 0 free] PV /dev/md7 VG VolGroup00 lvm2 [139.72 GB / 0 free] PV /dev/md8 VG VolGroup00 lvm2 [139.72 GB / 0 free] PV /dev/md9 VG VolGroup00 lvm2 [139.72 GB / 139.72 GB free] Total: 10 [1.36 TB] / in use: 10 [1.36 TB] / in no VG: 0 [0 ] (evidently /dev/md9 isn't being used ... emergency spare?) And from there, they created the logical volumes which lvscan says are: lvscan ACTIVE '...

...96256 blocks [2/2] [UU] md5 : active raid1 hdk1[1] hde1[0] 976640 blocks [2/2] [UU] md6 : active raid1 hdk5[1] hde5[0] 292672 blocks [2/2] [UU] md7 : active raid1 hdk6[1] hde6[0] 1952896 blocks [2/2] [UU] md8 : active raid1 hdk7[1] hde7[0] 976640 blocks [2/2] [UU] md9 : active raid1 hdk8[1] hde8[0] 9765376 blocks [2/2] [UU] md10 : active raid0 hdk9[1] hde9[0] 12108800 blocks 4k chunks md12 : active raid5 hdk3[3] hde3[2] hdc2[1] hda2[0] 59978304 blocks level 5, 32k chunk, algorithm 2 [4/4] [UUUU] md11 : active raid1 hdk4[1] hde4[0] 1702...

...esystem Size Used Avail Use% Mounted on /dev/md5 939M 237M 654M 27% / /dev/md0 91M 22M 65M 25% /boot /dev/md6 277M 8.1M 254M 4% /tmp /dev/md7 1.8G 1.3G 595M 69% /usr /dev/md8 938M 761M 177M 82% /var /dev/md9 9.2G 2.6G 6.1G 30% /home /dev/md10 11G 2.1G 8.7G 19% /scratch /dev/md12 56G 43G 13G 77% /global The /usr and /var filesystems keep switching to ro mode following the detection of errors. This has been happening on a daily basis since switching to e...

Hello, Sorry to sound like a bad record, but I'm trying to figure out why I'm getting "Bad gzip magic numbers" errors when ISOlinux is trying to inflate the kernel. Right now I'm clueless as to what's wrong. I've tried various kernels compiled on a few different platforms. Has anyone ever seen this before? ANyone know where a better forum to ask this question