• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: 1TB drive - can only access a small portion  (Read 4750 times)
VanHalen
Newbie
*

Karma: 0
Posts: 14


View Profile
« on: June 22, 2011, 05:11:21 AM »

Partitioned  and then formatted a 1TB USB drive with ext3. Mounted it and can access it over the network. I started to move files and all of a sudden it says the disk is full. It appears that I am only seeing 7.3 GB of the drive. Not sure what to do next as it can't seem to find where I missed something in the setup.
Logged

spinifex
Full Member
***

Karma: 8
Posts: 167



View Profile WWW
« Reply #1 on: June 22, 2011, 07:35:38 AM »

post the result of
# fdisk -l

and

# tune2fs -l /dev/sda

change the 'sda' to whatever the drive is

Logged

VanHalen
Newbie
*

Karma: 0
Posts: 14


View Profile
« Reply #2 on: June 22, 2011, 08:14:50 AM »

I have confirmed that all of the files are being written to my 8G SD card so that is why I hit the limit.
I have some misconfiguration for sure.

fdisk -l

Disk /dev/mmcblk0: 7948 MB, 7948206080 bytes
81 heads, 10 sectors/track, 19165 cylinders
Units = cylinders of 810 * 512 = 414720 bytes
Disk identifier: 0x9017b865

        Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk0p1   *           1       19165     7761820   83  Linux

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x2f55a6a0

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1       60801   488384001   83  Linux

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xe8900690

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1

tune2fs -l /dev/sdb1
tune2fs 1.41.4 (27-Jan-2009)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          31d7ec16-b2c4-4e58-9b38-cb7a3ae7214c
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype s                                                                                                                     parse_super large_file
Filesystem flags:         unsigned_directory_hash
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              61054976
Block count:              244190000
Reserved block count:     12209500
Free blocks:              240306876
Free inodes:              61054965
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      965
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Filesystem created:       Mon Jun 20 12:35:24 2011
Last mount time:          Tue Jun 21 13:48:03 2011
Last write time:          Tue Jun 21 13:53:06 2011
Mount count:              1
Maximum mount count:      36
Last checked:             Mon Jun 20 12:35:24 2011
Check interval:           15552000 (6 months)
Next check after:         Sat Dec 17 11:35:24 2011
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      c7ecfcad-c3b2-40bb-82a8-f2157f4f4c03
Journal backup:           inode blocks
Logged

VanHalen
Newbie
*

Karma: 0
Posts: 14


View Profile
« Reply #3 on: June 26, 2011, 06:47:47 AM »

Made a few changes and I have isolated the problem to my second hard drive connected via the hub to the Sheevaplug. Both USB drives appear to be mounted correctly but in windows the second drive is pointing to the 8 G SD card while the first drive I am able now to access the drive (500G).
Logged

VanHalen
Newbie
*

Karma: 0
Posts: 14


View Profile
« Reply #4 on: June 28, 2011, 05:35:00 AM »

Given up with this WB 1TB drive. I have tried numerous "solutions" and have deleted the partition and formatted twice all with the same problems.
Plugged it into my Winxp machine and have run all of the diagnostics and it comes up passing.
My conclusion is there is a compatibility problem with this particular WD MyBook and the Debian software.
Logged

birdman
Sr. Member
****

Karma: 4
Posts: 443


View Profile WWW
« Reply #5 on: June 28, 2011, 05:05:15 PM »

Ah - you said a USB drive.  IIRC a MyBook is weird and has 4 partitions (and a specific driver for Windows?).  So you need to do multiple LUN scanning.
e.g.
http://www.linuxquestions.org/questions/linux-hardware-18/problems-with-wd-my-book-1tb-external-drive-564130/
http://www.linuxforums.org/forum/red-hat-fedora-linux/104572-mount-wd-my-book-usb-drive.html
Logged

VanHalen
Newbie
*

Karma: 0
Posts: 14


View Profile
« Reply #6 on: July 02, 2011, 04:45:01 AM »

As a experiment I went out and bought a Thermaltake BlacX Duet docking station so I could try another hard drive to see if the same access problem occurs. Yes it does. Same behavior, primary drive (500G) I can rw to from WinXP, the second folder shows up in WinXP but the access is back to the 8G SD card.
This seems to confirm it is not the WB MyBook 1TB drive but something else in my configuration.

Logged

birdman
Sr. Member
****

Karma: 4
Posts: 443


View Profile WWW
« Reply #7 on: July 02, 2011, 05:46:11 PM »

This seems to confirm it is not the WB MyBook 1TB drive but something else in my configuration.
What is that configuration.
Where have you mounted the drive? ((Evidence?)
You mention network access - what sort of network access?
What happens if you access the (mounted) file-system directly from the Plug?
Logged

VanHalen
Newbie
*

Karma: 0
Posts: 14


View Profile
« Reply #8 on: July 05, 2011, 03:54:47 PM »

This seems to confirm it is not the WB MyBook 1TB drive but something else in my configuration.
What is that configuration.
Where have you mounted the drive? ((Evidence?)
You mention network access - what sort of network access?
What happens if you access the (mounted) file-system directly from the Plug?
Cleaned up some of my settings and made sure that I did not duplicate any of the names. Now I can see both shares in Winxp My Network Places and can confirm that I am accessing both drives. I have a minor security access problem as one is completely Read/Writable while the other I can only access and not write yet.
Logged

VanHalen
Newbie
*

Karma: 0
Posts: 14


View Profile
« Reply #9 on: July 05, 2011, 04:07:37 PM »

This seems to confirm it is not the WB MyBook 1TB drive but something else in my configuration.
What is that configuration.
Where have you mounted the drive? ((Evidence?)
You mention network access - what sort of network access?
What happens if you access the (mounted) file-system directly from the Plug?
Cleaned up some of my settings and made sure that I did not duplicate any of the names. Now I can see both shares in Winxp My Network Places and can confirm that I am accessing both drives. I have a minor security access problem as one is completely Read/Writable while the other I can only access and not write yet.
Quick fix and I can now rw both usb hard drives. I have to send my 3TB drive back so I needed to move the files to the 1TB drive so I can't reconnect it until I get the replacement 3TB drive.
Logged

VanHalen
Newbie
*

Karma: 0
Posts: 14


View Profile
« Reply #10 on: July 14, 2011, 04:27:50 AM »

Success!. Replacement 3TB drive arrived, moved files and now have the 1TB drive successfully connected to the Sheevaplug. Transferred a few movies and my popcorn hour can access them. Next is to watch a few to see if any stutter occurs.
Logged

Pages: [1]
Print
Jump to: