toca180
Posts: 16
Joined: Sat Jul 07, 2012 5:34 pm
Location: Kent, England

USB hard drive not recognised

Fri Aug 10, 2012 8:47 pm

Hi

I am having problems getting a USB hard drive connected. I have a Raspberry Pi with Arch Linux installed on a USB hard drive. This boots fine. The hard drive that I have Arch Linux installed on is an external 2.5in USB drive. I have this powered from a powered USB hub but connected directly to the bottom USB port on my Pi. I then have this USB hub connected to the top USB port on my Pi. I have then connected another 2.5in USB hard drive to the USB hub. I then get the following in the kernel.log:

Code: Select all

Aug 10 21:37:14 alarmpi kernel: [  154.542425] usb 1-1.2: new high speed USB device number 14 using dwc_otg
Aug 10 21:37:14 alarmpi kernel: [  154.642851] usb 1-1.2: New USB device found, idVendor=04b4, idProduct=6560
Aug 10 21:37:14 alarmpi kernel: [  154.642883] usb 1-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Aug 10 21:37:14 alarmpi kernel: [  154.655107] hub 1-1.2:1.0: USB hub found
Aug 10 21:37:14 alarmpi kernel: [  154.655385] hub 1-1.2:1.0: 4 ports detected
Aug 10 21:37:28 alarmpi kernel: [  168.672399] usb 1-1.2: reset high speed USB device number 14 using dwc_otg
Aug 10 21:37:28 alarmpi kernel: [  168.752339] usb 1-1.2: device descriptor read/64, error -71
Aug 10 21:37:28 alarmpi kernel: [  168.942343] usb 1-1.2: device descriptor read/64, error -71
Aug 10 21:37:28 alarmpi kernel: [  169.132347] usb 1-1.2: reset high speed USB device number 14 using dwc_otg
Aug 10 21:37:28 alarmpi kernel: [  169.212349] usb 1-1.2: device descriptor read/64, error -71
Aug 10 21:37:28 alarmpi kernel: [  169.402347] usb 1-1.2: device descriptor read/64, error -71
Aug 10 21:37:29 alarmpi kernel: [  169.592356] usb 1-1.2: reset high speed USB device number 14 using dwc_otg
Aug 10 21:37:29 alarmpi kernel: [  170.012217] usb 1-1.2: device not accepting address 14, error -71
Aug 10 21:37:29 alarmpi kernel: [  170.092352] usb 1-1.2: reset high speed USB device number 14 using dwc_otg
Aug 10 21:37:30 alarmpi kernel: [  170.512222] usb 1-1.2: device not accepting address 14, error -71
Aug 10 21:37:30 alarmpi kernel: [  170.622234] hub 1-1.2:1.0: hub_port_status failed (err = -19)
Aug 10 21:37:30 alarmpi kernel: [  170.622281] hub 1-1.2:1.0: hub_port_status failed (err = -19)
Aug 10 21:37:30 alarmpi kernel: [  170.622305] hub 1-1.2:1.0: hub_port_status failed (err = -19)
Aug 10 21:37:30 alarmpi kernel: [  170.622327] hub 1-1.2:1.0: hub_port_status failed (err = -19)
Aug 10 21:37:30 alarmpi kernel: [  170.622346] hub 1-1.2:1.0: activate --> -19
Aug 10 21:37:30 alarmpi kernel: [  170.622619] usb 1-1.2: USB disconnect, device number 14
Aug 10 21:37:30 alarmpi kernel: [  170.702364] usb 1-1.2: new high speed USB device number 15 using dwc_otg
Aug 10 21:37:30 alarmpi kernel: [  170.782477] usb 1-1.2: device descriptor read/64, error -71
Aug 10 21:37:30 alarmpi kernel: [  170.972346] usb 1-1.2: device descriptor read/64, error -71
Aug 10 21:37:30 alarmpi kernel: [  171.162344] usb 1-1.2: new high speed USB device number 16 using dwc_otg
Aug 10 21:37:30 alarmpi kernel: [  171.242348] usb 1-1.2: device descriptor read/64, error -71
Aug 10 21:37:30 alarmpi kernel: [  171.432349] usb 1-1.2: device descriptor read/64, error -71
Aug 10 21:37:31 alarmpi kernel: [  171.622349] usb 1-1.2: new high speed USB device number 17 using dwc_otg
Aug 10 21:37:31 alarmpi kernel: [  172.042219] usb 1-1.2: device not accepting address 17, error -71
Aug 10 21:37:31 alarmpi kernel: [  172.122357] usb 1-1.2: new high speed USB device number 18 using dwc_otg
Aug 10 21:37:32 alarmpi kernel: [  172.542218] usb 1-1.2: device not accepting address 18, error -71
Aug 10 21:37:32 alarmpi kernel: [  172.542481] hub 1-1:1.0: unable to enumerate USB device on port 2
The hard drive works when directly connected to my laptop running Arch Linux and also when connected via the same USB hub. I have made sure that my Arch Linux install on the Pi is up to date (pacman -Syu). Do you have any idea why this would be happening and what I can try to fix this? If you need any more information, just let me know and I will provide it.

Thanks
Robert

toca180
Posts: 16
Joined: Sat Jul 07, 2012 5:34 pm
Location: Kent, England

Re: USB hard drive not recognised

Sun Aug 12, 2012 10:27 am

Hi

Sorry to reply to mu own post but I thought I would add more information.

