forum.excito.org

Posted: **26 Feb 2009, 15:24**

Hi
I have bought a ICY hard disk box, Link.

It works quite good (in win XP) but little noisy.

To the problem - my Linux skills, they suck.
The cabinet contains two hard disk but I can only find one in Bubba.

Output from

Code: Select all

dmesg

usb-storage: waiting for device to settle before scanning
Vendor: ST316002 Model: 3AS Rev:
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 38 00 00
sda: assuming drive cache: write through
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 38 00 00
sda: assuming drive cache: write through
sda: sda1

...

usb-storage: waiting for device to settle before scanning
Vendor: ST316002 Model: 3AS Rev:
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 38 00 00
sdb: assuming drive cache: write through
SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 38 00 00
sdb: assuming drive cache: write through
sdb: sdb1

what i can find out from this printout is that there is two disk and linked to sda and sdb. It says that the is vendor ST316002 for sda and the same for sdb, but it should be ST325082 for one of them (the disk are of different model).

When I test

Code: Select all

fdisk -l dev/sda

I get no print out
but with

Code: Select all

fdisk -l dev/sdb

I get this printout

Disk dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
dev/sdb1 19457 19457 8032+ 83 Linux

when I tried the disk in my Ubuntu 8.10 it couldn't find the other disk (the one Bubba finds ST316002), why?

I appreciate any help on to find the second disk!!!
Do I need to post more information in order to present the full picture, please speak up and I will post it asap.

ps. if there are a good way to get my Ubuntu home folder at Bubba would be a plus, so each user on Ubuntu machine would save there files on Bubba as a backup ds.

Posted: **26 Feb 2009, 16:47**

Hi,

What happen if you swap the disks? Is it the opposite (detects only the other one)?

What do you get if you type:

Code: Select all

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

/Johan

Posted: **28 Feb 2009, 03:39**

I will try to swap the disk later today, I post an update later.
Note: when I plugged the box in to my Ubuntu machine I only saw the other disk (ST325082)...

when running udevinfo on sda I got "couldn't get the class device"

when running sdb I got

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.

device '/sys/block/sdb' has major:minor 8:16
looking at class device '/sys/block/sdb':
SUBSYSTEM="block"
SYSFS{dev}="8:16"
SYSFS{range}="16"
SYSFS{removable}="0"
SYSFS{size}="312581808"
SYSFS{stat}=" 1 0 8 30 0 0 0 0 0 30 30"

follow the class device's "device"
looking at the device chain at '/sys/devices/platform/at91_ohci/usb1/1-1/1-1:1.0/host3/target3:0:0/3:0:0:0':
BUS="scsi"
ID="3:0:0:0"
DRIVER="sd"
SYSFS{device_blocked}="0"
SYSFS{iocounterbits}="32"
SYSFS{iodone_cnt}="0x8"
SYSFS{ioerr_cnt}="0x0"
SYSFS{iorequest_cnt}="0x8"
SYSFS{max_sectors}="240"
SYSFS{model}="3AS "
SYSFS{queue_depth}="1"
SYSFS{queue_type}="none"
SYSFS{rev}=""
SYSFS{scsi_level}="3"
SYSFS{state}="running"
SYSFS{timeout}="30"
SYSFS{type}="0"
SYSFS{vendor}="ST316002"

Posted: **28 Feb 2009, 17:20**

I have now change the hard drives position in the box.

out put of dmesg

usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
Vendor: ST316002 Model: 3AS Rev:
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 38 00 00
sda: assuming drive cache: write through
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 38 00 00
sda: assuming drive cache: write through
sda: sda1
sd 0:0:0:0: Attached scsi disk sda
usb-storage: device scan complete
usb 1-1: USB disconnect, address 2
usb 1-1: new full speed USB device using at91_ohci and address 3
usb 1-1: configuration #1 chosen from 1 choice
scsi1 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
Vendor: ST316002 Model: 3AS Rev:
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 38 00 00
sda: assuming drive cache: write through
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 38 00 00
sda: assuming drive cache: write through
sda: sda1
sd 1:0:0:0: Attached scsi disk sda
usb-storage: device scan complete
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 38 00 00
sda: assuming drive cache: write through
sda: sda1
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
sda: Mode Sense: 00 38 00 00
sda: assuming drive cache: write through
sda: sda1
usb 1-1: USB disconnect, address 3
eth0: Link down.
eth0: Link now 100-FullDuplex
eth0: Link down.
eth0: Link down.
eth0: Link now 100-FullDuplex
eth0: Link down.
eth0: Link now 100-FullDuplex
eth0: Link down.
eth0: Link now 100-FullDuplex
1:0:0:0: rejecting I/O to dead device
1:0:0:0: rejecting I/O to dead device
1:0:0:0: rejecting I/O to dead device
Buffer I/O error on device sda, logical block 0
lost page write due to I/O error on sda
EXT2-fs error (device sda): ext2_readdir: bad page in #2
1:0:0:0: rejecting I/O to dead device
1:0:0:0: rejecting I/O to dead device
1:0:0:0: rejecting I/O to dead device
Buffer I/O error on device sda, logical block 0
lost page write due to I/O error on sda
EXT2-fs error (device sda): ext2_get_inode: unable to read inode block - inode=2 , block=13
usb 1-1: new full speed USB device using at91_ohci and address 4
usb 1-1: configuration #1 chosen from 1 choice
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
Vendor: ST316002 Model: 3AS Rev:
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 38 00 00
sdb: assuming drive cache: write through
SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 38 00 00
sdb: assuming drive cache: write through
sdb: sdb1
sd 2:0:0:0: Attached scsi disk sdb
usb-storage: device scan complete
usb 1-1: USB disconnect, address 4
usb 1-1: new full speed USB device using at91_ohci and address 5
usb 1-1: configuration #1 chosen from 1 choice
scsi3 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 5
usb-storage: waiting for device to settle before scanning
Vendor: ST316002 Model: 3AS Rev:
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 38 00 00
sdb: assuming drive cache: write through
SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 38 00 00
sdb: assuming drive cache: write through
sdb: sdb1
sd 3:0:0:0: Attached scsi disk sdb
usb-storage: device scan complete
1:0:0:0: rejecting I/O to dead device
1:0:0:0: rejecting I/O to dead device
1:0:0:0: rejecting I/O to dead device
Buffer I/O error on device sda, logical block 0
lost page write due to I/O error on sda
EXT2-fs error (device sda): ext2_readdir: bad page in #2
1:0:0:0: rejecting I/O to dead device
1:0:0:0: rejecting I/O to dead device
1:0:0:0: rejecting I/O to dead device
Buffer I/O error on device sda, logical block 0
lost page write due to I/O error on sda
EXT2-fs error (device sda): ext2_get_inode: unable to read inode block - inode=2 , block=13
1:0:0:0: rejecting I/O to dead device
1:0:0:0: rejecting I/O to dead device
1:0:0:0: rejecting I/O to dead device
Buffer I/O error on device sda, logical block 0
lost page write due to I/O error on sda
EXT2-fs error (device sda): ext2_readdir: bad page in #2
1:0:0:0: rejecting I/O to dead device
1:0:0:0: rejecting I/O to dead device
1:0:0:0: rejecting I/O to dead device
Buffer I/O error on device sda, logical block 0
lost page write due to I/O error on sda
EXT2-fs error (device sda): ext2_get_inode: unable to read inode block - inode=2 , block=13
eth0: Link down.
eth0: Link now 100-FullDuplex
1:0:0:0: rejecting I/O to dead device
Buffer I/O error on device sda, logical block 0
lost page write due to I/O error on sda
usb 1-1: USB disconnect, address 5
usb 1-1: new full speed USB device using at91_ohci and address 6
usb 1-1: configuration #1 chosen from 1 choice
scsi4 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 6
usb-storage: waiting for device to settle before scanning
Vendor: ST325082 Model: 3AS Rev:
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 00 38 00 00
sda: assuming drive cache: write through
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 00 38 00 00
sda: assuming drive cache: write through
sda: sda1
sd 4:0:0:0: Attached scsi disk sda
usb-storage: device scan complete

I found both disk this time but the ST316002 (the one that worked before) where disconnected 4 times.

when I do fdisk -l for sda

Disk dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
dev/sda1 * 1 30402 244196352 7 HPFS/NTFS

which look fine but when I do it for sdb I got no reply.

for udevinfo -a -p /sys/block/sda and ../sdb

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.

device '/sys/block/sda' has major:minor 8:0
looking at class device '/sys/block/sda':
SUBSYSTEM="block"
SYSFS{dev}="8:0"
SYSFS{range}="16"
SYSFS{removable}="0"
SYSFS{size}="488397168"
SYSFS{stat}=" 5 44 392 260 0 0 0 0 0 260 260"

follow the class device's "device"
looking at the device chain at '/sys/devices/platform/at91_ohci/usb1/1-1/1-1:1.0/host4/target4:0:0/4:0:0:0':
BUS="scsi"
ID="4:0:0:0"
DRIVER="sd"
SYSFS{device_blocked}="0"
SYSFS{iocounterbits}="32"
SYSFS{iodone_cnt}="0xc"
SYSFS{ioerr_cnt}="0x0"
SYSFS{iorequest_cnt}="0xc"
SYSFS{max_sectors}="240"
SYSFS{model}="3AS "
SYSFS{queue_depth}="1"
SYSFS{queue_type}="none"
SYSFS{rev}=""
SYSFS{scsi_level}="3"
SYSFS{state}="running"
SYSFS{timeout}="30"
SYSFS{type}="0"
SYSFS{vendor}="ST325082"

