Totally Bricked C3000, Can use only D+B Menu Options

[lareya]

Okay,
I have been trying now for two days straight to get into the diagnostic menu. I have HDD2 Error, and I can't get past it. I have done the OK & Power on thing. (menu 3 -1-Y) I have done it extensively. But i still get the same error. I have gone to the page for Restoring a C3000 from scratch I am trying to do that also. I can't get into the DB menu or the DM menu. I have been trying over and over and over. I took my batteries out for overnight even - still, can't get into any of the useful diagnostic menus.

what is the trick? I have all my files on the CF card (512mb)

I'm really frusterated! I had Cackobeta on and X/QT from when I received the Zaurus. I tried to re-install cacko, the first part worked on that, but when I tried the Second part (3-1-Y) I get the same error:

error Hdd2,
EXT3-fs unable to read superblock
hdc2: bad access: block=2, count=2

any more ideas? I am getting tired of yanking out the battery and trying to do a DM or DB

Lareya

[lareya]

Okay, then if this is hopless (after another round of trying to get the DM menu up by removing batterty overnight, plugging in the electric (cuz no lights if I don't), and then only way to do get anything to work is to turn on the machine & press D+M at the same time. It just boots up with the linux guy and gives me this error:

EXT-FS unrecognized mount option quiet
hda: hda1
hda: hda1
cramfs: wrong magic
hda: hda1
hda: hda1
VFS: Can't find a Minix or Minix V2 fileyststem on device 03:01.
hda: hda1
hda: hda1
MSDOS FS: IO charset utf8
Trying to free nonexistent resource <7000000-f700000f>
hdc: ST68022CF, ATA DISK drive
ide1 at0xf7000000-0xf7000007,0xf700000e on irq 136
hdc: 15625008 sectors (8000 MB) w/128kiB Cache, CHS=15501/16/63
hdc: [PTBL ] [972/255/631] hdc1
ide_cs: hdc: Vcc = 3.3, Vpp = 0.0
hdc: hdc1
hdc: hdc1
kjournald starting. Comit interval 5 seconds
EXT3-fs: mounted filesytem with ordered data mode.
hdc2: bad access: block=2, count=2
EXT#-fs: unable to read superblock
mount: Mounting /dev/hdc2 on /hdd2 failed: Invalid argument
HDD2 Error!! start check battery !

If no one can help me, can you please recommend a place where I can send my Z to get fixed?
I bought it second hand, so have no warranty.

Lareya

[stbrock]

This thread might help.

[lareya]

Thinks for your reply. I will try all those types of codes. This is really frusterating. I am about to just toss this whole thing out my window!

Is there any other way I can do a nand backup? can I take out the card (yes open case) and do it from my pc?

Lareya

[lareya]

Okay here is what I get when I try to flash cacko beta1 with the ok key + On/Off 4-1-y (menu)


Zaurus CF updater
kernel

0% 100%
Sucess!
RO file system
Flash erasing ... done
0% 100%

Sucess
Master Version
Success!

HDD RO filesystem
Now formatting ....
Now Extracting ...

then it blacks out after a while, and boots to the ol' familiar error that I copied so laborously above that no one seems to tell me what it means - my hard drives are hosed? my drives are not mounted? I have no flash memory? I don't know. But it is the same always.

I still can't seem to get into a NAND menu - altho with the last help from stbrock, I have more keys to try over and over again.....ad nauseaum. I think I am going to go stark raving mad

Lareya

[lareya]

Okay here is what I get when I do the ok key + On/Off 2-2-Y (menu)

[System HDD check]
Now checking HDD1...
/dev/hdc1: 3182/977280 files (0.1% non-contiguous), 55091/1951889 blocks
ok

Now checking HDD2...
fsk.ext3: Invalid argument while trying to open /dev/hdc2
/dev/hdc2:
the superbolock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:

e2fsck -b 8193 <device>

Error!

File system errors left uncorrected.

I would love to run e2fsck, but can't get to a prompt to do it in!!!

(I hope it is okay to keep posting my details/errors)

Lareya

[stbrock]

The 3000 works a good bit differently from my 860, so I'm just guessing here. Using Fn+D+N I got to a somewhat different group of diagnostic menus than I'd seen before and tried a number of different things and was not sure exactly what finally worked or why. In my case, I got a lot of messages which sounded like trashed hardware and was about to throw the 860 in the garbage more than once, but ultimately the messages seemed to be artifacts of scrambled OS files that went away once I got the NAND restore to quit failing.

You might try flashing the Sharp ROM instead of Cacko. I believe both Conic and Trisoft have original NAND files. Flashing from different brands of CF card seemed to make a difference for me. Then there is erasing using the diagnostic menu and other exciting menu options to try in desperation. You probably can't make things worse -- its already bricked and none of the menus will make it explode on you AFAIK.

If all this fun eventually wears thin, Trisoft might be more likely to undertake a repair in your situation than some other dealers from what I've seen posted.

[Mjolinor]

I think I would take the microdrive out and check the file system on a PC with a card reader. If it isn't OK then repartition it on the PC.

You will need a Linux PC to do it but a live boot one such as Knoppix or Ubuntu will work.

[Meanie]

You should boot into the DMR using the D+B key option. Once you get in there, you can use fdisk and e2fsck to check your disk and partitions.

Unplug everything from your Zaurus, then pull out your battery. Press and hold D and B keys and reinsert battery. Make sure you keep both keys depressed while putting the battery back in and after locking the lid, press the on button. The Zaurus should now boot into the DMR partition and you can login using root with no password.

fdisk -l /dev/hda

should show you your partition table and you should have 3 partitions.
/dev/hda1 should be ext3
/dev/hda2 should be ext3
/dev/hda3 should be vfat

if you dont have them, then you need to recreate the partitions using fdisk.

if they exist, then you can use e2fsck to check /dev/hda2 and fsck.vfat to check /dev/hda3
or you can just reformat the partitions which probably would be faster if you dont want to keep what is on those partitions.

[lareya]

some how I was able to get a zaurus prompt, and I login as root.
Now I did this command

fdisk -l /dev/hda and I got this message
modprobe: modprobe: Can't locate module block-major-3

I ran this command: e2fsck -b 8193 /hda
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains and ext2filewywtem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

When I tried this:
fdisk /dev/hda I get this Again -
modprobe: modprobe: Can't locate module block-major-3
modprobe: modprobe: Can't locate module block-major-3

fdisk /hda again tried this
Unable to open /hda

fsck.vfat -a /dev/hda I get this -
modprobe: modprobe: Can't locate module block-major-3
open /dev/hda: No such device or address


I am not going to turn this Zaurus off, so please someone help me.
Is there something else I can use? run off my CF or SD card?
I just want to reformat my drive and set it with the three partitions like meanie said.

Lareya

[lareya]

I was able to get into the NAND menu. I followed the instructions found Returning Your Zaurus SL-C3000 To It's Factory Settings regarding placing the NAND file on a CF card for my c3000, however when I hit return/OK twice it has this on the menu
file:systc300.dbk
Execute restore?
and then it seems to be hanging. I don't see/hear anything going on. It seems frozen.

Any susgestions?

Lareya

[distortion]

this sounds not good at all, sorry to hear about your troubles. looks like you have tried most of the things i would go for, im a long way from being an expert but here are a few other things i would try:
cacko and pdaxrom have a lot of usefull nand utilities in there install scripts. it could be worth trying to at least get something working with them. if you can even get a bootstrap image to go into flash rom then you will have more tools to get things going.
it sounds to me like your hard drive is either dead or the has a very broken layout. im on a windoze pc at the mo and cant check what i had to use to raise disks from the dead before but there is a huge amount of info on this for linux in general. fdisk should find something and dmesg should tell you if not, why not.

will try and follow your post and also see if i can find anything out this evening. best of luck with it.
stan

[distortion]

there is a link to trisoft on this page

http://www.oesf.org/forums/index.php?showtopic=9038

the pdf manual is good and only heard good reports about trisoft. the restore script 'might' get things back to the origional state.

[Mjolinor]

I was able to get into the NAND menu.  I followed the instructions found Returning Your Zaurus SL-C3000 To It's Factory Settings regarding placing the NAND file on a CF card for my c3000, however when I hit return/OK twice it has this on the menu
file:systc300.dbk
Execute restore? 
and then it seems to be hanging.  I don't see/hear anything going on.  It seems frozen. 

Any susgestions?

Lareya

You did tell it to "execture restore" I assume? It can take a while.

[lareya]

Yes, I did tell it to execute restore. That is when it just hung - nothing, no indicator, nothing. Stayed that way until I left for home (30 -40 minues). I had to take the batteries out for it to do something.

Regarding the okay/On menu: I get the japanese prompts, but am unable to do anything here either. It is selected on the number 1, and no amount of coaxing can get it to move to the 3rd option. I try to move it with arrow keys, try to move it with sylus, try to move it with the number. Nothing....just sets there. I hit the okay key, and it still sits there (it is my understanding that 1. is the cancel prompt. Will nothing works except to pull the batteries out again.

I am going to try and get into the other menu (D + M/B) and see if I can do anygood (damage) there. It is upsetting, cuz I got it with cacko beta, and XQT second hand - without a SD/CF card in it. I didn't flash it . But, it seemed to choke on removal of the CF card cuz I was trying to put in a CF wireless card and it froze. I couldln't get it to boot up after that in cacko beta. I have been trying ever since then to get it to flash or Nand with the info on trisoft, and the other sites I have mentioned in my above posts. With my 860, it was easy to flash between roms. I never seemed to have this much problems with it, and I was BRAND new with linux then.

So I am able to login as root, but my partitions are not there. what are the commands to repartition my hard drive? fdisk -l /dev/hda yields this info
/dev/hda: 512mb (it finds my CF card)
Device /dev/hda1
Boot *
Start 1
End 991
Blocks 499432+
ID 6
System Fat16

/dev/hda2
Boot
Start 1
End 1
Blocks 0
ID 0
System Empty


Partition 1 has different physical/logical endings:
phys=(991,15,63) logical=(990,15,63)

/dev/hda2
Partition 2 has different physical/logical beginnings (non-Linux?):
phys=(0,0,0) logical=(0,0,1)
Partition 2 has different physical/logical endings:
phys=(0,0,0) logical=(4260880,4,4)
Partition 2 does not end on cylinder boundary.

Because my 4g mdrive was toast, I put in a 8g CF card - since I read that you could just re-partition the drive. The orginal 4g mdrive did the same thing. Both cards act the same.

Lareya.
(thinking about to give up and sell them for a Dell Axiom or an OQ00)