I have just tried to connect an external 3.5in external hard drive directly to my Pi. This has its own external power supply. This has worked fine. So this must mean that my Pi is ok. I guess my USB hub is not compatible with my Pi. Has any one else used a Sitecom 4 port USB 2.0 hub, model number: CN-019?

Thanks
Robert

techpaul
Posts: 1512
Joined: Sat Jul 14, 2012 6:40 pm
Location: Reading, UK
Contact: Website

Re: USB hard drive not recognised

Sun Aug 12, 2012 10:32 am

Is your hub a powered or UN-powered hub?

There is not enough power on the Pi USB ports or an UNpowered hub connected to a Pi to supply a USB hard drive, even a 2.5 inch one.

If you can power the USB hub, then it might work.
Just another techie on the net - For GPIO boards see http:///www.facebook.com/pcservicesreading
or http://www.pcserviceselectronics.co.uk/pi/

elatllat
Posts: 1337
Joined: Sat Dec 17, 2011 5:05 pm

Re: USB hard drive not recognised

Sun Aug 12, 2012 7:05 pm

His hub is powered; link to his hub: http://www.sitecom.com/showdownload.php ... 8&hasacr=1

what is the output of this:

Code: Select all

lsusb -v | grep -iP "Transfer Type.*(Interrupt|Isochronous)" | wc -l
6 related problems:
https://www.google.ca/#hl=en&q=site%3Ah ... ror+-71%22
2160p + USB3 + Wayland: https://hardkernel.com

FAQ : https://raspberrypi.stackexchange.com

Unanswered: https://www.raspberrypi.org/forums/search.php?search_id=unanswered

elatllat
Posts: 1337
Joined: Sat Dec 17, 2011 5:05 pm

Re: USB hard drive not recognised

Sun Aug 12, 2012 7:57 pm

2160p + USB3 + Wayland: https://hardkernel.com

FAQ : https://raspberrypi.stackexchange.com

Unanswered: https://www.raspberrypi.org/forums/search.php?search_id=unanswered

toca180
Posts: 16
Joined: Sat Jul 07, 2012 5:34 pm
Location: Kent, England

Re: USB hard drive not recognised

Tue Aug 21, 2012 8:44 pm

Hi

Sorry for not posting sooner but I thought I had ticked the box to get emails about replies.

The out put of:

Code: Select all

lsusb -v | grep -iP "Transfer Type.*(Interrupt|Isochronous)" | wc -l
is:

Code: Select all

6
Yes, the hub is powered. I have since tried to other hubs. Both seems to work fine to start with but then cause my Pi to "stop working". By this I mean I can no longer SSH into it and have to power off an on again. I an running my Pi headless as I do no have access to a monitor and my TV is not is the same room as my wired network. The other to hubs that I have tried are: Belkin F4U018-BLK, 7 port powered and the one I currently have attached is Belkin FSU231, 4 port powered hub. The last few lines of /var/log/kernel.log when I have the FSU231 connected before I power off when it "stops working" are:

Code: Select all

