Re: 2TB USB hard drive for backing up
Am Donnerstag, 3. Mai 2012 schrieb Ellwood Blues:
> 2012/4/30 Martin Steigerwald <Martin@lichtvoll.de>:
> > Am Montag, 30. April 2012 schrieb Ellwood Blues:
> >> 2012/4/30 Martin Steigerwald <Martin@lichtvoll.de>:
> >> > Am Montag, 30. April 2012 schrieb Chris Bannister:
> >> >> On Sun, Apr 29, 2012 at 08:27:03PM +0200, Martin Steigerwald
wrote:
> >> >> > Hmmm, I´d avoid those with 4 KB hardware sectors that lie to
> >> >> > the OS they have 512 byte sectors. Although I think even those
> >> >> > should work. But with 512 byte sectors you have a 2 TB limit
> >> >> > when you use MBR partitioning.
> >> >> >
> >> >> > 3 TB disks with 4 KB sectors both hardware (physical) and
> >> >> > software (logical) should just work, provided the Linux is new
> >> >> > enough.
> >> >> >
> >> >> > On Squeeze use -cu as additional options (see manpage).
> >> >>
> >> >> Sorry for jumping in here, but I can't figure out (from your
> >> >> post) which command requires the additional options: -cu. Which
> >> >> manpage?
> >> >
> >> > fdisk. Sorry if I didn´t mention it anywhere in my post.
> >>
> >> Thanks, I've tried everything but not success. The problem is that
> >> the disk is already half full and aligned with WD tools. I am just
> >> waiting for linux to be able to read it and write it as efficiently
> >> as Windows does it, at the moment I am not able to read it, which
> >> is very frustrating.
> >
> > I would like to see some information from the disk, like
> >
> > - relevant stuff from hdparm -I /dev/yourdisk (feel free to skip
> > serial number if you do not want to post it here)
> > - fdisk -cul /dev/yourdisk
> > - tail -fn0 /var/log/syslog / dmesg when the kernel detects the disk
> >
> > for starters.
> >
> > You need to use GPT if the disk reports 512 byte sectors to the OS.
> > Thats no problem, when its just a data disk. Try gdisk on the disk.
>
> Sorry for the delay. Her you have what you've asked attached as files
> and as text on the message:
>
>
> /dev/sdf:
>
> ATA device, with non-removable media
> Model Number: WDC WD30EZRX-00MMMB0
> Serial Number: WD-WCAWZxxxxxxx
> Firmware Revision: 80.00A80
> Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev
> 2.5, SATA Rev 2.6, SATA Rev 3.0
> Standards:
> Supported: 8 7 6 5
> Likely used: 8
> Configuration:
> Logical max current
> cylinders 16383 16383
> heads 16 16
> sectors/track 63 63
> --
> CHS current addressable sectors: 16514064
> LBA user addressable sectors: 268435455
> LBA48 user addressable sectors: 5860533168
> Logical Sector size: 512 bytes
> Physical Sector size: 4096 bytes
> Logical Sector-0 offset: 0 bytes
> device size with M = 1024*1024: 2861588 MBytes
> device size with M = 1000*1000: 3000592 MBytes (3000 GB)
[…]
So here we have 3 TB, but…
> May 3 18:18:50 relampago3 kernel: [ 3931.976021] usb 1-4: new
> high-speed USB device number 4 using ehci_hcd
> May 3 18:18:50 relampago3 kernel: [ 3932.108900] usb 1-4: New USB
> device found, idVendor=152d, idProduct=2329
> May 3 18:18:50 relampago3 kernel: [ 3932.108907] usb 1-4: New USB
> device strings: Mfr=1, Product=2, SerialNumber=5
> May 3 18:18:50 relampago3 kernel: [ 3932.108911] usb 1-4: Product:
> USB to ATA/ATAPI Bridge
> May 3 18:18:50 relampago3 kernel: [ 3932.108914] usb 1-4:
> Manufacturer: JMicron May 3 18:18:50 relampago3 kernel: [
> 3932.108917] usb 1-4:
> SerialNumber: 152D20329000
> May 3 18:18:50 relampago3 kernel: [ 3932.110324] usb-storage 1-4:1.0:
> Quirks match for vid 152d pid 2329: 8020
> May 3 18:18:50 relampago3 kernel: [ 3932.110360] scsi7 : usb-storage
> 1-4:1.0 May 3 18:18:50 relampago3 mtp-probe: checking bus 1, device
> 4: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-4"
> May 3 18:18:50 relampago3 mtp-probe: bus: 1, device: 4 was not an MTP
> device May 3 18:18:57 relampago3 hddtemp[1872]: /dev/sda: WDC
> WD2500JS-75NCB3: 34 C May 3 18:19:06 relampago3 kernel: [
> 3948.470324] scsi 7:0:0:0: Direct-Access WDC WD30 EZRX-00MMMB0
> PQ: 0 ANSI: 2 CCS May 3 18:19:06 relampago3 kernel: [
> 3948.472796] sd 7:0:0:0: [sdf] 1565565872 512-byte logical blocks:
> (801 GB/746 GiB)
… here we have 801 GB.
Now thats strange.
What kernel is this?
I think its an kernel issue, cause this is before any partitioning.
The device reports 512-byte logical blocks. But it would be nice to know
the physical size as well. It might have 4096 byte there. If it has thats
one of the disks I tell the students of my Linux trainings to through out
of the window ;). It would report 512 byte to the OS and basically lie to
it to stay compatible with older Windows versions, while using 4 KiB as
physical hardware sector size. I recommend either 512/512 or 4096/4096, so
both the same size.
I would try with 3.2 backport kernel in case you use Squeeze.
> fdisk: opción inválida -- c
> GNU Fdisk 1.2.4
This only works with util-linux fdisk not gnu-fdisk.
merkaba:/sys/block/sda> fdisk -c -u -l /dev/sda
Disk /dev/sda: 300.1 GB, 300069052416 bytes
255 heads, 63 sectors/track, 36481 cylinders, total 586072368 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes <==
I/O size (minimum/optimal): 512 bytes / 512 bytes <==
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 2048 10239 4096 83 Linux
/dev/sda2 10240 401407 195584 ef EFI (FAT-12/16/32)
/dev/sda3 * 401408 987135 292864 83 Linux
/dev/sda4 987136 586072063 292542464 8e Linux LVM
Here with this Intel SSD 320 both sizes are reported as 512 byte (while
the erase block size is larger for sure).
> Error: The backup GPT table is corrupt, but the primary appears OK, so
> that will be used.
> o OK
> c Cancel
> o
> Error: Can't have a partition outside the disk!
Ah. I would try a newer kernel. ;)
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
Reply to: