Jump to content
XPEnology Community

gnoboot

Member
 View Profile  See their activity

  • Posts

    278

  • Joined

  • Last visited

 Content Type 

Posts posted by gnoboot

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    I have a strange problem running gnoboot-alpha-10.4 with DSM 5.0-4458 on a Gigabyte GA-H87M-HD3. Either warm or cold booting the unit, I will lose LAN connectivity while it's staring services, maybe 5 to 10 minutes after boot. Unplugging and re-inserting the ethernet cable will restore LAN access. It continues to stay up, the longest I've left it alone has been 12hrs. I can transfer files and was also able to update to DSM 5.0-4458 Update 1.

     

    dmesg or lspci?

     

    I'm having some issues with the SSD caching.

     

    Runing gnoboot 10.4 with 4458 update 1

     

    When creating a read-write SSD cache, the message "system failed to mount ssd cache ...."

     

    The following appears in /var/log/messages:

     

    Mar 30 01:20:54 SKW-SAN hotplugd: ##### ACTION:add
Mar 30 01:20:54 SKW-SAN hotplugd: DEVICE:/proc/bus/usb/000/000
Mar 30 01:20:54 SKW-SAN hotplugd: hotplugd.c:1406 Device  is not in hotplugd supported list.
Mar 30 01:22:00 SKW-SAN hotplugd: usb_get_device_id.c:56 failed get usb id Vendor=0000, ProdID=0000, SN=ffffffd0ffffffa2ffffffc3ffffffac
Mar 30 01:22:00 SKW-SAN hotplugd: hotplugd.c:990 failed get usb device id from usb config, DEVICE=/proc/bus/usb/000/000
Mar 30 01:22:00 SKW-SAN hotplugd: ##### ACTION:add
Mar 30 01:22:00 SKW-SAN hotplugd: DEVICE:/proc/bus/usb/000/000
Mar 30 01:22:00 SKW-SAN hotplugd: hotplugd.c:1406 Device  is not in hotplugd supported list.
Mar 30 01:22:51 SKW-SAN synocheckshare: synocheckshare_vol_mount.c:47 Export Share [iNTERNAL] [/dev/vg1/volume_1] [/volume1]
Mar 30 01:22:52 SKW-SAN cupsd[28626]: [conf.c:1893] Filter "pstoraster" not found.
Mar 30 01:22:59 SKW-SAN synoindex: index_index_add_ex.c:125 Indexing daemon is not running
Mar 30 01:23:18 SKW-SAN flashcachehandler.cgi: space_ssd_cache_disk_init.c:71 [iNFO] Clean all partitions of [/dev/sde]
Mar 30 01:23:18 SKW-SAN flashcachehandler.cgi: space_ssd_cache_disk_init.c:79 [iNFO] Create [/dev/sde1]
Mar 30 01:23:18 SKW-SAN flashcachehandler.cgi: space_ssd_cache_disk_init.c:71 [iNFO] Clean all partitions of [/dev/sdf]
Mar 30 01:23:18 SKW-SAN flashcachehandler.cgi: space_ssd_cache_disk_init.c:79 [iNFO] Create [/dev/sdf1]
killall: synolunbkp: no process killed
Mar 30 01:23:24 SKW-SAN hotplugd: usb_get_device_id.c:56 failed get usb id Vendor=0000, ProdID=0000, SN=ffffffd0ffffffa2ffffffc3ffffffac
Mar 30 01:23:24 SKW-SAN hotplugd: hotplugd.c:990 failed get usb device id from usb config, DEVICE=/proc/bus/usb/000/000
Mar 30 01:23:24 SKW-SAN hotplugd: ##### ACTION:add
Mar 30 01:23:24 SKW-SAN hotplugd: DEVICE:/proc/bus/usb/000/000
Mar 30 01:23:24 SKW-SAN hotplugd: hotplugd.c:1406 Device  is not in hotplugd supported list.
Mar 30 01:23:25 SKW-SAN kernel: [ 1258.355767] EXT_INFO: EXIT Extent-Pool
Mar 30 01:23:26 SKW-SAN kernel: [ 1259.026918] init: crond main process (16962) killed by TERM signal
Mar 30 01:23:30 SKW-SAN synocheckshare: synocheckshare_vol_unmount.c:147 Unmount Share [iNTERNAL] [/dev/vg1/volume_1] [/volume1]
Mar 30 01:23:31 SKW-SAN flashcachehandler.cgi: flashcache_create.c:130 failed to [/usr/syno/sbin/flashcache_create -s 57671680k -p back cachedev_0 /dev/md4 /dev/vg1/volume_1 1>/tmp/flashcache.system 2>&1], errno=No such file or directory, ret=256, WEXITSTATUS=1
Mar 30 01:23:31 SKW-SAN flashcachehandler.cgi: virtual_space_implement_op_lib.c:172 Failed to create layer on device [/dev/vg1/volume_1] of space [/dev/vg1/volume_1], ret=-1
Mar 30 01:23:31 SKW-SAN flashcachehandler.cgi: vspace_wrapper_create.c:77 failed to create virtual space on [/volume1]
Mar 30 01:23:31 SKW-SAN synocheckshare: synocheckshare_vol_mount.c:47 Export Share [iNTERNAL] [/dev/vg1/volume_1] [/volume1]
Mar 30 01:23:32 SKW-SAN cupsd[30809]: [conf.c:1893] Filter "pstoraster" not found.
Mar 30 01:23:32 SKW-SAN synorelayd: register_api_key.cpp:226 failed to send https request to [apiauth.synology.com], err=[0x2000]
Mar 30 01:23:32 SKW-SAN synorelayd[31054]: synorelayd.cpp:1221 stoped
Mar 30 01:23:32 SKW-SAN isccore: synocomm_types.c:268 szName eth0 10.2.0.4 is Active
Mar 30 01:23:32 SKW-SAN isccore: synocomm_types.c:268 szName eth0 10.2.0.4 is Active
Mar 30 01:23:32 SKW-SAN isccore: synocomm_types.c:268 szName eth1 10.3.0.4 is Active
Mar 30 01:23:32 SKW-SAN isccore: synocomm_types.c:268 szName eth2 172.16.2.1 is Active
Mar 30 01:23:33 SKW-SAN iss: synocomm_types.c:268 szName eth0 10.2.0.4 is Active
Mar 30 01:23:33 SKW-SAN iss: synocomm_types.c:268 szName eth0 10.2.0.4 is Active
Mar 30 01:23:33 SKW-SAN iss: synocomm_types.c:268 szName eth1 10.3.0.4 is Active
Mar 30 01:23:33 SKW-SAN iss: synocomm_types.c:268 szName eth2 172.16.2.1 is Active
Mar 30 01:23:33 SKW-SAN kernel: [ 1266.176294] EXT_INFO: INIT Extent-Pool
Mar 30 01:23:36 SKW-SAN flashcachehandler.cgi: flashcachehandler.cpp:238 Failed to create flashcache on /volume1 [0xEB00 servicecfg_internal_lib.c:104]
Mar 30 01:23:36 SKW-SAN kernel: [ 1269.215393] md: md4: set sdf1 to auto_remap [0]
Mar 30 01:23:36 SKW-SAN kernel: [ 1269.215394] md: md4: set sde1 to auto_remap [0]
Mar 30 01:23:36 SKW-SAN flashcachehandler.cgi: raid_remove.c:48 [info] clean RAID superblock of /dev/md4
Mar 30 01:23:37 SKW-SAN flashcachehandler.cgi: raid_clean_superblock.c:87 [info] Clean RAID superblock on '/dev/sde1'
Mar 30 01:23:37 SKW-SAN flashcachehandler.cgi: raid_clean_superblock.c:87 [info] Clean RAID superblock on '/dev/sdf1'
Mar 30 01:23:43 SKW-SAN hotplugd: usb_get_device_id.c:56 failed get usb id Vendor=0000, ProdID=0000, SN=ffffffd0ffffffa2ffffffc3ffffffac
Mar 30 01:23:43 SKW-SAN hotplugd: hotplugd.c:990 failed get usb device id from usb config, DEVICE=/proc/bus/usb/000/000
Mar 30 01:23:43 SKW-SAN hotplugd: ##### ACTION:add
Mar 30 01:23:43 SKW-SAN hotplugd: DEVICE:/proc/bus/usb/000/000
Mar 30 01:23:43 SKW-SAN hotplugd: hotplugd.c:1406 Device  is not in hotplugd supported list.
Mar 30 01:23:43 SKW-SAN hotplugd: usb_get_device_id.c:56 failed get usb id Vendor=0000, ProdID=0000, SN=ffffffd0ffffffa2ffffffc3ffffffac
Mar 30 01:23:43 SKW-SAN hotplugd: hotplugd.c:990 failed get usb device id from usb config, DEVICE=/proc/bus/usb/000/000
Mar 30 01:23:43 SKW-SAN hotplugd: ##### ACTION:add
Mar 30 01:23:43 SKW-SAN hotplugd: DEVICE:/proc/bus/usb/000/000
Mar 30 01:23:43 SKW-SAN hotplugd: hotplugd.c:1406 Device  is not in hotplugd supported list.

    [/quote

     

    Not sure, though, your SSD must be supported or listed to vendor's flash cache. I'll have dig more on your issue.

     

    @vasiliy_gr

    I'll patch 10.5 and try again. Have your tried Debian Wheezy using kernel 3.2 on this machine?

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    I'm running on bare hardware, no Esxi or the likes, how can I update from 10.3 to 10.5 without loosing what i have, thanks

    Just replace the zImage, revert as needed.

     

    Hi all, I'm back :grin:

     

    gnoboot, great work as usual. Using your latest image with the 5.0-4458 release, it's working fine so far. Only issue I have is that there's no sit0 support, and I can't initiate a tunnel through Hurricane Electric :/

     

    Is there any chance that you could compile it into the next release?

    You have to load ipv6 module, just google for it :smile:

     

    Already did so, but no luck. The sit0 device simply does not appear, nor do the commands (IP addresses redacted):

     

    ifconfig sit0 up
ifconfig sit0 inet6 tunnel ::xxx.xxx.xxx.xxx
ifconfig sit1 up
ifconfig sit1 inet6 add xxxx:xxxx:xxxx:xxxx::2/64
route -A inet6 add ::/0 dev sit1

     

    modprobe ipv6
ip tunnel add he-ipv6 mode sit remote xxx.xxx.xxx.xxx local xxx.xxx.xxx.xxx ttl 255
ip link set he-ipv6 up
ip addr add xxxx:xxxx:xxxx:xxxx::2/64 dev he-ipv6
ip route add ::/0 dev he-ipv6
ip -f inet6 addr

     

    The sit0 device simply doesn't exist, and by my knowledge it would require the sit.ko module (which is not compiled by default).

     

    Do you know the kernel config to enable?

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    @Gnoboot

    Hello Gnoboot,

    i have made a output file with ubuntu just like you asked.

    i hope you can help me with the intel centrino n-2230 wifi card.

    thanks for your time.

    gr marc

     

    04:00.0 Network controller: Intel Corporation Centrino Wireless-N 2230 (rev c4)
Subsystem: Intel Corporation Centrino Wireless-N 2230 BGN
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 	Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 48
Region 0: Memory at f7c00000 (64-bit, non-prefetchable) [size=8K]
Capabilities: 
Kernel driver in use: iwlwifi

     

    Wireless driver is already included, just load it using /etc/rc.local method.

     

    For the insmod :

    I boot normally (no change in grub) and then I open a putty session and when I do the following command

     

    I receive the error

    insmod: can't insert '/lib/modules/synoacl_ext4.ko': unknown symbol in module, or unknown parameter

    My bad, it doesn't work. Load the modules individually (i.e. insmod /lib/modules/synoacl_ext4.ko).

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    Hi all, I'm back :grin:

     

    gnoboot, great work as usual. Using your latest image with the 5.0-4458 release, it's working fine so far. Only issue I have is that there's no sit0 support, and I can't initiate a tunnel through Hurricane Electric :/

     

    Is there any chance that you could compile it into the next release?

    You have to load ipv6 module, just google for it :smile:

     

    Hello,

     

    I have downloaded your image (it is really impressive because the pat from Synology works immediately ), and I have some problems

    there is no ACL on windows (right click on a file / directory and Properties there is ne Security page).

    You say do do that

    Try to insmod GRUB option synoacl_ext4.ko and synoacl_vfs.ko in 10.4.

    I have made a insmod in a putty session but is not working.

    I don't understand the method you recommend

     

    kernel /zImage insmod=vmxnet3 <- GRUB option before you boot to DSM.

    # cat > /etc/rc.local << EOF

    #!/bin/sh

    source /etc/rc.subr

    source /.gnoboot/modules.d/99-install.conf

    source /.gnoboot/modules.d/05-media.conf

    source /.gnoboot/modules.d/04-virt.conf

    source /.gnoboot/modules.d/03-wifi.conf

    SYNOLoadModules \$MEDIA_MOD

    SYNOLoadModules \$VMWARE

    SYNOLoadModules \$HYPERV

    EOF

    # chmod 755 /etc/rc.local <- Run this command and lines above in your putty session.

     

    What must I do ?

    I add a line (before the EOF) with the insmod ?

    Doing the insmod directly doesn't work. <- If you are loading drivers from putty session. You command should be `insmod /lib/modules/synoacl*.ko`.

     

     

    Also is it possible to mount a ISCSI target from another computer with your image ?

    For example I create a ISCSI share from my own server and I mount it as normal drive for the GNOBoot? <- YES

     

    Also I can't manage to apply the last update from synology (I downlaoded the last file and installed normally but there is a Update1 file that can only be applied from inside the DSM). <- Please read the forums.

     

    Thank you for your time

    (I have clicked on every banner I was able to find on your web site).

     

    Marc

     

    Whatever the issue is, it's an ongoing thing... more entries over time. And it writes to associated files in /volume1/ each time... so it causes lots of writes.

    You are right, it writes to /volume1 and might fill up your disk. Just move the core files to another directory such as /tmp or /dev/null, http://justlearningtoblog.wordpress.com/2010/07/23/enable-core-dump-files-in-fedora/

     

    Add this line to your /etc/rc.local.

     

    sysctl -w kernel.core_pattern=/tmp/core.%p

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    As for HBA is second configuration - no problems at all. None of the hdds is missing, all numerated correctly from 1 to 8, system array is undamaged after reboot.

    Great! I'm still having issues with my vt-d HBA :sad:

     

    No, I haven't. I do not even know this option. :smile: I'll try it later when I learn what does this option mean. Anyway I do not had such a problem on 4.3 with trantor's hba build.

    It might be related to cpu_idle driver that I backported from kernel.org. Try it and let me know if it helps :grin:

     

    Sorry, I did not understand your idea about kexec-ing. :smile:

    I am using chrome. And in the situation described I saw moving around progress indicator on the dsm window for 4.5 minutes. But if I pressed reload button after smth about 1 minute from the start of reboot sequence - I instantly got into running dsm gui. Really it sounds strange but it was already running gui (without need to login). May be it is some trick from google in their chrome...

    Kexec enables you to boot another kernel w/o going thru BIOS. It's faster compared to normal reboot. You can get the SPK in my blog and try it:)

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    Try to insmod GRUB option synoacl_ext4.ko and synoacl_vfs.ko in 10.4.

     

    No, same ACL problem with insmod of the two modules. Back to 10.3 ACL handling OK. CloudSync etc working

     

    Are you using VM or baremetal? Could you boot to debug and send me /.gnoboot/debug.log?

    [SOLVED] NIC Support & Failover

    in Archives

    Posted

    Ah, ok... If you are using the 8168 driver, why don´t you list it? I can find only the "RealTek RTL-8169 Gigabit Ethernet (r8169)". The driver for this NIC is a bit diffrent because usually it is connected via PCIe while the 8168 is connected via PCI. Does this may make a difference?

     

    But if you are using this kind of driver, I would give it a try :mrgreen: What about the failover? Are both NICs recognized by the System?

     

    Greetz

    Updated the driver page in my blog. I don't think there's driver difference when using PCI vs PCIe.

     

    DSM is using Linux network bonding for NIC failover. Try it yourself or send me a network card for me to test;)

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    Hi, reverting back to 10.3 resolvs the volume ACL problem. regards Harry

    Try to insmod GRUB option synoacl_ext4.ko and synoacl_vfs.ko in 10.4.

     

    I'm seeing some weird stuff with gnoboot 10.4, which I don't think I've seen in past releases.

     

    If I boot up a VM with stock grub settings, drives will start off at slot 3 (sdc), since I didn't rmmod=ata_piix in grub yet. I create a test volume (on VM disk), all is good. Then I power down. Edit the grub to remove ata_piix, boot up and my volume is gone, but first disk in slot 1. Create volume, all good. Power down. Change grub back to stock. Power up, disk start at slot 3, and volume still intact - all good. Power down. Change grub again to remove ata_piix, power up. Volume gone again...

     

    So it seems if the volume is created, and the disk move up slots, it's okay. But if they move back, then volume goes poof. I'm not sure if the issue is DSM 5 (official) or gnoboot 10.4, but I've never seen a volume disappear after removing ata_piix before. When I say disappear, I mean disk there, but volume data lost in DSM.

     

    edit: rebooted VM with volume in MIA state, and on reboot it showed crashed this time.

     

    edit2: maybe this is related to the note about mpt2sas. "Disks are not properly initialize when using mpt2sas driver and VT-d during first boot of ESXi host, reboot VM until HBA is detected". I'm not using my HBA in this test VM, but maybe it has similar problem and when the volume was MIA (missing, but not marked as crashed yet), it was because disk wasn't properly initialized :?:

     

    I've seen this several times before, but it's on a iSCSI file backend. You have to delete the LUN to make it work again. I think this has something to do with improper shutdown (multiple "reboot -f") or a patch that I included while working on mpt2sas issue which didn't help. I will build another kernel w/o that patch for you to play. :grin:

     

    Hi!

     

    Checked the 10.4 version with two completely different configurations: N54L + 2GB + 6hdds and i5 + 4GB + lsi 9211 + 8hdds. Both with 5.0-4458 dsm. The first problem found is a boot time (from reboot confirmation button press in gui and up to login screen in browser). It takes something above 4.5 minutes to complete this process. During the first minute the progress is visible: bios, sas/sata data, grub, kernel, modules... But the other 3.5 minutes it simply shows "Post init" message and login prompt on local console and "Starting services" in SA. <- DSM is running scripts in /usr/syno/etc/rc.d and /usr/syno/cfgen. If you're using iSCSI this also adds more delay. Did you experience a missing device (e.g. sdaX) during fresh boot of your HBA?

     

    Ok, lets look on dmesg in this time position. First configuration:

    [spoiler=][ 34.694436] ata6.00: configured for UDMA/133

    [ 34.694440] ata6: EH complete

    [ 36.047627] loop: module loaded

    [ 36.066011] bond0: no IPv6 routers present

    [ 219.274928] findhostd uses obsolete (PF_INET,SOCK_PACKET)

    [ 227.490571] dsmnotify.cgi[22338]: segfault at 0 ip 000000000804ccb8 sp 00000000ffcdd3f0 error 6

    [ 227.570891] storagehandler.[22339]: segfault at 0 ip 000000000809e298 sp 00000000ffa00850 error 6

     

    Second configuration:

    [spoiler=][ 23.642702] netlink: 12 bytes leftover after parsing attributes.

    [ 25.971033] EXT4-fs (sdu1): mounted filesystem without journal. Opts: nodelalloc,synoacl,data=ordered,oldalloc

    [ 26.970741] init: synoindexd main process (19890) killed by USR2 signal

    [ 26.970756] init: synoindexd main process ended, respawning

    [ 27.639291] loop: module loaded

    [ 31.240239] eth0: no IPv6 routers present

    [ 64.841983] findhostd uses obsolete (PF_INET,SOCK_PACKET)

    [ 217.709290] dsmnotify.cgi[24394]: segfault at 0 ip 000000000804ccb8 sp 00000000ffe1d100 error 6

    [ 217.754241] storagehandler.[24395]: segfault at 0 ip 000000000809e298 sp 00000000ffd5c8e0 error 6

     

    Some incompatibility with 4458 version?.. <- yes, dsgpl-4.3 kernel

    Moreover here is dmesg output after some time without any activity from my side. First:

    [spoiler=][ 258.145105] dsmnotify.cgi[22624]: segfault at 0 ip 000000000804ccb8 sp 00000000ff85ff60 error 6

    [ 288.606194] dsmnotify.cgi[22698]: segfault at 0 ip 000000000804ccb8 sp 00000000ffcfca90 error 6

    [ 319.265492] dsmnotify.cgi[22837]: segfault at 0 ip 000000000804ccb8 sp 00000000ff8319f0 error 6

    [ 351.257970] dsmnotify.cgi[22896]: segfault at 0 ip 000000000804ccb8 sp 00000000ffa0c170 error 6

    [ 383.259143] dsmnotify.cgi[23025]: segfault at 0 ip 000000000804ccb8 sp 00000000ffa95490 error 6

    [ 415.260392] dsmnotify.cgi[23079]: segfault at 0 ip 000000000804ccb8 sp 00000000ff969d10 error 6

    [ 447.259978] dsmnotify.cgi[23209]: segfault at 0 ip 000000000804ccb8 sp 00000000fff31ab0 error 6

    [ 478.265114] dsmnotify.cgi[23269]: segfault at 0 ip 000000000804ccb8 sp 00000000ffac5330 error 6

    [ 509.262446] dsmnotify.cgi[23397]: segfault at 0 ip 000000000804ccb8 sp 00000000ff949830 error 6

    [ 540.263957] dsmnotify.cgi[23450]: segfault at 0 ip 000000000804ccb8 sp 00000000ff886d70 error 6

    [ 573.263792] dsmnotify.cgi[23580]: segfault at 0 ip 000000000804ccb8 sp 00000000ffec8220 error 6

    [ 604.296849] dsmnotify.cgi[23640]: segfault at 0 ip 000000000804ccb8 sp 00000000ffe0c970 error 6

    [ 636.265761] dsmnotify.cgi[23768]: segfault at 0 ip 000000000804ccb8 sp 00000000fff98a80 error 6

    [ 668.266895] dsmnotify.cgi[23821]: segfault at 0 ip 000000000804ccb8 sp 00000000ffb42670 error 6

    [ 700.267653] dsmnotify.cgi[23951]: segfault at 0 ip 000000000804ccb8 sp 00000000ff82af70 error 6

    [ 731.275980] dsmnotify.cgi[24012]: segfault at 0 ip 000000000804ccb8 sp 00000000ffb08ab0 error 6

    [ 763.286462] dsmnotify.cgi[24141]: segfault at 0 ip 000000000804ccb8 sp 00000000ffc1ca20 error 6

    And so on every 31 or 32 seconds while dsm gui is opened.

     

    The second configuration (dsm was closed and then opened again in half an hour):

    [spoiler=][ 281.254090] dsmnotify.cgi[24913]: segfault at 0 ip 000000000804ccb8 sp 00000000ff9324b0 error 6

    [ 281.258375] dsmnotify.cgi[24914]: segfault at 0 ip 000000000804ccb8 sp 00000000ffa0abc0 error 6

    [ 281.362402] dsmnotify.cgi[24916]: segfault at 0 ip 000000000804ccb8 sp 00000000ffd44720 error 6

    [ 337.758887] irq 16: nobody cared (try booting with the "irqpoll" option)

    [ 337.758890] Pid: 0, comm: swapper/0 Tainted: P O 3.2.40 #6

    [ 337.758891] Call Trace:

    [ 337.758892] [] ? add_interrupt_randomness+0x39/0x157

    [ 337.758900] [] ? __report_bad_irq+0x2c/0xb4

    [ 337.758902] [] ? note_interrupt+0x15d/0x1b7

    [ 337.758904] [] ? handle_irq_event_percpu+0xfa/0x117

    [ 337.758906] [] ? handle_irq_event+0x48/0x70

    [ 337.758908] [] ? handle_fasteoi_irq+0x74/0xae

    [ 337.758910] [] ? handle_irq+0x87/0x90

    [ 337.758912] [] ? do_IRQ+0x48/0x9f

    [ 337.758915] [] ? common_interrupt+0x6e/0x6e

    [ 337.758915] [] ? lapic_next_event+0x10/0x15

    [ 337.758920] [] ? IO_APIC_get_PCI_irq_vector+0x1c7/0x1c7

    [ 337.758923] [] ? intel_idle+0xd6/0x10c

    [ 337.758924] [] ? intel_idle+0xb6/0x10c

    [ 337.758927] [] ? cpuidle_idle_call+0x6d/0xb4

    [ 337.758929] [] ? cpu_idle+0x60/0x8c

    [ 337.758932] [] ? start_kernel+0x327/0x333

    [ 337.758935] [] ? early_idt_handlers+0x140/0x140

    [ 337.758937] [] ? x86_64_start_kernel+0x10b/0x118

    [ 337.758938] handlers:

    [ 337.758948] [] usb_hcd_irq

    [ 337.758950] Disabling IRQ #16

    [ 2208.023057] dsmnotify.cgi[25225]: segfault at 0 ip 000000000804ccb8 sp 00000000ffc54850 error 6

    [ 2208.073520] storagehandler.[25226]: segfault at 0 ip 000000000809e298 sp 00000000ffa17f00 error 6

    [ 2238.800620] dsmnotify.cgi[25640]: segfault at 0 ip 000000000804ccb8 sp 00000000ff832cb0 error 6

    [ 2269.391056] dsmnotify.cgi[25729]: segfault at 0 ip 000000000804ccb8 sp 00000000ffb5e2c0 error 6

    Here we see the same problem with dsmnotify.cgi while dsm is opened and some strange problem with irq. <- I'll try to find a patch/workaround for this traceback. Have you tried adding "irqpoll" boot option in GRUB?

    Also I tried to reboot with dsm web-gui closed. The same result in dmesg (dsmnotify.cgi and storagehandler segfault) and the same time according to SA. But if I manually refresh/reload browser page with dsm after 1 minute of reboot process (when I see local login prompt) - it shows dsm gui already up and running. <- You can't even close Firefox tab while DSM v5 is rebooting. Kexec-ing, maybe??? :lol:

     

    The last thought on this problem... The same delay for 3.5 minutes was also on reboot during installation. So it may exceed installation timeout with some configurations and will lead to installation error. May be it is a reason for installation problems with 4458 already reported. But I think that in this case it is necessary to repeat installation with SA (without rebooting) to make it possible for SA to configure already installed dsm. <- I've also noticed this behavior in 10.4, but I always cancel the installation once DSM is installed and manually configure it again. This saves time (5-10mins) rather than waiting for it to complete the installation.

     

    I have a quick question, how do I upgrade from gnoBoot Alpha 10.3 to 10.4 or future releases?

    I have my DSM 5 with gnoBoot 10.3 up and running and would like to do future upgrades without loosing my current configuration.

     

    Thanks a lot in advance!

     

    Zeek

    Just replace the zImage or use to kexec-tools to try out the new release and reboot if doesn't work.

     

    I replaced 10.4 zImage file from previous 10.3 vmdk using OSFMount+StarWind V2V.

     

    My previous 10.3 issues still exists:

    1. vSphere Client shows VMware Tools running but not installed (!). No IP address shown too. <- VM tools is compiled with minimal features.

    2. Video Station stream mkv but failed to transcode. Original playback quality works though. Won't fix any DSM related issue.

     

    My setup: ESXi on DC7900 / Q6600

     

    I have successfully installed gnoboot with DSM 5, thanks for that really great.

    but my wifi (intel centrino N-2230) does not work.

    is there anyone who can post a how to add these drivers(or other) to gnoboot?

    would be great.

    marc

     

    I can add your wifi, but you need to provide `lspci -vvv` result from a LInux box.

    N36L network speed

    in Archives

    Posted

    yeah, try the latest release. I doubt it would fix your network problem.

     

    I have another command that I'd like you try and post the results. Have you also tried changing the cables or restart the switch?

    > ethtool eth0

    N36L network speed

    in Archives

    Posted

    Edit GRUB before you boot to your NAS, you can do this by pressing E at the 2nd boot menu under kernel line. Make the following changes:

     

    kernel /zImage debug

     

    Once it booted up, you can send me /.gnoboot/debug.log.

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    Just use rmmod GRUB option to disable your 82574L chip.

     

    kernel /zImage rmmod=e1000e_new,e1000e

     

    But I think that would not even solve your problem.

     

    Changelog for igb 5.1.2

    * Change how driver update rx packet stats, to include additional packet types.

    * Add support for freeing q_vectors via RCU.

    * Change how PBA is reported when using flashless i210/i211.

    * Fixes to improve load performance for flashless i210 devices.

    * Add get/set_channels function for queue management via ethtool.

    * Update the number of tries for copper link in Media Auto Sense feature due to behavior with no cables.

    * Add function to output RSS table via ethtool. * Sync some RSS changes from upstream.

    * Fix for WOL issues found on some kernel versions.

    * Fix for PHY config issue found when changing PHY settings after init on some i354 platforms.

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    I'm running gnoboot 10.3 on bare hardware and having horrible transfer speeds, the motherboard I'm using has a quad i210 nic on board with the latest version of xeon cpu and 16gb ram, 8 3tb WD Red, as suggested I tried removing the e1000 module, i did this by ssh into the box and trying rmmod e1000.ko however i get the following error

     

    rmmod: can't unload 'e1000': unknown symbol in module, or unknown parameter

     

    any suggestions?

     

    thanks

    I'm still waiting for the next IGB driver release. I can't compile the latest version because of BUG#396.

    XPEnology gnoBoot

    in DSM 5.2 and earlier (Legacy)

    Posted

    QUESTION: Can't synodisk be patched to work like smartctl does?

     

    Anything related to DSM, won't fix. It's closed source.

     

    Update on XenServer Paravirtualization

     

    I tried to run gnoboot using XenServer PV (pygrub), however getting error in Xen console when starting VM:

    Internal error: xenopsd internal error: XenguestHelper.Xenctrl_dom_linux_build_failure(2, " panic: xc_dom_core.c:616: xc_dom_find_loader: no loader\\\"")

     

    Which i found is result of XenServer having pygrub compiled WITHOUT LZMA/XS support for kernel compression (which holds for last XenServer release http://discussions.citrix.com/topic/330 ... z-support/)

     

    gnoBoot what compression are you using? (I could not find it using `file zImage`)

     

    Anyway in XenServer 6.2.5 (beta) LZMA/XS is supported so if that is reason why it is not working then i would wait for XenServer 6.2.5 stable release (https://xen-orchestra.com/testing-xenserver-6-2-5-beta/).

     

    Thanks

     

    I'm using LZMA, will switch to GZIP next release.

     

    im having this strange problem since updating to 5.0 from the beta...

     

    I always had UPNP enabled in my router, but since the update this function criples my lan.. Every once in a while the network hangs for 2s, if i dissconnect the xpenology-box or disable upnp in the router everything is fine and as soon as i put it back on with upnp enabled in router the lan acts up...

    I have tried with a different cable but thats not it.

     

    Anyone got a clue on this?

     

    /etc/rc.network is very different from 5.0-4418 to 5.0-4458 that might be the problem. Trying replacing the file using older version.

×
×
  • Create New...