Aug 21 20:29:33 alarmpi kernel: [ 1860.172627] usb 1-1.2.4: reset high-speed USB device number 7 using dwc_otg
Aug 21 20:29:33 alarmpi kernel: [ 1860.273508] __dma_free_remap: freeing wrong coherent size (65536 != 4096)
Aug 21 20:29:33 alarmpi kernel: [ 1860.273545] Backtrace: 
Aug 21 20:29:33 alarmpi kernel: [ 1860.273609] [<c00115cc>] (dump_backtrace+0x0/0x10c) from [<c03aa360>] (dump_stack+0x18/0x1c)
Aug 21 20:29:33 alarmpi kernel: [ 1860.273642]  r6:00000000 r5:00001000 r4:ffd70000 r3:b6349f1d
Aug 21 20:29:33 alarmpi kernel: [ 1860.273693] [<c03aa348>] (dump_stack+0x0/0x1c) from [<c0015f7c>] (dma_free_coherent+0x1b8/0x1ec)
Aug 21 20:29:33 alarmpi kernel: [ 1860.273745] [<c0015dc4>] (dma_free_coherent+0x0/0x1ec) from [<c02b3610>] (__DWC_DMA_FREE+0x10/0x14)
Aug 21 20:29:33 alarmpi kernel: [ 1860.273792] [<c02b3600>] (__DWC_DMA_FREE+0x0/0x14) from [<c02ae78c>] (dwc_otg_hcd_qh_free+0xac/0xd4)
Aug 21 20:29:33 alarmpi kernel: [ 1860.273826] [<c02ae6e0>] (dwc_otg_hcd_qh_free+0x0/0xd4) from [<c02a9784>] (dwc_otg_hcd_endpoint_disable+0xa4/0xb8)
Aug 21 20:29:33 alarmpi kernel: [ 1860.273845]  r7:cea171e8 r6:cea171e0 r5:ce9f7ca0 r4:000000fa
Aug 21 20:29:33 alarmpi kernel: [ 1860.273899] [<c02a96e0>] (dwc_otg_hcd_endpoint_disable+0x0/0xb8) from [<c02abcbc>] (endpoint_disable+0x20/0x2c)
Aug 21 20:29:33 alarmpi kernel: [ 1860.273919]  r7:ce966400 r6:00000001 r5:ce966400 r4:ce9ce40c
Aug 21 20:29:33 alarmpi kernel: [ 1860.273975] [<c02abc9c>] (endpoint_disable+0x0/0x2c) from [<c0287bd4>] (usb_hcd_disable_endpoint+0x24/0x28)
Aug 21 20:29:33 alarmpi kernel: [ 1860.274004]  r4:ce9ce40c r3:c02abc9c
Aug 21 20:29:33 alarmpi kernel: [ 1860.274039] [<c0287bb0>] (usb_hcd_disable_endpoint+0x0/0x28) from [<c0289ef4>] (usb_disable_endpoint+0x68/0x88)
Aug 21 20:29:33 alarmpi kernel: [ 1860.274069] [<c0289e8c>] (usb_disable_endpoint+0x0/0x88) from [<c0289f58>] (usb_disable_interface+0x44/0x5c)
Aug 21 20:29:33 alarmpi kernel: [ 1860.274087]  r6:ce9c8c28 r5:00000001 r4:0000002c r3:ce9ce40c
Aug 21 20:29:33 alarmpi kernel: [ 1860.274141] [<c0289f14>] (usb_disable_interface+0x0/0x5c) from [<c02825a4>] (usb_reset_and_verify_device+0x354/0x490)
Aug 21 20:29:33 alarmpi kernel: [ 1860.274162]  r8:ce9c8c28 r7:00000004 r6:00000000 r5:ce9c64e0 r4:ce966400
Aug 21 20:29:33 alarmpi kernel: [ 1860.274193] r3:00000000
Aug 21 20:29:33 alarmpi kernel: [ 1860.274220] [<c0282250>] (usb_reset_and_verify_device+0x0/0x490) from [<c0282788>] (usb_reset_device+0xa8/0x168)
Aug 21 20:29:33 alarmpi kernel: [ 1860.274256] [<c02826e0>] (usb_reset_device+0x0/0x168) from [<c02b6e18>] (usb_stor_port_reset+0x5c/0x6c)
Aug 21 20:29:33 alarmpi kernel: [ 1860.274299] [<c02b6dbc>] (usb_stor_port_reset+0x0/0x6c) from [<c02b6fc0>] (usb_stor_invoke_transport+0x198/0x4fc)
Aug 21 20:29:33 alarmpi kernel: [ 1860.274318]  r5:cea12000 r4:ce9c2a80
Aug 21 20:29:33 alarmpi kernel: [ 1860.274349] [<c02b6e28>] (usb_stor_invoke_transport+0x0/0x4fc) from [<c02b5e60>] (usb_stor_transparent_scsi_command+0x10/0x14)
Aug 21 20:29:33 alarmpi kernel: [ 1860.274393] [<c02b5e50>] (usb_stor_transparent_scsi_command+0x0/0x14) from [<c02b82e0>] (usb_stor_control_thread+0x1a0/0x28c)
Aug 21 20:29:33 alarmpi kernel: [ 1860.274430] [<c02b8140>] (usb_stor_control_thread+0x0/0x28c) from [<c0044044>] (kthread+0x8c/0x94)
Aug 21 20:29:33 alarmpi kernel: [ 1860.274460] [<c0043fb8>] (kthread+0x0/0x94) from [<c002b8d0>] (do_exit+0x0/0x714)
Aug 21 20:29:33 alarmpi kernel: [ 1860.274476]  r6:c002b8d0 r5:c0043fb8 r4:ce891bec
Aug 21 20:30:40 alarmpi kernel: [ 1927.102718] usb 1-1.2.4: reset high-speed USB device number 7 using dwc_otg
Aug 21 20:31:25 alarmpi kernel: [ 1972.132836] usb 1-1.2.4: reset high-speed USB device number 7 using dwc_otg
Aug 21 20:31:59 alarmpi kernel: [ 2006.102829] usb 1-1.2.4: reset high-speed USB device number 7 using dwc_otg
Aug 21 20:32:43 alarmpi kernel: [ 2050.135310] usb 1-1.2.3: reset high-speed USB device number 6 using dwc_otg
Thanks
Robert

pepedog
Posts: 1043
Joined: Fri Oct 07, 2011 9:55 am

Re: USB hard drive not recognised

Tue Aug 21, 2012 10:15 pm

Probably the powered hub is feeding back into the rpi, on these forums there is a post about using PVC tape to stop 5 volt going to/from the powered hub

toca180
Posts: 16
Joined: Sat Jul 07, 2012 5:34 pm
Location: Kent, England

Re: USB hard drive not recognised

Wed Aug 22, 2012 8:02 pm

HI

Thank you very much for the tip about taping off the power pin in the USB cable. I have done that and my Pi has stayed up for just over an hour and counting. I am still getting lots of the following in the kernel.log:

Code: Select all

