itimpi

You need to run the newperms command on the lost+found folder before you will be able to access it via the network. The reiserfsck command will almost certainly have created it and all the files it contains as owned by 'root'.

Isn't that what I said (the username needs to all be lowercase)

That looks correct. it is quite normal to have to run with --rebuild-tree after having run with --rebuild-sb.

I seem to vaguely remember that you can have a problem if the username used is not all lower case at the Linux level?

Correct. Once the free space on the cache drive goes below the value specified as a minimum then all new files are written directly to the main disks bypassing the cache. The key item is picking a value for the minimum free space that will allow all files created before the minimum was reached to finish being written. What is a sensible value therefore depends on the maximum size of files you are likely to be writing, and the number that are being written in parallel. As an example I find that a value of 25GB works fine for me on my 250GB cache drive.

Dv8ed. With a split level of 2 then all your folders directly under Media are potentially going to be on all disks. Since you have different requirements for Movies and the other media types, perhaps you need more than one share set up so they can have different properties? The alternative is to manually manage things and copy explicitly to specific disks. However that adds an extra level of manual effort you may prefer not to have?

If you run several pre-clear cycles and the pending sectors does not get down to zero I would be tempted to RMA the drive. You do not want to use a drive that has pending sectors outstanding in unRAID

Not sure. Simply guessing as the system sounds unhappy at a level beyond the software level. The syslog might give an indication of what is happening under the covers. It will at least show what the Linux level thinks of the drives.

You mentioned that the machine was shut down while renovation was going on which suggests that it could have been moved around quite a bit so that the internals got disturbed. I would check that any daughter boards are properly seated and then check that all the cabling appears to be securely plugged in. Also check that there is not a lot of dust inside the system (in case it was not protected from this during renovation). The fact that you were having trouble even getting the system to boot is a bit suspicious.

There is an issue with changing the server name on any version if you do not reboot all devices connected to your network. This problem will auto-rectify itself if you leave things long enough but that can take many hours (or even days). This issue is not limited to unRAID - the same thing can happen if you change the network names of PC's.

But doesn't it wipe the MBR on step 4 & 5? Why is it still corrupt(?)? No idea - I assume that the write or read of the MBR did not work as expected. Maybe Joe L. will see this thread and have further insights.

It is saying the MBR was not cleared, so I expect 10 failed (that WILL read back the MBR).

If you are using RC11 then swapping cables is irrelevant as disks are recognized by their Id's and not their position. I suspect that you are not doing the steps for the swap-disable quite correctly.

Would it not have been possible to do it in one stage by putting the new 3TB disk in as parity, and the old 2TB disk to replace the 1TB disk and then do a swap-disable? In other words the mistake was to try and put the 3TB disk in place of the 1TB disk as one of the stages which breaks the rules that parity can never be smaller than any of the data disks. Thought I should check before I need to do this in anger !

The agony of losing a disk is causing these "duh" moments. Sorry, I dont know what I was thinking. I know what you mean (I am prone to 'duh' moments myself at times). I hope the fact that now you realise what you are seeing is expected behaviour it will at least reduce the stress

With a split level of 2 the movie folder can be replicated on different disks if the path is movies/moviename. When you added the subtitle file that is logically inside this moviename folder then the disk it will go on will depend on your free space allocation method. If it is only the top level 'Movies' folder that you want to allow to be replicated across disks, but any moviename folder under this to be contrained to one disk you would need a split level of 1.

with the structure you mention you are going to need at least a split level of 2! A level of one will only allow the media folder to be replicated across disks. For any folder below that once it has been created on a disk all further content of that folder (and its sub-folders) is constrained to the single disk. This explains the behaviour that you are seeing. A split level of 2 would allow folders such as media/TV_Shows and media/movies to also be replicated across disks and only sub-folders of those constrained to a single disk. I think that is the behaviour you are looking for?

That does look a little strange! Certainly on my system the Free Space value reflects the total of all the disks that are allowed to hold that share. You might want to check the "Share Settings" option under the Setting Tab. I am not sure what happens if there is any sort of discrepancy between the values there for included and excluded disks and the values for the individual shares on the Shares tab.

It is difficult to guess at what might be going wrong - your symptoms are certainly not something I have seen others reporting. I also think that some screen shots of the disk configuration and the share configuration (for the relevant shares) might help with understanding how you are trying to set things up. It might also be worth attaching a syslog covering the period where things go wrong to see if anything useful shows up there.

It sounds as if your /dev/sdj device is dropping offline for some reason. I think a syslog will be needed for anyone to give any sort of diagnosis. That would at least show if the disk is ever being seen by the system or starts of working and then is being disabled. It must be worth checking all cabling in case any have worked loose.

Just a point - in this context 'stock' just means running without any plugins - it does not mean you should not be using the 5.0 rc11 release. The intention is to isolate genuine unRAID errors from those that might be caused by plugins not 9yet) running correctly with the current release.

The manual you linked to covers 2 variants of that motherboards , and points out that one of the differences is one model only has 2 DIMM slots. It also states that the maximum memory supported on the 2-slot variant of the board is 4GB (2 x 2GB) so unless you can find something to the contrary then you will not be able to go above this. Having said that I would not be surprised if that was a BIOS limitation that has since been increased so it might be worthwhile to check the BIOS release notes to see if any update increased that limit.

Is the price the same if we are not US based? I am interested in getting some from your next batch.

The sd? Names are allocated dynamically by Linux as it sees devices so you cannot directly control them. They will tend to be consistent between boots if you have made no hardware changes, but even then they can change if a device is slower/faster to respond than normal.

Note that just because a disk shows up as unformatted in the unRAID GUI does not necessarily mean that the data cannot be recovered from it. It will also show as unformatted if for any reason it failed to mount. Quite often it is possible to recover such disks back to a mountable state using the linux 'reiserfsck' command. It depends on whether you want to invest the effort to check that route out?