USB drives shown as internal disks


Recommended Posts

Hello everyone,

 

I got my xpenology box almost perfectly running on DSM 5.2.

My only problem is, that any USB drive I plug in is shown as an internal hard drive.

 

I changed the synoinfo.conf to support my 25 drive bay.

 

These are my changes :

0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000     0x0000             (ESATA)
0000 0000 0000 0000 0001 1111 1111 1111 1111 1111 1111     0x1ffffff           (SATA)
0000 0011 1111 1111 1100 0000 0000 0000 0000 0000 0000     0x3ffc000000    (USB)

 

I hope someone can give me a solution for this problem.

 

Best regards Adrian

Link to post
Share on other sites

if you don't need, or don't plan to use USB drives

 

you can simply set USB to Zero

 

You can still boot from the USB drive, even when you set the USB drive to zero.

 

XPEnology will just ignore USB ports after the DSM OS is loaded.

Link to post
Share on other sites

AllGamer has a good point - set the USB and Esata to '0's so that you can debug the internal drives settings. Once thats working right you can tweak the USB

 

another thought is to start the usb count from the next 'binary block' eg

 

0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0x0000000000 (ESATA)

0000 0000 0000 0001 1111 1111 1111 1111 1111 1111 0x0001ffffff (SATA)

1111 1111 1111 0000 0000 0000 0000 0000 0000 0000 0xfff0000000 (USB)

Link to post
Share on other sites

yup, that's what I do when I'm troubleshooting controller / missing HDD issues.

 

I first disable both USB and eSATA to find and make sure everything is working, before adding the USB back into the config file.

 

It's a lot less headache to figure out why some disk are not being seen.

 

most of the time are the Onboard SATA / IDE ports from the motherboards playing tricks.

 

I noticed most time, even when you "Disable" the onboard SATA / IDE in the BIOS they are still seen by XPEnology DSM and that can causes weird things.

So, I've learned it's best to always leave them "Enabled" in BIOS, then let XPE DSM sort it out after boot.

 

That means using the example above, if you planned to use 25 disk (25 SATA ports), and you got exactly some controllers that gives you exactly 25 ports, you will have to add the extra SATA / IDE ports from your motherboard, assuming the motherboard supports 6 SATA + 2 IDE then your actual number should be 31 drives or 33 drives depending how the IDE ports are being treated.

 

IDE are recognized differently from motherboard to motherboard, sometimes they are recognized as part of the SATA, sometimes properly identified as PATA.

Link to post
Share on other sites
  • 9 months later...
  • 1 month later...

I hate to help necro a year old thread BUT.

 

1. The original posters problem was never fixed. When he says the USB drives are showing up as internal drives, how is disabling USB a solution at all????

 

2. I have the same issue and have tried several things to no avail.

 

I have a 24 bay RAID setup plus 2 onboard ASRock SATA ports that are enabled. By my math that should be 26 ports.

 

If I have 12 drives plugged in (10 on the RAID, 2 on the ASRock SATA ports), I plug in the USB drive and it comes up as the port 21 internal drive.

 

I've plugged in 21 hard drives, and it fills slots 1-21. When I plug in a USB drive then, it comes up as drive 22, still showing as an internal hard drive.

 

I intend to use the USB drive for the Key Manager, which doesn't allow you to save to any drive except a USB drive.

 

With the original config, the USB drives work perfect, but all the additional hard drives beyond 12 show up as eSata:

maxdisks="12"

esataportcfg="0xff000"

internalportcfg="0xfff"

usbportcfg="0x300000"

 

Set as 24 ports with esata enabled, the USB Drives show up as internal drives, and cannot be selected for the encryption manager:

maxdisks="24"

esataportcfg="0xff000000"

internalportcfg="0xffffff"

usbportcfg="0x300000000"

 

Set as 26 ports with esata disabled and 6 USB ports, same problem with the USB drives:

maxdisks="26"

esataportcfg="0x0"

internalportcfg="0x3ffffff"

usbportcfg="0xfc000000"

 

So I thought, possibly I need to set it to only 20 disks so that the 21st disk would come up as a USB Drive, but even set as only 20 internal disks, the thumb drive comes up as an internal disk 21.

 