Aug 22 20:47:37 alarmpi kernel: [ 3108.113560] usb 1-1.2.3: reset high-speed USB device number 6 using dwc_otg
Aug 22 20:49:33 alarmpi kernel: [ 3223.794169] usb 1-1.2.4: reset high-speed USB device number 7 using dwc_otg
Aug 22 20:49:33 alarmpi kernel: [ 3223.994180] usb 1-1.2.4: reset high-speed USB device number 7 using dwc_otg
Aug 22 20:50:38 alarmpi kernel: [ 3289.184537] usb 1-1.2.4: reset high-speed USB device number 7 using dwc_otg
Aug 22 20:52:22 alarmpi kernel: [ 3393.000640] usb 1-1.2.4: reset high-speed USB device number 7 using dwc_otg
Aug 22 20:52:39 alarmpi kernel: [ 3409.861805] usb 1-1.2.4: reset high-speed USB device number 7 using dwc_otg
Aug 22 20:54:03 alarmpi kernel: [ 3494.192639] usb 1-1.2.3: reset high-speed USB device number 6 using dwc_otg
Aug 22 20:54:07 alarmpi kernel: [ 3497.942662] usb 1-1.2.4: reset high-speed USB device number 7 using dwc_otg
Aug 22 20:54:44 alarmpi kernel: [ 3534.733037] usb 1-1.2.4: reset high-speed USB device number 7 using dwc_otg
Aug 22 20:55:06 alarmpi kernel: [ 3557.273227] usb 1-1.2.4: reset high-speed USB device number 7 using dwc_otg
Aug 22 20:55:20 alarmpi kernel: [ 3570.833427] usb 1-1.2.4: reset high-speed USB device number 7 using dwc_otg
Aug 22 20:58:59 alarmpi kernel: [ 3790.195598] usb 1-1.2.4: reset high-speed USB device number 7 using dwc_otg
Is this something to be worried about? If so, do you have any suggestions?

Thanks
Robert

pepedog
Posts: 1043
Joined: Fri Oct 07, 2011 9:55 am

Re: USB hard drive not recognised

Wed Aug 22, 2012 9:51 pm

Some things to try
In /boot/cmdline.txt add smsc95xx.turbo_mode=N (requires reboot)
In /etc/sysctl.conf change vm.min_free_kbytes=16384 (requires reboot)
Format hard drive
Last resort, change hard drive

toca180
Posts: 16
Joined: Sat Jul 07, 2012 5:34 pm
Location: Kent, England

Re: USB hard drive not recognised

Thu Aug 23, 2012 7:26 am

Hi

Thanks for the reply. I have checked the /boot/cmdline.txt and smsc95xx.turbo_mode=N is in there. I had already looked for that from another post I found searching the forum. I'm not sure what I have in my /etc/sysctl.conf as I am at work now but will check when I get home.

I forgot to mention that my last post was using the Belkin FSU231 hub. When you say try a different hard drive do you mean the one connected directly to the Pi or the ones connected to the hub? I was thinking about trying different enclosures for the 2 hard drives connected to the hub as I am getting the same problems from 2 hubs. (The hard drives I have connected to the hub are Seagate 2.5in hard drives in Icybox enclosues.)

Thanks
Robert

toca180
Posts: 16
Joined: Sat Jul 07, 2012 5:34 pm
Location: Kent, England

Re: USB hard drive not recognised

Sat Aug 25, 2012 9:45 am

Hi

Code: Select all

In /boot/cmdline.txt add smsc95xx.turbo_mode=N (requires reboot)
This was already set like this.

Code: Select all

In /etc/sysctl.conf change vm.min_free_kbytes=16384 (requires reboot)
I have just set this and rebooted.

I have also changed the enclosures that I am using for the Seagate hard drives. This seems to have had some effect. As now I am only getting:

Code: Select all

Aug 25 10:40:01 alarmpi kernel: [  296.730872] usb 1-1.2.3: reset high-speed USB device number 6 using dwc_otg
Aug 25 10:41:00 alarmpi kernel: [  356.400851] usb 1-1.2.3: reset high-speed USB device number 6 using dwc_otg
Aug 25 10:41:01 alarmpi kernel: [  356.920803] usb 1-1.2.4: reset high-speed USB device number 7 using dwc_otg
Aug 25 10:41:07 alarmpi kernel: [  363.160895] usb 1-1.2.3: reset high-speed USB device number 6 using dwc_otg
Aug 25 10:41:44 alarmpi kernel: [  400.270794] usb 1-1.2.3: reset high-speed USB device number 6 using dwc_otg
So I now only get lots of for device 6 and very few for 7. Is there anything else I can try?

Thanks
Robert

UPDATE:

I just had this is the kernel.log:

Code: Select all

Aug 25 10:45:46 alarmpi kernel: [  642.478231] Unable to handle kernel NULL pointer dereference at virtual address 00000000
I can now no longer SSH to my Pi. Is this a new problem?

Thanks
Robert

pepedog
Posts: 1043
Joined: Fri Oct 07, 2011 9:55 am

Re: USB hard drive not recognised

Sat Aug 25, 2012 4:56 pm

I would say the file system is corrupted at this point

toca180
Posts: 16
Joined: Sat Jul 07, 2012 5:34 pm
Location: Kent, England

Re: USB hard drive not recognised

Sat Aug 25, 2012 9:32 pm

Hi

I probably should have said that turning my Pi off and on again and I could log in fine.

Thank you for the reply. I have run check disk on the root file system (ext4) and that is fine. Could this have something to do with me having set up software (mdadm) raid level 1 on the 2 hard drives set up on the USB hub and that is building?

Code: Select all

mdadm --create --verbose /dev/md/md_home --level=1 --raid-devices=2 /dev/sdb1 /dev/sdc1
If so, is there any way round this?

UPDATE:
If I stop the raid but leave the hard drives connected I get no errors in the kernel.log and I am still able to SSH in after a few hours. I am using raid as I plan to have all my data on the raid shared up via samba so I can access it from all my computers to replace a NAS hard drive I have. Also may be run something like miniDLNA so I can access the data from the PS3.

Thanks
Robert

toca180
Posts: 16
Joined: Sat Jul 07, 2012 5:34 pm
Location: Kent, England

Re: USB hard drive not recognised

Mon Aug 27, 2012 7:06 pm

Hi

I have been doing a bit more experimentation. I have reformatted both the hard drives to ext4. I have then mounted them and tested out writing to both of them are the same time. So I ran the following 2 commands in 2 seperate screen sessions running at the same time:

Code: Select all

dd if=/dev/zero of=/tmp/sdb1/test bs=1M count=400000
and

Code: Select all

dd if=/dev/zero of=/tmp/sdc1/test bs=1M count=400000
The 2 USB drives were mounted at /tmp/sdb1 and /tmp/sdc1. sdb1 ran fine but sdc1 had problems (kernel.log):

Code: Select all

Aug 26 09:50:47 alarmpi kernel: [  219.321972] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
Aug 26 09:50:57 alarmpi kernel: [  229.943806] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null)
Aug 26 10:24:57 alarmpi kernel: [ 2269.326234] usb 1-1.2.4: reset high-speed USB device number 7 using dwc_otg
Aug 26 14:06:52 alarmpi kernel: [15584.750363] usb 1-1.2.3: reset high-speed USB device number 6 using dwc_otg
Aug 26 14:26:33 alarmpi kernel: [16766.483848] usb 1-1.2.4: USB disconnect, device number 7
Aug 26 14:26:34 alarmpi kernel: [16766.500994] sd 2:0:0:0: [sdc] Unhandled error code
Aug 26 14:26:34 alarmpi kernel: [16766.501075] sd 2:0:0:0: [sdc]  Result: hostbyte=0x01 driverbyte=0x00
Aug 26 14:26:34 alarmpi kernel: [16766.501106] sd 2:0:0:0: [sdc] CDB: cdb[0]=0x2a: 2a 00 14 29 67 f8 00 00 f0 00
Aug 26 14:26:34 alarmpi kernel: [16766.501163] end_request: I/O error, dev sdc, sector 338257912
Aug 26 14:26:34 alarmpi kernel: [16766.501398] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3258970112 size 126976 starting block 42282269)
Aug 26 14:26:34 alarmpi kernel: [16766.501663] sd 2:0:0:0: [sdc] Unhandled error code
Aug 26 14:26:34 alarmpi kernel: [16766.501712] sd 2:0:0:0: [sdc]  Result: hostbyte=0x01 driverbyte=0x00
Aug 26 14:26:34 alarmpi kernel: [16766.501738] sd 2:0:0:0: [sdc] CDB: cdb[0]=0x2a: 2a 00 14 29 68 e8 00 00 f0 00
Aug 26 14:26:34 alarmpi kernel: [16766.501844] end_request: I/O error, dev sdc, sector 338258152
Aug 26 14:26:34 alarmpi kernel: [16766.502022] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3259092992 size 126976 starting block 42282299)
Aug 26 14:26:34 alarmpi kernel: [16766.502281] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3259215872 size 126976 starting block 42282329)
Aug 26 14:26:34 alarmpi kernel: [16766.502456] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3259338752 size 126976 starting block 42282359)
Aug 26 14:26:34 alarmpi kernel: [16766.502613] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3259461632 size 126976 starting block 42282389)
Aug 26 14:26:34 alarmpi kernel: [16766.502776] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3259584512 size 126976 starting block 42282419)
Aug 26 14:26:34 alarmpi kernel: [16766.502936] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3259707392 size 126976 starting block 42282449)
Aug 26 14:26:34 alarmpi kernel: [16766.503116] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3259830272 size 126976 starting block 42282479)
Aug 26 14:26:34 alarmpi kernel: [16766.503290] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3259953152 size 126976 starting block 42282509)
Aug 26 14:26:34 alarmpi kernel: [16766.503453] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3260076032 size 126976 starting block 42282539)
Aug 26 14:26:34 alarmpi kernel: [16766.503610] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3260198912 size 126976 starting block 42282569)
Aug 26 14:26:34 alarmpi kernel: [16766.503775] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3260321792 size 126976 starting block 42282599)
Aug 26 14:26:34 alarmpi kernel: [16766.503931] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3260444672 size 126976 starting block 42282629)
Aug 26 14:26:34 alarmpi kernel: [16766.504091] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3260567552 size 126976 starting block 42282659)
Aug 26 14:26:34 alarmpi kernel: [16766.504245] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3260690432 size 126976 starting block 42282689)
Aug 26 14:26:34 alarmpi kernel: [16766.504407] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3260813312 size 126976 starting block 42282719)
Aug 26 14:26:34 alarmpi kernel: [16766.504565] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3260936192 size 126976 starting block 42282749)
Aug 26 14:26:34 alarmpi kernel: [16766.504727] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3261059072 size 126976 starting block 42282779)
Aug 26 14:26:34 alarmpi kernel: [16766.504884] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3261181952 size 126976 starting block 42282809)
Aug 26 14:26:34 alarmpi kernel: [16766.505047] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3261304832 size 126976 starting block 42282839)
Aug 26 14:26:34 alarmpi kernel: [16766.505204] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3261427712 size 126976 starting block 42282869)
Aug 26 14:26:34 alarmpi kernel: [16766.505363] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3261550592 size 126976 starting block 42282899)
Aug 26 14:26:34 alarmpi kernel: [16766.505518] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3261673472 size 126976 starting block 42282929)
Aug 26 14:26:34 alarmpi kernel: [16766.505679] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3261796352 size 126976 starting block 42282959)
Aug 26 14:26:34 alarmpi kernel: [16766.505838] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3261919232 size 126976 starting block 42282989)
Aug 26 14:26:34 alarmpi kernel: [16766.506004] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3262042112 size 126976 starting block 42283019)
Aug 26 14:26:34 alarmpi kernel: [16766.506163] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3262164992 size 126976 starting block 42283049)
Aug 26 14:26:34 alarmpi kernel: [16766.506326] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3262287872 size 126976 starting block 42283079)
Aug 26 14:26:34 alarmpi kernel: [16766.506482] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3262410752 size 126976 starting block 42283109)
Aug 26 14:26:34 alarmpi kernel: [16766.506649] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3262533632 size 126976 starting block 42283139)
Aug 26 14:26:34 alarmpi kernel: [16766.506817] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3262656512 size 126976 starting block 42283169)
Aug 26 14:26:34 alarmpi kernel: [16766.506979] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3262779392 size 126976 starting block 42283199)
Aug 26 14:26:34 alarmpi kernel: [16766.507133] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3262902272 size 126976 starting block 42283229)
Aug 26 14:26:34 alarmpi kernel: [16766.507295] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3263025152 size 126976 starting block 42283259)
Aug 26 14:26:34 alarmpi kernel: [16766.507392] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3263148032 size 20480 starting block 42283264)
Aug 26 14:26:34 alarmpi kernel: [16766.507561] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3263168512 size 126976 starting block 42283294)
Aug 26 14:26:34 alarmpi kernel: [16766.507726] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3263291392 size 126976 starting block 42283324)
Aug 26 14:26:34 alarmpi kernel: [16766.507876] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3263414272 size 126976 starting block 42283354)
Aug 26 14:26:34 alarmpi kernel: [16766.508044] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3263537152 size 126976 starting block 42283384)
Aug 26 14:26:34 alarmpi kernel: [16766.508198] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3263660032 size 126976 starting block 42283414)
Aug 26 14:26:34 alarmpi kernel: [16766.508357] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3263782912 size 126976 starting block 42283444)
Aug 26 14:26:34 alarmpi kernel: [16766.508513] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3263905792 size 126976 starting block 42283474)
Aug 26 14:26:34 alarmpi kernel: [16766.508680] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3264028672 size 126976 starting block 42283504)
Aug 26 14:26:34 alarmpi kernel: [16766.508850] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3264151552 size 126976 starting block 42283534)
Aug 26 14:26:34 alarmpi kernel: [16766.509016] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3264274432 size 126976 starting block 42283564)
Aug 26 14:26:34 alarmpi kernel: [16766.509172] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3264397312 size 126976 starting block 42283594)
Aug 26 14:26:34 alarmpi kernel: [16766.509339] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3264520192 size 126976 starting block 42283624)
Aug 26 14:26:34 alarmpi kernel: [16766.509494] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3264643072 size 126976 starting block 42283654)
Aug 26 14:26:34 alarmpi kernel: [16766.509659] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3264765952 size 126976 starting block 42283684)
Aug 26 14:26:34 alarmpi kernel: [16766.509814] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3264888832 size 126976 starting block 42283714)
Aug 26 14:26:34 alarmpi kernel: [16766.509976] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3265011712 size 126976 starting block 42283744)
Aug 26 14:26:34 alarmpi kernel: [16766.510129] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3265134592 size 126976 starting block 42283774)
Aug 26 14:26:34 alarmpi kernel: [16766.510292] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3265257472 size 126976 starting block 42283804)
Aug 26 14:26:34 alarmpi kernel: [16766.510443] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3265380352 size 126976 starting block 42283834)
Aug 26 14:26:34 alarmpi kernel: [16766.510607] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3265503232 size 126976 starting block 42283864)
Aug 26 14:26:34 alarmpi kernel: [16766.510761] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3265626112 size 126976 starting block 42283894)
Aug 26 14:26:34 alarmpi kernel: [16766.510926] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3265748992 size 126976 starting block 42283924)
Aug 26 14:26:34 alarmpi kernel: [16766.511081] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3265871872 size 126976 starting block 42283954)
Aug 26 14:26:34 alarmpi kernel: [16766.511244] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3265994752 size 126976 starting block 42283984)
Aug 26 14:26:34 alarmpi kernel: [16766.511396] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3266117632 size 126976 starting block 42284014)
Aug 26 14:26:34 alarmpi kernel: [16766.511560] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3266240512 size 126976 starting block 42284044)
Aug 26 14:26:34 alarmpi kernel: [16766.511734] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3266363392 size 126976 starting block 42284074)
Aug 26 14:26:34 alarmpi kernel: [16766.511915] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3266486272 size 126976 starting block 42284104)
Aug 26 14:26:34 alarmpi kernel: [16766.512068] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3266609152 size 126976 starting block 42284134)
Aug 26 14:26:34 alarmpi kernel: [16766.512237] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3266732032 size 126976 starting block 42284164)
Aug 26 14:26:34 alarmpi kernel: [16766.512394] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3266854912 size 126976 starting block 42284194)
Aug 26 14:26:34 alarmpi kernel: [16766.512561] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3266977792 size 126976 starting block 42284224)
Aug 26 14:26:34 alarmpi kernel: [16766.512714] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3267100672 size 126976 starting block 42284254)
Aug 26 14:26:34 alarmpi kernel: [16766.512878] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3267223552 size 126976 starting block 42284284)
Aug 26 14:26:34 alarmpi kernel: [16766.513033] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3267346432 size 126976 starting block 42284314)
Aug 26 14:26:34 alarmpi kernel: [16766.513202] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3267469312 size 126976 starting block 42284344)
Aug 26 14:26:34 alarmpi kernel: [16766.513358] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3267592192 size 126976 starting block 42284374)
Aug 26 14:26:34 alarmpi kernel: [16766.513526] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3267715072 size 126976 starting block 42284404)
Aug 26 14:26:34 alarmpi kernel: [16766.513684] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3267837952 size 126976 starting block 42284434)
Aug 26 14:26:34 alarmpi kernel: [16766.513847] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3267960832 size 126976 starting block 42284464)
Aug 26 14:26:34 alarmpi kernel: [16766.514005] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3268083712 size 126976 starting block 42284494)
Aug 26 14:26:34 alarmpi kernel: [16766.514173] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3268206592 size 126976 starting block 42284524)
Aug 26 14:26:34 alarmpi kernel: [16766.514330] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3268329472 size 126976 starting block 42284554)
Aug 26 14:26:34 alarmpi kernel: [16766.514494] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3268452352 size 126976 starting block 42284584)
Aug 26 14:26:34 alarmpi kernel: [16766.514651] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3268575232 size 126976 starting block 42284614)
Aug 26 14:26:34 alarmpi kernel: [16766.514813] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3268698112 size 126976 starting block 42284644)
Aug 26 14:26:34 alarmpi kernel: [16766.514970] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3268820992 size 126976 starting block 42284674)
Aug 26 14:26:34 alarmpi kernel: [16766.515135] EXT4-fs warning (device sdc1): ext4_end_bio:251: I/O error writing to inode 12 (offset 3268943872 size 114688 starting block 42284702)
Aug 26 14:26:34 alarmpi kernel: [16766.515583] JBD2: Detected IO errors while flushing file data on sdc1-8
Aug 26 14:26:34 alarmpi kernel: [16766.515751] Aborting journal on device sdc1-8.
Aug 26 14:26:34 alarmpi kernel: [16766.516053] JBD2: I/O error detected when updating journal superblock for sdc1-8.
Aug 26 14:26:34 alarmpi kernel: [16766.516244] EXT4-fs (sdc1): delayed block allocation failed for inode 12 at logical offset 39595422 with max blocks 153 with error -30
Aug 26 14:26:34 alarmpi kernel: [16766.516271] EXT4-fs (sdc1): This should not happen!! Data will be lost
Aug 26 14:26:34 alarmpi kernel: [16766.516281] 
Aug 26 14:26:34 alarmpi kernel: [16766.517521] EXT4-fs error (device sdc1) in ext4_da_writepages:2317: Journal has aborted
Aug 26 14:26:34 alarmpi kernel: [16766.517903] EXT4-fs error (device sdc1) in ext4_reserve_inode_write:4494: Journal has aborted
Aug 26 14:26:34 alarmpi kernel: [16766.517988] EXT4-fs (sdc1): previous I/O error to superblock detected
Aug 26 14:26:34 alarmpi kernel: [16766.518175] EXT4-fs error (device sdc1) in ext4_dirty_inode:4621: Journal has aborted
Aug 26 14:26:34 alarmpi kernel: [16766.518215] EXT4-fs (sdc1): previous I/O error to superblock detected
Aug 26 14:26:34 alarmpi kernel: [16766.518475] EXT4-fs error (device sdc1) in ext4_da_write_end:2552: Journal has aborted
Aug 26 14:26:34 alarmpi kernel: [16766.518543] EXT4-fs (sdc1): previous I/O error to superblock detected
Aug 26 14:26:34 alarmpi kernel: [16766.519136] EXT4-fs (sdc1): previous I/O error to superblock detected
Aug 26 14:26:34 alarmpi kernel: [16766.519383] EXT4-fs error (device sdc1): ext4_journal_start_sb:327: Detected aborted journal
Aug 26 14:26:34 alarmpi kernel: [16766.519417] EXT4-fs (sdc1): Remounting filesystem read-only
Aug 26 14:26:34 alarmpi kernel: [16766.519467] EXT4-fs (sdc1): previous I/O error to superblock detected
Aug 26 14:26:34 alarmpi kernel: [16766.522737] EXT4-fs (sdc1): ext4_da_writepages: jbd2_start: 2048 pages, ino 12; err -30
Aug 26 14:26:34 alarmpi kernel: [16767.251094] usb 1-1.2.4: new high-speed USB device number 8 using dwc_otg
Aug 26 14:26:34 alarmpi kernel: [16767.355746] usb 1-1.2.4: New USB device found, idVendor=04fc, idProduct=0c25
Aug 26 14:26:34 alarmpi kernel: [16767.355827] usb 1-1.2.4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Aug 26 14:26:34 alarmpi kernel: [16767.355850] usb 1-1.2.4: Product: USB to Serial-ATA bridge
Aug 26 14:26:34 alarmpi kernel: [16767.355867] usb 1-1.2.4: Manufacturer: Sunplus Technology Inc.
Aug 26 14:26:34 alarmpi kernel: [16767.355883] usb 1-1.2.4: SerialNumber: ST9500325A            S2WBZ359
Aug 26 14:26:34 alarmpi kernel: [16767.385179] scsi3 : usb-storage 1-1.2.4:1.0
Aug 26 14:26:35 alarmpi kernel: [16768.386034] scsi 3:0:0:0: Direct-Access     ST950032 5AS                   PQ: 0 ANSI: 2
Aug 26 14:26:35 alarmpi kernel: [16768.393391] sd 3:0:0:0: [sdd] 976773168 512-byte logical blocks: (500 GB/465 GiB)
Aug 26 14:26:35 alarmpi kernel: [16768.396545] sd 3:0:0:0: [sdd] Write Protect is off
Aug 26 14:26:35 alarmpi kernel: [16768.396622] sd 3:0:0:0: [sdd] Mode Sense: 38 00 00 00
Aug 26 14:26:35 alarmpi kernel: [16768.399503] sd 3:0:0:0: [sdd] No Caching mode page present
Aug 26 14:26:35 alarmpi kernel: [16768.399586] sd 3:0:0:0: [sdd] Assuming drive cache: write through
Aug 26 14:26:35 alarmpi kernel: [16768.414866] sd 3:0:0:0: [sdd] No Caching mode page present
Aug 26 14:26:35 alarmpi kernel: [16768.414939] sd 3:0:0:0: [sdd] Assuming drive cache: write through
Aug 26 14:26:35 alarmpi kernel: [16768.467912]  sdd: sdd1
Aug 26 14:26:35 alarmpi kernel: [16768.479822] sd 3:0:0:0: [sdd] No Caching mode page present
Aug 26 14:26:35 alarmpi kernel: [16768.479875] sd 3:0:0:0: [sdd] Assuming drive cache: write through
Aug 26 14:26:35 alarmpi kernel: [16768.479902] sd 3:0:0:0: [sdd] Attached SCSI disk
Aug 27 14:26:59 alarmpi kernel: [103194.052670] EXT4-fs (sdc1): error count: 6
Aug 27 14:26:59 alarmpi kernel: [103194.052700] EXT4-fs (sdc1): initial error at 1345987593: ext4_da_writepages:2317
Aug 27 14:26:59 alarmpi kernel: [103194.052737] EXT4-fs (sdc1): last error at 1345987593: ext4_journal_start_sb:327
This seems rather odd. Does this mean that I have a problem with one of the hard drives (they were both bought brand new)? Or is this a problem with the Pi writing to both of them at the same time?

