I dunno what happened. I'm connected to my computer via serial and USB (In USB mode.) and I'm uploading music. This is about the third day I've had it, everything has been great up until now. While uploading some tunes, I got hit with a hard error. Said something to the tune of SYNCHRONIZATION FAILED AT 6XXXX With only the O.K. button to continue. So I hit O.K., and Emplode went away. Now, my empeg is sitting here clicking. Click... Click... Click... Which is definitly the hard-drive. Sounds as though (Under careful ear) that it is writing clickity clickity clickity, then a noticable hard CLICK. You could keep time by it, seems to hard click every second. Doesn't sound ugly, sounds more like the drive is stuck on a bad block or something and doesn't know what to do. So I powered it down, powered it back up. Same deal. Disconnected everything and let it sit for a couple hours. Same problem. Reconnected everything and re-uploaded 6a. The drive stopped it's clicking while the flash upgrade was happening, but then as soon as it was done. Click Click Click. I tried synchronizing it again, but emplode hangs on the synchronizing part. This happen to anyone else? Or am I looking at a serious problem?

That does sound serious, from your description it looks very much like a failed hard disk. I guess it had to happen to one of us one of these days (the good thing is that if a hard disk is going to fail it tends to be in first couple of days or years later, like most complex electro-mechanical devices).

I assume that you have contacted empeg to let them know ?

__
Unit serial number 47 (was 330 in the queue)...

Yes, I wrote them. I'm somewhat savvy in the way of computers, although I don't know Linux. I did download the developers flash, and then connect to the unit via serial cable. And was treated to the following error basically repeated over and over...

hda: irq timeout: status=0xd0 { Busy }
end_request: I/O error, dev 03:04 (hda), sector 178654

So it looks to me as though it's a bad sector. I guess there is no scandisk for the empeg? Worst comes to worst I will have to send it in to the U.S. support center. Give that place it's first customer.

Nope, Second. Im sending my empeg there on Monday because my display was broken the day i opened it. :( Do you know where its located by any chance?
-Jordan

While at the prompt ($ )do the following:

$ rw

$ fsck -y /dev/hda4

$ ro

This should fix your file problems if any. It should also avoid bad sectors if it encounteres them

Good Luck

[email protected]

...a little note: don't mount rw to do a fsck. It doesn't need it, as it access the device directly, and it'll all mess up as the drive is still mounted. A better idea is to do:

$ umount /dev/hda4
$ fsck ...

Hugo

Sorry about that! You should always umount (unmout) a mounted partition before you do an fsck. This avoid the OS writing to disk as you are checking it.

Sorry about that.

[email protected]

Tell that to Microsloth...I haven't gotten through a complete Win98 Defrag/Scandisk since I bought the box a year ago!

_~= Dearing =~_
"WAY too happy about having #99."

Does this look healthy? Me thinks I got a bad drive... It keeps on keeping on with the bad blocks. Click Click Click.


Pass 1: Checking inodes, blocks, and sizes
hda: status error: status=0x09 { DataRequest Error }
hda: status error: error=0x04 { DriveStatusError }
hda: drive not ready for command
hda: status error: status=0x01 { Error }
hda: status error: error=0x04 { DriveStatusError }
hda: drive not ready for command
hda: status error: status=0x01 { Error }
hda: status error: error=0x04 { DriveStatusError }
hda: drive not ready for command
hda: status error: status=0x01 { Error }
hda: status error: error=0x04 { DriveStatusError }
hda: drive not ready for command
ide0: reset: success
hda: irq timeout: status=0xd0 { Busy }
ide0: reset: success
hda: irq timeout: status=0xd0 { Busy }
end_request: I/O error, dev 03:04 (hda), sector 54618
Error reading block 27309 (Attempt to read block from filesystem resulted in sho
rt read) while reading indirect blocks of inode 2050. Ignore error? yes

hda: status timeout: status=0xd0 { Busy }
hda: drive not ready for command
ide0: reset: success
hda: irq timeout: status=0xd0 { Busy }
ide0: reset: success
hda: irq timeout: status=0xd0 { Busy }
end_request: I/O error, dev 03:04 (hda), sector 55132
Error reading block 27566 (Attempt to read block from filesystem resulted in sho
rt read) while reading indirect blocks of inode 2050. Ignore error? yes

hda: status timeout: status=0xd0 { Busy }
hda: drive not ready for command
ide0: reset: success
hda: irq timeout: status=0xd0 { Busy }
ide0: reset: success
hda: irq timeout: status=0xd0 { Busy }
end_request: I/O error, dev 03:04 (hda), sector 55646
Error reading block 27823 (Attempt to read block from filesystem resulted in sho
rt read) while reading indirect blocks of inode 2050. Ignore error? yes

You most definitely need to call tech support



Kamau Wanguhu
[email protected]
http://www.BORGcube.com

Yea, now if they'll just answer my email... Day 3... No reply at all. Of course, I think their down in Florida with all that Hurricane activity and Tsunami's and what not. So they might not be in. Or worse yet, their pinned under a telephone pole.

If you're getting no response from us-support, please mail us directly ([email protected] should be able to help) - though we have talked to them recently and they are operational again.

Hugo