Recommended Posts

Hello,

 

I´m using it as baremetal. I don´t know in which Mode the Adapter is running. I diddnt switch anything so it runs unmodifeyd. The Volume was not shown in DSM. In 10.4 all runs fine.

 

THX fpr xour help!

 

Boot to debug mode by editing gnoboot-alpha boot menu, send your /.gnoboot/debug.log. Can you also provide a DSM screenshoot?

 

kernel /zImage debug

Link to post
Share on other sites

DEBUG from 10.4 or 10.5?

 

Here some DATA from MEGACLI:

 

Product Name : PERC H310 Adapter

Serial No : 2BG09XX

FW Package Build: 20.10.2-0002

 

BIOS Version : 4.29.00_4.12.05.00_0x05110000

Preboot CLI Version: 03.02-015:#%00008

Ctrl-R Version : 3.00-0020

NVDATA Version : 3.09.03-0038

FW Version : 2.120.14-1504

Boot Block Version : 2.02.00.00-0001

 

Virtual Drives : 1

Degraded : 0

Offline : 0

Physical Devices : 4

Disks : 4

Critical Disks : 0

Failed Disks : 0

Link to post
Share on other sites
Does anybody have a problem where a virtual machine with DSM5.0-4458 would shutdown every day a random time because of "disk overheating" ?

Disks are virtual, how can they overheat ? :smile:

 

Also from /var/log/messages i frequently have such errors :

 

Mar 25 15:05:01 DSMesxi5 SystemInfo.cgi: disk_info_get.c:82 Failed to open /dev/sdc, errno=No such file or directory

 

 

And this are always the last line before each forced shutdown. Any info on that?

 

 

I have the same problem. I use ESXi5.0, with gnoBoot10.5. Using a 64GB virtual disk as the installation for DSM5, and passthrough a LSI 9122-8i to this VM. For the longest time, i kept thinking one of the disk on the LSI controller is overheating, but none of them go over 41C. Now reading your post, realizing it's the virtual disk. Also, in my ESXi, the VM controller is set to ParaVirtual.

Link to post
Share on other sites
Hello,

 

with 10.5 my PERC310 (8 SATA/SAS-Port Controller) doesnt work, the Volume is not showing up...with 10.4 it works great...PLS Help :smile:

I´ve created the Volume in the BIOS settings (4 SAS Drives / 1 Volume) so i dont have to create an Software-Raid in the DSM.

I'm using 9211-8i and it works (IR mode) for me on ESXi+vt-d. Are you using baremetal or vt-d? Doesn't show in DSM or doesn't detect the disk?

 

 

Have you been able to get disks conected to the 9211-8i to start from Disk1-Disk8?

Do i need to blacklist any other drivers to make sure theres no unused slots before the disks on the raid card?

 

Also , Will flashing IT firmware instead of IR benifit in any way?

Link to post
Share on other sites
Hello,

 

with 10.5 my PERC310 (8 SATA/SAS-Port Controller) doesnt work, the Volume is not showing up...with 10.4 it works great...PLS Help :smile:

I´ve created the Volume in the BIOS settings (4 SAS Drives / 1 Volume) so i dont have to create an Software-Raid in the DSM.

I'm using 9211-8i and it works (IR mode) for me on ESXi+vt-d. Are you using baremetal or vt-d? Doesn't show in DSM or doesn't detect the disk?

 

 

Have you been able to get disks conected to the 9211-8i to start from Disk1-Disk8?

Do i need to blacklist any other drivers to make sure theres no unused slots before the disks on the raid card?

 

Also , Will flashing IT firmware instead of IR benifit in any way?

 

 

Someone here said you can't install DSM directly onto a disk over a passthroughed SATA controller.

Link to post
Share on other sites
Hello,

 

I´m using it as baremetal. I don´t know in which Mode the Adapter is running. I diddnt switch anything so it runs unmodifeyd. The Volume was not shown in DSM. In 10.4 all runs fine.

 

THX fpr xour help!

 

Boot to debug mode by editing gnoboot-alpha boot menu, send your /.gnoboot/debug.log. Can you also provide a DSM screenshoot?

 

kernel /zImage debug

 

Here it is. THX again!

debug10_4_5.zip

Link to post
Share on other sites
Updated to 10.5

 

Tried adding SSD cache

 

Still the same problem :sad:

 

SKW-SAN> tail -f /var/log/messages

Apr 7 20:58:37 SKW-SAN iss: synocomm_types.c:268 szName eth0 10.2.0.4 is Active

Apr 7 20:58:37 SKW-SAN iss: synocomm_types.c:268 szName eth1 10.3.0.4 is Active

Apr 7 20:58:37 SKW-SAN iss: synocomm_types.c:268 szName eth2 172.16.2.1 is Active

