New USB Disk Wont mount

[fvdw]

after doing some reading it might be as simple as that your device is not defined in the usb.ids database

Attached a modified version of that database.
You need to replace the existing usb.ids fil in folder /usr/share by the one in the zip archive attached.
the try again to connect your usb disk

(I assume you are familiar with winscp to copy it otherwise put in the the share with nam public , connect via ssh and copy it

Code: Select all

cp /share/1000/public/usb.ids /usr/share/

[rafesl]

ok, we are making steady though slightly unexplained progress.

Having been unable to get much done for the last few days I went to have a go last night, where I discovered the disk was now available to mount.
Happy days... no idea why the change but I'll take that.
So next I did a reboot to test and still there after that. lovely.
BUT the strange thing is that the drive is not recognised in the "USB Disks" section of the firmware.
I have done an mkfs on it so I'm sure its ok from that point of view.

I tried copying in that ids file but that didn't change anything.

Also of note is that the SMART command UI & command line aren't working. It gives an error
"/dev/sdc: Unknown USB bridge [0x0bc2:0x3320 (0x100)]"

It gives that whether or not I'm using the USB hub.

So the disk is accesible, is there any magic I can do to make it appear in the UI?

thanks for all the help so far.

Rafe

[Jocko]

Hi rafesl,

So next I did a reboot to test and still there after that. lovely.

I assume that you mean that the relevant nodes are now present in the folder /dev

BUT the strange thing is that the drive is not recognised in the "USB Disks" section of the firmware.

Please post the mount command output.

Code: Select all

mount

I think I know the reason for this. As you have a USB hub disk, the udev rules handle it as an unsupported disk

To check this suggestion. unplug your disk and in putty, start syslog service:

Code: Select all

syslogd

So now plug again your usb disk and post the file content : /var/log/messages.
If I am right, you should find lines with 'mrvlUdevdUnsupported'

Post also the output of

Code: Select all

udevinfo -a -p /sys/block/sdb/sdb1

(I assume that sdb is the device name of your usb disk, you can see that with the command 'fdisk -l')
Note: other idea, if your disk is a gpt disk, version 15.0 doesn't mount the usb disk (it's now implemented in the next version 15.1). But I will see that in messages file...

[rafesl]

Mount command:

Code: Select all


