rikadoo

If you`ve made an xpenology bootstick you can change the SN and Mac adres, you can use your serial and mac from the DS413j but then you cant use the quickconnect from the DS413j . The rest of the info can you find on google, or this forum.

Stoarge manegr and overview can you repair paritition? and can you make a smart dump?

Yes, but only with a clean install! Not with an upgrade, after that the DSM webpage is not reachable! @ error, that`s right, i got the same faultcode.

The DSM 6.0 Beta is out! https://www.synology.com/nl-nl/dsm/6.0beta/ReleaseNote Testing it right now on Hyper-V Tried to update from 5.2 with latest XPenoboot, it says update ok but can`t acces the DSM page. Now i tried a Clean install en now it works, but volumes are unmounted.

excellent maybe next release of xpenology could bring us a fix The best is probably a XPenoboot boot based on the new Synology product RS18016xs+ We will see i hope the developers of xpenoboot will make btrfs workable for use at xpenology NAS systems.

When i look at the snapshot menu from a youtube movie there has to be a shared folder next to ISCSI LUN snapshot. Maybe when you make an btrfs raid partition you can see the extra at the data protection manager. Well i give up, i hope the next XPenology version is the bootloader from an RC18015xs, then btrfs will work i`m sure of that

I just tested it in Hyper-v so no problems for me if the installation doesn`t work anymore. But i can`t find cemd, it is not in the path you`ve given me. Also i attach a screen of the snapshot menu.

Where can i find cemd? I want to replace it in my virtualbox installation. You can find Snapshots in Menu --> Data Protection Manager

I tested it with adding support_dr_snap="yes", i get the new snapshot management. Only problem i got is that my volume with btrfs is crashing, can`t make an raid configuration. (this is with hyper-v)

the 2 files from 5.1 en 5.2 beta are both the same. I don`t know if that makes any sence?

Also got the same problem over here i just tested in Virtualbox en also got an IP, but when i go to the addres in the webbrowser it can`t find the NAS, also DSM Assistant don`t find the NAS.

It looks like the same problemen i got. Couldn expand raid shr volume. I tried another bootimage. When i used the new bootimage tot USB it expanded and works perfectly. This is the topic. Further in it there is a link tot an fixed bootimage. Try that ons. viewtopic.php?f=2&t=5233

Also got a problem here with SHR raid 5, added 2 disks to 1 volume SHR (3TB), after a few hours 1 disk was ready and the volume has 1 disk fault tolerance. But the 3th disk rebuild was about 1.5 days. After 100% i couldn`t expand the volume to max. I used the test version and a few seconds later max volume. 3x 3TB (5TB affective). I also used the new version XPEnoboot 5.1-5022.2 from XPenology.nl but this one doesn`t work to expand SHR. Can i use the test version?

i also downloaded the iso from xpenology.nl but i can`t get the iso booting... But when it does i think you have to choose upgrade in the menu and then update from the webpage

Yes this works, thank you! But has this anything to do with the messages i get in the logs?

It says that i have the latest update. Update 5. Youre version is up to date.

Hello, i have a homebuild NAS PC with XPenology the latest version DSM 5.0 update 5. Everything works perfect but i have in the menu on the webpage a 1. It saids it needs an update or something, has anyone else the same? And what can i do about this? Has this anything to do with this in the messages.log:

I dont have a HP system, i have a homebuild system wit an Pentium en MSI motherboard. i have no idee what the problem is.

Not yet... Hmm thats not the problem i got then. My drives get in hibernation, but i think once in an hour it get out of hibernate itself....

Well the hibernate issues without the usb didn`t solve. I did run the hibernate debug tool on the background with Putty open. When the NAS is waking up i get this: Sep 2 19:16:49 NAS-PC kernel: [10067.545123] [/.htaccess] opened by pid 21926 [u:(/usr/bin/httpd), comm:(httpd)] Sep 2 19:16:54 NAS-PC kernel: [10072.821836] sd 0:0:0:0: sda: cmd run - tag ff - 28 00 00 4b ff 80, pid:11108, comm:kworker/1:2 Sep 2 19:16:54 NAS-PC kernel: [10072.821865] sd 1:0:0:0: sdb: cmd run - tag ff - 28 00 00 4b ff 80, pid:11108, comm:kworker/1:2 Sep 2 19:16:54 NAS-PC kernel: [10072.821882] sd 2:0:0:0: sdc: cmd run - tag ff - 28 00 00 4b ff 80, pid:11108, comm:kworker/1:2 Sep 2 19:20:06 NAS-PC kernel: [10264.844034] [/etc/passwd] opened by pid 28835 [u:(-ash), comm:(ash)] I did not opend the webpage or anything else i am only running Putty.

