Polanskiman

tape: sudo lsblk -o NAME,FSTYPE,SIZE,MOUNTPOINT,LABEL,STATE,MODEL Et envoi le résultat. On verra à partir de là.

Est il possible d'ecrire quelque chose apres la derniere ligne qui dit "expected argument"? Je conseil de booter sur un live cd (usb) ubuntu et tenter un fsck comme indiqué dans l'image que tu as attaché.

C'est la même personne. Double post.

Ta solution: http://forum.synology.com/enu/viewtopic ... 24#p329110

Supposedly there is. Still in development.

Il ne peut pas telneter d'apres ses dires. Par contre je ne comprends pas pourquoi il ne peut pas faire de hard reset.

Cela ressemble a une corruption d'un fichier systme. Pour commencer tu peux essayer de formater ta clef usb et reinstaller xpenoboot sur la clef usb. Mais a priori cela semble plutot etre lié au disque dur. Essaye pour commencer avec la clef usb et tiens nous au courant. Sent from my iPhone using Tapatalk

Reset du système me semble la solution la plus appropriée et a priori tu ne perdras pas tes données. Simple, rapide, efficace.

L'intérêt étant?

Good to know your problem is solved. Sent from my iPhone using Tapatalk

Was initially going to say the same thing then I thought this would have been the 1st thing you tried. Assumptions...mother of..! Sent from my iPhone using Tapatalk

Read below:

As a test I would recommend trying to burn a ubuntu live cd on your flash drive and see if it boots. If not then it's either your hardware or a configuration problem within your bios. Could also be that the xpenoboot file got corrupted somehow. Sent from my iPhone using Tapatalk

Strange. Your Bios is configured properly to boot from a usb key? Modification of the syslinux.cfg file is normally only needed to change the serial and mac addresses but which will not prevent booting DSM if not edited. Sent from my iPhone using Tapatalk

Cette fonctionalité n'est pas encore implémenté dans Xpenology ou du moins ne marche plus trop bien dans la derniere version. C'est une question de module. La revision est en cours et devrait voir le jour possiblement dans la prochaine mise à jour du boot loader d'Xpenology. Pour Ref:

Your built in wifi and bluetooth are working? Sent from my iPhone using Tapatalk

Updates are incremental. You can install update 2 without installing the 1st one. Personally though I always stay one or two updates behind (unless the updates are severe issues being addressed) even with my genuine Synology and even more so with Xpenology for obvious reasons. With Xpenology you can update within the UI BUT I would recommend you do it manually, that is, downloading the .pat file outside of the UI from synology's website and then uploading it manually to your Xpenology within the UI. Sent from my iPhone using Tapatalk

Good to see your problem is solved. Sent from my iPhone using Tapatalk

Good news. Sent from my iPhone using Tapatalk

Setup a custom DDNS. Simple, fast and free. Sent from my iPhone using Tapatalk

Did you check the hardware supported list: viewtopic.php?t=10973 Sent from my iPhone using Tapatalk

You better ask this question directly to Trantor.

Not sure what your issue is but if I was you I would first start by burning your bootloader again on your usb stick to make sure the problem is not on that side. I doubt it though. After and If possible I would also reinstall DSM and use one Hard drive to start with and see if you have the same problem. Then add each drive at a time and reboot each time. To me it looks like a permission related problem where it gets reset after a shutdown. If anyone has a better explantion please correct me.

Got your new mobo?

Make sure your bios is configured correctly and that if you scheduled a shutdown prior a boot make sure it has enough time to shutdown completly. But as said above some Bios are not fully compatible with this feature. Try updating your bios if the above doesn't solve the problem. Sent from my iPhone using Tapatalk