Thanks
Robert

pepedog
Posts: 1043
Joined: Fri Oct 07, 2011 9:55 am

Re: USB hard drive not recognised

Mon Aug 27, 2012 8:09 pm

I have reformatted both the hard drives to ext4.....
Haven't done this for a while but thought order was
fdisk create partitions both drives and set as raid
Create array
Format the array, ie don't format each drive

User avatar
Leland
Posts: 3
Joined: Mon Aug 27, 2012 10:58 pm
Location: Kansas, U.S.A.

Re: USB hard drive not recognised

Tue Aug 28, 2012 1:12 am

For what its worth... I am trying to do something very similar (dual USB attached SATA drives, mirrored using Linux RAID 1) and am seeing the same resets. I will let you know if I find anything... I think that I am going to focus on the powered USB hub next.

toca180
Posts: 16
Joined: Sat Jul 07, 2012 5:34 pm
Location: Kent, England

Re: USB hard drive not recognised

Tue Aug 28, 2012 7:45 am

Haven't done this for a while but thought order was
fdisk create partitions both drives and set as raid
Create array
Format the array, ie don't format each drive
Yes, I originally partitioned the drives with 1 partition each set to Linux Raid Auto Detect. Then created the raid array with mdadm (command posted earlier). Then formatted the raid array to ext4. What I was reffering to when I said I formatted them to ext4 was I stopped the raid and repartitioned the drives as standard Linux partions and then formatted them as ext4. I did this to test out if it was transferring a lot of data to the drives was the problem as it seemed to stop working when the raid was rebuilding.