Thnx for the topic, i will try and see if anything happens. You are right, update 4

Nobody who can help me?

Hello, i`m new here. I`m from the netherlands and i`m using XPenology for about a few months. I`m very happy with it and everything works fine. But there is 1 thing what isnt working well, hibernate. This is my system: Intel Pentium G3420 Boxed MSI H97M-G43 3x Seagate Barracuda 7200.14 ST3000DM001, 3TB Cooler Master N400 KKN1 Crucial Ballistix BLS2CP4G3D1609DS1S00CEUv 2x4GB Seasonic G-Serie 360Watt Crucial M550 M.2 128GB Mine problem is my NAs gets into hibernate but every 10 minutes is goes off hibernate. I also have this with al the packages diabled, so its not sickbeard of plex whats running on the back. I have a small log and it saids this: This is the log from today. Aug 25 16:12:41 NAS-PC scemd: modules/disk_hibernation.c:2068 Force hibernation enable, idle minutes 10 Aug 25 16:12:41 NAS-PC scemd: modules/disk_hibernation.c:2098 Eunit Deep sleep timer 0 Aug 25 16:12:46 NAS-PC scemd: scemd.c:173 fan_type=9, raid_type=1, led_type=3, thermal_type=2, diskled_ctrl_type=1, auto_poweron_type=1, dual_power_type=1, usbcopy_type=2, fan_number=2, eunit_pwron_type=2, pis_type=0, rtc_type=3, lcm_type=2, wifi_wps_type=254 Aug 25 16:12:46 NAS-PC scemd: write to uart2 error, error=(5)Input/output error Aug 25 16:12:47 NAS-PC scemd: modules/fan_speed_adjust_common.c:116 Type: INTERNAL Fan Mode: HIGH Aug 25 16:12:48 NAS-PC scemd: modules/fan_check_common.c:449 can't read data. Aug 25 16:12:48 NAS-PC scemd: modules/fan_check_common.c:513 can't get ttyS1 data. Aug 25 16:12:48 NAS-PC scemd: modules/raid_sys_volume_check.c:144 MD0 active disks 4, designed disks 12 Aug 25 16:12:48 NAS-PC scemd: modules/raid_sys_volume_check.c:144 MD1 active disks 4, designed disks 12 Aug 25 16:12:49 NAS-PC scemd: modules/scemd_connector.c:103 scemd connector thread start. Aug 25 16:12:49 NAS-PC scemd: enclosure_list_enum.c:43 SYNOEnclosureExpanderEnum() failed. [0x0D00] Aug 25 16:12:49 NAS-PC scemd: enclosure_enum_by_valid_link.c:589 Fail to SYNOEnclosureListEnum(). Aug 25 16:12:49 NAS-PC scemd: net_wol_enable.c:176 Failed to disable wake-on-lan power Aug 25 16:12:49 NAS-PC scemd: net_wol_enable.c:220 Fail to setup WOL power. Aug 25 16:12:49 NAS-PC scemd: modules/net.c:222 failed to disable WOL. Interface [eth0] Aug 25 16:12:49 NAS-PC scemd: net_wol_enable.c:176 Failed to disable wake-on-lan power Aug 25 16:12:49 NAS-PC scemd: net_wol_enable.c:220 Fail to setup WOL power. Aug 25 16:12:49 NAS-PC scemd: modules/net.c:222 failed to disable WOL. Interface [eth1] Aug 25 16:12:49 NAS-PC scemd: net_wol_enable.c:176 Failed to disable wake-on-lan power Aug 25 16:12:49 NAS-PC scemd: net_wol_enable.c:220 Fail to setup WOL power. Aug 25 16:12:49 NAS-PC scemd: modules/net.c:222 failed to disable WOL. Interface [eth2] Aug 25 16:12:49 NAS-PC scemd: net_wol_enable.c:176 Failed to disable wake-on-lan power Aug 25 16:12:49 NAS-PC scemd: net_wol_enable.c:220 Fail to setup WOL power. Aug 25 16:12:49 NAS-PC scemd: modules/net.c:222 failed to disable WOL. Interface [eth3] Aug 25 16:12:49 NAS-PC scemd: scemd.c:173 fan_type=9, raid_type=1, led_type=3, thermal_type=2, diskled_ctrl_type=1, auto_poweron_type=1, dual_power_type=1, usbcopy_type=2, fan_number=2, eunit_pwron_type=2, pis_type=0, rtc_type=3, lcm_type=2, wifi_wps_type=254 Aug 25 16:12:49 NAS-PC scemd: scemd.c:394 WIFI/WPS button is not support on this model. Aug 25 16:13:02 NAS-PC scemd: write to uart2 error, error=(5)Input/output error Aug 25 16:13:02 NAS-PC scemd: modules/service.c:178 SCEMD: Failed to put the SysRun light up. Aug 25 16:13:03 NAS-PC scemd: write to uart2 error, error=(5)Input/output error Aug 25 16:13:03 NAS-PC scemd: modules/flashcache_volume_check.c:996 Initialize the last check time for flashcache Aug 25 16:13:03 NAS-PC scemd: write to uart2 error, error=(5)Input/output error Aug 25 16:14:49 NAS-PC scemd: scemd.c:451 stop manutild. Aug 25 16:54:08 NAS-PC scemd: modules/disk_hibernation.c:2338 The internal disks wake up from hibernation. Aug 25 16:54:26 NAS-PC scemd: write to uart2 error, error=(5)Input/output error Aug 25 17:16:05 NAS-PC scemd: modules/disk_hibernation.c:2338 The internal disks wake up from hibernation. Aug 25 17:16:12 NAS-PC scemd: write to uart2 error, error=(5)Input/output error Aug 25 17:34:09 NAS-PC scemd: modules/disk_hibernation.c:2338 The internal disks wake up from hibernation. Aug 25 17:34:21 NAS-PC scemd: write to uart2 error, error=(5)Input/output error Aug 25 18:04:03 NAS-PC scemd: modules/disk_hibernation.c:2338 The internal disks wake up from hibernation. Aug 25 18:04:10 NAS-PC scemd: write to uart2 error, error=(5)Input/output error Aug 25 18:38:15 NAS-PC scemd: modules/disk_hibernation.c:2338 The internal disks wake up from hibernation. Aug 25 18:38:16 NAS-PC scemd: write to uart2 error, error=(5)Input/output error Aug 25 18:54:15 NAS-PC scemd: modules/disk_hibernation.c:2338 The internal disks wake up from hibernation. Aug 25 18:54:17 NAS-PC scemd: write to uart2 error, error=(5)Input/output error Aug 25 19:29:30 NAS-PC scemd: modules/disk_hibernation.c:2338 The internal disks wake up from hibernation. Aug 25 19:29:40 NAS-PC scemd: write to uart2 error, error=(5)Input/output error Aug 25 20:14:11 NAS-PC scemd: modules/disk_hibernation.c:2338 The internal disks wake up from hibernation. Aug 25 20:14:21 NAS-PC scemd: write to uart2 error, error=(5)Input/output error Aug 25 20:18:22 NAS-PC scemd: modules/disk_hibernation.c:2602 The USB disk 1 wake up from hibernation. As you can see the problem looks for me this: write to uart2 error, error=(5)Input/output error I dont know what it is, maybe someone here knows what to do? If there are more logs needed tell me which one and i will post it.