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.

Acer H340 External Enclosure

Featured Replies

I'm not sure if this is the correct forum (or if it should be in hardware), but I thought I'd give it a shot here.  I'm setting up an older Acer H340 (small form factor server originally for WHS, with 4 internal bays connected to onboard SATA, and a Marvell 6121 running an eSATA port) to run unRaid 5.0 rc8a .  I also have a Sans Digigital TR4M external enclosure, which I used on the box under WHS.  The external enclosure works fine with 1 drive in the TR4M, but doesn't detect additional drives.  I did a bit of searching and found that I should add ahci.marvell_enable=1 to syslinux.config, however this still doesn't help.  I also have another machine that I verified it isn't a hardware problem with.

 

So currently, what I see:

    The machine boots, with only 1 LED on in the TR4M for the first drive.

    Drive 1 is added to the array, but Drive 2 doesn't show up in the unRaid console or unMenu, or as an sd[x] item under /dev  like the other drives.

    There is no change when I manually do the following commands (also suggested where I saw the syslinux.config change)

        rmmod ahci

        modprobe ahci marvell_enable=1

 

In syslog I see the following lines (first 4 I think are for the 4 internal drives, then the next ones are for the Marvell, where it lists 2 errors, but then appears to list ata5 and ata6 which I would assume would be the 2 drives in the external enclosure.

 

Feb 13 07:41:53 unraid-server1 kernel: scsi0 : ahci (Drive related)

Feb 13 07:41:53 unraid-server1 kernel: scsi1 : ahci (Drive related)

Feb 13 07:41:53 unraid-server1 kernel: scsi2 : ahci (Drive related)

Feb 13 07:41:53 unraid-server1 kernel: scsi3 : ahci (Drive related)

Feb 13 07:41:53 unraid-server1 kernel: ata1: SATA max UDMA/133 abar m1024@0xf02c0400 port 0xf02c0500 irq 40 (Drive related)

Feb 13 07:41:53 unraid-server1 kernel: ata2: SATA max UDMA/133 abar m1024@0xf02c0400 port 0xf02c0580 irq 40 (Drive related)

Feb 13 07:41:53 unraid-server1 kernel: ata3: SATA max UDMA/133 abar m1024@0xf02c0400 port 0xf02c0600 irq 40 (Drive related)

Feb 13 07:41:53 unraid-server1 kernel: ata4: SATA max UDMA/133 abar m1024@0xf02c0400 port 0xf02c0680 irq 40 (Drive related)

Feb 13 07:41:53 unraid-server1 kernel: ahci 0000:0a:00.0: Disabling your PATA port. Use the boot option 'ahci.marvell_enable=0' to avoid this. (Drive related)

Feb 13 07:41:53 unraid-server1 kernel: ahci 0000:0a:00.0: controller can't do NCQ, turning off CAP_NCQ (System)

Feb 13 07:41:53 unraid-server1 kernel: ahci 0000:0a:00.0: controller can't do PMP, turning off CAP_PMP (System)

Feb 13 07:41:53 unraid-server1 kernel: ahci 0000:0a:00.0: masking port_map 0x7 -> 0x3 (Drive related)

Feb 13 07:41:53 unraid-server1 kernel: ahci: SSS flag set, parallel bus scan disabled (Drive related)

Feb 13 07:41:53 unraid-server1 kernel: ahci 0000:0a:00.0: AHCI 0001.0000 32 slots 3 ports 3 Gbps 0x3 impl IDE mode (Drive related)

Feb 13 07:41:53 unraid-server1 kernel: ahci 0000:0a:00.0: flags: 64bit stag led slum part  (Drive related)

Feb 13 07:41:53 unraid-server1 kernel: scsi4 : ahci (Drive related)

Feb 13 07:41:53 unraid-server1 kernel: scsi5 : ahci (Drive related)

Feb 13 07:41:53 unraid-server1 kernel: scsi6 : ahci (Drive related)

Feb 13 07:41:53 unraid-server1 kernel: ata5: SATA max UDMA/133 abar m1024@0xf0400000 port 0xf0400100 irq 17 (Drive related)

Feb 13 07:41:53 unraid-server1 kernel: ata6: SATA max UDMA/133 abar m1024@0xf0400000 port 0xf0400180 irq 17 (Drive related)

Feb 13 07:41:53 unraid-server1 kernel: ata7: DUMMY (Drive related).

 

Later in syslog I see "up" messages for the first 5 drives, like the following, but only a down message for ata6 (which I assume is the 6th hard drive)

 

Drive 5

Feb 13 08:32:48 unraid-server1 kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related)

Feb 13 08:32:48 unraid-server1 kernel: ata5.00: ATA-8: WDC WD20EARS-22MVWB0, 51.0AB51, max UDMA/133 (Drive related)

Feb 13 08:32:48 unraid-server1 kernel: ata5.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 0/32) (Drive related)

Feb 13 08:32:48 unraid-server1 kernel: ata5.00: configured for UDMA/133 (Drive related)

 

Drive 6

Feb 13 08:32:48 unraid-server1 kernel: ata6: SATA link down (SStatus 0 SControl 300) (Drive related)

 

I'm not sure what else to check to try narrowing this problem down, so any help would be appreciated.

  • Author

Here is the syslog, as mentioned it is 5.0 Rc 8a version on an Acer H340.

 

Hardware is as follows

  Intel Atom 230 @ 1.60 Ghz

  Intel 82801 GR/GH (ICH74) on board SATA Controller

  Marvell 6121 SATA Controller (drives the eSata port in use)

 

Syslog.txt

Here is the syslog, as mentioned it is 5.0 Rc 8a version on an Acer H340.

 

Hardware is as follows

  Intel Atom 230 @ 1.60 Ghz

  Intel 82801 GR/GH (ICH74) on board SATA Controller

  Marvell 6121 SATA Controller (drives the eSata port in use)

 

People here report that the TR4M doesn't work on the H340:

 

http://www.mediasmartserver.net/2009/09/10/setting-up-esata-port-multiplication-with-the-acer-aspire-easystore/

  • Author

It actually worked in WHS with the Acer, and seems like the hardware should be supported since I've seen other references to it working with a change to enable AHCI on the Marvell controller, (in the syslog, and attachments, it seems to see all 6 drives connected, it just can't make the 6th drive available to emhttp in unraid, possibly because it shows the 6th drive with a link status of down for some reason).

Archived

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

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.