the "Connect" button...

[zander]

hi,

i just complete the big upgrade. i would like to mount an external usb 1tb MyBook. the help pages says i must press Connect to use the disk but i can't see the button.

the connecting of the disk does show up in syslog...

Jul 3 16:26:33 bubba kernel: usb 1-1.2: new high speed USB device using fsl-ehci and address 3
Jul 3 16:26:33 bubba kernel: usb 1-1.2: configuration #1 chosen from 1 choice
Jul 3 16:26:33 bubba kernel: scsi4 : SCSI emulation for USB Mass Storage devices
Jul 3 16:26:33 bubba kernel: usb-storage: device found at 3
Jul 3 16:26:33 bubba kernel: usb-storage: waiting for device to settle before scanning
Jul 3 16:26:33 bubba Bubba::Apt[32027]: 0, Loop: is still running
Jul 3 16:26:33 bubba Bubba::Apt[32027]: 0, Loop time: time=1246663646 now=1246663616, t=30
Jul 3 16:26:33 bubba kernel: usbcore: registered new interface driver hiddev
Jul 3 16:26:33 bubba kernel: input: Western Digital My Book as /devices/platform/fsl-ehci.0/usb1/1-1/1-1.2/1-1.2:1.1/input/input0
Jul 3 16:26:33 bubba kernel: input: USB HID v1.11 Device [Western Digital My Book] on usb-fsl-ehci.0-1.2
Jul 3 16:26:33 bubba kernel: usbcore: registered new interface driver usbhid
Jul 3 16:26:33 bubba kernel: usbhid: v2.6:USB HID core driver
Jul 3 16:26:33 bubba kernel: mice: PS/2 mouse device common for all mice
Jul 3 16:26:38 bubba kernel: scsi 4:0:0:0: Enclosure WD My Book Device 104a PQ: 0 ANSI: 4
Jul 3 16:26:38 bubba kernel: scsi 4:0:0:0: Attached scsi generic sg1 type 13
Jul 3 16:26:38 bubba kernel: usb-storage: device scan complete

please advise,

-zander

[tor]

Hi Zander,

Do you see the disk listed in "Disk information" and in "Partition information" och the Disk page?

/Tor

[zander]

no,

i do not. all i see is this WDC WD10EACS-00D on sda. and it's home partition.


-zander

[carl]

no,

i do not. all i see is this WDC WD10EACS-00D on sda. and it's home partition.


-zander

If you have access to an terminal, could you give us the output of following commands (as root):

Code: Select all

diskmanager list_devices debug
blkid

[zander]

hi,

here is the output from the two commands...

bubba:/home/af# diskmanager list_devices debug
[
{
"dev" : "/dev/sda3",
"label" : "",
"model" : "WDC WD10EACS-00D",
"mountpath" : "",
"size" : "2313360",
"type" : "partition",
"usage" : "unused",
"uuid" : "",
"vendor" : "ATA"
},
{
"dev" : "/dev/sda2",
"label" : "",
"model" : "WDC WD10EACS-00D",
"mountpath" : "",
"size" : "1931655600",
"type" : "partition",
"usage" : "pv",
"uuid" : "",
"vendor" : "ATA",
"vgroup" : "bubba"
},
{
"dev" : "/dev/sda1",
"label" : "Bubba_root",
"model" : "WDC WD10EACS-00D",
"mountpath" : "/",
"size" : "19551042",
"type" : "partition",
"usage" : "mounted",
"uuid" : "648b3583-0270-4276-94c7-85a979f7e543",
"vendor" : "ATA"
}
]
bubba:/home/af#

and...

bubba:/home/af# blkid
/dev/mapper/bubba-storage: LABEL="Bubba home" UUID="1c6ae816-bd1a-447c-90db-c092f26cfcc4" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda1: LABEL="Bubba root" UUID="648b3583-0270-4276-94c7-85a979f7e543" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda3: TYPE="swap"
bubba:/home/af#

please advise.

thank you,

-zander

[tor]

Hi again zander,

After some digging in our kernel config it seems like we have missed to enable a feature thats called, "SCSI Enclosure Services". This means that your MyBook wont work with our current kernel since it seem to use this feature.

I have added this to our issue-tracking system and this would, hopefully, be added to the next kernel we release.

/Tor

[zander]

@Tor...

thank you. this has been puzzling me for sometime now.

it is good to have an explanation at ~last~.

do you have a notion of when the bubba esata external drives will be available again?

thank you again,

-zander

[tojacob]

Is there a list of supported external drives? Anyone who can share the brand and model of their working external eSATA disk? I need a disk to run RAID-1.

[nitram]

Hi all,

I also added bubba|storage to the second esata port but he won't show up in the disk section.

Tried the port where my other external disk is connected, this one was for raid1, which is (after placing all back to original location) now fucked up :
RAID array degraded
Disk missing in RAID array '/dev/md0'.

And still no new disk to be seen

Any suggestions where i should look to tackle the problem ?

Thanks,

Martin

[nitram]

