I'm having an issue with my array.

 

I was migrating data from one server to another, and in the beginning had no parity disk. I have everything backed up to crashplan for two of my shares. I added a third disk to the array, and added some more data, and then added the parity disk.

 

When I added the parity disk, one of my normal disks had a SMART failure, and now it can't be mounted or reformatted at all. I got a new disk to replace it with but I can't seem to reformat that one either to rebuild the array. It shows up as unmountable, and when I hit format, literally nothing happens.

 

Here is my log:

 

 

Mar 23 20:36:44 NeverlandUNRAID logger: meta-data=/dev/md3 isize=512 agcount=4, agsize=183141659 blks

Mar 23 20:36:44 NeverlandUNRAID logger: = sectsz=512 attr=2, projid32bit=1

Mar 23 20:36:44 NeverlandUNRAID logger: = crc=1 finobt=1

Mar 23 20:36:44 NeverlandUNRAID logger: data = bsize=4096 blocks=732566633, imaxpct=5

Mar 23 20:36:44 NeverlandUNRAID logger: = sunit=0 swidth=0 blks

Mar 23 20:36:44 NeverlandUNRAID logger: naming =version 2 bsize=4096 ascii-ci=0 ftype=1

Mar 23 20:36:44 NeverlandUNRAID logger: log =internal log bsize=4096 blocks=357698, version=2

Mar 23 20:36:44 NeverlandUNRAID logger: = sectsz=512 sunit=0 blks, lazy-count=1

Mar 23 20:36:44 NeverlandUNRAID logger: realtime =none extsz=4096 blocks=0, rtextents=0

Mar 23 20:36:44 NeverlandUNRAID emhttp: shcmd: shcmd (214): exit status: 1

Mar 23 20:36:44 NeverlandUNRAID emhttp: shcmd (215): mkdir -p /mnt/disk3

Mar 23 20:36:44 NeverlandUNRAID kernel: buffer_io_error: 254 callbacks suppressed

Mar 23 20:36:44 NeverlandUNRAID kernel: Buffer I/O error on dev md3, logical block 16, async page read

Mar 23 20:36:44 NeverlandUNRAID kernel: Buffer I/O error on dev md3, logical block 16, async page read

Mar 23 20:36:44 NeverlandUNRAID emhttp: shcmd (216): set -o pipefail ; mount -t xfs -o noatime,nodiratime /dev/md3 /mnt/disk3 |& logger

Mar 23 20:36:44 NeverlandUNRAID logger: mount: /dev/md3: can't read superblock

Mar 23 20:36:44 NeverlandUNRAID emhttp: shcmd: shcmd (216): exit status: 32

Mar 23 20:36:44 NeverlandUNRAID emhttp: mount error: No file system (32)

Mar 23 20:36:44 NeverlandUNRAID emhttp: shcmd (217): rmdir /mnt/disk3

Mar 23 20:36:44 NeverlandUNRAID kernel: XFS (md3): SB validate failed with error -5.

Mar 23 20:36:44 NeverlandUNRAID emhttp: shcmd (218): :>/etc/samba/smb-shares.conf

Mar 23 20:36:44 NeverlandUNRAID emhttp: shcmd (219): cp /etc/netatalk/afp.conf- /etc/netatalk/afp.conf

Mar 23 20:36:44 NeverlandUNRAID avahi-daemon[13716]: Files changed, reloading.

Mar 23 20:36:44 NeverlandUNRAID avahi-daemon[13716]: Files changed, reloading.

Mar 23 20:36:44 NeverlandUNRAID avahi-daemon[13716]: Files changed, reloading.

Mar 23 20:36:44 NeverlandUNRAID emhttp: Restart SMB...

Mar 23 20:36:44 NeverlandUNRAID emhttp: shcmd (220): killall -HUP smbd

Mar 23 20:36:44 NeverlandUNRAID emhttp: shcmd (221): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service

Mar 23 20:36:44 NeverlandUNRAID avahi-daemon[13716]: Files changed, reloading.

Mar 23 20:36:44 NeverlandUNRAID avahi-daemon[13716]: Service group file /services/smb.service changed, reloading.

Mar 23 20:36:44 NeverlandUNRAID emhttp: shcmd (222): pidof rpc.mountd &> /dev/null

Mar 23 20:36:44 NeverlandUNRAID emhttp: shcmd (223): /etc/rc.d/rc.atalk status

Mar 23 20:36:44 NeverlandUNRAID emhttp: Restart AFP...

Mar 23 20:36:44 NeverlandUNRAID emhttp: shcmd (224): /etc/rc.d/rc.atalk reload |& logger

Mar 23 20:36:44 NeverlandUNRAID emhttp: shcmd (225): cp /etc/avahi/services/afp.service- /etc/avahi/services/afp.service

Mar 23 20:36:44 NeverlandUNRAID avahi-daemon[13716]: Files changed, reloading.

Mar 23 20:36:44 NeverlandUNRAID avahi-daemon[13716]: Service group file /services/afp.service changed, reloading.

Mar 23 20:36:45 NeverlandUNRAID avahi-daemon[13716]: Service "NeverlandUNRAID" (/services/smb.service) successfully established.

Mar 23 20:36:45 NeverlandUNRAID avahi-daemon[13716]: Service "NeverlandUNRAID-AFP" (/services/afp.service) successfully established.

 

EDIT: All I want to do is lose/replace the failed disk, I don't care about the data. all of my data was moved onto the array before the last disk was added.

Tools -> New Config will un-allocate your disks. Then you can re-allocate them, omitting the failed one. Then you can start the array and let parity build. That will get you where you want to be.

 

If you need more help post your diagnostics. That tiny snippet of a syslog doesn't help at all.

 

Apologies! I thought I was helping. Your Tools -> New Config was exactly what I was looking for. Thank you so much!