Thanks
Robert

lausser
Posts: 2
Joined: Sun Sep 02, 2012 7:24 pm

Re: USB hard drive not recognised

Sun Sep 02, 2012 7:30 pm

Hi,
i tried the same (2-usb-stick-mirror)....without luck. I took some notes here: http://labs.consol.de/lang/en/blog/rasp ... el-sticks/
It's in german, but from the code samples you might get the idea. I tried it with usb3.0- and usb2.0-sticks. I also reduced the bus speed from 480 to 12mbs. Nothing helped. The Usb hub has a 4A power supply.
Gerhard

toca180
Posts: 16
Joined: Sat Jul 07, 2012 5:34 pm
Location: Kent, England

Re: USB hard drive not recognised

Tue Sep 04, 2012 6:23 pm

Google Translate did a pretty good job on the German text. That is pretty much the result I get. Glad it is not just me having the problems.

For me I am going to abandon raid and go with a cron job running rsync to copy the contents from one drive to the other. For me this will be ok as I will be using it for a NAS and media server. I will not be updating the contents too often,only when I get new CDs and take more pictures with my camera. Running the cron job twice a day should be fine for me. Not sure this will work for everyone though.

Thanks
Robert

Return to “Arch”

Who is online

Users browsing this forum: No registered users and 1 guest