USB Unassigned device added as rootfs (Solved)

[willgreen]

Hi, I have trying to add a USB 1.5TB drive as an unassigned device but its being added as rootfs drive of about 6GB.  The other day I installed a 1.5TB drive and it did the same thing, when I transferred some files it said it was full after 5GB. So I removed it and added it again after changing share settings to include all disk as I had previously remove a drive and shrank the array.  

 

 

Added drive and seemed ok

 

In Kusader the drive is there but its empty

 

Then back to the unassigned devices tab it shows a 1.5TB drive as a lot smaller 

 

Now its showing as an empty drive

tower-diagnostics-20171216-1700.zip

 

Any ideas thanks

 

 

Edited December 16, 2017 by willgreen

[dlandon]

Remove the preclear plugin and see if the drive shows the proper size.

[willgreen]

 

4 hours ago, dlandon said:

Remove the preclear plugin and see if the drive shows the proper size.

 

I removed the preclear plugin, It displays the correct size on the main page, I had to restart the array as when I click unmount it wouldn`t unmount the disk 

 

I still cant access the drive in Krusader, I used spaceinvaders video to do settings, Container Path: /UNASSIGNED -> /mnt/disks/

 

But I can access the drive in MC via putty and copy files to it.

 

 

Where should I point my Path: /UNASSIGNED to access the unassigned drives

 

Thanks

[Squid]

4 hours ago, willgreen said:

 
 
I removed the preclear plugin, It displays the correct size on the main page, I had to restart the array as when I click unmount it wouldn`t unmount the disk 

 
I still cant access the drive in Krusader, I used spaceinvaders video to do settings, Container Path: /UNASSIGNED -> /mnt/disks/

 
But I can access the drive in MC via putty and copy files to it.
 

 
Where should I point my Path: /UNASSIGNED to access the unassigned drives
 
Thanks

The drive is showing as empty in krusader because of this. https://forums.lime-technology.com/topic/57181-real-docker-faq/#comment-564314

 

and you want to set /unassigned to /mnt/disks as rw:slave per the above link

Sent from my SM-T560NU using Tapatalk
 

Edited December 17, 2017 by Squid

[dlandon]

12 hours ago, willgreen said:

 

 

I removed the preclear plugin, It displays the correct size on the main page, I had to restart the array as when I click unmount it wouldn`t unmount the disk 

 

I still cant access the drive in Krusader, I used spaceinvaders video to do settings, Container Path: /UNASSIGNED -> /mnt/disks/

 

But I can access the drive in MC via putty and copy files to it.

 

 

Where should I point my Path: /UNASSIGNED to access the unassigned drives

 

Thanks

If you click the unmount button and the disk does not unmount, it is probably from the disk being busy.  Check the system log and see what unassigned devices says about why it cannot unmount the device.

[Squid]

Having Krusader still pointed to the disk will be enough to keep the drive busy and unable to unmount. 

[willgreen]

17 hours ago, Squid said:

The drive is showing as empty in krusader because of this. https://forums.lime-technology.com/topic/57181-real-docker-faq/#comment-564314

 

and you want to set /unassigned to /mnt/disks as rw:slave per the above link

Sent from my SM-T560NU using Tapatalk
 

Thanks that has worked, I can now access USB drives from within Krusader. But why was it showing as a 6GB disk in the WebGUI (3rd pic)?

 

8 hours ago, dlandon said:

If you click the unmount button and the disk does not unmount, it is probably from the disk being busy.  Check the system log and see what unassigned devices says about why it cannot unmount the device.

 

6 hours ago, Squid said:

Having Krusader still pointed to the disk will be enough to keep the drive busy and unable to unmount. 

I forgot that the disk could have been busy and stop the unmount