Unraid 6 RC4 - Cache drive problem

[mattyg]

Hey guys,

Trying to add a cache drive to my unraid server.

 

I am able to successfully add the cache drive and add it on my shares but nothing is being cached when i transfer files.

Doint a bit of investigation:

- On the main page, the cache drive shows as having 0 B of space available.. despite me formatting it before hand.

- When I access the cache drive directly (ie //Server/cache) it says I dont have permission to copy files.

- When I check permission from shell, it says "drwxr-xr-x 2 root  root  16384 Jan  1  1970 cache"

- I have rebooted many times with and without the cache drive added.

 

I have tried to change the permissions of the drive but doesnt seem to work.

 

Im a bit stumped.

 

Any ideas?

 

thanks,

 

Matt

[trurl]

What do you mean you formatted it before hand? You must let unRAID format any disks it uses. What is the file system?

[mattyg]

it was an SSD i repurposed from a windows PC. I formatted the drive in windows before i removed it just to remove any of the old data..

In Unraid, it says the drive is VFAT (even though when i formatted it in windows im pretty sure it was NTFS)..

 

I would have thought as soon as I added the drive to unraid that it would reformat the drive into either XFS or reiserfs?

 

thanks,

 

Matt

[trurl]

Stop the array. Click on the drive. Choose the filesystem. Start the array. Let unRAID format.

[mattyg]

thanks trurl,

 

already tried that..

When I do that and start the array, the drive has "unmountable" next to it. ie sdf

 

from syslog

##############

 

Jun  7 00:46:58 Jiraiya kernel: XFS (md3): Mounting V4 Filesystem

Jun  7 00:46:58 Jiraiya kernel: XFS (md3): Ending clean mount

Jun  7 00:46:58 Jiraiya emhttp: shcmd (244): xfs_growfs /mnt/disk3 |& logger

Jun  7 00:46:58 Jiraiya logger: meta-data=/dev/md3              isize=256    agcount=4, agsize=183141659 blks

Jun  7 00:46:58 Jiraiya logger:          =                      sectsz=512  attr=2, projid32bit=0

Jun  7 00:46:58 Jiraiya logger:          =                      crc=0        finobt=0

Jun  7 00:46:58 Jiraiya logger: data    =                      bsize=4096  blocks=732566633, imaxpct=5

Jun  7 00:46:58 Jiraiya logger:          =                      sunit=0      swidth=0 blks

Jun  7 00:46:58 Jiraiya logger: naming  =version 2              bsize=4096  ascii-ci=0 ftype=0

Jun  7 00:46:58 Jiraiya logger: log      =internal              bsize=4096  blocks=357698, version=2

Jun  7 00:46:58 Jiraiya logger:          =                      sectsz=512  sunit=0 blks, lazy-count=1

Jun  7 00:46:58 Jiraiya logger: realtime =none                  extsz=4096  blocks=0, rtextents=0

Jun  7 00:46:58 Jiraiya emhttp: shcmd (245): mkdir -p /mnt/cache

Jun  7 00:46:58 Jiraiya emhttp: shcmd (246): set -o pipefail ; mount -t xfs -o noatime,nodiratime /dev/sdf1 /mnt/cache |& logger

Jun  7 00:46:58 Jiraiya kernel: XFS (sdf1): Invalid superblock magic number

Jun  7 00:46:58 Jiraiya logger: mount: wrong fs type, bad option, bad superblock on /dev/sdf1,

Jun  7 00:46:58 Jiraiya logger:        missing codepage or helper program, or other error

Jun  7 00:46:58 Jiraiya logger:        In some cases useful info is found in syslog - try

Jun  7 00:46:58 Jiraiya logger:        dmesg | tail  or so

Jun  7 00:46:58 Jiraiya logger:

Jun  7 00:46:58 Jiraiya emhttp: shcmd: shcmd (246): exit status: 32

Jun  7 00:46:58 Jiraiya emhttp: mount error: No file system (32)

Jun  7 00:46:58 Jiraiya emhttp: shcmd (247): rmdir /mnt/cache

Jun  7 00:46:58 Jiraiya emhttp: shcmd (248): sync

Jun  7 00:46:58 Jiraiya emhttp: shcmd (249): mkdir /mnt/user0

Jun  7 00:46:58 Jiraiya emhttp: shcmd (250): /usr/local/sbin/shfs /mnt/user0 -disks 14 -o noatime,big_writes,allow_other  |& logger

Jun  7 00:46:58 Jiraiya emhttp: shcmd (251): mkdir /mnt/user

Jun  7 00:46:58 Jiraiya emhttp: shcmd (252): /usr/local/sbin/shfs /mnt/user -disks 15 2048000000 -o noatime,big_writes,allow_other -o remember=0  |& logger

Jun  7 00:46:58 Jiraiya emhttp: shcmd (253): cat - > /boot/config/plugins/dynamix/mover.cron <<< "# Generated mover schedule:#01240 3 * * * /usr/local/sbin/mover |& logger#012"

Jun  7 00:46:58 Jiraiya emhttp: shcmd (254): /usr/local/sbin/update_cron &> /dev/null

Jun  7 00:46:58 Jiraiya emhttp: shcmd (255): :>/etc/samba/smb-shares.conf

Jun  7 00:46:58 Jiraiya avahi-daemon[20885]: Files changed, reloading.

Jun  7 00:46:58 Jiraiya emhttp: Restart SMB...

Jun  7 00:46:58 Jiraiya emhttp: shcmd (256): killall -HUP smbd

Jun  7 00:46:58 Jiraiya emhttp: shcmd (257): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service

Jun  7 00:46:58 Jiraiya avahi-daemon[20885]: Files changed, reloading.

 

###################

[scottc]

You will probably have to do a pre-clear on the drive with the pre-clear script

[mattyg]

I think I have it fixed..

 

I deleted all existing partitions on the drive using fdisk..

I then added the drive as the cache drive and started the array..

 

Only now would it appear as an "unmountable" drive with the option to format the drive through unraid.

unraid has formatted the drive and put the btrfs filesystem.

 

Do you think there is anything wrong with how I have done this? ie instead of doing a preclear.. (dont like doing preclears on an SSD)

 

thanks,

 

Matt

[trurl]

I think I have it fixed..

 

I deleted all existing partitions on the drive using fdisk..

I then added the drive as the cache drive and started the array..

 

Only now would it appear as an "unmountable" drive with the option to format the drive through unraid.

unraid has formatted the drive and put the btrfs filesystem.

 

Do you think there is anything wrong with how I have done this? ie instead of doing a preclear.. (dont like doing preclears on an SSD)

 

thanks,

 

Matt

I think you should be good now. The partitions Windows put on it were probably the problem.