Search:

It is working great here. I want to thank you. I had serious c-spine injuries a few years ago and this server helps my children so it really means a lot to me to be able to get this back up and...

As for the read only. I read somewhere that it stary in that state until the swap is written to. Then it changes. A new one is attached below.

free -m

total used free ...

Thanks for your patience..I guess its a bit to learn on the fly. I made the change then rebooted here are the reports for your review:
cat /etc/fstab

# /etc/fstab: static file system information....

The first one may just have been a copy paste issue..


Here is the new fstab

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
#...

# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks....

sudo update-initramfs -u

update-initramfs: Generating /boot/initrd.img-3.13.0-63-generic
W: mdadm: the array /dev/md/Server1:1 with UUID b2e96d72:2f85ad85:b7038442:2e68be61
W: mdadm: is...

I think I got it..

swapoff /dev/md127
mkswap /dev/md127
swapon /dev/md127

then ran cat /proc/mdstat and got this


Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5]...

I just rebooted and its the same as the last one.
cat /etc/mdadm/mdadm.conf


# Please refer to mdadm.conf(5) for information about this file.
#

# by default (built-in), scan all partitions...

Ok. The udid makes sense to me now...Here is the latest output


Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md127 : active (auto-read-only) raid1...

Ok. I got the mdadm.conf to match the sda5 and db5 udid. However the blikid still remains as the old one.

Ok, to be certain I understand...

Take the udid from the fstab above and enter that in mdadm.conf in the place of the md1's udid?

Here is how things look as of now:

sudo parted -l



Model: ATA TOSHIBA DT01ACA1 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos

It is identical to what is already in fstab

blkid

/dev/sda1: UUID="8a05d97d-72df-34e1-f462-ad65b4925eb9" UUID_SUB="f67a6e41-4737-922d-0733-11a4ca6b6bfa" LABEL="server2:0" TYPE="linux_raid_member"
/dev/sda5:...

mdadm /dev/md1 --remove /dev/sda5

mdadm: error opening /dev/md1: No such file or directory


mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sda5 /dev/sdb5

mdadm: /dev/sda5 appears...

The first two commands are in error so I stopped


root@Server1:~# mdadm /dev/md1 --remove /dev/sda5
mdadm: cannot get array info for /dev/md1
root@Server1:~# mdadm --zero-superblock /dev/sda5...

sudo parted -l


Model: ATA TOSHIBA DT01ACA1 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos

Number Start End Size Type File...

I would live to be walked through the process. I am in and out for most of the day here as well. Its winterize the pool day for me today......But please yes lets see what we can do with it in...

Just the fact that it was inactive is what i am confused about. Do I not need that swap raid?

It seemed to go well but then I saw this:


md1 : inactive sda5[0](S)
1950720 blocks super 1.2

md0 : active raid1 sdb1[2] sda1[0]
14638976 blocks super 1.2 [2/2] [UU]

md2 :...

Managed to get another identical drive today so here goes..Do I need to remove the old drive first in mdadm?

Hey..Thanks a million for your assistance. In the end I pulled the drive and tested it and it has many many errors..I couldn't even low level format it...I will be replacing the drive with a new...

Ill try the first option first..Thanks

Similar result:



mdadm: add new device failed for /dev/sdb1 as 2: Invalid argument

sudo mdadm --zero-superblock /dev/sdb6
mdadm: Unrecognised md component device - /dev/sdb6
# sudo mdadm /dev/md0 --add /dev/sdb1
mdadm: add new device failed for /dev/sdb1 as 2: Invalid argument
#