gnoboot

XPEnology gnoBoot

Recommended Posts

Hi, after updating to gnoboot-alpha10.4 i have a problem with existing shares on the volume. New shares are OK. regards Harry

Share this post


Link to post
Share on other sites

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 :?:

Share this post


Link to post
Share on other sites
@cooledspirit and anyone running dsm 5

 

when you say : "I installed gnoBoot alpha 10.4 with DSM 5"

 

Do you mean the beta or the release.... I'm asking because I can't seem to get 4458 release to install.

 

I installed the regular DSM 5.0 4458. I did upgrade from 4.3 to 5.0 beta (Trantor release) first though. I afterwards switched to GNOboot and besides that one particularity it appears to be working nicely.

Share this post


Link to post
Share on other sites

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.

 

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?..

 

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.

 

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.

 

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.

Share this post


Link to post
Share on other sites

Ok., got 4458 to install,

 

had to reboot and select gnoboot.me and start the 4458 version, uploaded the official 4458 pat and it's working (In vmware)

 

Happy to have this, I can now do some testing (with snapshots) and not mess up my 1812+

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites
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

 

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. Attempted to reinstall vmtool spk but same result.

2. Video Station stream mkv but failed to transcode. Original playback quality works though.

 

My setup: ESXi on DC7900 / Q6600

Edited by Guest

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

Thanks for your quick reply your doing great work, do you mean i have to boot from a live cd to provide you with the information i get from the command `lspci -vvv`?

Share this post


Link to post
Share on other sites
Thanks for your quick reply your doing great work, do you mean i have to boot from a live cd to provide you with the information i get from the command `lspci -vvv`?

yes, your wifi should be connected.

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites
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?

Share this post


Link to post
Share on other sites
Hi, im on ESX 5.1. Yes, can switch back to 10.4 and create a debug log.

And lsmod from both versions. Thanks!

Share this post


Link to post
Share on other sites
Hi, im on ESX 5.1. Yes, can switch back to 10.4 and create a debug log.

And lsmod from both versions. Thanks!

 

Yep, how can i transfer the files. PM message size is to short.

Share this post


Link to post
Share on other sites

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?

I do not use ISCSI on those two configurations. Anyway the delay problem seems to be not a real delay but some notification problem between dsm and its web-gui.

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.

A little problem occured: I lost my nfs access configuration on exported folders. So I had to repair it manually. But I believe that it is a problem of upgrade from 4.3 to 5.0 dsm version.

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?

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.

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:

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...

Share this post


Link to post
Share on other sites

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:)

Share this post


Link to post
Share on other sites

Update for Xen Paravirtualization

 

Hi 10.4-vfat is recognized by XenServer 6.2SP1 in PV mode (pygrub) as bootable however during booting it get stuck after "Re-scanning disks". (Tried 10.4-ext2 but no luck)

 

21dqv0y.png

 

I am booting with these arguments: "root=/dev/md0 console=hvc0 sn=... debug=true", perhaps root=?? is wrong?

 

Any idea what to try next?

 

 

Console output with debug=true