Apr 7 20:58:37 SKW-SAN kernel: [ 632.060284] EXT_INFO: INIT Extent-Pool

Apr 7 20:58:40 SKW-SAN flashcachehandler.cgi: flashcachehandler.cpp:238 Failed to create flashcache on /volume1 [0xEB00 servicec fg_internal_lib.c:104]

Apr 7 20:58:40 SKW-SAN kernel: [ 634.627242] md: md4: set sdf1 to auto_remap [0]

Apr 7 20:58:40 SKW-SAN kernel: [ 634.627243] md: md4: set sde1 to auto_remap [0]

Apr 7 20:58:40 SKW-SAN flashcachehandler.cgi: raid_remove.c:48 [info] clean RAID superblock of /dev/md4

Apr 7 20:58:41 SKW-SAN flashcachehandler.cgi: raid_clean_superblock.c:87 [info] Clean RAID superblock on '/dev/sde1'

Apr 7 20:58:41 SKW-SAN flashcachehandler.cgi: raid_clean_superblock.c:87 [info] Clean RAID superblock on '/dev/sdf1'

Apr 7 20:58:46 SKW-SAN hotplugd: usb_get_device_id.c:56 failed get usb id Vendor=0000, ProdID=0000, SN=ffffffd0ffffffa2ffffffc3ffffffac

Apr 7 20:58:46 SKW-SAN hotplugd: hotplugd.c:990 failed get usb device id from usb config, DEVICE=/proc/bus/usb/000/000

Apr 7 20:58:46 SKW-SAN hotplugd: ##### ACTION:add

Apr 7 20:58:46 SKW-SAN hotplugd: DEVICE:/proc/bus/usb/000/000

Apr 7 20:58:46 SKW-SAN hotplugd: hotplugd.c:1406 Device is not in hotplugd supported list.

Apr 7 20:58:46 SKW-SAN hotplugd: usb_get_device_id.c:56 failed get usb id Vendor=0000, ProdID=0000, SN=ffffffd0ffffffa2ffffffc3ffffffac

Apr 7 20:58:46 SKW-SAN hotplugd: hotplugd.c:990 failed get usb device id from usb config, DEVICE=/proc/bus/usb/000/000

Apr 7 20:58:46 SKW-SAN hotplugd: ##### ACTION:add

Apr 7 20:58:46 SKW-SAN hotplugd: DEVICE:/proc/bus/usb/000/000

Apr 7 20:58:46 SKW-SAN hotplugd: hotplugd.c:1406 Device is not in hotplugd supported list.

 

Haven't looked into it :lol: .

 

Hello,

 

with 10.5 my PERC310 (8 SATA/SAS-Port Controller) doesnt work, the Volume is not showing up...with 10.4 it works great...PLS Help :smile:

I´ve created the Volume in the BIOS settings (4 SAS Drives / 1 Volume) so i dont have to create an Software-Raid in the DSM.

I'm using 9211-8i and it works (IR mode) for me on ESXi+vt-d. Are you using baremetal or vt-d? Doesn't show in DSM or doesn't detect the disk?

 

*

For me i have always problem with Realtek network card 10DE:8136 rev=02 ( motherboard HP IPMEL-AE PEGATRON )

no IP ...?

 

 

addon cards

8086:1229 rev=02 OK

10DE:8169 rev=02 OK

 

I have a log with RR62x failed ...with no card in the computer

 

if i plug a RR622 card run , no problem in sata mode with only one HDD no RAID << fine ****

 

*** to change something or it really takes me a very detailed explanation **

** I know almost nothing linux !! ***

 

Pierre

 

Try to blacklist r8169 using rmmod GRUB option.

BTW, I have tried MagicPro PCTV Dual USB adaptor on my Xpenology box with 10.5 alpha, the dongle is not recognized by video station.

Did you load the drivers in /etc/rc.local?

 

 

bump :smile:, anything new? Or any idea what shoul I try?

Try it again using 10.5, added more boot-up messages to trace your problem.

 

