Verbose means that the screen displays the loading sequence, and perhaps where it gets stuck. This is how I realise the first time that the drive was being checked as opposed to the machine not booting.
My Receptor did this again recently. This time, I noticed that it had been booted 38 times since the last check, suggesting the HD check is set to occur every 39 boots in OS 1.7. If true, this is something to know for gigging musos since you can do boot 39 at home to get around the long boot time, and have the quick boot sequence at your gig.
If nothing shows up after pressing the F12 key, the problem is "unknown" since it could be many things (bios error, psu failure, cpu failure, ram failure, motherboard failure, etc.) so you need to open a ticket to contact Muse about what to do next.
Stuck on initializing - don't panic
-
- KVRian
- Topic Starter
- 571 posts since 14 Oct, 2004 from UK
-
- KVRian
- Topic Starter
- 571 posts since 14 Oct, 2004 from UK
Sorry I never saw your post.
If nothing happens when pressing F12, then you need to contact Muse as it's likely there is a more serious problem than simply disk check.
If nothing happens when pressing F12, then you need to contact Muse as it's likely there is a more serious problem than simply disk check.
-
- KVRer
- 11 posts since 13 Jun, 2008
I just had this issue pop up while programming some new patches in my receptor. I had to restart the box after a plugin froze things up, then I found myself looking at a perpetual "Initializing system" message.
This is, of course, annoying and in my opinion, unnecessary. As soon as the forced disk check is complete, I'll shut it off and do manual checks every now and then.
FYI, you can do this by using tune2fs or a similar linux tool (provided you have root shell access to your receptor).
typing tune2fs -c 0 -i 0 /dev/sda1 will disable filechecks, where /dev/sda1 is the volume the box uses for storage (you can see this by typing "mount" or "cat /etc/fstab"
Not removing automatic disk checking directly contradicts the reliability-concept of the receptor, In my opinion! (indeed, what'd happen if your receptor starts checking its harddrive just before showtime? nightmare!)
This is, of course, annoying and in my opinion, unnecessary. As soon as the forced disk check is complete, I'll shut it off and do manual checks every now and then.
FYI, you can do this by using tune2fs or a similar linux tool (provided you have root shell access to your receptor).
typing tune2fs -c 0 -i 0 /dev/sda1 will disable filechecks, where /dev/sda1 is the volume the box uses for storage (you can see this by typing "mount" or "cat /etc/fstab"
Not removing automatic disk checking directly contradicts the reliability-concept of the receptor, In my opinion! (indeed, what'd happen if your receptor starts checking its harddrive just before showtime? nightmare!)
-
- KVRist
- 91 posts since 22 Dec, 2006
If I understand you correctly, you can disable this "frightening" filecheck thing everyone is complaining about by doing what you've just described.octotonic wrote:I'll shut it off and do manual checks every now and then.
FYI, you can do this by using tune2fs or a similar linux tool (provided you have root shell access to your receptor).
typing tune2fs -c 0 -i 0 /dev/sda1 will disable filechecks, where /dev/sda1 is the volume the box uses for storage (you can see this by typing "mount" or "cat /etc/fstab"
Not removing automatic disk checking directly contradicts the reliability-concept of the receptor, In my opinion! (indeed, what'd happen if your receptor starts checking its harddrive just before showtime? nightmare!)
I am not a Linux geek (far from it, actually...), but I would like to disable that for safety. Receptor is my only module, so if I get stuck before a gig, I just can't imagine what I'll do...
Is the procedure you have given in the previous message OK? I've always been afraid of doing the root access thing and tweak the register... Maybe I'll ask a friend.
Demierra
-
- KVRer
- 11 posts since 13 Jun, 2008
yep, that's correct. As soon as my receptor is done fsck'ing, I'll post the exact procedure to do just this.demierra wrote:
If I understand you correctly, you can disable this "frightening" filecheck thing everyone is complaining about by doing what you've just described.
I am not a Linux geek (far from it, actually...), but I would like to disable that for safety. Receptor is my only module, so if I get stuck before a gig, I just can't imagine what I'll do...
Is the procedure you have given in the previous message OK? I've always been afraid of doing the root access thing and tweak the register... Maybe I'll ask a friend.
Demierra
Gaining root shell access to your receptor is easy, however you need some basic linux skills. Best leave it to someone a bit more experienced, and make sure you follow the tutorial _exactly_. You can find a good tutorial by googling for "muse receptor root access".
-
- KVRian
- Topic Starter
- 571 posts since 14 Oct, 2004 from UK
Very good of you, but I suggest you post the procedure at the Yahoo group as Muse don't like users posting advanced stuff here.