128 GB limit with USB / Firewire external HDD
Don't think we have done this one recently, apologies if we have: Having run out of disk space on an external firewire 120 GB drive, I thought it would be fun to fit a bigger disk and installed a 400 GB drive into the enclosure. No dice, SuSE sees only 128GB of it. Explore, discover some enclosures appear to have limitations in this regard. Buy new enclosure, this one does USB2 & Firewire, and manufacturers rate it to 400 GB. Use YaST partitioner to provide a single partition - success! Partitioner sees: /dev/sda1 372.6GB Linux native /media/usbdisk 0 48640 And the device appears to mount OK: # mount | grep sda /dev/sda1 on /media/usbdisk type subfs (rw,nosuid,nodev,sync,fs=reiserfs) So get on with rsync'ing data across, but it stops :-( Why? # df /media/usbdisk/ Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 134202876 134201336 1540 100% /media/usbdisk So different parts of the system appear to have different views of the disk and partition concerned: YaST can see the 400GB disk, but the filesystem can apparently only see 128GB again? The machine has ide disks with partitions > 128GB without difficulty. Because it seemed to matter in some related discussions at lists.suse.com: # rpm -qa | grep hal hal-0.5.4-6.2 hal-resmgr-0.1_SVNr59-2 This phenomenon appears in the same way on two separate machines running SuSE 10. Anyone got a clue how to get the system to 'see' the remaining part of the disk in the same way the YaST partitioner appears to see it? I do realise that there may be hardware issues here, but it would be very interesting to hear from anyone who has a large external usb2 or firewire disk running successfully. Cheers Fergus
On Thursday 27 October 2005 11:46, Fergus Wilde wrote:
Don't think we have done this one recently, apologies if we have: <snip>
it would be very
interesting to hear from anyone who has a large external usb2 or firewire disk running successfully. Cheers Fergus
I got a 200 mb USB... Have no problems... Jerry
Fergus Wilde a écrit :
Don't think we have done this one recently, apologies if we have:
Having run out of disk space on an external firewire 120 GB drive, I thought it would be fun to fit a bigger disk and installed a 400 GB drive into the enclosure. No dice, SuSE sees only 128GB of it. Explore, discover some enclosures appear to have limitations in this regard. Buy new enclosure, this one does USB2 & Firewire, and manufacturers rate it to 400 GB.
Use YaST partitioner to provide a single partition - success! Partitioner sees:
/dev/sda1 372.6GB Linux native /media/usbdisk 0 48640
And the device appears to mount OK:
# mount | grep sda
/dev/sda1 on /media/usbdisk type subfs (rw,nosuid,nodev,sync,fs=reiserfs)
So get on with rsync'ing data across, but it stops :-( Why?
# df /media/usbdisk/ Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 134202876 134201336 1540 100% /media/usbdisk
So different parts of the system appear to have different views of the disk and partition concerned: YaST can see the 400GB disk, but the filesystem can apparently only see 128GB again? The machine has ide disks with partitions > 128GB without difficulty.
Because it seemed to matter in some related discussions at lists.suse.com:
# rpm -qa | grep hal
hal-0.5.4-6.2 hal-resmgr-0.1_SVNr59-2
This phenomenon appears in the same way on two separate machines running SuSE 10. Anyone got a clue how to get the system to 'see' the remaining part of the disk in the same way the YaST partitioner appears to see it? I do realise that there may be hardware issues here, but it would be very interesting to hear from anyone who has a large external usb2 or firewire disk running successfully. Cheers Fergus
Hello, I run a 250GB USB or Firewire (2 interfaces) without any problem. Michel
On 10/27/05, Fergus Wilde
Don't think we have done this one recently, apologies if we have:
Having run out of disk space on an external firewire 120 GB drive, I thought it would be fun to fit a bigger disk and installed a 400 GB drive into the enclosure. No dice, SuSE sees only 128GB of it. Explore, discover some enclosures appear to have limitations in this regard. Buy new enclosure, this one does USB2 & Firewire, and manufacturers rate it to 400 GB.
Use YaST partitioner to provide a single partition - success! Partitioner sees:
/dev/sda1 372.6GB Linux native /media/usbdisk 0 48640
And the device appears to mount OK:
# mount | grep sda
/dev/sda1 on /media/usbdisk type subfs (rw,nosuid,nodev,sync,fs=reiserfs)
So get on with rsync'ing data across, but it stops :-( Why?
# df /media/usbdisk/ Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 134202876 134201336 1540 100% /media/usbdisk
So different parts of the system appear to have different views of the disk and partition concerned: YaST can see the 400GB disk, but the filesystem can apparently only see 128GB again? The machine has ide disks with partitions > 128GB without difficulty.
Because it seemed to matter in some related discussions at lists.suse.com:
# rpm -qa | grep hal
hal-0.5.4-6.2 hal-resmgr-0.1_SVNr59-2
This phenomenon appears in the same way on two separate machines running SuSE 10. Anyone got a clue how to get the system to 'see' the remaining part of the disk in the same way the YaST partitioner appears to see it? I do realise that there may be hardware issues here, but it would be very interesting to hear from anyone who has a large external usb2 or firewire disk running successfully. Cheers Fergus
Strange, I routinely partition, format and use 128+ GiB drives: PATA/SATA I routinely use preformated 128+ GiB drives: USB/Firewire. Also, I personally have never used Yast to partition/format anything that big. I either use fdisk interactively or sfdisk (IIRC) from scripts for partitioning. So I'm thinking that either Yast has generic issue partitioning/formating large drives, Or maybe it has a specific issue partitioning/formating large USB drives? Why don't you try one of the other partitioning tools. HTH Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century
On Thursday 27 October 2005 10:46, Fergus Wilde wrote:
Don't think we have done this one recently, apologies if we have:
Having run out of disk space on an external firewire 120 GB drive, I thought it would be fun to fit a bigger disk and installed a 400 GB drive into the enclosure. No dice, SuSE sees only 128GB of it. Explore, discover some enclosures appear to have limitations in this regard. Buy new enclosure, this one does USB2 & Firewire, and manufacturers rate it to 400 GB.
Use YaST partitioner to provide a single partition - success! Partitioner sees:
/dev/sda1 372.6GB Linux native /media/usbdisk 0 48640
And the device appears to mount OK:
# mount | grep sda
/dev/sda1 on /media/usbdisk type subfs (rw,nosuid,nodev,sync,fs=reiserfs)
So get on with rsync'ing data across, but it stops :-( Why?
# df /media/usbdisk/ Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 134202876 134201336 1540 100% /media/usbdisk
So different parts of the system appear to have different views of the disk and partition concerned: YaST can see the 400GB disk, but the filesystem can apparently only see 128GB again? The machine has ide disks with partitions > 128GB without difficulty.
Because it seemed to matter in some related discussions at lists.suse.com:
# rpm -qa | grep hal
hal-0.5.4-6.2 hal-resmgr-0.1_SVNr59-2
This phenomenon appears in the same way on two separate machines running SuSE 10. Anyone got a clue how to get the system to 'see' the remaining part of the disk in the same way the YaST partitioner appears to see it? I do realise that there may be hardware issues here, but it would be very interesting to hear from anyone who has a large external usb2 or firewire disk running successfully. Cheers Fergus
On Wed, 2005-11-02 at 12:56 +0000, Fergus Wilde wrote:
Having run out of disk space on an external firewire 120 GB drive, I
thought it would be fun to fit a bigger disk and installed a 400 GB drive into the enclosure. No dice, SuSE sees only 128GB of it.
I have not followed this thread, so please forgive me if I miss the point, but on Suse 9.3 and on 10 a regular provider of ISO's... a friend of mine, brings his 400GB usb dsk along and I copy from him and upload regularly. When I see him next time I will ask what the make is of the drive and USB housing. He was also running 9.3 and has moved to 10 with no problems. Point being,, I don't think that it is completely acurate to say there is a 128GB limit on USB drives. my 2c Chadley
On Thursday 27 October 2005 10:46, Fergus Wilde wrote: Sorry about the last one, things falling on keyboard ... several people were kind enough to reply to my original query (below), to say they'd had no problems with external usb disks > 128GB. I continued to meet this limitation if I allowed the automounting facility to handle the usb disk and to give it a name under /media. Other oddities included df describing the disk has having 0 bytes of 0 total free. The disk would declare itself as /dev/sda1, and by setting a conventional mountpoint in /etc/fstab I am now able manually to mount and umount the disk, with the result that it displays its real size, accurate df readings and so on. So a partial solution only - perhaps the oddities are due to something about the usb disk enclosure hardware or firmware. Thanks to all who emailed me to share their experiences, Best Fergus
Don't think we have done this one recently, apologies if we have:
Having run out of disk space on an external firewire 120 GB drive, I thought it would be fun to fit a bigger disk and installed a 400 GB drive into the enclosure. No dice, SuSE sees only 128GB of it. Explore, discover some enclosures appear to have limitations in this regard. Buy new enclosure, this one does USB2 & Firewire, and manufacturers rate it to 400 GB.
Use YaST partitioner to provide a single partition - success! Partitioner sees:
/dev/sda1 372.6GB Linux native /media/usbdisk 0 48640
And the device appears to mount OK:
# mount | grep sda
/dev/sda1 on /media/usbdisk type subfs (rw,nosuid,nodev,sync,fs=reiserfs)
So get on with rsync'ing data across, but it stops :-( Why?
# df /media/usbdisk/ Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 134202876 134201336 1540 100% /media/usbdisk
So different parts of the system appear to have different views of the disk and partition concerned: YaST can see the 400GB disk, but the filesystem can apparently only see 128GB again? The machine has ide disks with partitions > 128GB without difficulty.
Because it seemed to matter in some related discussions at lists.suse.com:
# rpm -qa | grep hal
hal-0.5.4-6.2 hal-resmgr-0.1_SVNr59-2
This phenomenon appears in the same way on two separate machines running SuSE 10. Anyone got a clue how to get the system to 'see' the remaining part of the disk in the same way the YaST partitioner appears to see it? I do realise that there may be hardware issues here, but it would be very interesting to hear from anyone who has a large external usb2 or firewire disk running successfully. Cheers Fergus
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2005-11-02 at 13:01 -0000, Fergus Wilde wrote:
Sorry about the last one, things falling on keyboard ... several people were kind enough to reply to my original query (below), to say they'd had no problems with external usb disks > 128GB. I continued to meet this limitation if I allowed the automounting facility to handle the usb disk and to give it a name under /media. Other oddities included df describing the disk has having 0 bytes of 0 total free.
The disk would declare itself as /dev/sda1, and by setting a conventional mountpoint in /etc/fstab I am now able manually to mount and umount the disk, with the result that it displays its real size, accurate df readings and so on. So a partial solution only - perhaps the oddities are due to something about the usb disk enclosure hardware or firmware.
Try the command 'lshal', and see wht it reports about that drive and disk. There could be two "udi" entries, one for the drive, another for the media - - I'm unsure, I don't have a usb disk to try that out. The one for the media should show the size, perhaps it gets the info wrong. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDaQxstTMYHG2NR9URAoFaAJ4+1Z6JwBXuWqffxrS2enQma8d46ACfcXdG 7uVj34SSd/IzflRWiIdSsfo= =iphA -----END PGP SIGNATURE-----
participants (6)
-
Carlos E. R.
-
Catimimi
-
Chadley Wilson
-
Fergus Wilde
-
Greg Freemyer
-
Jerry Westrick