HDD not recognized after upgrade to 0.5.1.1 from 0.4.7.31.

[tshoag85]

I have searched the forum for hours without finding an exact match to my problem so here it is...

I have a WDTV Live (non-plus) that has been running 1.02.21_WDLXTV_Live-0.4.7.3 with PsychoTHC_OSD_MOD_v6.5.3 with Belkin USB Hub attached to 2x2TB HDDs and 1x3TB HDD (partitioned into 1TB and 2TB) and everything was working fine.

Yesterday I upgraded to the 1.02.21_WDLXTV_Live-0.5.1.1 and all went well (aside from the stuck on 0% issue which was remedied by unplugging the usb stick and plugging it back in). Nothing else has changed but after plugging in the USB drives (via usb hud or directly) the WDTV does not recognize the 3TB drive any longer. The other two drives show up as they did before but neither of the partitions from the 3TB drive show up like they used to. If 0.5.1.1 uses the same kernel as 0.4.7.3, I don't believe that the drive support would change. However, I am not sure what else could be causing this. I hooked up the drive to my computer and there was no damage to the data or partitions.

How can I get the WDTV to recognize the 3TB HDD partitions?

[recliq]

Have you checked the disk in windows (chkdsk)?
If the WD even thinks the drive is marked dirty it won't mount it.

[RMerlin]

Have you checked the disk in windows (chkdsk)?
If the WD even thinks the drive is marked dirty it won't mount it.

Good thing it's not as picky with dirty UMSP plugins

[tshoag85]

Yes, chkdsk came back clean on both partitions.

[recliq]

Yes, chkdsk came back clean on both partitions.

Shall this be interpreted as "It still doesn't mount" ?

[tshoag85]

Yes, chkdsk came back clean on both partitions.

Shall this be interpreted as "It still doesn't mount" ?

Yes, i ran chkdsk, it said there was no issues and it still doesn't mount.

[tshoag85]

Anyone have any idea why the HDD would not be recognized now that I have upgraded? Nothing else has changed.

[tshoag85]

Went back to 0.4.7.31 and the drive partitions show up as they did before. Not sure what it is about 0.5.1.1 that was not recognizing drive. I guess I have to stick with 0.4.7.31 for now.

[colinpowell]

I am having the same problem - an HDD that previously worked consistently is now intermittently recognised by the WDTV upon upgrade from 0.4.5.3 to 0.5.1.1. Nothing else has changed in the system setup.

I have a single WD HDD (1TB) enclosure (passport, I think it is called?) connected via USB directly to the WDTV. I may have to revert back to an earlier version - but wish to retain UMSP youtube subscriptions.

[mad_ady]

To make sure it is seen after standby, you need to eject it first. Either from the remote, or by adding these lines in POWER_DOWN_ACTION (see the webend):

Code: Select all

umount /dev/sda1; eject /dev/sda


For this to work, you mustn't use any app.bins, osd.bins, etc.