It's through the USB hub that the problem is caused. I just connected it direct and it works so I guess my USB powered drive is ok direct as it seems to work ok - when I connect via the hub only wii flow seems to recognise it.
Is the DOL file also on the HDD? if it is, it might be that the forwarder can't find it. In that case you'd have to move your DOL file to an SD card or update the forwarder to one that supports UStealth (if such a thing has been made yet ) If it's actually getting into GX and can't initialize the drive ... not sure what to tell you in that case.
Having reliability issues over here with stealthed drives.
essentially using a stealthed drive, loaders only seem to initialize my hdd maybe 1 in 10.
most successful loader for initializing drive is usbloader gx, and yes I have tried cfg as well as wiiflow, and yes I am using the latest versions of the loaders as supplied in OP's post.
initializing problems are not present when the drive is not stealthed, however my primary issue is the nag.
I feel I should point out at this point that I am aware of using boot order to avoid the nag, however the system is primarily used by children aged between 4 and 13 (yes the youngest is quite good at mario), and trying to teach kids to put games back in their cases (the whole reason the wii was originally softmodded) never mind boot order processes to young children is difficult at best.
bottom line I just honestly don't trust one of them to not accidentally choose to reformat the drive with their games library on it.
I have a funny feeling it's going to be down to the age of my hdd, but if anyone is able to offer any suggestions I would be most appreciative.
also slightly off topic but has anyone got disc install working for usbloader gx on vWii?
when I try to install game to hdd using the system, the system seems to think game size is 0, and my freespace on drive is 0 then fails the install with a not enough space error.
at work atm and plan on re-looking at the issue when I get home, but in the mean time I leave this message in the hope someone is able to help with my woes.
I just compiled WiiMC today following this tutorial* as I also wanted to be able to use WiiMC with UStealth.
I modified, or more accurately, removed line 570 of fileop.cpp as suggested by Cyan and got rid of a couple of brackets as there was no longer an if statement. This gets rid of the MBR Signature Verification. Hopefully this is sufficient and I haven't caused a bigger unseen problem. I have tested it on my Wii U, however, and everything seems to be working so far.
Here are the compiled boot.dol and boot.elf. Once again, I'm not sure if I made some mistake making the necessary edit or in the compilation, so use these at your own risk. I haven't done anything with code for probably five years, so it's a distinct possibility. However, following the tutorial I linked to it should be possible to compile your own modified version, even for someone not familiar with development environments.
Good luck, and if anyone decides to use this (besides me), I'd be very interested to hear if it works.
Newer, bigger drives won't be supported as they use a different geometry - usually 4Kb sectors. For years, hard drives have had 512 byte sectors, but much bigger drives (usually over 2Tb) use 4kb sectors and the software (not only u-Stealth, but the USB launchers themselves) have been developed to work with 512kb drive geometries.
It was mentioned in the opening post
I haven't tested on a drive with 4kb sectors (newer) as I don't have one and it may work on one with 512b sector emulation, but I don't know.