Now it happened to me too.

 

Just did insert a new parity drive and hit Start. This is what I do see now.

 

Any suggestions?

 

Thanks

Harald

bla.txt

Just click "Stop" and then "Start"

 

As with everybody else, the disks did not mount.

 

If you want to try mounting one by command line, before you stop and re-start, try this

 

mkdir -p /mnt/disk1

mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md1 /mnt/disk1

 

You'll perhaps be able to tell if it is a timing thing if the mount succeeds..

Thanks for your fast reply.

 

Just did Stop/Start and everything is on track. Will I end with 1,5 billion sync errors now that I stopped parity upgrade?

 

I'm wondering what the previous Sync was doing with all data disks shown as Unformatted. It even showed read values for the unmounted data disks - very interesting.

 

Thanks again.

Harald

 

Thanks for your fast reply.

 

Just did Stop/Start and everything is on track.

I guess you did not try to manually mount the disk before the stop/start.  Too bad, might have given Tom another clue.

Will I end with 1,5 billion sync errors now that I stopped parity upgrade?

I would expect them, yes.  You do NOT have parity protection until a full parity check/build is performed.

I'm wondering what the previous Sync was doing with all data disks shown as Unformatted. It even showed read values for the unmounted data disks - very interesting.

If the "md" device was connected to the assigned drives it would not have known you had not mounted the "md" devices (or that the mount had failed)

 

Basically, it sounded as if it was going along as it was supposed to.  It has nothing to do with if a drive is mounted, ot not, or formatted, or not, to parity it is just a collection of bits.

Thanks again.

Harald

 

You are welcome.