hdd problem

[adm]

Or maybe there's a better way of doing it.

It reminds me of one of the early Topfield PVR features where during boot-up the OS didn't wait long enough for the HDD to spin up from cold. Cured, I remember, by the simple act of adding a extra small delay before attempting to read the disk during the boot process. Perhaps with 2.5 inch disks and slower startup-ups for green drives the timing is marginal for some HDDs?

I've recently put back a USB memory stick into the mix. When the internal HDD (2.5 inch, 1TB fitted by the sponsor) goes missing the USB stick is always found.

[ccs]

It reminds me of one of the early Topfield PVR features where during boot-up the OS didn't wait long enough for the HDD to spin up from cold. Cured, I remember, by the simple act of adding a extra small delay before attempting to read the disk during the boot process. Perhaps with 2.5 inch disks and slower startup-ups for green drives the timing is marginal for some HDDs?

Yes, it would be much better if more time was given to allow the HDD to get ready, assuming it's the same issue that Toppies sometimes suffered from.

I've recently put back a USB memory stick into the mix. When the internal HDD (2.5 inch, 1TB fitted by the sponsor) goes missing the USB stick is always found.

How does the stick work in practice? Does it become the default movie location, using the same folders/bookmarks that the timers expect?
I always imagined a stick would just be another location which your timers would have to explicitly use.

[birdman]

Is init 3 the right one to do a full reboot??

Er, no. That will put the system into state 3 - which should be what it is already in, so would do nothing.
If you want a full reboot then the command to use is:

reboot

[birdman]

Yes, it would be much better if more time was given to allow the HDD to get ready, assuming it's the same issue that Toppies sometimes suffered from.

Or some way for the BIOS (or whatever) to either not respond until it is done, or to be able to indicate it is still initializing hardware and therefore not to query it yet.

How does the stick work in practice? Does it become the default movie location, using the same folders/bookmarks that the timers expect?

I've seen this a few times. In my case it "took over" the hard disk location, and was mounted as /media/hdd. I've stopped that by ensuring the partitions are mounted by UUID, so if the disk fails to spin up I have no disk at all (although it hasn't done that since I forced the mount locations).

[ccs]

I've seen this a few times. In my case it "took over" the hard disk location, and was mounted as /media/hdd. I've stopped that by ensuring the partitions are mounted by UUID, so if the disk fails to spin up I have no disk at all (although it hasn't done that since I forced the mount locations).

Now you mention it, so have I - I fitted a usb stick when I first got the box, and was very confused when recordings "failed", only to find them later on the memory stick.
So the missing hdd has probably been happening almost from day 1.

[birdman]

Actually, on thinking about it, it was probably not that the disk didn't show up, but that the USB stick and the hdd were detected in the "wrong" (== different) order. So the USB stick became /media/hdd and the hdd became /media/hdd2.

[adm]

I've seen this a few times. In my case it "took over" the hard disk location, and was mounted as /media/hdd.

When my HDD went missing the USB stick was still identified as /media/usb

etc/fstab seems to have the correct UUID for the HDD and USB

[Donkeyface]

Are people still having this problem? i posted this issue back in july and got nothing back!
http://www.world-of-satellite.com/sh...873#post363873

i get this problem twice a month at the moment but a restart fix's for the next week or 2.

I have had this on Hades up to version 3.2.9.
has this issues been resolved yet or some kind of work around?

Cheers