ESata HDD problem
fiery
5 Sep 2010
It seems that vu+ duo with OpenPli 2010-07-25-master can't recognize my external HDD SAMSUNG STORY STATION PLUS 1.5TB (HX-DE015EB/A62), connected through eSata. The drive runs and lights up when vu+ starts, but it doesn't appear in the recognized drives. I formatted the drive in ext3 format using gparted on my laptop first. The HDD that it uses is Samsung HD154UI, which is reported from other users to work when connected as internal drive.
VU+ duo has also an internal SAMSUNG HD502HJ HDD which works fine. Here is what dmesg outputs:
VU+ duo has also an internal SAMSUNG HD502HJ HDD which works fine. Here is what dmesg outputs:
brcm-pm: enabling power to SATA blockAny help is appreciated.
sata_svw 0000:01:00.0: version 4.0
sata_svw 0000:01:00.0: delay 1 second.
ata1: SATA max UDMA/133 cmd 0xB0510000 ctl 0xB0510020 bmdma 0xB0510030 irq 42
ata2: SATA max UDMA/133 cmd 0xB0510100 ctl 0xB0510120 bmdma 0xB0510130 irq 42
scsi0 : sata_svw
JFFS2 notice: (22) check_node_data: wrong data CRC in data node at 0x067d6800: ead 0x21d87be5, calculated 0x4218b1a.
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl F0000)
scsi1 : sata_svw
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl F0000)
ata2.00: ATA-8, max UDMA/133, 976773168 sectors: LBA48 NCQ (depth 0/32)
ata2.00: configured for UDMA/133
Vendor: ATA Model: SAMSUNG HD502HJ Rev: 1AJ1
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1
sd 1:0:0:0: Attached scsi disk sda
sd 1:0:0:0: Attached scsi generic sg0 type 0
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
NTFS driver 2.1.27 [Flags: R/W MODULE].
cdfs 2.6.18 loaded.
JFFS2 notice: (22) check_node_data: wrong data CRC in data node at 0x06dc1000: ead 0x98d98ca6, calculated 0x449971f1.
fiery
5 Sep 2010
xener,
Thank you for your suggestion, but I don't want to bother additionally opening the box. Internal drive should be there, so it's not an option to remove it. External HDD works fine when connected by USB, but it's a lot slower than eSata. It's obvious that ata1 interface can't negotiate with the drive and the problem seems to be hidden in one of the following cases:
1. eSATA interface doesn't work in automatic mode and Vu+ can't bring the SATA II drive to SATA I mode properly. Samsung has a DOS utility that limit their HDDs in SATA I (1.5 Gbps) mode only. I spend 4 hours last night trying to flash the eSata drive in that mode, but unfortunately DOS doesn't recognize eSata drives too.
2. sata_svw kernel module in OpenPli doesn't work with eSata drives. It may need an additional driver like usbhid required for USB keyboards. Also, I didn't find any reports of successfully connected eSata drives on the OpenPli image.
3. It may be a bug in OpenPli. In VTI image v4.1 with kernel update 2.6.18-7.3 there is a fix for external HDD(ESATA) recognition problem.
Anyone with successfully running eSata drive on OpenPli?
Thank you for your suggestion, but I don't want to bother additionally opening the box. Internal drive should be there, so it's not an option to remove it. External HDD works fine when connected by USB, but it's a lot slower than eSata. It's obvious that ata1 interface can't negotiate with the drive and the problem seems to be hidden in one of the following cases:
1. eSATA interface doesn't work in automatic mode and Vu+ can't bring the SATA II drive to SATA I mode properly. Samsung has a DOS utility that limit their HDDs in SATA I (1.5 Gbps) mode only. I spend 4 hours last night trying to flash the eSata drive in that mode, but unfortunately DOS doesn't recognize eSata drives too.
2. sata_svw kernel module in OpenPli doesn't work with eSata drives. It may need an additional driver like usbhid required for USB keyboards. Also, I didn't find any reports of successfully connected eSata drives on the OpenPli image.
3. It may be a bug in OpenPli. In VTI image v4.1 with kernel update 2.6.18-7.3 there is a fix for external HDD(ESATA) recognition problem.
Anyone with successfully running eSata drive on OpenPli?
nfnovice
5 Sep 2010
I was under the impression that you could have EITHER sata internal or e-sata external - not both ... is that the issue here
best test to prove t is as xener said .. try it without internal drive .
best test to prove t is as xener said .. try it without internal drive .
VU+NL
6 Sep 2010
According to the specs of the BCM 7335 there is a dual port SATA 2, but I am not sure if the present VUplus-drivers support that.
fiery
6 Sep 2010
Another user on the vuplus-support.co.uk forum has successfully used an external esata drive along with an internal one. He's used DE and VTI images which recognize both drives differently (/dev/sdb1 and /dev/sda1). He has a problem with initialization of external drive, but vu+ duo worked for him with both drives. I'll ask him what drives he has and what dmesg outputs for him.
It seems that my next try is to install DE or VTI image.
It seems that my next try is to install DE or VTI image.
fiery
6 Sep 2010
So far, that user has successfully connected both an internal drive and an external eSata drive on OpenPli. Here is the link to his post with his dmesg output: http://www.vuplus-su...ard-drive/page2.
The only difference that I see is that his external drive is SATA-150 and main is SATA II with auto switch to 1.5 Gbps mode.
Anyone with successfully connected eSata (3Gbps) drive to VU+?
The only difference that I see is that his external drive is SATA-150 and main is SATA II with auto switch to 1.5 Gbps mode.
Anyone with successfully connected eSata (3Gbps) drive to VU+?