Hello, now I`m trying gnoboot-alpha-10.5 and v10.4 directly on hardware (MB GA-EP-DS4). Installed latest DSM 5.0-4458. I have some issuses with that configuration.

 

1. When system boots up I have to wait about 5min to be available on the network, or unplug and plug in Lan cable. Motherboard using Realtek 8111C Chip.

2. Unable to install Update 1 no matter if trying automatic or manual update. System loads update the saying that the file is broken.

3. My DVB-T dongle not workig (works well on Trantor version and 4.3). This is Manta dvbtusb01 it is based on chipset It9135. As I see drivers are present in system, but Videostation not recognizes any tv card.

dmesg

[64440.720177] ------------[ cut here ]------------
[64440.720184] WARNING: at drivers/ata/libata-core.c:5348 ata_qc_issue+0x51/0x371()
[64440.720186] Hardware name: EP45-DS4
[64440.720188] Modules linked in: it913x_fe(O) cifs udf isofs loop btusb(O) hidp(O) rfcomm(O) bluetooth(O) ip6t_LOG nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables xt_limit xt_state xt_tcpudp xt_multiport ipt_LOG nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack iptable_filter ip_tables x_tables usbhid hid usblp usb_storage uhci_hcd etxhci_hcd xhci_hcd ohci_hcd ehci_hcd bromolow_synobios(P) btrfs zlib_deflate hfsplus md4 hmac i2c_algo_bit fuse vfat fat chainiv cpufreq_conservative cpufreq_powersave cpufreq_performance cpufreq_ondemand mperf processor cpufreq_stats freq_table dm_snapshot crc_itu_t quota_v2 quota_tree usbcore psnap p8022 llc usb_common zram(C) mpt2sas synoacl_ext4(P) synoacl_vfs(P) hptiop 3w_sas 3w_9xxx 3w_xxxx mv61xx(P) mvsas hpsa arcmsr aic7xxx aic79xx pm80xx(O) aic94xx aacraid megaraid_sas megaraid_mbox megaraid_mm mptsas mptspi mptscsih mptbase scsi_transport_spi scsi_wait_scan sg ata_piix sata_uli sata_svw sata_qstor sata_inic162x sata_sis pata_sis stex sata_sx4 sata_promise sata_nv sata_via sata_sil pata_serverworks pata_oldpiix pata_sch pata_artop pata_atp867x pata_pdc202xx_old pata_pdc2027x pata_it821x pata_hpt3x2n pata_hpt37x pata_hpt366 pata_hpt3x3 pdc_adma pata_via pata_sil680 pata_rdc pata_ninja32 pata_netcell pata_marvell pata_jmicron pata_cmd64x pata_ali ata_generic iscsi_tcp libiscsi_tcp libiscsi enic qlge qlcnic qla3xxx netxen_nic mlx4_en mlx4_core cxgb4vf cxgb4 cxgb3 cxgb cnic ipv6 bnx2x bna be2net sis900 sis190 jme atl1e(O) atl1c atl2(O) atl1(O) alx(O) sky2 skge via_velocity crc_ccitt via_rhine r8169(O) r8168(O) 8139too 8139cp tg3(O) libphy b44(O) bnx2 mmc_core ssb(O) uio forcedeth ixgbe ixgb igb_new(O) ioatdma e1000e_new(O) e1000 e100 dca pcnet32 amd8111e tulip mdio mii container fan thermal_sys compat(O) cryptd ecryptfs sha512_generic sha256_generic sha1_generic ecb aes_x86_64 authenc des_generic libcrc32c crc32c eseqiv krng ansi_cprng cts rng aes_generic md5 cbc cryptomgr pcompress aead crypto_hash crypto_blkcipher crypto_wq crypto_algapi [last unloaded: it913x_fe]
[64440.720342] Pid: 6118, comm: md0_raid1 Tainted: P         C O 3.2.40 #8
[64440.720344] Call Trace:
[64440.720348]  [] ? ata_qc_issue+0x51/0x371
[64440.720351]  [] ? ata_qc_issue+0x51/0x371
[64440.720355]  [] ? warn_slowpath_common+0x78/0x8d
[64440.720359]  [] ? ata_qc_issue+0x51/0x371
[64440.720362]  [] ? ata_qc_reinit+0x6d/0x7d
[64440.720365]  [] ? ata_ioc32+0x15/0x15
[64440.720368]  [] ? ata_scsi_translate+0xda/0x10f
[64440.720371]  [] ? ata_scsi_queuecmd+0x3f/0x70
[64440.720376]  [] ? scsi_dispatch_cmd+0x295/0x2fe
[64440.720379]  [] ? scsi_request_fn+0x4e7/0x516
[64440.720383]  [] ? blk_queue_bio+0x294/0x2b8
[64440.720386]  [] ? generic_make_request+0x91/0xd0
[64440.720389]  [] ? submit_bio+0xa6/0xaf
[64440.720393]  [] ? md_super_write+0x58/0x83
[64440.720396]  [] ? md_update_sb+0x2e6/0x455
[64440.720399]  [] ? md_check_recovery+0x221/0x579
[64440.720403]  [] ? raid1d+0x33/0x1298
[64440.720407]  [] ? need_resched+0x1e/0x28
[64440.720410]  [] ? __schedule+0x515/0x52f
[64440.720414]  [] ? __switch_to+0x142/0x27c
[64440.720417]  [] ? calc_global_load+0x191/0x191
[64440.720420]  [] ? schedule_timeout+0x1e/0xb8
[64440.720424]  [] ? default_spin_lock_flags+0x5/0x9
[64440.720427]  [] ? _raw_spin_lock_irqsave+0x1e/0x27
[64440.720431]  [] ? default_spin_lock_flags+0x5/0x9
[64440.720434]  [] ? _raw_spin_lock_irqsave+0x1e/0x27
[64440.720437]  [] ? md_thread+0xe4/0x102
[64440.720441]  [] ? wake_up_bit+0x22/0x22
[64440.720444]  [] ? md_trim_bio+0x105/0x105
[64440.720447]  [] ? kthread+0x6a/0x72
[64440.720451]  [] ? kernel_thread_helper+0x4/0x10
[64440.720454]  [] ? kthread_bind+0x5c/0x5c
[64440.720457]  [] ? gs_change+0x13/0x13
[64440.720459] ---[ end trace 8e0b7a312ad2c2cc ]---

 

Any suggestions ?

 

Thanks

Try to blacklist r8169 using rmmod GRUB option. Did you load the DVB drivers in /etc/rc.local?

/

Related to DVB dongle:

There is no file rc.local in my system - is this something missed ? or maybe I have to create this one ?

Can You told me how can I load drivers ? I`m still not familiar in linux/synology. I found rivers used in previous 4.3 trantor version its called dvb-usb-it9135-01.fw and dvb-usb-it9135-02.fw. Those files are present in /volume1/@appstore/VideoStation/etc/KernelFirmwares.

 