root@moviestore:/usr/bin # mount
rootfs on / type rootfs (rw)
/dev/root on / type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
/dev/sda2 on / type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
/dev/sda5 on /rw_fs type ext3 (rw,noatime,errors=continue,barrier=1,data=ordered)
tmpfs on /rw_fs/tmp/usr/var type tmpfs (rw,relatime,size=5000k)
/dev/sda8 on /share/1000 type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered)
/dev/sdb1 on /rw_fs/tmp/mnt/External_1 type fuseblk (rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
/dev/sdb1 on /share/1000/External_1 type fuseblk (rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
/dev/root on /lacie-boot type ext3 (rw,relatime,errors=continue,barrier=1,data=ordered)



cat /var/log/messages

Code: Select all


Jan 14 23:42:36 moviestore syslog.info syslogd started: BusyBox v1.21.0
Jan 14 23:42:49 moviestore local2.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/lsusb -v -d 0bc2:3320
Jan 14 23:43:01 moviestore local2.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/vol_id -l /dev/sdd1
Jan 14 23:43:01 moviestore local2.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/mkdir -m 777 -p /mnt/Volume_1
Jan 14 23:43:01 moviestore local2.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/fdisk -l /dev/sdd
Jan 14 23:43:01 moviestore local0.warn API[2014/01/14 23:43:01] exthddfunc_mountExtHdd.finc(109)[3058]: unknown filesystem ee
Jan 14 23:43:01 moviestore local2.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/mv_reg_bit_set 0x10108 6 1
Jan 14 23:43:06 moviestore local2.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/mv_reg_bit_set 0x10108 6 0



Code: Select all


root@moviestore:/usr/bin # udevinfo -a -p /sys/block/sdd/sdd1

udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all possibly useful attributes
in the udev key format.
Only attributes within one device section may be used together in one rule,
to match the device for which the node will be created.

  looking at device '/block/sdd/sdd1':
    KERNEL=="sdd1"
    SUBSYSTEM=="block"
    SYSFS{ro}=="0"
    SYSFS{dev}=="8:49"
    SYSFS{size}=="5860530176"
    SYSFS{stat}=="      11       64      600       60        0        0        0        0        0       50       60"
    SYSFS{partition}=="1"
    SYSFS{start}=="2048"
    SYSFS{discard_alignment}=="0"
    SYSFS{alignment_offset}=="0"
    SYSFS{inflight}=="       0        0"

  looking at device '/devices/platform/orion-ehci.0/usb1/1-1/1-1.3/1-1.3.4/1-1.3.4:1.0/host4/target4:0:0/4:0:0:0/block/sdd':
    ID=="sdd"
    BUS=="block"
    DRIVER==""
    SYSFS{ro}=="0"
    SYSFS{dev}=="8:48"
    SYSFS{size}=="5860533160"
    SYSFS{stat}=="      23       67      720      110        0        0        0        0        0      100      110"
    SYSFS{range}=="16"
    SYSFS{discard_alignment}=="0"
    SYSFS{events}==""
    SYSFS{ext_range}=="256"
    SYSFS{events_poll_msecs}=="-1"
    SYSFS{alignment_offset}=="0"
    SYSFS{inflight}=="       0        0"
    SYSFS{removable}=="0"
    SYSFS{capability}=="50"
    SYSFS{events_async}==""

  looking at device '/devices/platform/orion-ehci.0/usb1/1-1/1-1.3/1-1.3.4/1-1.3.4:1.0/host4/target4:0:0/4:0:0:0/block':
    ID=="block"
    BUS==""
    DRIVER==""

  looking at device '/devices/platform/orion-ehci.0/usb1/1-1/1-1.3/1-1.3.4/1-1.3.4:1.0/host4/target4:0:0/4:0:0:0':
    ID=="4:0:0:0"
    BUS=="scsi"
    DRIVER=="sd"
    SYSFS{rev}=="0711"
    SYSFS{type}=="0"
    SYSFS{scsi_level}=="7"
    SYSFS{model}=="Expansion Desk  "
    SYSFS{state}=="running"
    SYSFS{queue_type}=="none"
    SYSFS{modalias}=="scsi:t-0x00"
    SYSFS{iodone_cnt}=="0x46"
    SYSFS{iorequest_cnt}=="0x46"
    SYSFS{timeout}=="30"
    SYSFS{evt_media_change}=="0"
    SYSFS{max_sectors}=="240"
    SYSFS{ioerr_cnt}=="0x1e"
    SYSFS{queue_depth}=="1"
    SYSFS{vendor}=="Seagate "
    SYSFS{device_blocked}=="0"
    SYSFS{iocounterbits}=="32"

  looking at device '/devices/platform/orion-ehci.0/usb1/1-1/1-1.3/1-1.3.4/1-1.3.4:1.0/host4/target4:0:0':
    ID=="target4:0:0"
    BUS=="scsi"
    DRIVER==""
    SYSFS{uevent}=="DEVTYPE=scsi_target"

  looking at device '/devices/platform/orion-ehci.0/usb1/1-1/1-1.3/1-1.3.4/1-1.3.4:1.0/host4':
    ID=="host4"
    BUS=="scsi"
    DRIVER==""
    SYSFS{uevent}=="DEVTYPE=scsi_host"

  looking at device '/devices/platform/orion-ehci.0/usb1/1-1/1-1.3/1-1.3.4/1-1.3.4:1.0':
    ID=="1-1.3.4:1.0"
    BUS=="usb"
    DRIVER=="usb-storage"
    SYSFS{bInterfaceClass}=="08"
    SYSFS{modalias}=="usb:v0BC2p3320d0100dc00dsc00dp00ic08isc06ip50in00"
    SYSFS{bInterfaceSubClass}=="06"
    SYSFS{bInterfaceProtocol}=="50"
    SYSFS{bNumEndpoints}=="02"
    SYSFS{supports_autosuspend}=="1"
    SYSFS{bAlternateSetting}==" 0"
    SYSFS{bInterfaceNumber}=="00"

  looking at device '/devices/platform/orion-ehci.0/usb1/1-1/1-1.3/1-1.3.4':
    ID=="1-1.3.4"
    BUS=="usb"
    DRIVER=="usb"
    SYSFS{dev}=="189:5"
    SYSFS{bDeviceSubClass}=="00"
    SYSFS{bDeviceProtocol}=="00"
    SYSFS{devpath}=="1.3.4"
    SYSFS{idVendor}=="0bc2"
    SYSFS{speed}=="480"
    SYSFS{bNumInterfaces}==" 1"
    SYSFS{bConfigurationValue}=="1"
    SYSFS{bMaxPacketSize0}=="64"
    SYSFS{busnum}=="1"
    SYSFS{devnum}=="6"
    SYSFS{configuration}==""
    SYSFS{bMaxPower}=="100mA"
    SYSFS{authorized}=="1"
    SYSFS{bmAttributes}=="c0"
    SYSFS{bNumConfigurations}=="1"
    SYSFS{maxchild}=="0"
    SYSFS{bcdDevice}=="0100"
    SYSFS{avoid_reset_quirk}=="0"
    SYSFS{quirks}=="0x0"
    SYSFS{serial}=="NA4MBKFM"
    SYSFS{version}==" 2.10"
    SYSFS{urbnum}=="348"
    SYSFS{ltm_capable}=="no"
    SYSFS{manufacturer}=="Seagate"
    SYSFS{removable}=="unknown"
    SYSFS{idProduct}=="3320"
    SYSFS{bDeviceClass}=="00"
    SYSFS{product}=="Expansion Desk"

  looking at device '/devices/platform/orion-ehci.0/usb1/1-1/1-1.3':
    ID=="1-1.3"
    BUS=="usb"
    DRIVER=="usb"
    SYSFS{dev}=="189:2"
    SYSFS{bDeviceSubClass}=="00"
    SYSFS{bDeviceProtocol}=="01"
    SYSFS{devpath}=="1.3"
    SYSFS{idVendor}=="058f"
    SYSFS{speed}=="480"
    SYSFS{bNumInterfaces}==" 1"
    SYSFS{bConfigurationValue}=="1"
    SYSFS{bMaxPacketSize0}=="64"
    SYSFS{busnum}=="1"
    SYSFS{devnum}=="3"
    SYSFS{configuration}==""
    SYSFS{bMaxPower}=="100mA"
    SYSFS{authorized}=="1"
    SYSFS{bmAttributes}=="e0"
    SYSFS{bNumConfigurations}=="1"
    SYSFS{maxchild}=="4"
    SYSFS{bcdDevice}=="0100"
    SYSFS{avoid_reset_quirk}=="0"
    SYSFS{quirks}=="0x0"
    SYSFS{version}==" 2.00"
    SYSFS{urbnum}=="54"
    SYSFS{ltm_capable}=="no"
    SYSFS{removable}=="unknown"
    SYSFS{idProduct}=="6254"
    SYSFS{bDeviceClass}=="09"

  looking at device '/devices/platform/orion-ehci.0/usb1/1-1':
    ID=="1-1"
    BUS=="usb"
    DRIVER=="usb"
    SYSFS{dev}=="189:1"
    SYSFS{bDeviceSubClass}=="00"
    SYSFS{bDeviceProtocol}=="01"
    SYSFS{devpath}=="1"
    SYSFS{idVendor}=="058f"
    SYSFS{speed}=="480"
    SYSFS{bNumInterfaces}==" 1"
    SYSFS{bConfigurationValue}=="1"
    SYSFS{bMaxPacketSize0}=="64"
    SYSFS{busnum}=="1"
    SYSFS{devnum}=="2"
    SYSFS{configuration}==""
    SYSFS{bMaxPower}=="100mA"
    SYSFS{authorized}=="1"
    SYSFS{bmAttributes}=="e0"
    SYSFS{bNumConfigurations}=="1"
    SYSFS{maxchild}=="4"
    SYSFS{bcdDevice}=="0100"
    SYSFS{avoid_reset_quirk}=="0"
    SYSFS{quirks}=="0x0"
    SYSFS{version}==" 2.00"
    SYSFS{urbnum}=="39"
    SYSFS{ltm_capable}=="no"
    SYSFS{removable}=="unknown"
    SYSFS{idProduct}=="6254"
    SYSFS{bDeviceClass}=="09"

  looking at device '/devices/platform/orion-ehci.0/usb1':
    ID=="usb1"
    BUS=="usb"
    DRIVER=="usb"
    SYSFS{dev}=="189:0"
    SYSFS{bDeviceSubClass}=="00"
    SYSFS{bDeviceProtocol}=="01"
    SYSFS{devpath}=="0"
    SYSFS{idVendor}=="1d6b"
    SYSFS{speed}=="480"
    SYSFS{bNumInterfaces}==" 1"
    SYSFS{bConfigurationValue}=="1"
    SYSFS{bMaxPacketSize0}=="64"
    SYSFS{authorized_default}=="1"
    SYSFS{busnum}=="1"
    SYSFS{devnum}=="1"
    SYSFS{configuration}==""
    SYSFS{bMaxPower}=="0mA"
    SYSFS{authorized}=="1"
    SYSFS{bmAttributes}=="e0"
    SYSFS{bNumConfigurations}=="1"
    SYSFS{maxchild}=="1"
    SYSFS{bcdDevice}=="0309"
    SYSFS{avoid_reset_quirk}=="0"
    SYSFS{quirks}=="0x0"
    SYSFS{serial}=="orion-ehci.0"
    SYSFS{version}==" 2.00"
    SYSFS{urbnum}=="25"
    SYSFS{ltm_capable}=="no"
    SYSFS{manufacturer}=="Linux 3.9.5 ehci_hcd"
    SYSFS{removable}=="unknown"
    SYSFS{idProduct}=="0002"
    SYSFS{bDeviceClass}=="09"
    SYSFS{product}=="Marvell Orion EHCI"

  looking at device '/devices/platform/orion-ehci.0':
    ID=="orion-ehci.0"
    BUS=="platform"
    DRIVER=="orion-ehci"
    SYSFS{modalias}=="platform:orion-ehci"
    SYSFS{uframe_periodic_max}=="100"

  looking at device '/devices/platform':
    ID=="platform"
    BUS==""
    DRIVER==""
    SYSFS{uevent}==""


I'm fairly sure it is a gpt disk.

One other thing I noticed. I was able to do an mkfs.ext4 on it.... which I'm assuming would work like an mkfs -t ext4 on other Linux systems. But I was then unable to mount the disk. Once I redid it as an mkfs.ext3 I was able to mount no problem. The error given was that ext4 was an unknown file system type.

Thank you.

Rafe

[Jocko]

Hi rasefl,

Indeed your disk is a gpt disk

Code: Select all

Jan 14 23:43:01 moviestore local0.warn API[2014/01/14 23:43:01] exthddfunc_mountExtHdd.finc(109)[3058]: unknown filesystem ee

So you have two solutions :
- wait the next version (make a patch for version 15.0 it's not handy because currently many files are updated and need a big job to control if they can run with version 15.0)
- reformat your disk to get a dos disk (use gdisk and destroy the gpt structure) and use fdisk to make the new partition table

[rafesl]

Thanks for that.

I'll have a play this evening and decide what to do.

Rafe

[rafesl]

With the new FW its up and operational.
Thank you so much guys for all the help and the new version.

One thing which didn't work completely properly initially was that a "df -k" was throwing up an error about "/share/1000/Volume_1" not existing.
I created the file manually and then all was happy.
Later on I went back and removed the directory and created a symlink instead to /rwfs/tmp/Volume_1 (that path may not be exact but its similar at least).
Is that ok?

I have 2 disks attached via a powered USB hub. One is coming up on /share/1000/External_1 and the other /share/1000/Volume_1. Is that intentional or an oversight as a result of the new gpt etc support? I'm operational so I dont mind, just curious.

Thanks again.

Rafe

[fvdw]

Need to talk with Jocko on your last remark. He made some changes in te scripts. But if I remember correct the disk are mounted using the disk label as mount point with /share/1000 as prefix, so if the the disk labels are External_1 and Volume_1 then what you described is correct.
But need to have a closer look at the script.
Are the labels of the two usb disks corresponding with these names of the mountpoint ?

[Jocko]

I have 2 disks attached via a powered USB hub. One is coming up on /share/1000/External_1 and the other /share/1000/Volume_1. Is that intentional or an oversight as a result of the new gpt etc support? I'm operational so I dont mind, just curious.

As writing by fvdw, this is the standard behavior:
if the mounted partition has a label then the mount point is : label_partitionnumber (=> External_1)
if the mounted partition doesn't have a label then mount point is : Volume_partitionnumber (=> Volume_1)

otherwise I don't understand well why do you want to play with the mountpoint "Volume_1" (symlink,...)

[rafesl]

otherwise I don't understand well why do you want to play with the mountpoint "Volume_1" (symlink,...)

The only reason is because of transmission.
It defaults to saving to /share/1000/tr-downloads.
But I'm low on space there, so after I start a download, I tend to move the save location to the new disk. Rather than trying to remember the /rwfs/ICANTREMEMBETHENEXTBIT I just just /share/1000/Volume_1. Easy ;) .