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 » Tue Oct 20, 2015 1:03 am

hi there. its been ages since i have been in the forum. but i came again because i have an issue after many years. i just got a 4tb western digital hdd, which i put in an external case. the hdd is formated in ntfs and is a gpt partition (otherwise my pc wouldnt see the whole 4tb space). after reading a lot in this forum, i installed this firmware 1.05.04_V_WDLXTV.COM_WDLXTV_LIVE-0.5.1.1. still no luck and the wd live wont see my hdd. ive posted in the firmwares thread but they redirected me here. i cant format in ext3 as from what i read ext3 is a linux partition and i have a windows pc. so, is there any simple solution to my problem? will it be perhaps fixed in a future update of firmware? should we expect a new update?
before anyone says that the hdd or external case have a problem, the hdd is shown with also no problems at all, in my raspberry pi that i use as a media player and in my windows pc as well...i am puzzled...

cheers and thanx
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 20, 2015 1:34 am

Please post the output of the following commands:
Code: Select all
fdisk -l
dmesg
lsusb
User avatar
mad_ady
Developer
 
Posts: 4549
Joined: Fri Nov 05, 2010 9:08 am
Location: Bucharest, Romania

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

Postby BURNIN AMBITION » Tue Oct 20, 2015 2:25 am

mad_ady wrote:Please post the output of the following commands:
Code: Select all
fdisk -l
dmesg
lsusb

thank you for your answer. it took me some time to figure out how to execute the commands. finally i did it. here are the results (mind you the hdd is connected to the wd live, but it isnt recognised
Code: Select all
WDTVLIVE login: root
  _  _  _ ______  _       _     _ _______ _     _
(_)(_)(_|______)(_)     (_)   (_|_______|_)   (_)
  _  _  _ _     _ _         ___      _    _     _
| || || | |   | | |       |   |    | |  | |   | |
| || || | |__/ /| |_____ / / \ \   | |   \ \ / /
  \_____/|_____/ |_______)_|   |_|  |_|    \___/
           1.05.04_V_WDLXTV.COM_WDLXTV_LIVE-0.5.1.1