Lan: Try to blacklist r8169 using rmmod GRUB option - But how can I do that ?

Link to post
Share on other sites
Hello,

 

with 10.5 my PERC310 (8 SATA/SAS-Port Controller) doesnt work, the Volume is not showing up...with 10.4 it works great...PLS Help :smile:

I´ve created the Volume in the BIOS settings (4 SAS Drives / 1 Volume) so i dont have to create an Software-Raid in the DSM.

I'm using 9211-8i and it works (IR mode) for me on ESXi+vt-d. Are you using baremetal or vt-d? Doesn't show in DSM or doesn't detect the disk?

 

 

Have you been able to get disks conected to the 9211-8i to start from Disk1-Disk8?

Do i need to blacklist any other drivers to make sure theres no unused slots before the disks on the raid card?

 

Also , Will flashing IT firmware instead of IR benifit in any way?

 

You have to blacklist the boot image disk (ata_piix) using rmmod GRUB option.

 

Put the following lines in your /boot/grub/menu_alpha.lst

 

kernel /zImage rmmod=ata_piix,r8169,r8169_new

 

To load the wireless or multimedia drivers, put the following lines in /etc/rc.local.

 

#!/bin/sh
source /etc/rc.subr
source /.gnoboot/modules.d/03-wifi.conf
source /.gnoboot/modules.d/05-media.conf
SYNOLoadModules $WIFI_MOD
SYNOLoadModules $MEDIA_MOD 

 

If video station still doesn't work, then you have to figure it out by yourself. I don't support anything related to DSM.

Link to post
Share on other sites

Hello everybody,

 

Maybe a absolute NOOB question but I hope someone will be so kind to give me a awnser. Currently I am running the latest version of DSM 4.3 on an Intel D2700MUD. I just recently looked at the forum again after a while because I wanted to check if there was a update for the new DSM 5.0.

I stumbled across this post and was wondering if this can be installed on my Intel motherboard without EXSI or do I have to wait for a new version from Trantor?

If it is possible where can I find the correct update/install tutorial.

 

Thank you in advance for your time and effort

 

Cheers

 

Burner1977

Link to post
Share on other sites

I'm using 9211-8i and it works (IR mode) for me on ESXi+vt-d. Are you using baremetal or vt-d? Doesn't show in DSM or doesn't detect the disk?

 

What's your ESXi version? Any issues with 9211-8i so far? I'm looking for a stable card to pass it through ..

Link to post
Share on other sites

