PirateBox is not accessible - please help!!!

Posted by d-677 
This forum is currently read only. You can not log in or make any changes. This is a temporary situation.
Now, this forum is in read-only mode. You find details Details hereContinue on /r/PirateBox
PirateBox is not accessible - please help!!!
August 25, 2019 09:51AM
Hey everybody!

I am new to PirateBox and got mine working two days ago. Everything was running fine. I did some changes (changed the upload-folder, loaded up some files, configured the minidlna) and was quiet pleased how well everything was going.
I decided to use my PirateBox as storage for my music and e-books, so I directly put my music-library on the USB-Stick into the Folder "Shared/MUSIC". And this is where it starts to get me frustrated:

Since I loaded my music (roughly 70gb) to the USB-Stick, I can't access PiratBox anymore. That means, if I ping it, i get no response from it. Yet it is shown in the list of available networks.
I checked the USB-Stick in the meantime and realized, that the PirateBox seems to place a "HEADER.txt" and a "README.txt" in every (Sub-)Folder in the MUSIC-directory. So here is my question for you, the more advanced and experienced PirateBox-users:

Is it normal, that after putting a lot of files on the USB-Stick, that PirateBox needs some time for indexing all the new folders/subfolders/files/etc.?

And if "yes", how long does that usually take? In my case it is now 12h since I put the files on the USB and started PirateBox and I still can't reach it.

I am happy if somebody can help me with this! smiling smiley
Re: PirateBox is not accessible - please help!!!
August 25, 2019 10:09AM
I thought the following information might be useful to detect the error:

If I try to connect to the PiratBox I get a message that it takes longer as usual and in the end Windows is telling the connection is limited. If I use my phone (Android) to connect to PirateBox I get the message that PirateBox failed to provide an ip-adress.


If I ping PirateBox at 192.168.1.1 I get the following message four times:


Quote

PING: transmit failed. General Failure.


I also tried to reach it via puTTy, but that failed too.



Edited 1 time(s). Last edit at 08/25/2019 10:14AM by d-677.
UPDATE!
August 25, 2019 11:45AM
PirateBox seems to have completed the indexing of the whole MUSIC-folder, since in every directory and subdirectory the files "HEADER.txt" and "README.txt" are created. Since that I can normally connect to PirateBox without having limited access. I am also able to ping PirateBox with normal response.

YET I still cannot access PirateBox via the Browser. Neither 192.168.1.1 nor piratbox.lan are working. Connecting to PirateBox via SSH works, but as soon as I cd to /opt/piratebox/ and do a "ls"-command, the connection fails.
Is it possible that the problem is connected to the USB-stick? I am using a USB 2.0 stick with 128gb from HAMA. It is formated with FAT32 and worked well bevor (when there was a small amount of data on the stick).

Please help, I am really frustrated by now sad smiley

ADD: I deleted the index.html on the USB-Stick an created it again. Now I CAN access PirateBox via the Browser AND I can access the entire filesystem via SSH. But as soon as I open the Shared-folder, I only see weird symbols. If I click on one of the links I am redirected to the mainpage...

Here is a screenshot of the Shared-folder:



heres the link to the screenshot: https://ibb.co/nfp6Qmp

Quote

root@Yl5aCKBz:/mnt/usb# dmesg | tail -n 20
[ 2061.740000] FAT-fs (sda1): error, invalid access to FAT (entry 0x3394291e)
[ 2061.750000] FAT-fs (sda1): error, invalid access to FAT (entry 0xe41b240d)
[ 2061.750000] FAT-fs (sda1): error, invalid access to FAT (entry 0x545d0088)
[ 2061.760000] FAT-fs (sda1): error, invalid access to FAT (entry 0xc03d7df0)
[ 2061.770000] FAT-fs (sda1): error, invalid access to FAT (entry 0x384005cc)
[ 2061.780000] FAT-fs (sda1): error, invalid access to FAT (entry 0xaa337b94)
[ 2061.790000] FAT-fs (sda1): error, invalid access to FAT (entry 0x97ec36fe)
[ 2061.790000] FAT-fs (sda1): error, invalid access to FAT (entry 0x9b2e280e)
[ 2061.800000] FAT-fs (sda1): error, invalid access to FAT (entry 0x2afaa961)
[ 2061.810000] FAT-fs (sda1): error, invalid access to FAT (entry 0x504002b7)
[ 2061.820000] FAT-fs (sda1): error, invalid access to FAT (entry 0x60ca97dd)
[ 2061.830000] FAT-fs (sda1): error, invalid access to FAT (entry 0x567d7a5f)
[ 2061.830000] FAT-fs (sda1): error, invalid access to FAT (entry 0x38328994)
[ 2061.840000] FAT-fs (sda1): error, invalid access to FAT (entry 0x37fec463)
[ 2061.850000] FAT-fs (sda1): error, invalid access to FAT (entry 0xefe4100d)
[ 2061.860000] FAT-fs (sda1): error, invalid access to FAT (entry 0x2f706dae)
[ 2061.870000] FAT-fs (sda1): error, invalid access to FAT (entry 0x3b17c241)
[ 2061.870000] FAT-fs (sda1): error, invalid access to FAT (entry 0xbc71cdb6)
[ 2061.880000] FAT-fs (sda1): error, invalid access to FAT (entry 0x23576bee)
[ 2061.890000] FAT-fs (sda1): error, invalid access to FAT (entry 0xb3b8e35b)
root@Yl5aCKBz:/mnt/usb# dmesg | grep sda
[ 249.880000] FAT-fs (sda1): error, invalid access to FAT (entry 0x2e90441c)
.
.
.



Edited 1 time(s). Last edit at 08/25/2019 12:17PM by d-677.