Ok, 1 of 2 problems is solved.

The raid is now recovering.
I did a fsck on /dev/sdb1 (which was the disk that was kicked out of the array)
$ sudo e2fsck /dev/sdb1
e2fsck 1.40-WIP (14-Nov-2006)
/dev/sdb1: recovering journal
Truncating orphaned inode 540673 (uid=0, gid=0, mode=0100644, size=0)
/dev/sdb1: clean, 14163/120733696 files, 39321288/241456928 blocks
Added sdb1 in the raid again:
$ sudo mdadm /dev/md0 --add /dev/sdb1
mdadm: re-added /dev/sdb1

And now it is recovering:
$ sudo mdadm --query --detail /dev/md0
/dev/md0:
Version : 00.90.03
Creation Time : Tue Jul 7 16:33:32 2009
Raid Level : raid1
Array Size : 965827712 (921.09 GiB 989.01 GB)
Used Dev Size : 965827712 (921.09 GiB 989.01 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent

Update Time : Sun Jan 31 16:12:56 2010
State : clean, degraded, recovering
Active Devices : 1
Working Devices : 2
Failed Devices : 0
Spare Devices : 1
Rebuild Status : 2% complete
UUID : 9474a51e:d18a7c5c:df0cda93:a002faa0 (local to host bubba)
Events : 0.136298
Number Major Minor RaidDevice State
0 8 2 0 active sync /dev/sda2
2 8 17 1 spare rebuilding /dev/sdb1

But my new bubba|storage connected to the other esata port is still not found in the 'disk' section

Any hint is welcome.

Thanks,
Martin

[nitram]

Ok, I reconnected the new bubba storage which has a WD10EARS 1TB disk in it.
I even cut away some of the plastic from the esata cable just in case it had something to do with the deep connector issue.
When i put the power on it, the syslog shows the following:

Feb 1 17:31:14 bubba kernel: ata4: exception Emask 0x10 SAct 0x0 SErr 0x90000 action 0xe frozen
Feb 1 17:31:14 bubba kernel: ata4: SError: { PHYRdyChg 10B8B }
Feb 1 17:31:14 bubba kernel: ata4: hard resetting link
Feb 1 17:31:14 bubba kernel: ata4: SATA link down (SStatus 0 SControl 310)
Feb 1 17:31:14 bubba kernel: ata4: EH complete
Feb 1 17:32:13 bubba kernel: ata4: exception Emask 0x10 SAct 0x0 SErr 0x50000 action 0xe frozen
Feb 1 17:32:13 bubba kernel: ata4: SError: { PHYRdyChg CommWake }
Feb 1 17:32:13 bubba kernel: ata4: hard resetting link
Feb 1 17:32:19 bubba kernel: ata4: link is slow to respond, please be patient (ready=-19)
Feb 1 17:32:23 bubba kernel: ata4: COMRESET failed (errno=-16)
Feb 1 17:32:23 bubba kernel: ata4: hard resetting link
Feb 1 17:32:26 bubba kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Feb 1 17:32:26 bubba kernel: ata4.00: both IDENTIFYs aborted, assuming NODEV
Feb 1 17:32:26 bubba kernel: ata4: EH complete

Can someone explain what is going on ?

Thanks.

Regards,
Martin

[nitram]

I continued and tried some options for my new bubba|storage with 1TB disk.

1 - Removed existing external raid 1 disk from the array
# mdadm /dev/md0 --fail /dev/sdb1 --remove /dev/sdb1
mdadm: set /dev/sdb1 faulty in /dev/md0
mdadm: hot removed /dev/sdb1
2 - turned off the power of sdb1 disk and removed e-sata cable
3 - connected the same e-sata cable to the new bubba|storage
4 - power on bubba|storage (you can hear the disk spinning)
5 - system collapsed ? ssh sessions gone, web sessions gone, noway to connect to it anymore (blue light stayed on, so it looked like it was working normal?)
6 - disconnect from power and reconnect
7 - after 15 minutes still blinking blue light
8 - disconnect the power again and also disconnect the e-sata cables (so nothing is connected anymore)
9 - power on and bubba is coming back online again
10 - connected bubba|storage to e-sata port and powered on the disk
11 - nothing in the syslog that could indicate new disk
12 - removed bubba|storage and connected 'old' raid disk sdb1 again on same port and same cable
13 - powered on the disk and it's showing up in the syslog
14 - added the disk to the array again
# mdadm /dev/md0 --add /dev/sdb1
15 - Array is recovering again

So people from excito, can I assume that the bubba|storage is faulty ? Or are there more options to test?

Regards,
Martin

[johannes]

Dear Martin,

Sorry for the late reply. On of our sw guys (Carl) thinks the disk is faulty, so the only option would be to return it to us for exchange. You can send either the whole storage or the disk only.

We'll attend to it immediately when it comes in, a new one is on it's way to you within 1-2 days from that.

Please email support@excito.com for details of the return. We will need some kind of purchase receipt (or order no) as well.

Best Regards,
/Johannes