Ok. I have encoutered some small issues (with my "perfect" set up) but I think it's going in the correct direction.
Just to make someones else life easier, I am adding 3 photos.
After buying those USB hubs (cheap ones),I was able to connect all the hard drives to the powered usb hubs
and the powered hubs to those cheap ones.
From the cheap blue USB hubs there is a tweaked cable going into Raspberry.
In those cheap blue USB hubs, I have removed the red +5V wire (as you may be able to see on the third photo)
What was surprising, I was not able to connect two powered USB hubs into one cheap blue HUB.
I had to use two of them, otherwise the power was kicking the hard drives really badly.
There was a workaround in it by using a chain connection (powered USB hub to Powered USB hub and then to cheap blue HUB and then to Raspberry) but this way I was loosing one powered USB port on the "expensive" HUB.
Current issues I am having are my USB3.0 enclosures, which are not working fine after Raspberry Pi will be restarted.
I've already spent another 2 hours on it and found again some minor issues, to which I can't locate answers.
Please see results of the investigation:
ntfs-3g installed. All USB ports are available.
Connecting Hard Drive in USB3.0 enclosure results in:
positive result by sudo blkid
positive result in sudo lsusb
positive result in fdisk -l
HDDs are visible with labels, and with UUIDs, I can see devices on dev/sda and on /dev/sdb and the disks are being automatically mounted to /media/Label1 / media/Label2
Great.. Happy from the results I have attached the rest of the hard drives,
also those in normal USB2.0 enclosures (by the usb cables).
All of them resulted in only positive effect. But once I've restarted the Raspberry by "sudo shutdown -r now" I have noticed that in /media folder I can see files only from hard drives in enclosures of USB 2.0.
First check:
sudo blkid
the results includes only /dev/sdc, /dev/sdd and /dev/sde. Disks /dev/sda and /dev/sdb are not on the list
fdisk give me the same and disks could not be found.
I have unplugged them and plugged them back in - all good. I can see all the files again. Restarted again and found that those are missing again. Nowhere to find in dev or /mnt/ or /media
blkid is not showing them, lsusb also does not provide any info.
The only traces I have found were:
syslog:
Code: Select all
Oct 13 08:58:46 raspberrypi kernel: [ 7.342457] sd 2:0:0:0: [sdd] Test WP failed, assume Write Enabled
Oct 13 08:58:46 raspberrypi kernel: [ 7.351113] sd 2:0:0:0: [sdd] Asking for cache data failed
Oct 13 08:58:46 raspberrypi kernel: [ 7.357985] sd 2:0:0:0: [sdd] Assuming drive cache: write through
Oct 13 08:58:46 raspberrypi kernel: [ 7.898545] sd 2:0:0:0: [sdd] 625142448 512-byte logical blocks: (320 GB/298 GiB)
Oct 13 08:58:46 raspberrypi kernel: [ 7.910353] sd 2:0:0:0: [sdd] No Caching mode page found
Oct 13 08:58:46 raspberrypi kernel: [ 7.917032] sd 2:0:0:0: [sdd] Assuming drive cache: write through
Oct 13 08:58:46 raspberrypi kernel: [ 7.924368] sd 2:0:0:0: [sdd] Attached SCSI disk
Oct 13 08:58:46 raspberrypi kernel: [ 8.068943] sd 4:0:0:0: [sde] READ CAPACITY failed
Oct 13 08:58:46 raspberrypi kernel: [ 8.074965] sd 4:0:0:0: [sde]
Oct 13 08:58:46 raspberrypi kernel: [ 8.079298] Result: hostbyte=0x00 driverbyte=0x08
Oct 13 08:58:46 raspberrypi kernel: [ 8.085153] sd 4:0:0:0: [sde]
Oct 13 08:58:46 raspberrypi kernel: [ 8.089457] Sense Key : 0x2 [current]
Oct 13 08:58:46 raspberrypi kernel: [ 8.094376] sd 4:0:0:0: [sde]
Oct 13 08:58:46 raspberrypi kernel: [ 8.098661] ASC=0x4 ASCQ=0x1
Oct 13 08:58:46 raspberrypi kernel: [ 8.103577] sd 4:0:0:0: [sde] Test WP failed, assume Write Enabled
Oct 13 08:58:46 raspberrypi kernel: [ 8.112039] sd 4:0:0:0: [sde] Asking for cache data failed
Oct 13 08:58:46 raspberrypi kernel: [ 8.118810] sd 4:0:0:0: [sde] Assuming drive cache: write through
Oct 13 08:58:46 raspberrypi kernel: [ 8.744966] sd 4:0:0:0: [sde] 488397168 512-byte logical blocks: (250 GB/232 GiB)
Oct 13 08:58:46 raspberrypi kernel: [ 8.756433] sd 4:0:0:0: [sde] No Caching mode page found
Oct 13 08:58:46 raspberrypi kernel: [ 8.763072] sd 4:0:0:0: [sde] Assuming drive cache: write through
Oct 13 08:58:46 raspberrypi kernel: [ 8.770522] sd 4:0:0:0: [sde] Attached SCSI disk
Oct 13 08:58:46 raspberrypi kernel: [ 8.776932] Freeing unused kernel memory: 140K (c05bd000 - c05e0000)
Oct 13 08:58:46 raspberrypi kernel: [ 12.262526] bcm2708-i2s bcm2708-i2s.0: Failed to create debugfs directory
Oct 13 08:58:46 raspberrypi kernel: [ 17.916687] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
Oct 13 08:58:46 raspberrypi kernel: [ 18.391474] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
Oct 13 08:58:46 raspberrypi kernel: [ 24.194352] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Oct 13 08:58:46 raspberrypi kernel: [ 24.326181] fuse init (API version 7.22)
Oct 13 08:58:46 raspberrypi kernel: [ 30.338992] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Oct 13 08:58:46 raspberrypi kernel: [ 31.911352] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
And what is really funny. The only place I have found some information that those hard drives are connected, was Gparted Parition Editor.
But the only thing I was able to check, was the disk information with yellow warning /etc/mtab missing, it's too risky to continue
Unplugging the hard drive and plugging it back resolves all the problems.
Any ideas?
Tomorrow I am planning to change the hard drives enclosures back to some old USB 2.0 which will probably resolve the problems,
but anyone might have an idea why the disks are working fine with plug and play but not after soft reboot ? (I have also tried with rootdelay and usbwait options)