Thank full of all help I can get!!!

Posted: **28 Feb 2009, 18:34**

Hi,

First of all, I'm no expert on the subject.

I glanced through the datasheet and noticed a maximum startup current of 2.8A each on your harddisk models (with a bit of guessing on my part). The datasheet for the cabinett mention a maximum of 2A. To me it sounds like a possible power supply problem, which might explain the "rejecting I/O to dead device" entries in your logs (too much current during start up, causing drive to restart). Have you tried running the drives one at a time in the cabinet (still a bit too much according to the data sheets I found)?

As mentioned, I was guessing on the exact model of hard disks. Might be worth checking out though.

I can't explain why it is working in windows, but it wouldn't be the first difference.

/Johan

Posted: **01 Mar 2009, 10:18**

Maybe because the windows box can push some spare voltage over the usb line? I know bubba won't have that luxury

Posted: **01 Mar 2009, 15:39**

Thanks for the input! why do I not read the data sheets more carefull?

It sounds like a probably cause. But the cabinett is not powerd by Bubba and it doesn't explain why it works in windows.

Posted: **01 Mar 2009, 16:09**

Have you tried running the disks one at a time in the cabinette and examine the output of udevinfo? By the way, is the above output all you get? I'm missing some parts.

Have you tried udevmonitor (you need to be root to run it). Once started, connect the device and examine the output.

/Johan

Posted: **02 Mar 2009, 05:04**

What I find rather surprising is that according to specs the icy box is delivered with a 2A power supply, which is not enough to power two hard disks. Thats why I think it pulls extra voltage from the desktop.

Posted: **02 Mar 2009, 13:44**

6feet5 wrote:Have you tried running the disks one at a time in the cabinette and examine the output of udevinfo? By the way, is the above output all you get? I'm missing some parts.

Have you tried udevmonitor (you need to be root to run it). Once started, connect the device and examine the output.

/Johan

I will try to run them alone and post the output to night. Yes, it is all output that I got from udevinfo

Posted: **02 Mar 2009, 13:50**

Ubi wrote:What I find rather surprising is that according to specs the icy box is delivered with a 2A power supply, which is not enough to power two hard disks. Thats why I think it pulls extra voltage from the desktop.

I agree, it is wird. I do not have other SATA disk to try with

and it should be a budget solution...

I have run the cabinett on three machines.
1. HP - Compaq nc 4200 windows both disk visible and working (laptop)
2. Home configured stationary computer AMD 3200 64bit, Ubuntu 8.10 32 bit. only one disk visible (the opposit from the one I saw in Bubba)
3. Bubba server only one visible disk.

Posted: **05 Mar 2009, 15:33**

Hi
At last, I have now tested some with udevinfo.
I now have a matrix over the different output

HD1 Slott 2 wrote: Device '/sys/block/sda' has major:minor 8:0 looking at class device '/sys/block/sda': SUBSYSTEM="block" SYSFS{dev}="8:0" SYSFS{range}="16" SYSFS{removable}="0" SYSFS{size}="312581808" SYSFS{stat}=" 1 0 8 30 0 0 0 0 0 30 30" follow the class device's "device" looking at the device chain at '/sys/devices/platform/at91_ohci/usb1/1-1/1-1:1.0/host5/target5:0:0/5:0:0:0': BUS="scsi" ID="5:0:0:0" DRIVER="sd" SYSFS{device_blocked}="0" SYSFS{iocounterbits}="32" SYSFS{iodone_cnt}="0x8" SYSFS{ioerr_cnt}="0x0" SYSFS{iorequest_cnt}="0x8" SYSFS{max_sectors}="240" SYSFS{model}="3AS " SYSFS{queue_depth}="1" SYSFS{queue_type}="none" SYSFS{rev}="" SYSFS{scsi_level}="3" SYSFS{state}="running" SYSFS{timeout}="30" SYSFS{type}="0" SYSFS{vendor}="ST316002"