Anyone else run into this or have a solution?

 

Thanks in advance.

 

Edit: I've also tried kicking it all the way up to 32 ports, but the system just goes into a reboot and prompts to re-install Synology.

Also just tried doing another edit at only 28 drives with the same thing rebooting and asking to re-install synology.

 

Notes about the system:

I'm using Xpenology with Jun's Mod 1.02-alpha, a Lsi Sas 9201-16I and an Intel Port expander. All of the drives are seen fine, it's just the USB drives that I'm having a problem with.

Link to post
Share on other sites
  • 3 years later...

Sorry to reopen this old thread, but did this ever get resolved? I have a 16x HDD (connected via two LSI 9211 controllers), 2x SSD (Cache on internal SATA ports), not using eSATA, but need the USB to show up as USB (not in storage manager).

 

The reason for the USB is for back up. It is 2x faster to back-up data with direct connect then to do it of GigE. Thanks in advance if anyone has solved this issue. Here are my current setting. If I go back to original file all works. I am on 3517xs with

 

maxdisks="24"

esataportcfg="0xff000000"

internalportcfg="0xffffff"

usbportcfg="0x300000000"

Link to post
Share on other sites
23 hours ago, powerplyer said:

Sorry to reopen this old thread, but did this ever get resolved? I have a 16x HDD (connected via two LSI 9211 controllers), 2x SSD (Cache on internal SATA ports), not using eSATA, but need the USB to show up as USB (not in storage manager).

 

you could try this, the usb position where the drives "start" is the same as in the original config

maxdisks="20"

internalportcfg="0xfffff"

esataportcfg="0x0"

usbportcfg="0xf00000"

Edited by IG-88
Link to post
Share on other sites

As always thank you very much IG-88. I need 24 ports. My configuration:

 

Supermicro X10 motherboard

6x SATA (internal ports)

16x SAS/SATA ports (2x HBA LSI 9211-8i)

2x USB 3.0 (For external drive connection)

NO eSATA ports. 

3617xs

 

Here is how I got is working. The key was not to mess with the usbportcfg settings.

maxdisks="24"
0000 0000 0000 0000 0000 0000 0000 0000 => esataportcfg ==>"0x0000 0000"
0000 0000 0011 0000 0000 0000 0000 0000 => usbportcfg ==>"0x0030 0000"
0000 1111 0000 1111 1111 1111 1111 1111 => internalportcfg ==>"0x0f0f ffff"

 

FYI still have not installed all the drives, but verified I "see" 24 open ports and USB is working as a USB device vs a USB internal storage. I will update once I have the system up and running. 

 

 

Edited by powerplyer
Link to post
Share on other sites
6 hours ago, powerplyer said:

internalportcfg ==>"0x0f0f ffff"

before relying on that it might be a good idea to check if the last 4 ports are really working in a raid set

there seems to be a 24 drive border but i'm not sure where exactly this is coming from, it was assumed to be related to single digit sdX drive assignment but i have seen a sdXX working lately with a controller "blocking" 32 positions (the layout and max was 16 in 918+ config)

the approved layout is within the first 24 in absolute positions in that bit layout of drive positions, anything beyond that is not really tested and from my point of view unsafe until its tested (like adding a raid drive or replacing a raid drive on that positions)

you will not use them now and might add drives later so if there is a problem you might get it out of the blue in a year or so when you don't remember that you did some special config

Link to post
Share on other sites
9 hours ago, IG-88 said:

before relying on that it might be a good idea to check if the last 4 ports are really working in a raid set

there seems to be a 24 drive border but i'm not sure where exactly this is coming from, it was assumed to be related to single digit sdX drive assignment but i have seen a sdXX working lately with a controller "blocking" 32 positions (the layout and max was 16 in 918+ config)

the approved layout is within the first 24 in absolute positions in that bit layout of drive positions, anything beyond that is not really tested and from my point of view unsafe until its tested (like adding a raid drive or replacing a raid drive on that positions)

you will not use them now and might add drives later so if there is a problem you might get it out of the blue in a year or so when you don't remember that you did some special config

Great feedback, had to order a backplane so will test it out once it arrives. thank you

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.