[[unRAID 6 beta14+] Unassigned Devices [former Auto Mount USB]]

I am seeing a similar problem with free space in / slowly reducing.    So far my investigations have suggested it is something in /var/cache/samba.

 

I suspect that stopping and starting samba resets the files so that the used space is temporarily reclaimed, which is possibly why uninstalling the plugin appeared to fix the problem.

 

[Note that the Dashboard does not display the free space of /]

 

Update: I now don't think it is /var/cache/samba but rather possibly something in /var/cron.  The strange thing is that 'df /' is showing a decrease of the free space at a rate of about 1% an hour, but 'du -x /' is not showing an equivalent change in the blocks used.

 

Update 2: removing the checksum plugin appears to have stopped the loss of free space on my system.    Jbhipps, do you have this plugin installed on your system?

[[SOLVED] reiserfsck -rebuild-tree suggested by reiserfsck]

It would certainly be a good idea to run a parity check to ensure that your parity is still correct.

 

Certainly you could do what you suggest but I suspect that your rebuilt disk would just recreate the original file system corruption.

 

The problem is that we don't know what caused the original file system corruption that made the system put the disk into read only mode.  There is some debate about when you should trust your data disks or your parity when there is a discrepancy ..... But the general consensus appers to be that in the absence of other evidence you should trust your data and correct your parity.

 

Whatever the case it is important to ensure that the data disks and parity agree to ensure correct operation in the future.

[[SOLVED] reiserfsck -rebuild-tree suggested by reiserfsck]

The sda, sdb, etc are the names of the disk devices, with sda1, sdb1, etc being the 1st partition on those disks.  When you use these names any writes are made to those disks/partitions only.  The order the physical disks are assigned to which name is determined by the order the disks respond during boot time, so can vary depending on each boot.

 

The md1, md2, etc are similar to the sda1, sdb1, etc partition names except the names are allocated according to which disk has been allocated to which unraid disk slot (so are consistent across system boots).  But most importantly, any write to these md devices not only update the physical disk partition but also the parity disk.

 

Therefore if you run reiserfsck on the sda1, sdb1 devices and it makes a change on the disk but not parity, your parity disk is now invalid for wherever the write was done

 

However if you run reiserfsck on the md1, md2, etc devices and a change is made to the disk then the parity is also updated thus ensuring that the parity disk remain valid.

[Upgrading unRAID from Version 5 to Version 6]

The license keys are not specific to the version of unraid.  So your 2 pro keys can be used with version 5 or version 6 .... No additional cost involved.

[Preclear plugin]

When this plugin installs it attempts to do:

 

# fix permissions of executable files
chmod +x /usr/local/sbin/readvz

 

However this file does not exist and therefore always generates an error message (as can be seen in several earlier posts of installs in this thread)

 

 

 

[unRAIDFindDuplicates.sh]

Getting 2 errors. Anyway to fix this?

 

./unRAIDFindDuplicates.sh: line 153: [!: command not found

 

and

 

ls: cannot access /mnt/disk*//mnt/user/.........

 

Please see attached.

 

Duppie

 

For the 2nd problem use the command line option '-i Movies' rather than '-i /mnt/user/Movies' ... The /mnt/user is automatically added to what is supplied to the -i parameter's value.