[quote name='"gnoboot

Put the following lines in your /boot/grub/menu_alpha.lst

 

kernel /zImage rmmod=ata_piix,r8169,r8169_new

 

 

Sorry but it is still not working for me. Again ive attached the Debug log.

 

10_5 ( not working)

[ 10.433168] sd_probe: Got UNKNOWN dev_prefix (sd)' date=' index (4), disk_name [b'](sde)[/b], disk_len (20)

10_4 (working)

[ 11.305137] sd_probe: Got UNKNOWN dev_prefix (sd), index (6), disk_name (sdg), disk_len (20)

 

The good News is that my cynergy t2 is working now :smile:

 

Her some Screens:

10_4

10_4_1.png10_4_2.png

10_5

10_5_1.png10_5_2.png

debug10_5_v2.zip

Link to post
Share on other sites

gnoBoot 10.4 works perfectly on my ESXi over past few weeks. Thank you for the great work and kudos to gnoBoot! :wink:

 

Now that 10.5 is out. Is there a way to remount boot drive and replace zImage within SSH? I used to replace zImage in vmdk but hope to make upgrade even simpler. :roll:

Link to post
Share on other sites

Sorry but it is still not working for me. Again ive attached the Debug log.

 

10_5 ( not working)

[ 10.433168] sd_probe: Got UNKNOWN dev_prefix (sd), index (4), disk_name (sde), disk_len (20)

10_4 (working)

[ 11.305137] sd_probe: Got UNKNOWN dev_prefix (sd), index (6), disk_name (sdg), disk_len (20)

 

The good News is that my cynergy t2 is working now :smile:

 

Did you try manually reloading mpt2sas driver after booting up DSM?

 

gnoboot> rmmod mpt2sas
gnoboot> insmod /lib/modules/mpt2sas.ko && dmesg | tail -n 50
or
gnoboot> insmod /lib/modules/mpt2sas.ko missing_delay=1000 && dmesg | tail -n 50

 

And post the result of 2nd command. :wink:

Link to post
Share on other sites

I'm fairly new to XPEnology and I like it a lot. I recently installed trantor's 4.3 build esxi v1.2 and it works fine on my ESXi 5.0 with VT-d.

But I prefer to start with DSM5.0. Unfortunately all DSM5 builds fail when I install the .pat-file. dmesg log shows:

 

md: md0 stopped
md: md1 stopped

 

I have setup the VM with 1x 32 MiB IDE HDD and 2x 2GiB SCSI disks; all vmdks.

I am unable to gather any useful info on what's going wrong during install. Is this something I can fix? Am I doing anything wrong, or is it missing drivers?

Both trantor's beta and gnoboot's show this symptom.

Any guidance would be appreciated.

Link to post
Share on other sites

Did you try manually reloading mpt2sas driver after booting up DSM?

 

gnoboot> rmmod mpt2sas
gnoboot> insmod /lib/modules/mpt2sas.ko && dmesg | tail -n 50
or
gnoboot> insmod /lib/modules/mpt2sas.ko missing_delay=1000 && dmesg | tail -n 50

 

And post the result of 2nd command. :wink:

 

No but doesnt work also...Here is the Output:

 

CyberDisk> rmmod mpt2sas
CyberDisk> insmod /lib/modules/mpt2sas.ko && dmesg | tail -n 50
[   37.555625] ata1: EH complete
[   37.556591] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   37.643176] usbcore: registered new interface driver dvb_usb_nova_t_usb2
[   37.695116] HDHomeRun: Begin init, version 0.0.15
[   37.711525] HDHomeRun: Waiting for userspace to connect
[   37.727298] HDHomeRun: End init
[   39.180914] EXT4-fs (sdu1): mounted filesystem without journal. Opts: nodelalloc,synoacl,data=ordered,oldalloc
[   39.682045] eth0: no IPv6 routers present
[   40.531764] init: synoindexd main process (23002) killed by USR2 signal
[   40.546852] init: synoindexd main process ended, respawning
[   44.487049] loop: module loaded
[   45.390210] dsmnotify.cgi[24493]: segfault at 0 ip 000000000804ccb8 sp 00000000ffaa35f0 error 6
[   46.556219] init: synoindexd main process (23280) killed by HUP signal
[   46.571046] init: synoindexd main process ended, respawning
[   46.615573] init: synomkthumbd main process (21838) killed by HUP signal
[   46.631786] init: synomkthumbd main process ended, respawning
[   46.681098] init: synomkflvd main process (21827) killed by HUP signal
[   46.696527] init: synomkflvd main process ended, respawning
[   47.031554] findhostd uses obsolete (PF_INET,SOCK_PACKET)
[   48.186136] init: synoindexd main process (24762) killed by HUP signal
[   48.200898] init: synoindexd main process ended, respawning
[   48.240284] init: synomkthumbd main process (24871) killed by HUP signal
[   48.255228] init: synomkthumbd main process ended, respawning
[   48.300927] init: synomkflvd main process (24880) killed by HUP signal
[   48.314912] init: synomkflvd main process ended, respawning
[   49.276112] init: synoindexd main process (25248) killed by HUP signal
[   49.289759] init: synoindexd main process ended, respawning
[   49.327884] init: synomkthumbd main process (25268) killed by HUP signal
[   49.341743] init: synomkthumbd main process ended, respawning
[   49.386283] init: synomkflvd main process (25280) killed by HUP signal
[   49.399369] init: synomkflvd main process ended, respawning
[   66.954905] dm request get [md2], push down wakeup no work
[   66.967637] wake up [sda5]
[   66.980073] wake up [sdb5]
[   66.987725] Sync page end [sda]
[   67.012371] Sync page end [sdb]
[   69.819634] dsmnotify.cgi[29539]: segfault at 0 ip 000000000804ccb8 sp 00000000fffd1d00 error 6
[   69.969304] dsmnotify.cgi[29541]: segfault at 0 ip 000000000804ccb8 sp 00000000ff85c2d0 error 6
[   74.189290] synobios_ioctl: SYNOIO_RTC_TIME_WRITE
[   74.201471] (0h, 10) (1h, 5) (2h, 12) (3h, 4) (4h, a) (5h, 3) (6h, 72)
[   76.034895] dsmnotify.cgi[29646]: segfault at 0 ip 000000000804ccb8 sp 00000000ffbbf800 error 6
[   77.153924] dsmnotify.cgi[29651]: segfault at 0 ip 000000000804ccb8 sp 00000000ff81ae70 error 6
[  100.793338] dsmnotify.cgi[29821]: segfault at 0 ip 000000000804ccb8 sp 00000000ffdf4750 error 6
[  108.260572] dsmnotify.cgi[29909]: segfault at 0 ip 000000000804ccb8 sp 00000000ff9a8660 error 6
[  116.138046] storagehandler.[29935]: segfault at 0 ip 000000000809e298 sp 00000000ffdf3210 error 6
[  117.115037] storagehandler.[31104]: segfault at 0 ip 000000000809e298 sp 00000000ff8b64f0 error 6
[  128.235820] storagehandler.[1241]: segfault at 0 ip 000000000809e298 sp 00000000ff948bc0 error 6
[  130.674121] mpt2sas version 13.100.00.00 unloading
[  131.414394] dsmnotify.cgi[2626]: segfault at 0 ip 000000000804ccb8 sp 00000000ffeb57d0 error 6
[  138.930116] mpt2sas version 13.100.00.00 loaded
CyberDisk> mount
/dev/root on / type ext4 (defaults)
none on /dev/pts type devpts (gid=4,mode=620)
/sys on /sys type sysfs (0)
/tmp on /tmp type tmpfs (0)
/proc/bus/usb on /proc/bus/usb type usbfs (0)
/dev/vg1000/lv on /volume1 type ext4 (usrjquota=aquota.user,grpjquota=aquota.gro
up,jqfmt=vfsv0,synoacl)
none on /proc/fs/nfsd type nfsd (0)
/volume1/@optware on /opt type bind (bind)
/dev/sdu1 on /volumeUSB1/usbshare type ext4 (nodelalloc,synoacl)
CyberDisk>

 

Output from 2nd Command:

 

CyberDisk> rmmod mpt2sas
CyberDisk> insmod /lib/modules/mpt2sas.ko missing_delay=1000 && dmesg | tail -n50
[  161.969731] dsmnotify.cgi[8142]: segfault at 0 ip 000000000804ccb8 sp 00000000ffec7fe0 error 6
[  170.636243] dsmnotify.cgi[8982]: segfault at 0 ip 000000000804ccb8 sp 00000000ffbb5210 error 6
[  173.648209] storagehandler.[8986]: segfault at 0 ip 000000000809e298 sp 00000000ff8c27b0 error 6
[  184.723040] storagehandler.[10902]: segfault at 0 ip 000000000809e298 sp 00000000ffe97920 error 6
[  193.089445] dsmnotify.cgi[12778]: segfault at 0 ip 000000000804ccb8 sp 00000000fff52040 error 6
[  195.941509] storagehandler.[12788]: segfault at 0 ip 000000000809e298 sp 00000000ffe9d590 error 6
[  201.942890] dsmnotify.cgi[14685]: segfault at 0 ip 000000000804ccb8 sp 00000000ffe02e00 error 6
[  207.034950] storagehandler.[14717]: segfault at 0 ip 000000000809e298 sp 00000000fff7b310 error 6
[  218.364656] storagehandler.[16620]: segfault at 0 ip 000000000809e298 sp 00000000ffc694b0 error 6
[  223.590774] dsmnotify.cgi[18545]: segfault at 0 ip 000000000804ccb8 sp 00000000ffd546c0 error 6
[  229.967952] storagehandler.[18579]: segfault at 0 ip 000000000809e298 sp 00000000ffe7e410 error 6
[  233.156291] dsmnotify.cgi[20004]: segfault at 0 ip 000000000804ccb8 sp 00000000ffae2cd0 error 6
[  241.047060] storagehandler.[20531]: segfault at 0 ip 000000000809e298 sp 00000000ff89dde0 error 6
[  252.137404] storagehandler.[22461]: segfault at 0 ip 000000000809e298 sp 00000000fff7d650 error 6
[  254.329469] dsmnotify.cgi[23802]: segfault at 0 ip 000000000804ccb8 sp 00000000ff9cc310 error 6
[  263.431710] storagehandler.[24392]: segfault at 0 ip 000000000809e298 sp 00000000ff9e9660 error 6
[  264.404245] dsmnotify.cgi[25673]: segfault at 0 ip 000000000804ccb8 sp 00000000ffd0e880 error 6
[  274.570618] storagehandler.[26352]: segfault at 0 ip 000000000809e298 sp 00000000ff823510 error 6
[  285.163223] dsmnotify.cgi[28300]: segfault at 0 ip 000000000804ccb8 sp 00000000ffe79900 error 6
[  285.906033] storagehandler.[28301]: segfault at 0 ip 000000000809e298 sp 00000000ff962be0 error 6
[  295.670636] dsmnotify.cgi[30302]: segfault at 0 ip 000000000804ccb8 sp 00000000ffdd3520 error 6
[  297.585090] storagehandler.[30304]: segfault at 0 ip 000000000809e298 sp 00000000ff878700 error 6
[  308.711157] storagehandler.[32193]: segfault at 0 ip 000000000809e298 sp 00000000ffd7cdf0 error 6
[  315.965049] dsmnotify.cgi[1617]: segfault at 0 ip 000000000804ccb8 sp 00000000ffcbdc90 error 6
[  319.831486] storagehandler.[1643]: segfault at 0 ip 000000000809e298 sp 00000000ffd928d0 error 6
[  326.940640] dsmnotify.cgi[3536]: segfault at 0 ip 000000000804ccb8 sp 00000000ffb07cb0 error 6
[  332.436420] storagehandler.[3556]: segfault at 0 ip 000000000809e298 sp 00000000ff858320 error 6
[  344.120451] storagehandler.[5462]: segfault at 0 ip 000000000809e298 sp 00000000ffc033c0 error 6
[  346.281777] dsmnotify.cgi[6850]: segfault at 0 ip 000000000804ccb8 sp 00000000fff50240 error 6
[  356.481092] storagehandler.[7467]: segfault at 0 ip 000000000809e298 sp 00000000ffa04920 error 6
[  358.211447] dsmnotify.cgi[8756]: segfault at 0 ip 000000000804ccb8 sp 00000000ffa2f750 error 6
[  367.587217] storagehandler.[9386]: segfault at 0 ip 000000000809e298 sp 00000000ffc72d20 error 6
[  376.989722] dsmnotify.cgi[11258]: segfault at 0 ip 000000000804ccb8 sp 00000000ffbb0860 error 6
[  379.404449] storagehandler.[11261]: segfault at 0 ip 000000000809e298 sp 00000000ffe31080 error 6
[  389.423992] dsmnotify.cgi[13180]: segfault at 0 ip 000000000804ccb8 sp 00000000ffab4110 error 6
[  390.531296] storagehandler.[13182]: segfault at 0 ip 000000000809e298 sp 00000000ff809580 error 6
[  401.852918] storagehandler.[15095]: segfault at 0 ip 000000000809e298 sp 00000000fff95f20 error 6
[  407.105192] dsmnotify.cgi[17017]: segfault at 0 ip 000000000804ccb8 sp 00000000ff8da910 error 6
[  413.262676] storagehandler.[17074]: segfault at 0 ip 000000000809e298 sp 00000000fff9a320 error 6
[  420.705384] dsmnotify.cgi[18989]: segfault at 0 ip 000000000804ccb8 sp 00000000ff9eda80 error 6
[  424.362638] storagehandler.[19001]: segfault at 0 ip 000000000809e298 sp 00000000ffbdf800 error 6
[  435.456894] storagehandler.[20905]: segfault at 0 ip 000000000809e298 sp 00000000ffccf270 error 6
[  437.710342] dsmnotify.cgi[22252]: segfault at 0 ip 000000000804ccb8 sp 00000000ffb34bf0 error 6
[  446.748137] storagehandler.[22841]: segfault at 0 ip 000000000809e298 sp 00000000ffd01010 error 6
[  451.956945] dsmnotify.cgi[24785]: segfault at 0 ip 000000000804ccb8 sp 00000000ffc323d0 error 6
[  458.149735] storagehandler.[24824]: segfault at 0 ip 000000000809e298 sp 00000000ff8622c0 error 6
[  462.546053] mpt2sas version 13.100.00.00 unloading
[  468.494519] dsmnotify.cgi[26762]: segfault at 0 ip 000000000804ccb8 sp 00000000ff85ab60 error 6
[  469.278760] storagehandler.[26763]: segfault at 0 ip 000000000809e298 sp 00000000ffa42b80 error 6
[  476.164348] mpt2sas version 13.100.00.00 loaded
CyberDisk>
CyberDisk> mount
/dev/root on / type ext4 (defaults)
none on /dev/pts type devpts (gid=4,mode=620)
/sys on /sys type sysfs (0)
/tmp on /tmp type tmpfs (0)
/proc/bus/usb on /proc/bus/usb type usbfs (0)
/dev/vg1000/lv on /volume1 type ext4 (usrjquota=aquota.user,grpjquota=aquota.gro
up,jqfmt=vfsv0,synoacl)
none on /proc/fs/nfsd type nfsd (0)
/volume1/@optware on /opt type bind (bind)
/dev/sdu1 on /volumeUSB1/usbshare type ext4 (nodelalloc,synoacl)
CyberDisk>

 

Unfortunately that did not work also. Hope you have a few more ideas :smile:

 

**Update**

 

Maybee i find it in the log. The Driver pata_atiixp is not loading. In 10_4 the followings line are in the Debug log:

 

[    9.719919] scsi4 : pata_atiixp
[    9.726470] scsi5 : pata_atiixp
[    9.730600] ata5: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xff00 irq 14
[    9.734748] ata6: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xff08 irq 15
[    9.893428] ata5.00: ATA-8: VB0250EAVER, HPG9, max UDMA/100
[    9.897910] ata5.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[    9.903037] ata5.00: limited to UDMA/33 due to 40-wire cable
[    9.914434] ata5.00: configured for UDMA/33
[    9.921341] scsi 4:0:0:0: Direct-Access     ATA      VB0250EAVER              HPG9 PQ: 0 ANSI: 5
[    9.934522] syno_disk_type_get: disk driver 'pata_atiixp'
[    9.935199] syno_disk_type_get: SATA syno_port_type 1
[    9.949450] sd_probe: Got SATA dev_prefix (sd), index (4), disk_name (), disk_len (20)
[    9.966513] sd 4:0:0:0: [sde] 488397168 512-byte logical blocks: (250 GB/232 GiB)
[    9.986160] sd 4:0:0:0: [sde] Write Protect is off
[    9.996842] sd 4:0:0:0: [sde] Mode Sense: 00 3a 00 00
[   10.007963] sd 4:0:0:0: [sde] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[   10.037812]  sde: sde1
[   10.050269] sd 4:0:0:0: [sde] Attached SCSI disk
[   10.315020] stex: Promise SuperTrak EX Driver version: 4.6.0000.4
[   10.483632] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   10.498291] sd 1:0:0:0: Attached scsi generic sg1 type 0
[   10.506497] sd 4:0:0:0: Attached scsi generic sg2 type 0

 

This lines i cant find in the 10_5 log. I know that this is the driver for the intgerated SATA-Controller of my n54l but this may prevent to load the Driver for thr SAS-HBA PERC 310 correctly!?

Edited by Guest
Link to post
Share on other sites

Sorry for may be stupid questions.

 

At the moment I am on gnoBoot 10.4 and DSM 5.0 update 2.

 

Is it Ok if I just replace zImage with the new one gnoboot-alpha10.5-zImage or put it at the same directory as old kernel and change grub menu to boot from new kernel?

 

Should I boot 1st time as gnoboot.me after any change of gnoboot zImage?

Link to post
Share on other sites

Notes:

Use /dev/gnoboot1 to mount ext2 boot image.

Thanks! That's help in name of type of boot. However, I got the following error message when trying to mount:

/ # mount -t ext2 /dev/gnoboot1 /mnt
mount: mounting /dev/gnoboot1 on /mnt failed: Invalid argument
/ #

Tried /boot and same result. I checked ext2 is available (cat /proc/filesystems). Guess the mount syntax isn't correct, right? Sorry for this basic linux question.

Link to post
Share on other sites

/ # mount -t ext2 /dev/gnoboot1 /mnt
mount: mounting /dev/gnoboot1 on /mnt failed: Invalid argument
/ #

Try using autodetection

 

# mount /dev/gnoboot1 /mnt

 

I guess you flashed the vfat-image, not ext2 :wink:

(I might be generally wrong in my understanding though :smile: )

Link to post
Share on other sites

 

 

Have you been able to get disks conected to the 9211-8i to start from Disk1-Disk8?

Do i need to blacklist any other drivers to make sure theres no unused slots before the disks on the raid card?

 

Also , Will flashing IT firmware instead of IR benifit in any way?

 

You have to blacklist the boot image disk (ata_piix) using rmmod GRUB option.

 

Put the following lines in your /boot/grub/menu_alpha.lst

 

kernel /zImage rmmod=ata_piix,r8169,r8169_new

 

I got my 9211-i8 now along with my 5bay backplate.

 

Right now im booting from a 55MB vmdk-file, and i have 3 disks connected to my 9211-8i

 

I added the paramterers you suggested and that removed 2 of the empty slots (making the disks i have connected to the raid controller disk 2,3,4 but the first "slot" is still marked as empty. is this fixable? (what more do i need to add to the rmmod?

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.