OESF Portables Forum
General Forums => General Discussion => Topic started by: daniel3000 on March 27, 2006, 11:46:57 am
-
Hello,
please help! It seems I got in serious trouble.
After many failed attempts to get bluetooth to work, I tried to install the bluetooth_support package from hluc's website.
I did it on the command line to see possble error messages. There were many ("bad tar header" followed be depmod error messages "cannot find ...bluez.o" or similar), then suddenly QTopia terminated and restarted.
Everything seemed normal.
then I decided to reboot the entire machine in order to have a clean system.
But when trying to mound hda1, it fails and gives me a "HDD1 error!!".
with B+D boot I tried an fsck on /dev/hda1 to no avail.
Strange: fdisk /dev/hda shows a fourth partition with Start secrot 1, End sector 1, 0 blocks and ID 0 ("Empty").
What's that? Is that normal? Deleting that partition does not work. It gives a warning "Warning: partition has empty type" and the partition is still there.
If I try to assign another type in fdisk using "t", it says "Partition 4 does not exist yet".
Well, what can I do now?
Thanks a lot
daniel
-
Seems after the fscks on hda1 and hda2 it mounts the FSs again, but still cannot boot correctly.
I don't get the HDD1 error anymore, but instead many, many error messages. Some of the interesting ones are scrolled away by looping ones so fast that I cannot read them.
Are they written to some file so I can read them in the B+D system?
After booting the INIT process the nightmare begins:
A looping message:
grep: /var/lib/pcmcia/stab: No such file or directory
After that (pressing Ctrl-C):
Can't open /etc/ioctl.save O_WRONLY: No space left on device
ending in
Can't find /dev in /etc/fstab
Rebooting the system
And the stuff begins again.
From B+D I can mount hda1 and hda2 without any problem rw.
Seems it mounts hda2 readonly or something like that...
daniel
-
I can only sympathize with you Daniel. I have had some really bad problems with my C3000. I think the small ram size really makes this machine a unstable. As soon as I get my machine up and running I am going to sell it, and get either the c1000, or the C31000. But the C3000 (which I love the white body), just is not stable.
If the 16mb RAM was able to be overcome, like just use the harddrive to boot up from, then it would be a much more stabler machine. IMHO, I am still a linux newbie, and I know you are an excellent hacker! I will be curious how you fix the problems.
Here is a good listing of places I have found that have helped other people (Unfortunatly not me)
http://www.xlfag.com/zaurus/ (http://www.xlfag.com/zaurus/)
http://www.trisoft.de/en_c3000howto.htm (http://www.trisoft.de/en_c3000howto.htm)
http://forum.zaurusfr.org/viewtopic.php?p=...ed8a589d7ad01df (http://forum.zaurusfr.org/viewtopic.php?p=36&sid=172059f7302191a7ded8a589d7ad01df)
Lareya
P.s.
I purchased your serial light for the Hp200lx a long time ago. I still have them and they work
-
I can only sympathize with you Daniel. I have had some really bad problems with my C3000. I think the small ram size really makes this machine a unstable. As soon as I get my machine up and running I am going to sell it, and get either the c1000, or the C31000. But the C3000 (which I love the white body), just is not stable.
If the 16mb RAM was able to be overcome, like just use the harddrive to boot up from, then it would be a much more stabler machine. IMHO, I am still a linux newbie, and I know you are an excellent hacker! I will be curious how you fix the problems.
Here is a good listing of places I have found that have helped other people (Unfortunatly not me)
http://www.xlfag.com/zaurus/ (http://www.xlfag.com/zaurus/)
http://www.trisoft.de/en_c3000howto.htm (http://www.trisoft.de/en_c3000howto.htm)
http://forum.zaurusfr.org/viewtopic.php?p=...ed8a589d7ad01df (http://forum.zaurusfr.org/viewtopic.php?p=36&sid=172059f7302191a7ded8a589d7ad01df)
Lareya
P.s.
I purchased your serial light for the Hp200lx a long time ago. I still have them and they work
[div align=\"right\"][a href=\"index.php?act=findpost&pid=120528\"][{POST_SNAPBACK}][/a][/div]
Aha, funny :-) I still have a list of all people having bought that light from me. But who are you?
I'll probably solve my problem restoring a backup of hdd2 manually via the B+D boot console.
I have already restored hdd1 from my backup Zaurus (identical machine, duplicated setup from some months ago).
hdd1 is read-only, so nothing should have changed since then.
Unfortunately, that was not the solution.
Now the next step will be a copy of hdd2 of the backup machine.
But hdd2 holds the applications, so I'll lose all applications installed after I lastly duplicated the setup onto the other Zaurus.
I'm also considering a new clean install of Cacko and all applications. WIll probably do so soon, but first will try to use this hdd2 restore method.
Firstly to learn about the system, secondly to save some time now, so I can work with the Zaurus tomorrow.
Having one operable Zaurus with all my current user data, I can then use the other one to make a fresh install.
A fresh install is probably the best solution anyway, because during all the attempts to install various things (Bluetooth, X/QT, a lot of applications I never need etc.) a lot of crap must have been collected on my file systems.
I'm especially curious if my bluetooth cards and dongles will finally work on a clean Cacko install :-]
Having learned a lot with my previous install (which is now almost a year old) I'll be able to kepp the new one quite clean and optimize everything from scratch.
And I have learner that I'll try new drivers etc FIRSTLY on the duplicated backup machine, then, if they work, also install them on the main machine!!
Fortunately, I have lost no user data, because I keep almost all user data on an SD card, and even the data on hdd3 is still intact (the B+D system just copies it over to another SD card, just in case the new installation will destroy some data, or I accidentally type "dd if=/mnt/card/hdd2_image of=/dev/hda3" to restore the hdd2 image form the backup machine :-))
I'm also considering switching to a C1000 (much room for wireless hardware inside :-) or a C3100 (advantage: much more room for applications on hdd2 than in a C1000!)
During my backup / restoring activities in the last few hours I saw that I have about 280MB of application data on hdd2, much too much for a C1000. ANd installing programs on card does not work well sometimes, I was told.
Well, time will tell.
take care!
daniel
-
SOLVED. PHEW!
As always, it was the last option of what I chose to restore.
I used the B+D console to restore from the backup unit with identical setup but older version of the setup:
/dev/hda1
--> No avail
/dev/hda2
--> No avail
/dev/mtdblock3 (/home)
--> Then it booted correctly again!
Then I re-restored the backuped (assumed to be defective) /dev/hda2 and now I am back in business with almost no data loss.
IÄm not sure if I have modified something in /home since the last duplication of my setup to the backup machine. If so, I'll probably notice it soon. I have also made a backup of the defective mtdblock3 partition, so I can restore single files from it in case I now lost something.
That was a long night. But I have learned a lot and have been reminded in the imporance of good backups.
good night
daniel
-
SOLVED. PHEW!
As always, it was the last option of what I chose to restore.
I used the B+D console to restore from the backup unit with identical setup but older version of the setup:
/dev/hda1
--> No avail
/dev/hda2
--> No avail
/dev/mtdblock3 (/home)
--> Then it booted correctly again!
Then I re-restored the backuped (assumed to be defective) /dev/hda2 and now I am back in business with almost no data loss.
IÄm not sure if I have modified something in /home since the last duplication of my setup to the backup machine. If so, I'll probably notice it soon. I have also made a backup of the defective mtdblock3 partition, so I can restore single files from it in case I now lost something.
That was a long night. But I have learned a lot and have been reminded in the imporance of good backups.
good night
daniel
[div align=\"right\"][a href=\"index.php?act=findpost&pid=120567\"][{POST_SNAPBACK}][/a][/div]
I looks like your problem is that you ran out of space on the flash during installation. The C3000 only has like 4MB for /home and all the the modules/drivers and /etc are also located on this tiny place
This was one of the reason why I am not running Sharp/Cacko on my C3000 anymore. pdaXrom and OZ run off the microdrive so this problem does not exist there.
-
I looks like your problem is that you ran out of space on the flash during installation. The C3000 only has like 4MB for /home and all the the modules/drivers and /etc are also located on this tiny place
This was one of the reason why I am not running Sharp/Cacko on my C3000 anymore. pdaXrom and OZ run off the microdrive so this problem does not exist there.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=120591\"][{POST_SNAPBACK}][/a][/div]
Regarding the possible reason for the problem pls. see my private email to you.
How does pdaXrom work on the 3000? Well enough for serious work without an enhanced danger of data loss compared to Cacko?
daniel
-
SOLVED. PHEW!
As always, it was the last option of what I chose to restore.
I used the B+D console to restore from the backup unit with identical setup but older version of the setup:
/dev/hda1
--> No avail
/dev/hda2
--> No avail
/dev/mtdblock3 (/home)
--> Then it booted correctly again!
Then I re-restored the backuped (assumed to be defective) /dev/hda2 and now I am back in business with almost no data loss.
IÄm not sure if I have modified something in /home since the last duplication of my setup to the backup machine. If so, I'll probably notice it soon. I have also made a backup of the defective mtdblock3 partition, so I can restore single files from it in case I now lost something.
That was a long night. But I have learned a lot and have been reminded in the imporance of good backups.
good night
daniel
[div align=\"right\"][a href=\"index.php?act=findpost&pid=120567\"][{POST_SNAPBACK}][/a][/div]
I looks like your problem is that you ran out of space on the flash during installation. The C3000 only has like 4MB for /home and all the the modules/drivers and /etc are also located on this tiny place
This was one of the reason why I am not running Sharp/Cacko on my C3000 anymore. pdaXrom and OZ run off the microdrive so this problem does not exist there.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=120591\"][{POST_SNAPBACK}][/a][/div]
I met the same problems some time ago, but not so lucky, I lost all the contents since no backup since I have owned it.
Meanie, would you like to give more information on the source of HDD1 crash? I was wondering whether this is a HDD problem.
-
SOLVED. PHEW!
As always, it was the last option of what I chose to restore.
I used the B+D console to restore from the backup unit with identical setup but older version of the setup:
/dev/hda1
--> No avail
/dev/hda2
--> No avail
/dev/mtdblock3 (/home)
--> Then it booted correctly again!
Then I re-restored the backuped (assumed to be defective) /dev/hda2 and now I am back in business with almost no data loss.
IÄm not sure if I have modified something in /home since the last duplication of my setup to the backup machine. If so, I'll probably notice it soon. I have also made a backup of the defective mtdblock3 partition, so I can restore single files from it in case I now lost something.
That was a long night. But I have learned a lot and have been reminded in the imporance of good backups.
good night
daniel
[div align=\"right\"][a href=\"index.php?act=findpost&pid=120567\"][{POST_SNAPBACK}][/a][/div]
I looks like your problem is that you ran out of space on the flash during installation. The C3000 only has like 4MB for /home and all the the modules/drivers and /etc are also located on this tiny place
This was one of the reason why I am not running Sharp/Cacko on my C3000 anymore. pdaXrom and OZ run off the microdrive so this problem does not exist there.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=120591\"][{POST_SNAPBACK}][/a][/div]
I met the same problems some time ago, but not so lucky, I lost all the contents since no backup since I have owned it.
Meanie, would you like to give more information on the source of HDD1 crash? I was wondering whether this is a HDD problem.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=120647\"][{POST_SNAPBACK}][/a][/div]
There are several reasons why you would get the hdd1 error message that I know off, but there are probably many more.
1. the filesystem on hdd1 is corrupted, but this is not very likely because hdd1 is read only most of the time so it gets rarely written to and hence has very slim chance of getting corrupted.
2. the partition table is corrupted which probably can happen if you had failed attempts of flashing another ROM or you have been playing around with fdisk and messed something up.
3. the microdrive is broke, but if that is the case, then a factory reset wouldn't do you much good either unless you only have a few bad sectors.
4. the flash is 100% full. /var and /etc are on flash so if its full, then no pid file can be generated and things will get screwy.
5. your mount point has been accidentally removed so you cannot mount /hdd1
6. rc.rofilesys is corrupted due to failed flashing or user modifications
7. you pull out your external CF card during boot just when the Z is trying to figure out which CF is the internal microdrive.
The only way to tell really is if you go into the emergency console with D+B during boot and have a look around to check what has happened.