Muse Research

Kermit Jagger · Post by **Kermit Jagger** » Fri Jan 30, 2009 2:19 am

Today when I started my Receptor it got stuck on "initializing system...".

Rebooting and pressing the F12 key to start in verbose mode (to see what's happening during the boot), I got the usual "/dev/hda4 has gone donkey's years without being checked, check forced".

Tell you what, with a 500Gb drive installed, you've got time for a coffee... and then some ! It took over 1 hour 30 minutes to get this done. Pff....

Anyway, don't panic if this happens. Your machine is not broken.

buscemi · Post by **buscemi** » Fri Jan 30, 2009 2:27 am

Oh yeah, in all my years running Unix systems I haven't seen "donkey's ears" in that particular error message but fsck can take quite a while on large drives. Tried it on a large array once and let it run for days!

Kermit Jagger · Post by **Kermit Jagger** » Fri Jan 30, 2009 3:42 am

Donkey's years was my own addition. The message was giving a number of days.

okiikahuna · Post by **okiikahuna** » Fri Jan 30, 2009 3:51 am

DON'T PANIC?????????

What if you are about to go on? You mean I should just calmly tell the audience/band leader/club owner/promoter or whoever that they will just have to wait an hour and a half? At a time like that, I'd say panic is the only rational reaction.

This hasn't happened to me yet, but it is completely unacceptable. Is there any way to cause the system to do this dev/hda4 check fsck thing on my own schedule, before I reach the critical donkey's years mark?

K.

batgab · Post by **batgab** » Fri Jan 30, 2009 5:57 am

In English, please...???

buscemi · Post by **buscemi** » Fri Jan 30, 2009 2:03 pm

Kermit Jagger wrote:Donkey's years was my own addition. The message was giving a number of days.

I know

I've seen the real error (too) many times in my days.

Kermit Jagger · Post by **Kermit Jagger** » Fri Jan 30, 2009 4:42 pm

But okiikahuna makes a valid point. If that had happened on the road, I'd have been mega p.... off !

There should be an option to remove the forced check.

buscemi · Post by **buscemi** » Fri Jan 30, 2009 4:56 pm

is there the option to skip when you use verbose mode?

Kermit Jagger · Post by **Kermit Jagger** » Fri Jan 30, 2009 6:59 pm

Nope. That's what I was hoping for, but I had to go through with it.

oGG · Post by **oGG** » Fri Jan 30, 2009 9:52 pm

okiikahuna wrote:This hasn't happened to me yet, but it is completely unacceptable. Is there any way to cause the system to do this dev/hda4 check fsck thing on my own schedule, before I reach the critical donkey's years mark?

Maybe, just maybe, Muse is implementing the new ext4 filesystem on future software releases. From what I understand, one of the new features of ext4 is that checking filesystems is waaaaay faster than it's predecessor ext3. It skips checking unused parts of the disk. This probably won't help anyone with a huge drive that's full to its limits, but anyway...

--
Olle Gustafsson

bulletproofmessenger · Sat Jan 31, 2009 7:43 am

Lucky me, i was in the middle of a performance tonight and my receptor decided to do just that.....

It froze up after the CPU i believe spiked and there was no way to restart it the normal way, so i was forced to hold the start button till it reset.

At which time i figured ok, i could be back running in 2 minutes... and of course, after hours, it is STILL not past the initalizing phase..

I have a 500gb hard drive which is NOWHERE near full, and the ONLY reason i left it on is because i found this post on my blackberry during the show when i was hunting for a fix!

To be honest.. im disappointed... i bought this thing to be stable and trust worthy and within my first few weeks, this is what happens...

Any thoughts or suggestions or something so this doesnt happen again!!!

mat123 · Post by **mat123** » Sat Jan 31, 2009 9:32 am

muse, can you give a recommendation what to do if this happens on stage?

-mat123

Kermit Jagger · Post by **Kermit Jagger** » Sat Jan 31, 2009 11:59 am

bulletproofmessenger wrote:i was hunting for a fix!

That's why I posted here, thinking I wouldn't be the only one to have his Receptor do this and wondering why.

bulletproofmessenger · Sat Jan 31, 2009 5:27 pm

Update... 12 hours later... still stuck..... now what?!

there has to be more than it just having to check the disk because its brand new first off. Second it only went into this mode i believe because i had to hold the power button to restart it after the CPU overloaded and it froze..

Any thoughts?

batgab · Post by **batgab** » Sat Jan 31, 2009 8:10 pm

Maybe somebody who has had this occur should open a ticket at Plugorama to get a quick answer; quicker than waiting for a response to this thread. And if you do, keep us posted on the solution, please.

Thanks.

Muse Research

KVR Audio

Stuck on initializing - don't panic