[    0.000000] Linux version 3.2.40 (root@gnoboot) (gcc version 4.2.0) #6 SMP Sat Mar 22 14:41:23 CST 2014
[    0.000000] Command line:  root=/dev/md0 console=hvc0 sn=... debug=true
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] ACPI in unprivileged domain disabled
[    0.000000] Released 0 pages of unused memory
[    0.000000] Set 0 page(s) to 1-1 mapping
[    0.000000] BIOS-provided physical RAM map:
[    0.000000]  Xen: 0000000000000000 - 00000000000a0000 (usable)
[    0.000000]  Xen: 00000000000a0000 - 0000000000100000 (reserved)
[    0.000000]  Xen: 0000000000100000 - 0000000020000000 (usable)
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] DMI not present or invalid.
[    0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[    0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
[    0.000000] No AGP bridge found
[    0.000000] last_pfn = 0x20000 max_arch_pfn = 0x400000000
[    0.000000] initial memory mapped : 0 - 027e7000
[    0.000000] Base memory trampoline at [ffff88000009b000] 9b000 size 20480
[    0.000000] init_memory_mapping: 0000000000000000-0000000020000000
[    0.000000]  0000000000 - 0020000000 page 4k
[    0.000000] kernel direct mapping tables up to 20000000 @ 26e5000-27e7000
[    0.000000] xen: setting RW the range 27cb000 - 27e7000
[    0.000000] Zone PFN ranges:
[    0.000000]   DMA      0x00000010 -> 0x00001000
[    0.000000]   DMA32    0x00001000 -> 0x00100000
[    0.000000]   Normal   empty
[    0.000000] Movable zone start PFN for each node
[    0.000000] early_node_map[2] active PFN ranges
[    0.000000]     0: 0x00000010 -> 0x000000a0
[    0.000000]     0: 0x00000100 -> 0x00020000
[    0.000000] On node 0 totalpages: 130960
[    0.000000]   DMA zone: 56 pages used for memmap
[    0.000000]   DMA zone: 5 pages reserved
[    0.000000]   DMA zone: 3923 pages, LIFO batch:0
[    0.000000]   DMA32 zone: 1736 pages used for memmap
[    0.000000]   DMA32 zone: 125240 pages, LIFO batch:31
[    0.000000] SMP: Allowing 2 CPUs, 0 hotplug CPUs
[    0.000000] No local APIC present
[    0.000000] APIC: disable apic facility
[    0.000000] APIC: switched to apic NOOP
[    0.000000] nr_irqs_gsi: 16
[    0.000000] PM: Registered nosave memory: 00000000000a0000 - 0000000000100000
[    0.000000] Allocating PCI resources starting at 20000000 (gap: 20000000:e0000000)
[    0.000000] Booting paravirtualized kernel on Xen
[    0.000000] Xen version: 4.1.5 (preserve-AD)
[    0.000000] setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:2 nr_node_ids:1
[    0.000000] PERCPU: Embedded 26 pages/cpu @ffff88001fc00000 s75776 r8192 d22528 u1048576
[    0.000000] pcpu-alloc: s75776 r8192 d22528 u1048576 alloc=1*2097152
[    0.000000] pcpu-alloc: [0] 0 1 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 129163
[    0.000000] Kernel command line: root=/dev/md0 ihd_num=1 netif_num=4 syno_hw_version=DS3612xs  root=/dev/md0 console=hvc0 sn=... debug=true
[    0.000000] Internal HD num: 1
[    0.000000] Internal netif num: 4
[    0.000000] Synology Hardware Version: DS3612xs-j
[    0.000000] Serial Number: ...
[    0.000000] PID hash table entries: 2048 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
[    0.000000] Checking aperture...
[    0.000000] No AGP bridge found
[    0.000000] Memory: 490052k/524288k available (3541k kernel code, 448k absent, 33788k reserved, 2920k data, 15192k init)
[    0.000000] Hierarchical RCU implementation.
[    0.000000] CONFIG_RCU_FANOUT set to non-default value of 32
[    0.000000] RCU dyntick-idle grace-period acceleration is enabled.
[    0.000000] NR_IRQS:4352 nr_irqs:288 16
[    0.000000] Console: colour dummy device 80x25
[    0.000000] console [tty0] enabled
[    0.000000] console [hvc0] enabled
[    0.000000] Xen: using vcpuop timer interface
[    0.000000] installing Xen timer for CPU 0
[    0.000000] Detected 1995.067 MHz processor.
[    0.000999] Calibrating delay loop (skipped), value calculated using timer frequency.. 3990.13 BogoMIPS (lpj=1995067)
[    0.000999] pid_max: default: 32768 minimum: 301
[    0.000999] Mount-cache hash table entries: 256
[    0.000999] CPU: Physical Processor ID: 0
[    0.000999] CPU: Processor Core ID: 0
[    0.000999] SMP alternatives: switching to UP code
[    0.030165] cpu 0 spinlock event irq 17
[    0.030207] Performance Events: unsupported p6 CPU model 15 no PMU driver, software events only.
[    0.030439] installing Xen timer for CPU 1
[    0.030459] cpu 1 spinlock event irq 23
[    0.030501] SMP alternatives: switching to SMP code
[    0.057923] Brought up 2 CPUs
[    0.063071] xor: automatically using best checksumming function: generic_sse
[    0.068003]    generic_sse:  2096.000 MB/sec
[    0.068012] xor: using function: generic_sse (2096.000 MB/sec)
[    0.068083] Grant table initialized
[    0.068182] NET: Registered protocol family 16
[    0.070009] PCI: setting up Xen PCI frontend stub
[    0.070021] PCI: pci_cache_line_size set to 64 bytes
[    0.082626] bio: create slab  at 0
[    0.099028] raid6: int64x1   1753 MB/s
[    0.115999] raid6: int64x2   2386 MB/s
[    0.133022] raid6: int64x4   2289 MB/s
[    0.150031] raid6: int64x8   1601 MB/s
[    0.167006] raid6: sse2x1    2945 MB/s
[    0.184001] raid6: sse2x2    5496 MB/s
[    0.200995] raid6: sse2x4    6304 MB/s
[    0.201008] raid6: using algorithm sse2x4 (6304 MB/s)
[    0.201223] ACPI: Interpreter disabled.
[    0.201430] xen/balloon: Initialising balloon driver.
[    0.203147] xen-balloon: Initialising balloon driver.
[    0.204135] vgaarb: loaded
[    0.205071] SCSI subsystem initialized
[    0.205107] libata version 3.00 loaded.
[    0.206045] PCI: System does not support PCI
[    0.206045] PCI: System does not support PCI
[    0.206487] Switching to clocksource xen
[    0.209711] pnp: PnP ACPI: disabled
[    0.222217] PCI: max bus depth: 0 pci_try_num: 1
[    0.222383] NET: Registered protocol family 2
[    0.222503] IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
[    0.222821] TCP established hash table entries: 16384 (order: 6, 262144 bytes)
[    0.222944] TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
[    0.223079] TCP: Hash tables configured (established 16384 bind 16384)
[    0.223090] TCP reno registered
[    0.223097] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.223109] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.223215] NET: Registered protocol family 1
[    0.223411] RPC: Registered named UNIX socket transport module.
[    0.223421] RPC: Registered udp transport module.
[    0.223426] RPC: Registered tcp transport module.
[    0.223432] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.223441] PCI: CLS 0 bytes, default 64
[    0.614288] platform rtc_cmos: registered platform RTC device (no PNP device found)
[    0.690959] VFS: Disk quotas dquot_6.5.2
[    0.691026] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.691274] Registering the id_resolver key type
[    0.693300] msgmni has been set to 957
[    0.693349] async_tx: api initialized (async)
[    0.693524] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[    0.693540] io scheduler noop registered
[    0.693546] io scheduler deadline registered
[    0.693604] io scheduler cfq registered (default)
[    0.698908] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[    0.711263] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[    0.711281] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    2.418865] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    2.620562] brd: module loaded
[    2.630271] blkfront: sda: barrier: enabled
[    2.641918]  sda: sda1
[    2.641973] This is not a kind of scsi disk 202
[    2.647008] Loading iSCSI transport class v2.0-870.
[    2.662592] blkfront: sdb: barrier: enabled
[    2.691288]  sdb: sdb1 sdb2
[    2.691343] This is not a kind of scsi disk 202
[    2.691370] This is not a kind of scsi disk 202
[    2.746364] rdac: device handler registered
[    2.797833] Initialising Xen virtual ethernet driver.
[    2.834916] i8042: PNP: No PS/2 controller found. Probing ports directly.
[    3.863745] i8042: No controller found
[    3.904804] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
[    3.905102] rtc_cmos: probe of rtc_cmos failed with error -38
[    3.909600] i2c /dev entries driver
[    3.925393] coretemp coretemp.0: Using relative temperature scale!
[    3.925436] md: linear personality registered for level -1
[    3.925445] md: raid0 personality registered for level 0
[    3.925454] md: raid1 personality registered for level 1
[    3.925461] md: raid10 personality registered for level 10
[    3.925467] md: raid6 personality registered for level 6
[    3.925474] md: raid5 personality registered for level 5
[    3.925480] md: raid4 personality registered for level 4
[    3.931199] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: dm-devel@redhat.com
[    3.931582] TCP cubic registered
[    3.931594] NET: Registered protocol family 17
[    3.931622] Registering the dns_resolver key type
[    3.939223] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    3.948025] Freeing unused kernel memory: 15192k freed
[    3.956296] Write protecting the kernel read-only data: 6144k
[    3.960594] Freeing unused kernel memory: 536k freed
[    3.961046] Freeing unused kernel memory: 260k freed
:: START /linuxrc.syno[  OK  ]
:: Checking hypervisor[  OK  ]
Detected hypervisor: xen
xen-domU
ash: xen-domU: unknown operand
:: Loading module xen-gntdev[  OK  ]
:: Loading module xen-gntalloc[  OK  ]
:: Loading module xenfs[  OK  ]
:: Loading module xen-evtchn[ BUSY ][    4.150104] Event-channel device installed.
[  OK  ]
:: Loading module virtio_blk[ BUSY ][    4.168911] virtio_blk: Unknown symbol register_virtio_driver (err 0)
[    4.168954] virtio_blk: Unknown symbol unregister_virtio_driver (err 0)
[    4.168965] virtio_blk: Unknown symbol virtqueue_add_buf_gfp (err 0)
[    4.168992] virtio_blk: Unknown symbol virtqueue_get_buf (err 0)
[    4.169005] virtio_blk: Unknown symbol virtqueue_kick (err 0)
[    4.169016] virtio_blk: Unknown symbol virtio_check_driver_offered_feature (err 0)
[FAILED]
:: Loading module virtio_net[ BUSY ][    4.184478] virtio_net: Unknown symbol register_virtio_driver (err 0)
[    4.184496] virtio_net: Unknown symbol virtqueue_enable_cb (err 0)
[    4.184507] virtio_net: Unknown symbol virtqueue_detach_unused_buf (err 0)
[    4.184539] virtio_net: Unknown symbol unregister_virtio_driver (err 0)
[    4.184549] virtio_net: Unknown symbol virtqueue_add_buf_gfp (err 0)
[    4.184556] virtio_net: Unknown symbol virtqueue_get_vring_size (err 0)
[    4.184567] virtio_net: Unknown symbol virtqueue_disable_cb (err 0)
[    4.184587] virtio_net: Unknown symbol virtqueue_get_buf (err 0)
[    4.184598] virtio_net: Unknown symbol virtqueue_kick (err 0)
[    4.184613] virtio_net: Unknown symbol virtio_check_driver_offered_feature (err 0)
[    4.184622] virtio_net: Unknown symbol virtqueue_enable_cb_delayed (err 0)
[FAILED]
:: Loading module virtio_ring[ BUSY ][    4.200130] virtio_ring: Unknown symbol virtio_check_driver_offered_feature (err 0)
[FAILED]
:: Loading module virtio[  OK  ]
:: Loading module virtio_balloon[ BUSY ][    4.233019] virtio_balloon: Unknown symbol virtqueue_add_buf_gfp (err 0)
[    4.233044] virtio_balloon: Unknown symbol virtqueue_get_buf (err 0)
[    4.271264] virtio_balloon: Unknown symbol virtqueue_kick (err 0)
[FAILED]
:: Loading module virtio_mmio[ BUSY ][    4.287118] virtio_mmio: Unknown symbol vring_transport_features (err 0)
[    4.287151] virtio_mmio: Unknown symbol vring_interrupt (err 0)
[    4.287161] virtio_mmio: Unknown symbol vring_new_virtqueue (err 0)
[    4.287192] virtio_mmio: Unknown symbol vring_del_virtqueue (err 0)
[FAILED]
:: Loading module virtio_pci[ BUSY ][    4.301443] virtio_pci: Unknown symbol vring_transport_features (err 0)
[    4.301473] virtio_pci: Unknown symbol vring_interrupt (err 0)
[    4.301483] virtio_pci: Unknown symbol vring_new_virtqueue (err 0)
[    4.301511] virtio_pci: Unknown symbol vring_del_virtqueue (err 0)
[FAILED]
:: Loading module virtio_console[ BUSY ][    4.315232] virtio_console: Unknown symbol virtqueue_detach_unused_buf (err 0)
[    4.315278] virtio_console: Unknown symbol virtqueue_add_buf_gfp (err 0)
[    4.315305] virtio_console: Unknown symbol virtqueue_get_buf (err 0)
[    4.315316] virtio_console: Unknown symbol virtqueue_kick (err 0)
[FAILED]
:: Re-scanning disks[ BUSY ][    4.340171] md: Autodetecting RAID arrays.
[    4.340194] This is not a kind of scsi disk 202
[    4.365505] This is not a kind of scsi disk 202
[    4.388421] md: Scanned 2 and added 2 devices.
[    4.388432] md: autorun ...
[    4.388437] md: considering sdb1 ...
[    4.388453] md:  adding sdb1 ...
[    4.388460] md: sdb2 has different UUID to sdb1
[    4.388473] md: created md0
[    4.388478] md: bind
[    4.388505] md: running: 
[    4.388826] bio: create slab  at 1
[    4.388970] md/raid1:md0: active with 1 out of 12 mirrors
[    4.389007] md0: detected capacity change from 0 to 2549940224
[    4.389317] md: considering sdb2 ...
[    4.389328] md:  adding sdb2 ...
[    4.390941] md: created md1
[    4.390949] md: bind
[    4.390967] md: running: 
[    4.396017] md/raid1:md1: active with 1 out of 12 mirrors
[    4.396049] md1: detected capacity change from 0 to 2147418112
[    4.397413] md: ... autorun DONE.
[    4.421155]  md1: unknown partition table
[  OK  ]
+ exec
[    4.498884] bromolow_synobios: module license 'Synology Inc.' taints kernel.
[    4.498903] Disabling lock debugging due to kernel taint

Share this post


Link to post
Share on other sites

I just noticed that my HDD do not spindown after the specified time of inactivity, anybody has the same problem ? Or even better ... a solution :smile: ?

 

Using GnoBoot 10.4, DSM 5.0 (4458) and IPKG installed (as well as Asterisk 1.8, though currently not running).

 

Many thanks for potential insights !

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now