USB drive not accessible

[robbiz]

installed a N5200 (fw ver 1.00.03) few days ago, 2 seagate 250GiB disks as raid1. setup users, groups works fine, access OK
planned to use 2 USB-drives for backup
connected 1st drive appeared as 'usbhdd' ; after disconnecting the drive data remained accessible.
connected 2nd drive data of 1st drive still accessible
('storage' screen showed USB disk present or not correct)
? is this 'usbhdd' folder stored on the raid ?

after reading the faq in the thecus download area (Before attaching an eSATA or USB disk drive to N5200, you have to partition and format it on a desktop computer or a notebook first) I made partitions with ext3, ntfs and fat32 on the usb-drives, but since then I never could access the drives again (no rights, network path not found)
? anyone with any idea ?

[robbiz]

USB-drives next chapter

my vendor told me to upgrade to 1.00.04 firmware. upgrade succeeded - still no access to USB port
I gave up
Anyway it wasn't a good idea with the backup via N5200 USB port.
Backup is done by the workstation! So even if USB would work, backup-data had to go 2 times over the LAN-wire (the backup-process is running on the workstation not on the N5200!)
Now USB-drives are connected to the workstation (they're doing fine) and backup-date are going across the LAN only one time.

[omega]

Hi robbiz,

today I tried to connect a USB drive to my N5200 too - and - no success....

So I checked what's going on when connecting a USB drive and I've found out, that the mount command is producing an error.
The reason for the error is that the mount uses the iochaset=utf8 option which is not available for ext2/3 and many other filesystems.
But it should work for NTFS filesystems (but only read-only).

Whenever a USB drive is connected to the N5200, the script /app/bin/usb.hotplug is called. Here is a (sh -x) trace of that script when it is called:

+ mkdir=/bin/mkdir
+ rmdir=/bin/rmdir
+ dir=
+ usbpath=/raid/data/usbhdd/
++ echo
++ cut -d : -f 1
++ cut -d - -f 2
+ usb_ports=
+ echo '/app/bin/usb.hotplug add '
+ case "$1" in
+ add_usb
+ led=0
+ led1=0
++ df
++ awk '/\/raid\/data/||/\/raid\/sys/'
+ raid='/dev/vg0/lv0 1456634992 308930568 1073711620 22% /raid/data
/dev/vg0/syslv 1032088 32880 946780 3% /raid/sys'
+ '[' '/dev/vg0/lv0 1456634992 308930568 1073711620 22% /raid/data
/dev/vg0/syslv 1032088 32880 946780 3% /raid/sys' '!=' '' ']'
+ sleep 5
++ cat /proc/scsi/scsi
++ awk '/Thecus:/{FS=" ";printf("%s:%s\n",$2,$3)}'
++ awk -F: '{if ($2>8) {printf("%s\n",$4)}}'
+ normal=sdf
+ for i in '$normal'
+ strExec='cat /proc/partitions|awk '\''/sdf/{FS=" ";print $4}'\'''
++ eval cat '/proc/partitions|awk' ''\''/sdf/{FS="' '";print' '$4}'\'''
+++ cat /proc/partitions
+++ awk '/sdf/{FS=" ";print $4}'
+ mount_usbs='sdf
sdf1'
+ for mount_usb in '$mount_usbs'
++ mount
++ grep '/dev/sdf '
+ chkmount=
+ '[' '' == '' ']'
+ /bin/mkdir -p /raid/data/usbhdd//sdf
+ echo 'Copy 1'
+ /bin/mount -o iocharset=utf8,umask=0,fmask=001,uid=99,gid=99 /dev/sdf /raid/data/usbhdd//sdf
mount: you must specify the filesystem type
+ '[' 32 -eq 0 ']'
+ sleep 5
++ mount
++ grep '/dev/sdf '
+ mount_ok=
+ '[' '' == '' ']'
+ /bin/rmdir -p /raid/data/usbhdd//sdf
rmdir: `/raid/data': Device or resource busy
+ for mount_usb in '$mount_usbs'
++ mount
++ grep '/dev/sdf1 '
+ chkmount=
+ '[' '' == '' ']'
+ /bin/mkdir -p /raid/data/usbhdd//sdf1
+ echo 'Copy 1'
+ /bin/mount -o iocharset=utf8,umask=0,fmask=001,uid=99,gid=99 /dev/sdf1 /raid/data/usbhdd//sdf1
mount: wrong fs type, bad option, bad superblock on /dev/sdf1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

+ '[' 32 -eq 0 ']'
+ sleep 5
++ mount
++ grep '/dev/sdf1 '
+ mount_ok=
+ '[' '' == '' ']'
+ /bin/rmdir -p /raid/data/usbhdd//sdf1
rmdir: `/raid/data': Device or resource busy
+ '[' 0 -ge 1 ']'
+ '[' 0 = 0 ']'
+ '[' 0 = 1 ']'
+ echo 'Copy 0'
+ echo 'Copy 0'


I will think about a workaround for this problem. The problem is, the directory where this script is located, is read-only, becase it is loop mounted from a file.

Andreas

[omega]

One more thing: the mount options used (iocharset=utf8,umask=0,fmask=001,uid=99,gid=99) are only valid for fat, vfat and umsdos filesystems. They are also not valid for NTFS.

It seems to me that Thecus was only testing the USB hard disk issue with fat formatted disks, nothing else.

I changed the script and now it is working as expected. The ext3 partition on my USB drive is mounted and I can access it without any problems.

I'll try to create and patch....

Andreas