cracksilver Posted February 27, 2019 Share Posted February 27, 2019 Hi there After restart my server (add some unassigned HD's) the server shows me the message that he is unable to write to flash drive. My flash drive is a new one (4 weeks) and I never had some problems. Does anyone know which corner I should start looking for where the problem is? added diagnostics.zop, pics of error message and main tab. Thanks a lot. greg tower-diagnostics-20190227-1737.zip Quote Link to comment
cracksilver Posted February 27, 2019 Author Share Posted February 27, 2019 after another restart again the same message.... 🤔 Quote Link to comment
JorgeB Posted February 27, 2019 Share Posted February 27, 2019 Run chkdsk on a Windows PC to see if it helps, it can also be a failing flash drive. Quote Link to comment
cracksilver Posted February 27, 2019 Author Share Posted February 27, 2019 Thanks. i've no windows - since 15 years windows free 😀 Did it on my mac: sorry, only in german... Dateisystem reparieren. Volume wurde erfolgreich deaktiviert. fsck_msdos -y /dev/rdisk2s1 ausführen ** /dev/rdisk2s1 ** Phase 1 - Preparing FAT ** Phase 2 - Checking Directories Invalid long filename entry for /CONFIG/PLUGINS/dockerMan Remove? yes ** Phase 3 - Checking for Orphan Clusters 479 files, 3679076 KiB free (919769 clusters) ***** FILE SYSTEM WAS MODIFIED ***** Exit-Code für Dateisystemprüfung lautet 0. Der ursprüngliche Zustand (aktiviert) wird wiederhergestellt. Vorgang erfolgreich. Now I'll reboot again and look at.. Quote Link to comment
cracksilver Posted February 27, 2019 Author Share Posted February 27, 2019 I got no error message again. But what does it mean this message? Last login: Wed Feb 27 18:30:02 +0100 2019 on /dev/pts/0. root@Tower:~# diagnostics Starting diagnostics collection... awk: cmd. line:1: (FILENAME=/tower-diagnostics-20190227-1834/logs/syslog.txt FNR=54) warning: Invalid multibyte data detected. There may be a mismatch between your data and your locale. done. ZIP file '/boot/logs/tower-diagnostics-20190227-1834.zip' created. Quote Link to comment
JorgeB Posted February 27, 2019 Share Posted February 27, 2019 Sorry, don't know. Quote Link to comment
cracksilver Posted February 27, 2019 Author Share Posted February 27, 2019 3 hours ago, johnnie.black said: Run chkdsk on a Windows PC to see if it helps, it can also be a failing flash drive. Thank you johnnie for this tip. It works again. I'm wondering why this error happened on the new USB stick... Quote Link to comment
bombz Posted March 31, 2019 Share Posted March 31, 2019 (edited) On 2/27/2019 at 3:45 PM, cracksilver said: Thank you johnnie for this tip. It works again. I'm wondering why this error happened on the new USB stick... I am getting the same error, when I was writing plex.txz to my flash it is getting a write error 'target access denied' I shut down the server tossed the USB into my local system to write the update (no issues) put it back in the server booted and still have the 'target access denied' error. I didn't do a chkdsk on my windows PC ... yet. I will see if that solves the concern Kingson USB 2.0 (new flash) EDIT: Scratch that, I am 'dumb' I saw I wasn't logged into my admin account, ugh. Please disregard. Also, thank you for the tips above all! Edited March 31, 2019 by bombz Quote Link to comment
cracksilver Posted March 31, 2019 Author Share Posted March 31, 2019 I never had this issue again. The server runs and runs and runs... Quote Link to comment
Squid Posted March 31, 2019 Share Posted March 31, 2019 8 hours ago, bombz said: I was writing plex.txz to my flash Not recommended to run PhAzE plugins (or god forbid the old official Plex unRaid plugin) for quite awhile now. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.