hcardle Posted September 24, 2020 Author Share #26 Posted September 24, 2020 So I got this. Where is the offending folder? How do I delete it? What else happens or what else do I need to do after this? Quote Link to comment Share on other sites More sharing options...
hcardle Posted September 24, 2020 Author Share #27 Posted September 24, 2020 I think I found it ok. Last entry here. So before I delete it ( assume this is the cmd; rm -r /.xpenoboot) What else happens or what else do I need to do after this? Quote Link to comment Share on other sites More sharing options...
billat29 Posted September 24, 2020 Share #28 Posted September 24, 2020 Yes. You just delete the directory. You need sudo prior to the command. (Make sure that you don't mistype the command). Nothing magical will happen. Just ls -la again to make sure it has gone. Why the fuss? It's a left over from 5.2 and not needed in 6.1.7. However, if it is there in 6.2.3 it will cause all the services to crash after boot. You then get about 5 seconds after boot to ssh in and delete the directory before ssh itself crashes and locks you out. Been there (only ran ls -l). Done that. Recovered that. Same feeling as you had when you first attempted upgrade and it all went horribly wrong. Quote Link to comment Share on other sites More sharing options...
IG-88 Posted September 24, 2020 Share #29 Posted September 24, 2020 4 hours ago, hcardle said: So before I delete it ( assume this is the cmd; rm -r /.xpenoboot) What else happens or what else do I need to do after this? if you feel uneasy then you try to rename it to "test" i've not seen anything about why this happens, my guess would be that dsm looks for hidden directorys starting with "." and try's to parse files in it (meant to be .syno but ends in wrong directory that should not be there on a original system) Quote Link to comment Share on other sites More sharing options...
billat29 Posted September 24, 2020 Share #30 Posted September 24, 2020 This is now a bit off topic but when I had my moment with this, I looked in the log afterwards and there were a number of entries along the lines of "xxx has been successfully terminated" as if it wasn't actually a crash but something had sent a signal to terminate the tasks. Also my shares were still up on the network. Quote Link to comment Share on other sites More sharing options...
hcardle Posted September 24, 2020 Author Share #31 Posted September 24, 2020 cheers guys Quote Link to comment Share on other sites More sharing options...
hcardle Posted September 26, 2020 Author Share #32 Posted September 26, 2020 So I have just deleted the xpenoboot directory and confirmed it is gone. I had lots of trouble getting Plex with a secure remote access connection. Its better but still seems to drop out randomly. I also couldnt see my movies on smart tv's. I fiddled around and seem to have it sorted for now. I think the "fix" was to renew the library folders. Thanks again. Quote Link to comment Share on other sites More sharing options...
hcardle Posted October 23, 2020 Author Share #33 Posted October 23, 2020 Update. it has been working fine until recently. I have had it on this entire time until it started to misbehave. So I tried rebooting. That didnt work, i ended up in the boot loop again. I pulled the mains plug and rebooted and got it back ok. Then I got a message about one of the drives but i managed to recover that ok, now i am getting a partition has crashed message. Data is still there OK. So I am going to back up the data to another drive and reinstall the system using option 2 on the bootloader. I think that is the way to go. Any other advice on why it crashed or how to recover? Quote Link to comment Share on other sites More sharing options...
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.