Sign up here and you can log into the forum!

What's the problem with GPT (>2 TB) support?

Have a question about devices internals, memory layout, reverse engineering, etc---This is the place for anything so technical that it would cause a n00b's head to 'splode

Re: What's the problem with GPT (>2 TB) support?   

Postby BURNIN AMBITION » Thu Oct 22, 2015 11:14 am

mad_ady wrote:Also, don't format the drive. If you have a USB drive around, try to use gparted (in a Linux live CD) and format it with GPT (it works even if it's < 2TB), create a partition an plug it into the WDTV. See if it picks it up. If the stick works, then you'd have to look into the hard drive geometry/cluster size. Maybe it's a nonstandard size somewhere...


well i am so angry at myself.
i downloaded gparted. created usb bootable stick, booted from it and launched gparted.
i could not find a way to format the usb stick in gpt. i could format it in whatever youwant but not gpt...

so, to avoid all this, what if i removed everything from my hdd and formated it in gpt again through windows (i cant use gparted for gpt partitions as i stated earlier and i dont know why), should that fix the error probably?
is there some other way to format in gpt other than windows disk manager, to ensure great results?
thank you for your patience with my problem
BURNIN AMBITION
n00b
 
Posts: 17
Joined: Sat Dec 25, 2010 12:05 pm

Re: What's the problem with GPT (>2 TB) support?   

Postby mad_ady » Thu Oct 22, 2015 9:43 pm

I wouldn't go through the trouble to format the "big" disk yet. The goal is to learn why it doens't work.

To format a regular (small) USB disk to GPT (note, you can't format the same disk you're booting from!), try these steps:
If you prefer a GUI tool, GParted will do the job. Click Device > Set Disklabel to create a new GPT data structure. Click Advanced, then select gpt from the Select new labeltype list, as shown in Figure 2. Click Create to create your new GPT data structures. You can then create new partitions in the same way you would if you were manipulating an MBR disk.


It selects MBR as default for disks < 2TB, so you need to force GPT selection as stated above. After that you can create a test NTFS/FAT32 partition (and format it).
User avatar
mad_ady
Developer
 
Posts: 4544
Joined: Fri Nov 05, 2010 9:08 am
Location: Bucharest, Romania

Re: What's the problem with GPT (>2 TB) support?   

Postby BURNIN AMBITION » Sun Oct 25, 2015 2:16 pm

hello again. let me post some updates.
i couldnt format the disk in gpt with gparted. no way at all. i couldnt select tocreate new label. so i went to my buddies house who is a linux freak. there were structure errors (and some more errors) in this usb stick even though windows could find it and play everything from it fine. so did wd.
finally we fixed the errors and changed the type of usb stick to gpt. it was not easy but we did it. after that we split the size in half, so we had 2 partitions. the mistake here was that we quick formatted the first part and slow formatted the second one.

i returned home and plugged the stick in wd. it couldnt be recognised. i plugged it in my windows pc and it couldnt be recognised either. i opened disk management. one partition was fine the second one (i am guessing the one that we did a quick format) wasnt ok. so i deleted it and there was unallocated space in it. after i did that, miracoulously windows could see the other partition. so did my western digital.
after that i booted in gparted, and created a new ntfs volume in the unallocated space. so i had again 2 partitions. after that i plugged the usb stick in western digital. it couldnt be recognised anymore.

