Hi, been using unraid for two or three years now, never run into problems, if only all software were this wonderful and stable I'd be out of work, so luckily it aint

 

I am now upgrading one of my data drives from 1TB to 2TB, been doing that before without problems.

My system before upgrading the drive was 4x2TB (1 parity, 3 data) and 2x1TB (both data of course). The disk I'm replacing is one of the two 1TBs.

 

- I stopped the system, powered down from the webui.

- Took out the drive I was replacing, and put in the new

- Powered on system, checked <"Yes I am sure I wanna..." ...and expand the file system>

-As expected, there is now heavy reading on all the old drives, and writing on the new.

 

My worry is that before the system went "live" (meaning that I could access the shares. and the rebuild x,xx% started), the reading and writing mentioned above kept on for a long time, probably 5-10 minutes, and there was also writing to Parity disk during that time. That has stopped since the system went live.

 

Now, I do of course understand why it reads from all old disks and writes to the new, that's how it works, what I'm not sure is right is tthe writing to parity in this process. As I didn't have access to the share while this took place there can't be my computer writing, deleting or modifying files.

Total "writes" on parity before system went live is 7547, while the other old drives with data each has only 10 or 11.

Reads on all the old drives, as I write, 107K and 115K, while writes on the new drive is 125K, in other words higher than the reads on the others.

 

Does this indicate I have a problem, or do I worry for no reason?

 

All answers are appreciated

 

*Please excuse my poor english, it is not my native language

I'm sure all is fine ... it was almost certainly simply formatting the replacement disk (creating a Reiser file system) before it began the process of rebuilding all of the data.    Sounds like exactly what would happen if you simply added another 2TB drive and told it to format.

 

 

The file system is not created independently before a rebuild. The entire partition is rebuilt. This is the abstraction layer below the file system. It's also why a rebuild does not correct file system issues. Any problems with a file system are recreated on the rebuilt drive. Writes are a normal part of mounting a file system in Linux. Depending on how the system was previously shutdown the journal may be replayed.

Thanks guys, it looks alright. Of course I can't remember every single file I have, but so far everything seems good