HD1 Slott 1 wrote: device '/sys/block/sda' has major:minor 8:0 looking at class device '/sys/block/sda': SUBSYSTEM="block" SYSFS{dev}="8:0" SYSFS{range}="16" SYSFS{removable}="0" SYSFS{size}="312581808" SYSFS{stat}=" 1 0 8 30 0 0 0 0 0 30 30" follow the class device's "device" looking at the device chain at '/sys/devices/platform/at91_ohci/usb1/1-1/1-1:1.0/host6/target6:0:0/6:0:0:0': BUS="scsi" ID="6:0:0:0" DRIVER="sd" SYSFS{device_blocked}="0" SYSFS{iocounterbits}="32" SYSFS{iodone_cnt}="0x8" SYSFS{ioerr_cnt}="0x0" SYSFS{iorequest_cnt}="0x8" SYSFS{max_sectors}="240" SYSFS{model}="3AS " SYSFS{queue_depth}="1" SYSFS{queue_type}="none" SYSFS{rev}="" SYSFS{scsi_level}="3" SYSFS{state}="running" SYSFS{timeout}="30" SYSFS{type}="0" SYSFS{vendor}="ST316002"

HD2 Slott 2 wrote: device '/sys/block/sda' has major:minor 8:0 looking at class device '/sys/block/sda': SUBSYSTEM="block" SYSFS{dev}="8:0" SYSFS{range}="16" SYSFS{removable}="0" SYSFS{size}="488397168" SYSFS{stat}=" 1 0 8 40 0 0 0 0 0 40 40" follow the class device's "device" looking at the device chain at '/sys/devices/platform/at91_ohci/usb1/1-1/1-1:1.0/host7/target7:0:0/7:0:0:0': BUS="scsi" ID="7:0:0:0" DRIVER="sd" SYSFS{device_blocked}="0" SYSFS{iocounterbits}="32" SYSFS{iodone_cnt}="0x8" SYSFS{ioerr_cnt}="0x0" SYSFS{iorequest_cnt}="0x8" SYSFS{max_sectors}="240" SYSFS{model}="3AS " SYSFS{queue_depth}="1" SYSFS{queue_type}="none" SYSFS{rev}="" SYSFS{scsi_level}="3" SYSFS{state}="running" SYSFS{timeout}="30" SYSFS{type}="0" SYSFS{vendor}="ST325082"

HD2 Slott 1 wrote: device '/sys/block/sda' has major:minor 8:0 looking at class device '/sys/block/sda': SUBSYSTEM="block" SYSFS{dev}="8:0" SYSFS{range}="16" SYSFS{removable}="0" SYSFS{size}="488397168" SYSFS{stat}=" 1 0 8 30 0 0 0 0 0 30 30" follow the class device's "device" looking at the device chain at '/sys/devices/platform/at91_ohci/usb1/1-1/1-1:1.0/host8/target8:0:0/8:0:0:0': BUS="scsi" ID="8:0:0:0" DRIVER="sd" SYSFS{device_blocked}="0" SYSFS{iocounterbits}="32" SYSFS{iodone_cnt}="0x8" SYSFS{ioerr_cnt}="0x0" SYSFS{iorequest_cnt}="0x8" SYSFS{max_sectors}="240" SYSFS{model}="3AS " SYSFS{queue_depth}="1" SYSFS{queue_type}="none" SYSFS{rev}="" SYSFS{scsi_level}="3" SYSFS{state}="running" SYSFS{timeout}="30" SYSFS{type}="0" SYSFS{vendor}="ST325082"

when having two disk in it is the one I call slott2 that is visible.
[edit] it is the slot 1 that is visible when two disk are attached[/edit]

I don't realy know what to look for, but why is the target changing every time? starts on 5 and end on 8.

I have not run the udevmonitor since it is not installed. Can I install it with apt-get?

Thank you!

Posted: **06 Mar 2009, 12:06**

Hi,

I just realized I've compared your udevinfo output from a bubbaserver with output from my bubbatwo. When I try it on my bubbaserver I get similar output as you so nothing is missing there.

I don't think you need to worry about the target number increasing, I've noticed the same when pluging a USB memory stick in and out. Not sure why it increases, but it hasn't caused me any problem.

As for udevmonitor I can't find it either so I guess the udev version is to old. I'm not sure if it is safe to upgrade it.

When you say it is always slot two that is available when having two disks, it makes me think the second disk somehow overrides the first one. Very strange. Have you tried changing the jumpers on the hard disks (cable select, master/slave)?

/Johan

Posted: **07 Mar 2009, 05:01**

Hi
The disk are SATA so there is no Master/Slave

The most likely answer to the problem (what I think) is that it is related to the power consumption. But I do not know how to test that I do not have any measurement equipment

Above matrix prove that the disk works and the the 2 different slots in the box work.

Posted: **07 Mar 2009, 06:56**

When you connect the device to your bubba, do you connect the USB cable first, then power it on? If so, have you tried connecting the unit after you power it on (waitin a couple of second after power on)?

/Johan

forum.excito.org

can't find USB disks

can't find USB disks