Re: DEFINITE BUG !!! "Not Installed / Not formatted" status
- This is exactly the problem I have experienced, but nothing I have
done so far as brought the unit back, it would seem that until a
unit can be re-recognised, there will not be a solution.
A number of people have reported that using devices with a Cypress
chipset does not experience the problem, have you tried interfaces
with this chipset?
--- In email@example.com, "K. Carter Sr."
> Your equipment is not the problem. I've had the same problem as
> many people are experiencing. A perfectly working NSLU2 for what
> ever the reason hiccups and your hard drive is no longer there. The
> NSLU2 reports your hard drive as Not Installed, "left the
> The only way to get it back is to re-format the drive. But WAIT!
> When I check the drive using several different programs that can
> read & write to the drive, they all show everything is there and in
> order. I can use the drive just fine attached to anything EXCEPT
> NSLU2 and access the files. I've also used a plethora of differentre-
> USB chipsets with different cases. The NSLU2 still has the same
> problem. I've even used a direct USB 2.0 to IDE cable capable of
> handling drives over 250 GB and that didn't stop the problem from
> When this problem happens, even though there is nothing physically
> wrong with the hard drive, you have to re-format it to get the
> to want to talk to it again. WEIRD!!!it
> Also, I was able to create the problem I think (I haven't done this
> more than once, maybe someone should follow up on this), if I
> altered the time stamp on the passwd file (by coping and resaving
> back to the hard drive, the NSLU2 refused to recognize the driveroot,
> ever again until I reformatted it again, like I said before, even
> though there is nothing wrong with the drive or the files on it.
> I've figured out other ways to get the NSLU2 to stop talking to the
> hard drive too, sometimes accessing a file with the uid set to
> or aborting a large file transfer, etc..., And once it's gone, it's
> I'm tring to figure out how to get it to re-recognize the drive
> after it has this problem. The problem is that even if I do figure
> out how to get the NSLU2 to see the HD again. It's just a matter of
> days, sometimes hours before something causes the NSLU to hiccup
> again and loose the hard drive. This needs a permanent solution.
> Oh well, back to the drawing board. If anyone figures out why the
> NSLU2 can't talk to the HD after and error, REPLY PLEEESE...