We have a 3TB external USB drive that I am trying to attach to some CentOS5 servers. I have tried an older Dell PE1950 and a newer R310 but neither one seems to be able to read the drive. It works no problem on windows servers/workstations and I was able to format with NTFS.
I know there are different methods for formatting large disks but this one doesn't even seem to show up as a /dev/ device. I supplied the dmesg output I see when I plug in the device. Is this a limitation of CentOS5? Do I need some additional package / driver / update?
usb 2-1.2: new high speed USB device using ehci_hcd and address 5 usb 2-1.2: configuration #1 chosen from 1 choice scsi7 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 5 usb-storage: waiting for device to settle before scanning Vendor: ASMT Model: 2105 Rev: 0 Type: Direct-Access ANSI SCSI revision: 06 sde : very big device. try to use READ CAPACITY(16). sde : READ CAPACITY(16) failed. sde : status=0, message=00, host=5, driver=00 sde : use 0xffffffff as device size SCSI device sde: 4294967296 512-byte hdwr sectors (2199023 MB) sde: Write Protect is off sde: Mode Sense: 43 00 00 00 sde: assuming drive cache: write through sde : very big device. try to use READ CAPACITY(16). sde : READ CAPACITY(16) failed. sde : status=0, message=00, host=5, driver=00 sde : use 0xffffffff as device size SCSI device sde: 4294967296 512-byte hdwr sectors (2199023 MB) sde: Write Protect is off sde: Mode Sense: 43 00 00 00 sde: assuming drive cache: write through sde:<6>usb 2-1.2: reset high speed USB device using ehci_hcd and address 5 usb 2-1.2: reset high speed USB device using ehci_hcd and address 5 usb 2-1.2: reset high speed USB device using ehci_hcd and address 5 usb 2-1.2: reset high speed USB device using ehci_hcd and address 5 sd 7:0:0:0: SCSI error: return code = 0x00070000 end_request: I/O error, dev sde, sector 0 Buffer I/O error on device sde, logical block 0 sd 7:0:0:0: SCSI error: return code = 0x00070000 end_request: I/O error, dev sde, sector 0 Buffer I/O error on device sde, logical block 0 usb 2-1.2: USB disconnect, address 5 sd 7:0:0:0: SCSI error: return code = 0x00070000 end_request: I/O error, dev sde, sector 0 Buffer I/O error on device sde, logical block 0 sd 7:0:0:0: SCSI error: return code = 0x00010000 end_request: I/O error, dev sde, sector 0 Buffer I/O error on device sde, logical block 0 sd 7:0:0:0: SCSI error: return code = 0x00010000 end_request: I/O error, dev sde, sector 0 Buffer I/O error on device sde, logical block 0 sd 7:0:0:0: SCSI error: return code = 0x00010000 end_request: I/O error, dev sde, sector 0 Buffer I/O error on device sde, logical block 0 sd 7:0:0:0: SCSI error: return code = 0x00010000 end_request: I/O error, dev sde, sector 0 Buffer I/O error on device sde, logical block 0 Dev sde: unable to read RDB block 0 sd 7:0:0:0: SCSI error: return code = 0x00010000 end_request: I/O error, dev sde, sector 0 Buffer I/O error on device sde, logical block 0 sd 7:0:0:0: SCSI error: return code = 0x00010000 end_request: I/O error, dev sde, sector 0 Buffer I/O error on device sde, logical block 0 unable to read partition table sd 7:0:0:0: Attached scsi disk sde sd 7:0:0:0: Attached scsi generic sg7 type 0 usb-storage: device scan complete usb 2-1.2: new high speed USB device using ehci_hcd and address 6 usb 2-1.2: configuration #1 chosen from 1 choice scsi8 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 6 usb-storage: waiting for device to settle before scanning Vendor: ASMT Model: 2105 Rev: 0 Type: Direct-Access ANSI SCSI revision: 06 sde : very big device. try to use READ CAPACITY(16). sde : READ CAPACITY(16) failed. sde : status=0, message=00, host=5, driver=00 sde : use 0xffffffff as device size SCSI device sde: 4294967296 512-byte hdwr sectors (2199023 MB) sde: Write Protect is off sde: Mode Sense: 43 00 00 00 sde: assuming drive cache: write through sde : very big device. try to use READ CAPACITY(16). sde : READ CAPACITY(16) failed. sde : status=0, message=00, host=5, driver=00 sde : use 0xffffffff as device size SCSI device sde: 4294967296 512-byte hdwr sectors (2199023 MB) sde: Write Protect is off sde: Mode Sense: 43 00 00 00 sde: assuming drive cache: write through sde:<6>usb 2-1.2: reset high speed USB device using ehci_hcd and address 6 usb 2-1.2: reset high speed USB device using ehci_hcd and address 6 usb 2-1.2: reset high speed USB device using ehci_hcd and address 6 usb 2-1.2: reset high speed USB device using ehci_hcd and address 6 usb 2-1.2: reset high speed USB device using ehci_hcd and address 6 INFO: task usb-stor-scan:26787 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. usb-stor-scan D ffffffff80150939 0 26787 35 26786 (L-TLB) ffff81005fad5640 0000000000000046 ffff81006427ce78 ffffffff800e4df4 0000000000000086 000000000000000a ffff81000ccfd7a0 ffff810037c1b100 0001039304f5b0b1 000000000000a05c ffff81000ccfd988 0000000300000000 Call Trace: [<ffffffff800e4df4>] blkdev_readpage+0x0/0xf [<ffffffff8006e1d7>] do_gettimeofday+0x40/0x90 [<ffffffff80028b44>] sync_page+0x0/0x43 [<ffffffff800e4df4>] blkdev_readpage+0x0/0xf [<ffffffff800637ea>] io_schedule+0x3f/0x67 [<ffffffff80028b82>] sync_page+0x3e/0x43 [<ffffffff8006392e>] __wait_on_bit_lock+0x36/0x66 [<ffffffff8003fce0>] __lock_page+0x5e/0x64 [<ffffffff800a0b8d>] wake_bit_function+0x0/0x23 [<ffffffff800c67ba>] read_cache_page+0xba/0x110 [<ffffffff8010a685>] read_dev_sector+0x28/0xcf [<ffffffff8010c061>] read_lba+0x49/0xac [<ffffffff800dbba2>] alternate_node_alloc+0x70/0x8c [<ffffffff8010c2f0>] efi_partition+0x99/0x5d4 [<ffffffff880a8917>] :sd_mod:sd_revalidate_disk+0xb74/0xc86 [<ffffffff8010c257>] efi_partition+0x0/0x5d4 [<ffffffff8010ad6c>] rescan_partitions+0x132/0x279 [<ffffffff800e56b0>] do_open+0x231/0x30f [<ffffffff800e589c>] __blkdev_get+0x6a/0x7c [<ffffffff8002d0e8>] wake_up_bit+0x11/0x22 [<ffffffff8010abdd>] register_disk+0x133/0x190 [<ffffffff801479df>] add_disk+0x34/0x3d [<ffffffff880a9492>] :sd_mod:sd_probe+0x2f7/0x355 [<ffffffff80056e02>] netlink_broadcast+0x2a9/0x2f1 [<ffffffff801c7d26>] driver_probe_device+0x52/0xaa [<ffffffff801c7d7e>] __device_attach+0x0/0x5 [<ffffffff801c74d1>] bus_for_each_drv+0x40/0x72 [<ffffffff801c7dd5>] device_attach+0x52/0x5f [<ffffffff801c71d8>] bus_attach_device+0x1a/0x35 [<ffffffff801c6498>] device_add+0x261/0x372 [<ffffffff8807e226>] :scsi_mod:scsi_sysfs_add_sdev+0x35/0x21b [<ffffffff8807c610>] :scsi_mod:scsi_probe_and_add_lun+0x8b1/0x9c9 [<ffffffff8807cab6>] :scsi_mod:scsi_alloc_target+0x268/0x329 [<ffffffff8807ccba>] :scsi_mod:__scsi_scan_target+0xc3/0x5c7 [<ffffffff8006342b>] wait_for_completion_interruptible_timeout+0xdf/0xfb [<ffffffff8008d0ad>] default_wake_function+0x0/0xe [<ffffffff8807d203>] :scsi_mod:scsi_scan_channel+0x45/0x70 [<ffffffff8807d2ee>] :scsi_mod:scsi_scan_host_selected+0xc0/0xfa [<ffffffff800a0947>] keventd_create_kthread+0x0/0xc4 [<ffffffff885c049f>] :usb_storage:usb_stor_scan_thread+0x12e/0x156 [<ffffffff800a0b5f>] autoremove_wake_function+0x0/0x2e [<ffffffff885c0371>] :usb_storage:usb_stor_scan_thread+0x0/0x156 [<ffffffff8003296e>] kthread+0xfe/0x132 [<ffffffff8005dfb1>] child_rip+0xa/0x11 [<ffffffff800a0947>] keventd_create_kthread+0x0/0xc4 [<ffffffff80032870>] kthread+0x0/0x132 [<ffffffff8005dfa7>] child_rip+0x0/0x11 usb 2-1.2: reset high speed USB device using ehci_hcd and address 6 sd 8:0:0:0: timing out command, waited 180s sd 8:0:0:0: SCSI error: return code = 0x06050000 end_request: I/O error, dev sde, sector 0 Buffer I/O error on device sde, logical block 0 usb 2-1.2: reset high speed USB device using ehci_hcd and address 6 usb 2-1.2: reset high speed USB device using ehci_hcd and address 6
james wrote:
We have a 3TB external USB drive that I am trying to attach to some CentOS5 servers. I have tried an older Dell PE1950 and a newer R310 but neither one seems to be able to read the drive. It works no problem on windows servers/workstations and I was able to format with NTFS.
I know there are different methods for formatting large disks but this one doesn't even seem to show up as a /dev/ device. I supplied the dmesg output I see when I plug in the device. Is this a limitation of CentOS5? Do I need some additional package / driver / update?
First, let me say I've not used USB drives - we have an eSATA external bay for backups. However, I've never had trouble with it. A few details:
1. You *MUST* use parted or gparted, and mklabel GPT; MBR can't deal with something over 2TB. 2. We've put a few 3TB SATA drives in servers, and no problems with any of the servers recognizing them, including Dells. (I will note all our 1950's are retired - they started having card problems a couple-three years ago, one or two a month.)
3. Have you tried other USB ports? I believe that some are slower - maybe the ones in the back might be faster, or there might be an internal faster port for USB storage.
mark
Update to CentOS6 or try reformatting them to multiple ext3 (under 2TB) partitions.
On 08/12/2013 09:59 AM, james wrote:
We have a 3TB external USB drive that I am trying to attach to some CentOS5 servers. I have tried an older Dell PE1950 and a newer R310 but neither one seems to be able to read the drive. It works no problem on windows servers/workstations and I was able to format with NTFS.
Mike McCarthy wrote:
Update to CentOS6 or try reformatting them to multiple ext3 (under 2TB) partitions.
On 08/12/2013 09:59 AM, james wrote:
We have a 3TB external USB drive that I am trying to attach to some CentOS5 servers. I have tried an older Dell PE1950 and a newer R310 but
neither
one seems to be able to read the drive. It works no problem on windows servers/workstations and I was able to format with NTFS.
Oh, right, related: it's almost a complete certainty that the drive's *real* blocksize is 4k, but has internal code to present it as 512bytes. When you format the drive, be 100% sure to align it correctly: for parted, tell it 0.0TB, which will put it at 1M. The alignment really *does* make a difference in access and throughput speed.
mark
Am 12.08.2013 17:07, schrieb m.roth@5-cent.us:
Mike McCarthy wrote:
Update to CentOS6 or try reformatting them to multiple ext3 (under 2TB) partitions.
On 08/12/2013 09:59 AM, james wrote:
We have a 3TB external USB drive that I am trying to attach to some CentOS5 servers. I have tried an older Dell PE1950 and a newer R310 but
neither
one seems to be able to read the drive. It works no problem on windows servers/workstations and I was able to format with NTFS.
Oh, right, related: it's almost a complete certainty that the drive's *real* blocksize is 4k, but has internal code to present it as 512bytes. When you format the drive, be 100% sure to align it correctly: for parted, tell it 0.0TB, which will put it at 1M. The alignment really *does* make a difference in access and throughput speed.
mark
Don't know where you take this certainty from, but to remind
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/...
"4 kilobyte physical sectors, 4 kilobyte logical sector harddisks
4 kilobyte physical sectors, 4 kilobyte logical sector harddisks require firmware and software modifications to function. This type of 4 kilobytes sector disks is currently not supported in Red Hat Enterprise Linux 5"
Have an external 3TB Seagate drive myself in the office for which this is the case.
Alexander
Alexander Dalloz wrote:
Am 12.08.2013 17:07, schrieb m.roth@5-cent.us:
Mike McCarthy wrote:
Update to CentOS6 or try reformatting them to multiple ext3 (under 2TB) partitions.
On 08/12/2013 09:59 AM, james wrote:
We have a 3TB external USB drive that I am trying to attach to some CentOS5 servers. I have tried an older Dell PE1950 and a newer R310 but neither one seems to be able to read the drive. It works no problem on windows servers/workstations and I was able to format with NTFS.
Oh, right, related: it's almost a complete certainty that the drive's *real* blocksize is 4k, but has internal code to present it as 512bytes. When you format the drive, be 100% sure to align it correctly: for parted, tell it 0.0TB, which will put it at 1M. The alignment really *does* make a difference in access and throughput speed.
Don't know where you take this certainty from, but to remind
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/...
"4 kilobyte physical sectors, 4 kilobyte logical sector harddisks
4 kilobyte physical sectors, 4 kilobyte logical sector harddisksrequire firmware and software modifications to function. This type of 4 kilobytes sector disks is currently not supported in Red Hat Enterprise Linux 5"
Have an external 3TB Seagate drive myself in the office for which this is the case.
I'll note right back at'cha that all of the 3TB drives we have appear to have firmware in them that will present the blocks as 512b.
mark
On Mon, Aug 12, 2013 at 02:56:59PM -0400, m.roth@5-cent.us wrote:
I'll note right back at'cha that all of the 3TB drives we have appear to have firmware in them that will present the blocks as 512b.
Many/most "advanced format" do "512e" but not all do.
The newer 1Tb disks I have do, as "smartctl -a" tells me:
User Capacity: 1,000,204,886,016 bytes [1.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical
Stephen Harris wrote:
On Mon, Aug 12, 2013 at 02:56:59PM -0400, m.roth@5-cent.us wrote:
I'll note right back at'cha that all of the 3TB drives we have appear to have firmware in them that will present the blocks as 512b.
Many/most "advanced format" do "512e" but not all do.
The newer 1Tb disks I have do, as "smartctl -a" tells me:
User Capacity: 1,000,204,886,016 bytes [1.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical
The logical (thought of the word after I hit <send>) is what I was talking about. My 2TB and 3TB do the same. Look at it from the disk manufacturers' standpoint: they *know* there's a zillion machines out there whose users want to use the larger drives, and aren't going to buy a new computer to do so.
mark
On 8/12/2013 6:59 AM, james wrote:
We have a 3TB external USB drive that I am trying to attach to some CentOS5 servers. I have tried an older Dell PE1950 and a newer R310 but neither one seems to be able to read the drive. It works no problem on windows servers/workstations and I was able to format with NTFS.
I know there are different methods for formatting large disks but this one doesn't even seem to show up as a/dev/ device. I supplied the dmesg output I see when I plug in the device. Is this a limitation of CentOS5? Do I need some additional package / driver / update?
CentOS 5 does not support GPT disks, and MBR disks have an absolute maximum size of 2TB
On 08/12/2013 12:21 PM, John R Pierce wrote:
... and MBR disks have an absolute maximum size of 2TB
Actually, no. The size of disk usable in an MBR partitioning scheme is dependent upon the disk's block size; with 4k blocks MBR can (and does) go above 2TB. We actually have a pair of Western Digital 3TB externals that are NTFS-formatted and MBR partitioned. Yes, this is non-standard and breaks the 'letter' of the MBR specs, but, it works fine on Windows, which is the target audience. The Mac-formatted Studio drives are GPT partitioned (and cost more). The Linux HFS and HFS+ filesystem drivers don't like the 3TB HFS+ formatted WD Studio 3TB I have here, either......
see: http://forums.anandtech.com/archive/index.php/t-2174705.html and the comment by Mark R down the page a bit. Seagate and WD both do this with external 3TB drives meant for PCs.
WD does something very similar for their MyBookLive models; these units are the network-attached ones, and 3TB single-drive and 6TB dual-drive units are common. The NAS embedded OS is Linux, and the main data partition is formatted 64k-blocksize ext4:
(This is on a 1TB model....)
LOMBL1:~# df -h Filesystem Size Used Avail Use% Mounted on /dev/md0 1.9G 541M 1.3G 30% / tmpfs 5.0M 0 5.0M 0% /lib/init/rw udev 10M 6.7M 3.4M 67% /dev tmpfs 5.0M 0 5.0M 0% /dev/shm tmpfs 100M 10M 90M 10% /tmp ramlog-tmpfs 20M 3.4M 17M 17% /var/log /dev/sda4 924G 922G 2.5G 100% /DataVolume LOMBL1:~# tune2fs -l /dev/sda4 tune2fs 1.41.12 (17-May-2010) Filesystem volume name: <none> Last mounted on: /CacheVolume Filesystem UUID: 2631203b-3cb5-4f63-b9ae-12fed7e5d0bd Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: unsigned_directory_hash Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 15144960 Block count: 15191355 Reserved block count: 0 Free blocks: 892140 Free inodes: 14734611 First block: 0 Block size: 65536 Fragment size: 65536 Reserved GDT blocks: 32 Blocks per group: 65528 Fragments per group: 65528 Inodes per group: 65280 Inode blocks per group: 255 Flex block group size: 16 Filesystem created: Thu Apr 7 19:26:05 2011 Last mount time: Tue Jun 4 16:02:59 2013 Last write time: Tue Jun 4 16:02:59 2013 Mount count: 15 Maximum mount count: 29 Last checked: Thu Apr 7 19:26:05 2011 Check interval: 15552000 (6 months) Next check after: Tue Oct 4 19:26:05 2011 Lifetime writes: 1173 GB 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: 4a2c0236-2d62-4779-bb5b-950094980616 Journal backup: inode blocks LOMBL1:~# LOMBL1:~# parted /dev/sda print Model: ATA WDC WD10EACS-00Z (scsi) Disk /dev/sda: 1000GB Sector size (logical/physical): 512B/512B Partition Table: gpt
Number Start End Size File system Name Flags 3 15.7MB 528MB 513MB linux-swap(v1) primary 1 528MB 2576MB 2048MB ext3 primary raid 2 2576MB 4624MB 2048MB ext3 primary raid 4 4624MB 1000GB 996GB ext4 Microsoft basic data
LOMBL1:~# cat /etc/debian_version 5.0.4 LOMBL1:~# uname -a Linux LOMBL1 2.6.32.11-svn70860 #1 Thu May 17 13:32:51 PDT 2012 ppc GNU/Linux LOMBL1:~#
Oh, but 64k blocksize ext4 is NOT supported on almost all PC linux distributions, including CentOS..... At least it's not a funky MBR format, and GPT is used.... And yet the MyBookLive runs Debian 5.0.4/PPC...... Go figure. For more info on the MyBookLive from a linux point of view, see http://mybookworld.wikidot.com/ (it's a fun box to play with, and much more robust than the previous 'World Edition' drives).
CentOS works fine with the SMB shares the MBL exports, and I'm using one right for backups.
On Mon, Aug 12, 2013 at 11:21 AM, John R Pierce pierce@hogranch.com wrote:
I know there are different methods for formatting large disks but this one doesn't even seem to show up as a/dev/ device. I supplied the dmesg output I see when I plug in the device. Is this a limitation of CentOS5? Do I need some additional package / driver / update?
CentOS 5 does not support GPT disks, and MBR disks have an absolute maximum size of 2TB
Did you mean does not support booting from gpt, or does not support them on USB? I have a pair of these running in in software raid one on an old 32-bit box running CentOS5.
# parted /dev/sde print
Model: ATA Hitachi HDS72303 (scsi) Disk /dev/sde: 3001GB Sector size (logical/physical): 512B/512B Partition Table: gpt
Number Start End Size File system Name Flags 1 1049kB 3001GB 3001GB ext3 raid
On 8/12/2013 9:59 AM, james wrote:
We have a 3TB external USB drive that I am trying to attach to some CentOS5 servers. I have tried an older Dell PE1950 and a newer R310 but neither one seems to be able to read the drive. It works no problem on windows servers/workstations and I was able to format with NTFS.
I've gone through the same scenario. I believe the USB layer/interface/driver/whatever in C5 is the pinch point. I have SATA attached GPT labeled 3TB disks working just fine in C5. Put the very same disk in a USB enclosure and it's not recognized as 3TB - sees it as some fraction of its true size.
I know the same disk/enclosure worked on Win7 & I'm pretty sure it worked on C6.
On 08/12/2013 01:20 PM, Toby Bluhm wrote:
I've gone through the same scenario. I believe the USB layer/interface/driver/whatever in C5 is the pinch point. I have SATA attached GPT labeled 3TB disks working just fine in C5. Put the very same disk in a USB enclosure and it's not recognized as 3TB - sees it as some fraction of its true size.
More likely it's the USB host controller on the USB-SATA interface board that's the pinch point. For the direct SATA connection, the drive may go into the 512e mode of the advanced format; perhaps the USB-SATA interface tells the drive the go into the 4k native mode during enclosure powerup? That would make sense for the symptoms you're seeing.
-
Alexander Dalloz -
james -
John R Pierce -
Lamar Owen -
Les Mikesell -
m.roth＠5-cent.us -
Mike McCarthy -
Stephen Harris -
Toby Bluhm