# 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: 2199.0 GB, 2199023255552 bytes
256 heads, 63 sectors/track, 266305 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sdb1               1      266306  2147483647+ ee EFI GPT
# 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...
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
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
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
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
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>sd 0:0:0:0: uevent: unsupported action-string; this will be ignored in a future kernel version<3> target0:0:0: uevent: unsupported action-string; this will be ignored in a future kernel version<3> host0: uevent: unsupported action-string; this will be ignored in a future kernel version<3>usb-storage 1-1:1.0: uevent: unsupported action-string; this will be ignored in a future kernel version<3>usb_endpoint usbdev1.2_ep02: uevent: unsupported action-string; this will be ignored in a future kernel version<3>usb_endpoint usbdev1.2_ep81: uevent: unsupported action-string; this will be ignored in a future kernel version<3>usb 1-1: uevent: unsupported action-string; this will be ignored in a future kernel version<3>usb_device usbdev1.2: uevent: unsupported action-string; this will be ignored in a future kernel version<3>usb_endpoint usbdev1.2_ep00: 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-2: new high speed USB device using tangox-ehci-hcd and address 3
usb 1-2: 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     WDC WD40 EZRX-00SPEB0     0    PQ: 0 ANSI: 6
sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
sd 1:0:0:0: [sdb] READ CAPACITY(16) failed
sd 1:0:0:0: [sdb] Result: hostbyte=0x05 driverbyte=0x00
sd 1:0:0:0: [sdb] Use 0xffffffff as device size
sd 1:0:0:0: [sdb] 4294967296 512-byte hardware sectors (2199023 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00
sd 1:0:0:0: [sdb] Assuming drive cache: write through
sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
sd 1:0:0:0: [sdb] READ CAPACITY(16) failed
sd 1:0:0:0: [sdb] Result: hostbyte=0x05 driverbyte=0x00
sd 1:0:0:0: [sdb] Use 0xffffffff as device size
sd 1:0:0:0: [sdb] 4294967296 512-byte hardware sectors (2199023 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00
sd 1:0:0:0: [sdb] Assuming drive cache: write through
sdb: unknown partition table
sd 1:0:0:0: [sdb] Attached SCSI disk
sd 1:0:0:0: Attached scsi generic sg1 type 0
usb-storage: device scan complete
sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
sd 1:0:0:0: [sdb] READ CAPACITY(16) failed
sd 1:0:0:0: [sdb] Result: hostbyte=0x05 driverbyte=0x00
sd 1:0:0:0: [sdb] Use 0xffffffff as device size
sd 1:0:0:0: [sdb] 4294967296 512-byte hardware sectors (2199023 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00
sd 1:0:0:0: [sdb] Assuming drive cache: write through
sdb: unknown partition table
usb 1-1: USB disconnect, address 2
# lsusb
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 003: ID 174c:55aa ASMedia Technology Inc.
Bus 001 Device 001: ID 0000:0000
#
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 20, 2015 3:07 am

I added code blocks for better readability. I can see that fdisk sees the drive as 2TB (which is expected, because it's an older version of fdisk), but the problem is that the kernel sees the drive as 2TB as well and fails to understand the partition table.

Can you tell us the following:
1. the output of uname -a
2. Are you running the ext3 version of 0.5.2.2 or the flash version? When you flashed did you have the fff file on your USB drive? Wait - I see you're running 0.5.1.1. Can you try to flash 0.5.2.2?
3. @lovilela: Can you give us a dmesg output from your working system?
User avatar
mad_ady
Developer
 
Posts: 4549
Joined: Fri Nov 05, 2010 9:08 am
Location: Bucharest, Romania

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

Postby BURNIN AMBITION » Tue Oct 20, 2015 3:36 am

mad_ady wrote:I added code blocks for better readability. I can see that fdisk sees the drive as 2TB (which is expected, because it's an older version of fdisk), but the problem is that the kernel sees the drive as 2TB as well and fails to understand the partition table.

Can you tell us the following:
1. the output of uname -a
2. Are you running the ext3 version of 0.5.2.2 or the flash version? When you flashed did you have the fff file on your USB drive? Wait - I see you're running 0.5.1.1. Can you try to flash 0.5.2.2?
3. @lovilela: Can you give us a dmesg output from your working system?


uname -a
Code: Select all
# uname -a
Linux WDTVLIVE 2.6.22.19-19-4 #9 PREEMPT Mon Aug 1 14:35:04 CST 2011 mips GNU/Linux
#


i am running the flash version and have also tried the 0.5.2.2 version with no luck. havent tried the ext3 version since i dont have linux in my pc. and yes i had the fff file in the usb. shouldnt i?

thank you for all your help. i hope we can sort it out. from what you say i understand that it should be working but it isnt... right?
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 20, 2015 4:17 am

Yes, it should be working. Can you also try to post the output of the commands on the first page? The ones in /proc especially? At least until lovilella gives us his output...
User avatar
mad_ady
Developer
 
Posts: 4549
Joined: Fri Nov 05, 2010 9:08 am
Location: Bucharest, Romania

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

Postby BURNIN AMBITION » Tue Oct 20, 2015 8:36 am

mad_ady wrote:Yes, it should be working. Can you also try to post the output of the commands on the first page? The ones in /proc especially? At least until lovilella gives us his output...


sorry for being a noob, but i checked the first page of this thread thoroughly and didnt find any commands to execute , other than the ones i already did. perhaps i missunderstood something?
should i reformat the hdd? and if yes (which will be a pain since it is almost full) what would be the proper procedure to create a gpt ntfs partition that will function ok with wd? (my pc and raspberry state that there is no problem with it, i also did check with chckdsk /f and also hd sentinel says it is fine


edit. i noticed that when i shut down wd the usb stick i have on it, still goes on (usb stick light, is on). perhaps this could be some bug of it and thats why it cant recognise my usb hdd as well? just guessing)
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 » Wed Oct 21, 2015 11:08 pm

Sorry, I thought I had them on the first page. Try this command:
Code: Select all
zcat /proc/config.gz | grep PARTITION


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...
User avatar
mad_ady
Developer
 
Posts: 4549
Joined: Fri Nov 05, 2010 9:08 am
Location: Bucharest, Romania

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

Postby BURNIN AMBITION » Thu Oct 22, 2015 12:55 am

mad_ady wrote:Sorry, I thought I had them on the first page. Try this command:
Code: Select all
zcat /proc/config.gz | grep PARTITION


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...


thank you my friend. i executed the code. here are the results

Code: Select all
# zcat /proc/config.gz | grep PARTITION
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
CONFIG_LDM_PARTITION=y
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_KARMA_PARTITION is not set
CONFIG_EFI_PARTITION=y
# CONFIG_SYSV68_PARTITION is not set
CONFIG_XENV_PARTITION=y


i hope they help.
ps. i dont have a usb drive other than a usb flash drive stick. if it is the same, i could try to do what you proposed, at night. anyway, thank you so much. cheers
ps2. yesterday i upgraded to the latest firmware.stilll no luck...
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 1:27 am

Yeah, output shows that EFI partitions are supported by the kernel. Try with any USB flash drive, doesn't matter the size. Also, enable and send me DMASOD_DEBUG log (/tmp/dmaosd.txt I think) after a boot with the GPT drive.
User avatar
mad_ady
Developer
 
Posts: 4549
Joined: Fri Nov 05, 2010 9:08 am
Location: Bucharest, Romania

PreviousNext

Return to WDTV Live

Who is online

Users browsing this forum: No registered users and 1 guest