Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

Any thoughts/experience with this controller?

rick.p
in Storage Devices and Controllers

Featured Replies

Simpler but not effective. Yes, the SY-PEX40013  is a 4 sata port. Two sata II ports and two sata I ports interfaced onto the IDE port of the JMB363 controller. I personally would not use it beyond the two sata II ports, there are cheaper alternatives for two ports.

 

If you're desperate, only use one of the SATA I ports for a total  of 3 drives.

 

Do yourself a favor a search on SY-PEX40013.

 

PB

  • Quote
    • 8 months later...

    Simpler but not effective. Yes, the SY-PEX40013  is a 4 sata port. Two sata II ports and two sata I ports interfaced onto the IDE port of the JMB363 controller. I personally would not use it beyond the two sata II ports, there are cheaper alternatives for two ports.

     

    If you're desperate, only use one of the SATA I ports for a total  of 3 drives.

     

    Do yourself a favor a search on SY-PEX40013.

     

    PB

     

    I wish I would of read this =)  Been swapping cables trying to figure out why one drive was only coming up at 1.5G.  Now any clue which port is which?  Gonna pull the card and check.

     

    Thanks!

  • Quote

    According to the description on amazon:

     

    2x SATA I (J3&J4) and 2x SATA II (J1&J2) ports

     

    Hope this helps.

  • Quote

    According to the description on amazon:

     

    2x SATA I (J3&J4) and 2x SATA II (J1&J2) ports

     

    Hope this helps.

     

    Thanks!

     

    That did help, at least it explains why my tower went haywire when I connected the 7th drive.  It was the cache drive and would bring the box down.

     

    Still seing some errors, but it's doing the parity check at 90-110MB/sec, which is better than 1MB.  =)

     

    Errors I'm seing are:

     

    Nov 30 22:55:48 Tower kernel: REISERFS (device md2): checking transaction log (md2)

    Nov 30 22:55:48 Tower kernel: REISERFS (device md2): Using r5 hash to sort names

    Nov 30 22:55:48 Tower emhttp: shcmd (22): chmod 770 '/mnt/disk2'

    Nov 30 22:55:48 Tower emhttp: shcmd (23): chown nobody:users '/mnt/disk2'

    Nov 30 22:55:48 Tower emhttp: shcmd (24): mkdir /mnt/disk3

    Nov 30 22:55:48 Tower emhttp: shcmd (25): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md3 /mnt/disk3 |& logger

    Nov 30 22:55:48 Tower kernel: REISERFS (device md3): found reiserfs format "3.6" with standard journal

    Nov 30 22:55:48 Tower kernel: REISERFS (device md3): using ordered data mode

    Nov 30 22:55:48 Tower kernel: REISERFS (device md3): journal params: device md3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

    Nov 30 22:55:48 Tower kernel: REISERFS (device md3): checking transaction log (md3)

    Nov 30 22:55:48 Tower kernel: REISERFS (device md3): Using r5 hash to sort names

    Nov 30 22:55:48 Tower emhttp: shcmd (26): chmod 770 '/mnt/disk3'

    Nov 30 22:55:48 Tower emhttp: shcmd (27): chown nobody:users '/mnt/disk3'

    Nov 30 22:55:48 Tower emhttp: shcmd (28): mkdir /mnt/disk4

    Nov 30 22:55:48 Tower emhttp: shcmd (29): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md4 /mnt/disk4 |& logger

    Nov 30 22:55:48 Tower kernel: REISERFS (device md4): found reiserfs format "3.6" with standard journal

    Nov 30 22:55:48 Tower kernel: REISERFS (device md4): using ordered data mode

    Nov 30 22:55:48 Tower kernel: REISERFS (device md4): journal params: device md4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

    Nov 30 22:55:48 Tower kernel: REISERFS (device md4): checking transaction log (md4)

    Nov 30 22:55:48 Tower kernel: REISERFS (device md4): Using r5 hash to sort names

    Nov 30 22:55:48 Tower emhttp: shcmd (30): chmod 770 '/mnt/disk4'

    Nov 30 22:55:48 Tower emhttp: shcmd (31): chown nobody:users '/mnt/disk4'

    Nov 30 22:55:48 Tower emhttp: shcmd (32): mkdir /mnt/disk5

    Nov 30 22:55:48 Tower emhttp: shcmd (33): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md5 /mnt/disk5 |& logger

    Nov 30 22:55:48 Tower kernel: REISERFS (device md5): found reiserfs format "3.6" with standard journal

    Nov 30 22:55:48 Tower kernel: REISERFS (device md5): using ordered data mode

    Nov 30 22:55:48 Tower kernel: REISERFS (device md5): journal params: device md5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30

    Nov 30 22:55:48 Tower kernel: REISERFS (device md5): checking transaction log (md5)

    Nov 30 22:55:48 Tower kernel: REISERFS (device md5): Using r5 hash to sort names

    Nov 30 22:55:48 Tower emhttp: shcmd (34): chmod 770 '/mnt/disk5'

    Nov 30 22:55:48 Tower emhttp: shcmd (35): chown nobody:users '/mnt/disk5'

    Nov 30 22:55:49 Tower emhttp: shcmd (36): mkdir /mnt/user

    Nov 30 22:55:49 Tower emhttp: shcmd (37): /usr/local/sbin/shfs /mnt/user -disks 2097150 -o noatime,big_writes,allow_other,default_permissions,use_ino

    Nov 30 22:55:49 Tower emhttp: shcmd (38): crontab -c /etc/cron.d -d &> /dev/null

    Nov 30 22:55:49 Tower emhttp: shcmd (39): /usr/local/sbin/emhttp_event disks_mounted

    Nov 30 22:55:49 Tower emhttp_event: disks_mounted

    Nov 30 22:55:49 Tower emhttp: shcmd (40): :>/etc/samba/smb-shares.conf

    Nov 30 22:55:49 Tower emhttp: shcmd (41): cp /etc/exports- /etc/exports

    Nov 30 22:55:49 Tower emhttp: shcmd (42): echo '/mnt/user/ISO -async,no_subtree_check,fsid=100 *(rw,insecure,anongid=100,anonuid=99,all_squash)' >>/etc/exports

    Nov 30 22:55:49 Tower emhttp: Restart SMB...

    Nov 30 22:55:49 Tower emhttp: shcmd (43): killall -HUP smbd

    Nov 30 22:55:49 Tower emhttp: shcmd (44): ps axc | grep -q rpc.mountd

    Nov 30 22:55:49 Tower emhttp: _shcmd: shcmd (44): exit status: 1

    Nov 30 22:55:49 Tower emhttp: Start NFS...

    Nov 30 22:55:49 Tower emhttp: shcmd (45): /etc/rc.d/rc.nfsd start |& logger

    Nov 30 22:55:49 Tower logger: Starting NFS server daemons:

    Nov 30 22:55:49 Tower logger:  /usr/sbin/exportfs -r

    Nov 30 22:55:49 Tower logger:  /usr/sbin/rpc.nfsd 8

    Nov 30 22:55:49 Tower logger:  /usr/sbin/rpc.mountd

    Nov 30 22:55:49 Tower mountd[1985]: Kernel does not have pseudo root support.

    Nov 30 22:55:49 Tower mountd[1985]: NFS v4 mounts will be disabled unless fsid=0

    Nov 30 22:55:49 Tower mountd[1985]: is specfied in /etc/exports file.

    Nov 30 22:55:49 Tower emhttp: shcmd (46): /usr/local/sbin/emhttp_event svcs_restarted

    Nov 30 22:55:49 Tower emhttp_event: svcs_restarted

    Nov 30 22:55:49 Tower kernel: sky2 0000:03:00.0: eth0: Link is up at 1000 Mbps, full duplex, flow control both

    Nov 30 22:56:07 Tower in.telnetd[1990]: connect from 192.168.1.3 (192.168.1.3)

    Nov 30 22:56:08 Tower login[1991]: invalid password for 'UNKNOWN'  on '/dev/pts/0' from 'new-host.home'

    Nov 30 22:56:11 Tower login[1991]: ROOT LOGIN  on '/dev/pts/0' from 'new-host.home'

    root@Tower:/var/log# tail -f /var/log/syslog 

    Nov 30 22:55:49 Tower emhttp: shcmd (46): /usr/local/sbin/emhttp_event svcs_restarted

    Nov 30 22:55:49 Tower emhttp_event: svcs_restarted

    Nov 30 22:55:49 Tower kernel: sky2 0000:03:00.0: eth0: Link is up at 1000 Mbps, full duplex, flow control both

    Nov 30 22:56:07 Tower in.telnetd[1990]: connect from 192.168.1.3 (192.168.1.3)

    Nov 30 22:56:08 Tower login[1991]: invalid password for 'UNKNOWN'  on '/dev/pts/0' from 'new-host.home'

    Nov 30 22:56:11 Tower login[1991]: ROOT LOGIN  on '/dev/pts/0' from 'new-host.home'

    Nov 30 22:58:37 Tower kernel: mdcmd (23): check CORRECT

    Nov 30 22:58:37 Tower kernel: md: recovery thread woken up ...

    Nov 30 22:58:37 Tower kernel: md: recovery thread checking parity...

    Nov 30 22:58:37 Tower kernel: md: using 1536k window, over a total of 2930266532 blocks.

    ^[[A

    Nov 30 22:59:02 Tower kernel: md: parity incorrect: 4539784

    Nov 30 22:59:04 Tower kernel: md: parity incorrect: 4807336

    Nov 30 22:59:08 Tower kernel: md: parity incorrect: 5365616

    Nov 30 22:59:34 Tower kernel: ata7.00: exception Emask 0x32 SAct 0x0 SErr 0x0 action 0xe frozen

    Nov 30 22:59:34 Tower kernel: ata7.00: irq_stat 0xffffffff, unknown FIS 00000000 00000000 00000000 00000000, host bus

    Nov 30 22:59:34 Tower kernel: ata7.00: failed command: READ DMA EXT

    Nov 30 22:59:34 Tower kernel: ata7.00: cmd 25/00:00:78:37:92/00:04:00:00:00/e0 tag 0 dma 524288 in

    Nov 30 22:59:34 Tower kernel:          res 50/00:00:77:3b:92/00:00:00:00:00/e0 Emask 0x32 (host bus error)

    Nov 30 22:59:34 Tower kernel: ata7.00: status: { DRDY }

    Nov 30 22:59:34 Tower kernel: ata7: hard resetting link

    Nov 30 22:59:35 Tower kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

    Nov 30 22:59:35 Tower kernel: ata7.00: configured for UDMA/133

    Nov 30 22:59:35 Tower kernel: ata7: EH complete

    Nov 30 23:00:27 Tower kernel: ata7: illegal qc_active transition (00000001->ffffffff)

    Nov 30 23:00:27 Tower kernel: ata7.00: exception Emask 0x2 SAct 0x0 SErr 0x0 action 0x6 frozen

    Nov 30 23:00:27 Tower kernel: ata7.00: failed command: READ DMA EXT

    Nov 30 23:00:27 Tower kernel: ata7.00: cmd 25/00:00:10:9b:28/00:04:01:00:00/e0 tag 0 dma 524288 in

    Nov 30 23:00:27 Tower kernel:          res 50/00:00:0f:9f:28/00:00:01:00:00/e0 Emask 0x2 (HSM violation)

    Nov 30 23:00:27 Tower kernel: ata7.00: status: { DRDY }

    Nov 30 23:00:27 Tower kernel: ata7: hard resetting link

    Nov 30 23:00:27 Tower kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

    Nov 30 23:00:27 Tower kernel: ata7.00: configured for UDMA/133

    Nov 30 23:00:27 Tower kernel: ata7: EH complete

    Nov 30 23:00:34 Tower kernel: ata7: illegal qc_active transition (00000001->ffffffff)

    Nov 30 23:00:34 Tower kernel: ata7.00: exception Emask 0x2 SAct 0x0 SErr 0x0 action 0x6 frozen

    Nov 30 23:00:34 Tower kernel: ata7.00: failed command: READ DMA EXT

    Nov 30 23:00:34 Tower kernel: ata7.00: cmd 25/00:00:28:78:3b/00:04:01:00:00/e0 tag 0 dma 524288 in

    Nov 30 23:00:34 Tower kernel:          res 50/00:00:27:7c:3b/00:00:01:00:00/e0 Emask 0x2 (HSM violation)

    Nov 30 23:00:34 Tower kernel: ata7.00: status: { DRDY }

    Nov 30 23:00:34 Tower kernel: ata7: hard resetting link

    Nov 30 23:00:35 Tower kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

    Nov 30 23:00:35 Tower kernel: ata7.00: configured for UDMA/133

    Nov 30 23:00:35 Tower kernel: ata7: EH complete

    Nov 30 23:03:31 Tower kernel: ata8: illegal qc_active transition (00000001->ffffffff)

    Nov 30 23:03:31 Tower kernel: ata8.00: exception Emask 0x2 SAct 0x0 SErr 0x0 action 0x6 frozen

    Nov 30 23:03:31 Tower kernel: ata8.00: failed command: READ DMA EXT

    Nov 30 23:03:31 Tower kernel: ata8.00: cmd 25/00:00:88:c6:40/00:04:03:00:00/e0 tag 0 dma 524288 in

    Nov 30 23:03:31 Tower kernel:          res 50/00:00:87:ca:40/00:00:03:00:00/e0 Emask 0x2 (HSM violation)

    Nov 30 23:03:31 Tower kernel: ata8.00: status: { DRDY }

    Nov 30 23:03:31 Tower kernel: ata8: hard resetting link

    Nov 30 23:03:32 Tower kernel: ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

    Nov 30 23:03:32 Tower kernel: ata8.00: configured for UDMA/133

    Nov 30 23:03:32 Tower kernel: ata8: EH complete

    Nov 30 23:03:56 Tower kernel: ata8: illegal qc_active transition (00000001->ffffffff)

    Nov 30 23:03:56 Tower kernel: ata8.00: exception Emask 0x2 SAct 0x0 SErr 0x0 action 0x6 frozen

    Nov 30 23:03:56 Tower kernel: ata8.00: failed command: READ DMA EXT

    Nov 30 23:03:56 Tower kernel: ata8.00: cmd 25/00:00:58:a3:88/00:04:03:00:00/e0 tag 0 dma 524288 in

    Nov 30 23:03:56 Tower kernel:          res 50/00:00:57:a7:88/00:00:03:00:00/e0 Emask 0x2 (HSM violation)

    Nov 30 23:03:56 Tower kernel: ata8.00: status: { DRDY }

    Nov 30 23:03:56 Tower kernel: ata8: hard resetting link

    Nov 30 23:03:57 Tower kernel: ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

    Nov 30 23:03:57 Tower kernel: ata8.00: configured for UDMA/133

    Nov 30 23:03:57 Tower kernel: ata8: EH complete

    Nov 30 23:04:20 Tower kernel: ata8.00: exception Emask 0x32 SAct 0x0 SErr 0x0 action 0xe frozen

    Nov 30 23:04:20 Tower kernel: ata8.00: irq_stat 0xffffffff, unknown FIS 00000000 00000000 00000000 00000000, host bus

    Nov 30 23:04:20 Tower kernel: ata8.00: failed command: READ DMA EXT

    Nov 30 23:04:20 Tower kernel: ata8.00: cmd 25/00:00:b0:20:cd/00:04:03:00:00/e0 tag 0 dma 524288 in

    Nov 30 23:04:20 Tower kernel:          res 50/00:00:af:24:cd/00:00:03:00:00/e0 Emask 0x32 (host bus error)

    Nov 30 23:04:20 Tower kernel: ata8.00: status: { DRDY }

    Nov 30 23:04:20 Tower kernel: ata8: hard resetting link

    Nov 30 23:04:21 Tower kernel: ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

    Nov 30 23:04:21 Tower kernel: ata8.00: configured for UDMA/133

    Nov 30 23:04:21 Tower kernel: ata8: EH complete

     

     

  • Quote

    • Archived

    This topic is now archived and is closed to further replies.

    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.