so i am very puzzled. at some point the gpt partition could be recognised by wd. at least that is a good thing.
i am starting to guess that there are errors in my 4tb hdd. but if there are, what is the correct way to fix them? boot in linux delete everything create a new gpt partition(just one) and then slowly format it? perhaps then it will be ok? (i am guessing that if i do that then i should format it again when i plug it in windows otherwise it wont be recognised?
any advice is welcome. thank you
BURNIN AMBITION
n00b
 
Posts: 17
Joined: Sat Dec 25, 2010 12:05 pm

Re: What's the problem with GPT (>2 TB) support?   

Postby mad_ady » Mon Oct 26, 2015 12:04 am

So your USB was seen with GPT and only one partition? I think I tried with only one partition as well. Can you paste back the output of these commands after you boot with the GPT usb disk and it works?
Code: Select all
fdisk -l
dmesg


I can't reccomend a way to test your partition, but I somehow doubt it's corrupted (or if it is, it may be because of WD's fault). But, if you have the option, back up all your data, and repartition and reformat your disk from within windows and copy your data back. Well, before copying it back, try to plug it in the WD one more time.
User avatar
mad_ady
Developer
 
Posts: 4544
Joined: Fri Nov 05, 2010 9:08 am
Location: Bucharest, Romania

Re: What's the problem with GPT (>2 TB) support?   

Postby BURNIN AMBITION » Mon Oct 26, 2015 3:04 pm

well i finally managed to execute the commands. for some reason wd couldnt recognise my usb stick again. i tried many times to format the second partition and new label etc. no luck. finally i formated it in gpart then logged back in windows and deleted it and reformatted the other partition. not with one partition only and half the space of the usb stick unallocated (still gpt and ntfs for the working partition, now wd recognises the usb stick and i executed the commands. here are the results
ps. on thursday probably ill go to my linux freak friends house and try to see if we can locate any errors in my hdd 4tb drive. thank you
Code: Select all
WDTVLIVE login: root
   _    _  ___  __    _  _  ____  _  _
  ( \/\/ )(   \(  )  ( \/ )(_  _)( )( )
   \    /  ) ) ))(__  )  (   )(   \\//
    \/\/  (___/(____)(_/\_) (__)  (__)
       1.05.04_V.WDLXTV_LIVE-0.5.2.2
# fdisk -l

Disk /dev/sigmblocka: 267 MB, 267911168 bytes
255 heads, 63 sectors/track, 32 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sigmblocka doesn't contain a valid partition table

Disk /dev/sigmblockb: 0 MB, 524288 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sigmblockb doesn't contain a valid partition table

Disk /dev/sigmblockc: 0 MB, 262144 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sigmblockc doesn't contain a valid partition table

Disk /dev/sigmblockd: 3 MB, 3145728 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sigmblockd doesn't contain a valid partition table

Disk /dev/sigmblocke: 3 MB, 3145728 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sigmblocke doesn't contain a valid partition table

Disk /dev/sigmblockf: 16 MB, 16777216 bytes
255 heads, 63 sectors/track, 2 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sigmblockf doesn't contain a valid partition table

Disk /dev/sigmblockg: 8 MB, 8388608 bytes
255 heads, 63 sectors/track, 1 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sigmblockg doesn't contain a valid partition table

Disk /dev/sigmblockh: 94 MB, 94371840 bytes
255 heads, 63 sectors/track, 11 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sigmblockh doesn't contain a valid partition table

Disk /dev/sigmblocki: 94 MB, 94371840 bytes
255 heads, 63 sectors/track, 11 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sigmblocki doesn't contain a valid partition table

Disk /dev/sigmblockj: 0 MB, 131072 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sigmblockj doesn't contain a valid partition table

Disk /dev/sigmblockk: 0 MB, 131072 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sigmblockk doesn't contain a valid partition table

Disk /dev/sigmblockl: 0 MB, 131072 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sigmblockl doesn't contain a valid partition table

Disk /dev/sdb: 7914 MB, 7914651648 bytes
255 heads, 63 sectors/track, 962 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sdb1               1         963     7729151+ ee EFI GPT
Partition 1 has different physical/logical beginnings (non-Linux?):
     phys=(0, 0, 1) logical=(0, 0, 2)
Partition 1 has different physical/logical endings:
     phys=(1023, 254, 63) logical=(962, 59, 57)
#


Code: Select all
WDTVLIVE login: root
      _ _ _  __  _   _  _ ____ _ _
      ))`)`) ))\ ))  ))/'  ))  ))`)
      ((,(,' ((_/((__// \  ((  ((,'
       1.05.04_V.WDLXTV_LIVE-0.5.2.2
# dmesg
Linux version 2.6.22.19-19-4 (ting@build30-System-Product-Name) (gcc version 4.3.2 (Sourcery G++ Lite 4.3-51) ) #9 PREEMPT Mon Aug 1 14:35:04 CST 2011
Physical map 0xc0000000 to 0x04000000, max remap/kernel size: 0x0c000000/0x18000000.
Configured for SMP865x, detected SMP8655 (revision unknown).
Detected CPU/System/DSP Frequencies: 499.50/333.00/333.00MHz
SMP86xx Enabled Devices under Linux/XENV 0xcfd0bcbc = 0x001b3efc
PCIHost Ethernet Ethernet1 IR FIP I2CM I2CS USB PCIDev1 PCIDev2 PCIDev3 PCIDev4 SATA SCARD SCARD1
CPU revision is: 0001937c
FPU revision is: 01739300
Determined physical RAM map:
memory: 05000000 @ 04000000 (usable)
Modified physical map 0xc0000000 to 0x04000000, max remap/kernel size: 0x10000000/0x18000000.
User-defined physical RAM map:
memory: 0c800000 @ 04000000 (usable)
Wasting 131072 bytes for tracking 4096 unused pages
Initrd not found or empty - disabling initrd
On node 0 totalpages: 16896
  DMA zone: 33 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 16863 pages, LIFO batch:3
  Normal zone: 0 pages used for memmap
Built 1 zonelists.  Total pages: 16863
Kernel command line: console=ttyS0 mem=200M
Primary instruction cache 32kB, 4-way, physically tagged, linesize 32 bytes.
Primary data cache 32kB, 4-way, physically tagged, no aliases, linesize 32 bytes
Synthesized TLB refill handler (20 instructions).
Synthesized TLB load handler fastpath (32 instructions).
Synthesized TLB store handler fastpath (32 instructions).
Synthesized TLB modify handler fastpath (31 instructions).
Cache parity protection disabled
PID hash table entries: 2048 (order: 11, 8192 bytes)
Using 249.750 MHz high precision timer.
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 4, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 3, 131072 bytes)
Memory: 198144k/204800k available (3392k kernel code, 6544k reserved, 703k data, 976k init, 0k highmem)
Calibrating delay loop... 332.59 BogoMIPS (lpj=1662976)
Mount-cache hash table entries: 2048
NET: Registered protocol family 16
PCI: Initializing SMP86xx PCI host controller
PCI: Remapped PCI I/O space 0x58000000 to 0xc0000000, size 64 kB
PCI: Remapped PCI config space 0x50000000 to 0xc0018000, size 10 kB
PCI: Configured SMP86xx as PCI slave with 1024MB PCI memory
PCI: Region size is 131072KB
PCI: Map DMA memory 0x04000000-0x10800000 for PCI at 0x48000000
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Time: TANGOX clocksource has been installed.
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 0, 16384 bytes)
TCP established hash table entries: 16384 (order: 3, 131072 bytes)
TCP bind hash table entries: 16384 (order: 2, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
NTFS driver 2.1.28 [Flags: R/O].
fuse init (API version 7.8)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
tango3dog: Hardware Watchdog Timer for SMP864x/SMP865x 0.1 (def. timeout: 30 sec)
Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = 9) is a 16550A
serial8250: ttyS1 at MMIO 0x0 (irq = 10) is a 16550A
loop: module loaded
tangox_enet0: detected phy  at address 0x01
tangox_enet0: Ethernet driver for SMP864x/SMP865x internal MAC core 0: 100Mbps Base at 0x26000
tangox_enet0: mac address 00:90:a9:77:c4:0c
tangox_enet1: unable to autodetect phy
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
USB Universal Host Controller Interface driver v3.0
driver tangox-ehci-hcd, 10 Dec 2004
TangoX USB initializing...
tangox-ehci-hcd tangox-ehci-hcd: TangoX USB 2.0
tangox-ehci-hcd tangox-ehci-hcd: new USB bus registered, assigned bus number 1
tangox-ehci-hcd tangox-ehci-hcd: irq 48, io mem 0xa0021400
tangox-ehci-hcd tangox-ehci-hcd: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
tangox-ohci-hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
TangoX USB was initialized.
Initializing TangoX USB OHCI Controller Membase=0xa0021500, irq=47
tangox-ohci-hcd tangox-ohci-hcd: USB Host Controller
tangox-ohci-hcd tangox-ohci-hcd: new USB bus registered, assigned bus number 2
tangox-ohci-hcd tangox-ohci-hcd: irq 47, io mem 0xa0021500
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
Not supported chip.
mice: PS/2 mouse device common for all mice
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
ieee80211_crypt: registered algorithm 'NULL'
Freeing unused kernel memory: 976k freed
sigmablock: module license 'Proprietary' taints kernel.

CS 0 vendor id 0x2c.......
CS 0 device id 0xda.......
................................................................................................................................................................................................................................................................

********************** Parition configureations for CS 0 *******************
**** parition 1  offset [0x00000000] + size [0x00080000] = [0x00080000] ****
**** parition 2  offset [0x00080000] + size [0x00040000] = [0x000c0000] ****
**** parition 3  offset [0x000c0000] + size [0x00300000] = [0x003c0000] ****
**** parition 4  offset [0x003c0000] + size [0x00300000] = [0x006c0000] ****
**** parition 5  offset [0x006c0000] + size [0x01000000] = [0x016c0000] ****
**** parition 6  offset [0x016c0000] + size [0x00800000] = [0x01ec0000] ****
**** parition 7  offset [0x01ec0000] + size [0x05a00000] = [0x078c0000] ****
**** parition 8  offset [0x078c0000] + size [0x05a00000] = [0x0d2c0000] ****
**** parition 9  offset [0x0d2c0000] + size [0x00020000] = [0x0d2e0000] ****
**** parition 10  offset [0x0d2e0000] + size [0x00020000] = [0x0d300000] ****
**** parition 11  offset [0x0d300000] + size [0x00020000] = [0x0d320000] ****
chip_index 0 pos 0

CS 1 vendor id 0x00.......
CS 1 device id 0x00.......
nand_probe Error on chip 1 ret code -13
em8xxx [/home/release/WDTV/bungalow_villa/villa_1.05.03_V/src/libs/3_8_0/mrua_SMP8654F_3_8_8_rc_6_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:1642] init_module: begun
em8xxx0 [/home/release/WDTV/bungalow_villa/villa_1.05.03_V/src/libs/3_8_0/mrua_SMP8654F_3_8_8_rc_6_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:1493] identify: board as unknown subid
em8xxx [/home/release/WDTV/bungalow_villa/villa_1.05.03_V/src/libs/3_8_0/mrua_SMP8654F_3_8_8_rc_6_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:1628] identify: device 0x8655 0x5 accepted with software tango3ES3
em8xxx [/home/release/WDTV/bungalow_villa/villa_1.05.03_V/src/libs/3_8_0/mrua_SMP8654F_3_8_8_rc_6_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:1707] mumk_register_tasklet 0xc009c000
mumk_register_tasklet: (0) tasklet c009c000 status @c0211f14
em8xxx [/home/release/WDTV/bungalow_villa/villa_1.05.03_V/src/libs/3_8_0/mrua_SMP8654F_3_8_8_rc_6_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:374] mumk_register_channel_tasklet[0] 0xc00a4000: pE=0xc0211cf0 ch_idx=33 module_id=0x3c 0xc0211d10
em8xxx [/home/release/WDTV/bungalow_villa/villa_1.05.03_V/src/libs/3_8_0/mrua_SMP8654F_3_8_8_rc_6_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:374] mumk_register_channel_tasklet[1] 0xc00ac000: pE=0xc0211cf0 ch_idx=35 module_id=0x3c 0xc0211d1c
em8xxx [/home/release/WDTV/bungalow_villa/villa_1.05.03_V/src/libs/3_8_0/mrua_SMP8654F_3_8_8_rc_6_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:374] mumk_register_channel_tasklet[2] 0xc00b4000: pE=0xc0211cf0 ch_idx=41 module_id=0x13c 0xc0211d28
em8xxx [/home/release/WDTV/bungalow_villa/villa_1.05.03_V/src/libs/3_8_0/mrua_SMP8654F_3_8_8_rc_6_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:374] mumk_register_channel_tasklet[3] 0xc00bc000: pE=0xc0211cf0 ch_idx=43 module_id=0x13c 0xc0211d34
em8xxx [/home/release/WDTV/bungalow_villa/villa_1.05.03_V/src/libs/3_8_0/mrua_SMP8654F_3_8_8_rc_6_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:374] mumk_register_channel_tasklet[4] 0xc00c4000: pE=0xc0211cf0 ch_idx=37 module_id=0x23c 0xc0211d40
em8xxx [/home/release/WDTV/bungalow_villa/villa_1.05.03_V/src/libs/3_8_0/mrua_SMP8654F_3_8_8_rc_6_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:374] mumk_register_channel_tasklet[5] 0xc00cc000: pE=0xc0211cf0 ch_idx=39 module_id=0x23c 0xc0211d4c
em8xxx [/home/release/WDTV/bungalow_villa/villa_1.05.03_V/src/libs/3_8_0/mrua_SMP8654F_3_8_8_rc_6_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:374] mumk_register_channel_tasklet[6] 0xc00d4000: pE=0xc0211cf0 ch_idx=69 module_id=0x3f 0xc0211d58
em8xxx [/home/release/WDTV/bungalow_villa/villa_1.05.03_V/src/libs/3_8_0/mrua_SMP8654F_3_8_8_rc_6_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:1804] init_module: done. Found 1 em8xxx
ir: cannot get major number
SMP86xx ir (253:0): driver loaded (wait_period = 300ms, buffer_size = 2)
led_rst: cannot get major number
led_rst: cannot get major number
SMP86xx led_rst (252:0): driver loaded.
ufsd: driver 8.5 (NTFS4LINUX_U85_013_S[2011-07-15-18:33:05]) LBD=ON with ioctl loaded at c0418000
NTFS read/write support included
Hfs+/HfsX read/write support included
Built for: Alfanetworks_wdtv_live_plus_2011-07-13

fctrl: Unknown symbol tangox_bmide_calc_speed
squashfs: version 3.4 (2008/08/26) Phillip Lougher
fuse init (API version 7.8)
em8xxx0 [/home/release/WDTV/bungalow_villa/villa_1.05.03_V/src/libs/3_8_0/mrua_SMP8654F_3_8_8_rc_6_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:875] em8xxx_release: unclean exit (1 entries)
ir: Enable NEC decoder (0x00000000)
ir: Enable RC5 decoder (0x00000000)
tangox-ehci-hcd tangox-ehci-hcd: uevent: unsupported action-string; this will be ignored in a future kernel version<3>hub 1-0:1.0: uevent: unsupported action-string; this will be ignored in a future kernel version<3>usb_endpoint usbdev1.1_ep81: uevent: unsupported action-string; this will be ignored in a future kernel version<3>usb usb1: uevent: unsupported action-string; this will be ignored in a future kernel version<3>usb_device usbdev1.1: uevent: unsupported action-string; this will be ignored in a future kernel version<3>usb_endpoint usbdev1.1_ep00: uevent: unsupported action-string; this will be ignored in a future kernel version<3>tangox-ohci-hcd tangox-ohci-hcd: uevent: unsupported action-string; this will be ignored in a future kernel version<3>hub 2-0:1.0: uevent: unsupported action-string; this will be ignored in a future kernel version<3>usb_endpoint usbdev2.1_ep81: uevent: unsupported action-string; this will be ignored in a future kernel version<3>usb usb2: uevent: unsupported action-string; this will be ignored in a future kernel version<3>usb_device usbdev2.1: uevent: unsupported action-string; this will be ignored in a future kernel version<3>usb_endpoint usbdev2.1_ep00: uevent: unsupported action-string; this will be ignored in a future kernel version<6>eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
usb 1-1: new high speed USB device using tangox-ehci-hcd and address 2
usb 1-1: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
scsi 0:0:0:0: Direct-Access     JetFlash Transcend 16GB   1100 PQ: 0 ANSI: 4
sd 0:0:0:0: [sda] 31334400 512-byte hardware sectors (16043 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] 31334400 512-byte hardware sectors (16043 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 0:0:0:0: [sda] Attached SCSI removable disk
sd 0:0:0:0: Attached scsi generic sg0 type 0
usb-storage: device scan complete
sd 0:0:0:0: [sda] 31334400 512-byte hardware sectors (16043 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
program dmaosd is using a deprecated SCSI ioctl, please convert it to SG_IO
usb 1-1: USB disconnect, address 2
usb 1-1: new high speed USB device using tangox-ehci-hcd and address 3
usb 1-1: configuration #1 chosen from 1 choice
scsi1 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
scsi 1:0:0:0: Direct-Access     Kingston DataTraveler SE9 PMAP PQ: 0 ANSI: 4
sd 1:0:0:0: [sda] 15458304 512-byte hardware sectors (7915 MB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 23 00 00 00
sd 1:0:0:0: [sda] Assuming drive cache: write through
sd 1:0:0:0: [sda] 15458304 512-byte hardware sectors (7915 MB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 23 00 00 00
sd 1:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 1:0:0:0: [sda] Attached SCSI removable disk
sd 1:0:0:0: Attached scsi generic sg0 type 0
usb-storage: device scan complete
sd 1:0:0:0: [sda] 15458304 512-byte hardware sectors (7915 MB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 23 00 00 00
sd 1:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
ufsd: use builtin utf8 instead of kernel utf8
ufsd: sda1 native journal need replay
ufsd: volume is dirty and "force" flag is not set
ufsd: use builtin utf8 instead of kernel utf8
ufsd: sda1 without journal
usb 1-1: USB disconnect, address 3
usb 1-1: new high speed USB device using tangox-ehci-hcd and address 4
usb 1-1: configuration #1 chosen from 1 choice
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
scsi 2:0:0:0: Direct-Access     Kingston DataTraveler SE9 PMAP PQ: 0 ANSI: 4
sd 2:0:0:0: [sdb] 15458304 512-byte hardware sectors (7915 MB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] 15458304 512-byte hardware sectors (7915 MB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 2:0:0:0: [sdb] Attached SCSI removable disk
sd 2:0:0:0: Attached scsi generic sg0 type 0
usb-storage: device scan complete
sd 2:0:0:0: [sdb] 15458304 512-byte hardware sectors (7915 MB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
ufsd: use builtin utf8 instead of kernel utf8
ufsd: sdb1 native journal need replay
ufsd: use builtin utf8 instead of kernel utf8
ufsd: sdb1 journal need replay
ufsd: use builtin utf8 instead of kernel utf8
ufsd: sdb1 without journal
#
BURNIN AMBITION
n00b
 
Posts: 17
Joined: Sat Dec 25, 2010 12:05 pm

Re: What's the problem with GPT (>2 TB) support?   

Postby mad_ady » Tue Oct 27, 2015 12:06 am

Ok. Please enable DMAOSD_DEBUG in the settings, reboot the WDTV with the USB stick attached and see if you get the following output in /tmp/dmaosd.log:
Code: Select all
EFI GPT found
FirstUsableLBA: 34
PartitionEntryLBA: 2
NumberOfPartitionEntries: 128


If you do, try the same experiment with your 4TB drive. You should be able to extract the file via FTP or SFTP (WinSCP)
User avatar
mad_ady
Developer
 
Posts: 4544
Joined: Fri Nov 05, 2010 9:08 am
Location: Bucharest, Romania

Re: What's the problem with GPT (>2 TB) support?   

Postby BURNIN AMBITION » Wed Nov 11, 2015 2:08 pm

sorry for replying so late, i have been way too busy.
i couldnt locate DMAOSD_DEBUG in the settings. i could find all sorts of dma commands but not this one.
this has started to become too time consuming for me.
in the meantime i formated my hdd, i recopied all my files and still the same outcome. i used the usb hdd in another friends media player (different brand) and it worked fine. i am sure it has nothing to do with my external hdd. perhaps ill stop using the wd since it has been such a hassle. sorry for wasting your time. take care
BURNIN AMBITION
n00b
 
Posts: 17
Joined: Sat Dec 25, 2010 12:05 pm

Re: What's the problem with GPT (>2 TB) support?   

Postby JoeySmyth » Wed Nov 11, 2015 8:22 pm

I'm able to use a 4TB with my WDTV Live Hub and WDTV 2014 Media Player ... and some people have reported 5TB ok as well

just sayin (works fine on later WDTV's)
User avatar
JoeySmyth
DLX'er
 
Posts: 67
Joined: Sat Sep 27, 2014 3:37 pm
Location: Down Under

Re: What's the problem with GPT (>2 TB) support?   

Postby rgalka » Tue Dec 29, 2015 10:45 am

Just a note to add to the conversation....

upgraded to 1.05.04_B.WDLXTV_PLUS-0.5.2.2 with no problems yet....

Tried my Seagate 3T again... still doesn't recognize.... BUT got a good deal on a WD MyBook 5T and that works... so far... ;O)
The WD came formatted as NTFS... I did nothing other than copy a bunch of movies over to it.. plugged it into the Live Plus and it was recognized and played the movies with not problems.

bob
rgalka
Donor
 
Posts: 131
Joined: Fri Jun 24, 2011 11:37 am

Re: What's the problem with GPT (>2 TB) support?   

Postby rgalka » Wed Jan 06, 2016 6:49 pm

OK.. so now I am having issues with the MyBook 5t...
When I first got it I put a movie on it and plugged it into the WDLIVW Plus and it was recognized and played the movie. Great.

So I copied over a folder of movies and noticed that the capacity was only showing as ~500 G... I had checked out the capacity initially and it was 5T???? started googling and found something similar on a WD forum with the suggestion to reformat it with the WD Quick formatter... did that.. seemed to do the trick.. but of course movies were gone... so stated again with a folder of movies.... WDTV recognized and played... created the .sheet folder and ran Thumbgen on those movies... no sheets on the WDTV.... of course the usb drive had a new id so updated the msheets dir entry.... sheets showed up.. no covers though...

but anyway I started copying over more folders... very slow from usb 2 to usb 3... but in the process I notice that the capacity had changed again... Grrrr....

Called WD and explained what was going on.... asked me to check the disk manager... the graphic bar area showed the MyBook as 5t, but the top part that is the list of all drives showed capacity of 500G... ?????
they had me do another quick format and of course that worked.. but movies gone again...

on further discussion about the WDLIVE PLUS I was told that was what was causing the problem.. well I don't know about that..

has anyone experienced anything similar???? I am going to move some files back and forth for the next couple of days and see if the capacity changes... if not I will connect to the WDLIVE and see what happens.
rgalka
Donor
 
Posts: 131
Joined: Fri Jun 24, 2011 11:37 am

PreviousNext

Return to WDTV Live

Who is online

Users browsing this forum: No registered users and 2 guests