Can't Locate Module Block-major-22

[Wareazy]

QUOTE(pelon @ Dec 29 2004, 03:08 PM)
I've created a HOWTO on restoring a C3000 from scratch.
Other than hardware problems, there should never be a need to send it back for reflashing.
I hope it helps.







I tried to Use the  guide to restore my zaurus 3000. I orignially screwed the pooch installing openBsd 3.7.  

And now i only get HDD1 error.

So following the instructions i get to step 4. type in the commands and get this
"
modprobe: modprobe: Can't locate module block-major-22
/dev/hdc: No such device or address

sfdisk: cannot open /dev/hdc read-write
"


If i try using the "mkhdd.sh" file i pretty much get the same error ... just more mombo jumbo to it ... MUCH MORE.

Some one help a newbie out please! Im going on a week trip to israel on thursday and would really love to have a working Zaurus by then!

[wiredog]

What did you do while installing OpenBSD that screwed it?  Any idea?  

I'm going to take a swing at it later today (on the C3000) if we can unbrick the C1000 and I'd like to know what went wrong...

[Wareazy]

What did you do while installing OpenBSD that screwed it?  Any idea? 

I'm going to take a swing at it later today (on the C3000) if we can unbrick the C1000 and I'd like to know what went wrong...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=81071\"][{POST_SNAPBACK}][/a][/div]

I hit no instead of yes at one of the prompts. I believe it was the formatting prompt but im not 100% on that.

Any help would be great! i've been bashing my head against the wall all weekend.

[wiredog]

All I can think of is do a B+D boot (to the emergency console) mkfs.ext2 hdd1 and hdd2 and then do option3->option1 from the maintenance menu to restore it to it's factory setting.  May need to format hdd3 as FAT as well.  

You need zimage, initrd.bin, updater.sh, and hdimage1.tgz on the sd or cf card when you do that.

[Wareazy]

All I can think of is do a B+D boot (to the emergency console) mkfs.ext2 hdd1 and hdd2 and then do option3->option1 from the maintenance menu to restore it to it's factory setting.  May need to format hdd3 as FAT as well. 

You need zimage, initrd.bin, updater.sh, and hdimage1.tgz on the sd or cf card when you do that.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=81079\"][{POST_SNAPBACK}][/a][/div]

Thanks Wiredog .. sounds like it might be something that would work ...

Any chance i can get that in idiot terms?

[Wareazy]

All I can think of is do a B+D boot (to the emergency console) mkfs.ext2 hdd1 and hdd2 and then do option3->option1 from the maintenance menu to restore it to it's factory setting.  May need to format hdd3 as FAT as well. 

You need zimage, initrd.bin, updater.sh, and hdimage1.tgz on the sd or cf card when you do that.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=81079\"][{POST_SNAPBACK}][/a][/div]

Just went through the first line of "mkfs.ext2 hdd1"
and i got

"
mke2fs 1.35 (28-Feb-2004)
Could not stat hdd1 --- No such file or directory

The device apparently does not exist: did you specify it correctly?
"

Any ideas ?

[wiredog]

Tio get to the emergency console unplug the Z and pull the battery. Wait about 5 seconds then reinsert the battery and plug it back in.  Hold down the B and D keys while pressing the On button, hold them until it starts to boot.  This boots it to an emergency console that runs entirely from the 16 Mb flash.  You should be able to 'mount -t ext2 /dev/hda /hdd1' from there.  If mounting fails, take a look at it with fdisk and see if the partition table got hosed.  Hopefully it didn't.  

If you can't fix it by hand, then try putting the files I mentioned (look around this site for links on where to get them, maybe try the Cacko ROM) on an SD card and resetting with those files (pull battery and power as above and, when you restart it, it should come up in a japanese menu.  Use option 3, then 1)

[Wareazy]

Tio get to the emergency console unplug the Z and pull the battery. Wait about 5 seconds then reinsert the battery and plug it back in.  Hold down the B and D keys while pressing the On button, hold them until it starts to boot.  This boots it to an emergency console that runs entirely from the 16 Mb flash.  You should be able to 'mount -t ext2 /dev/hda /hdd1' from there.  If mounting fails, take a look at it with fdisk and see if the partition table got hosed.  Hopefully it didn't. 

If you can't fix it by hand, then try putting the files I mentioned (look around this site for links on where to get them, maybe try the Cacko ROM) on an SD card and resetting with those files (pull battery and power as above and, when you restart it, it should come up in a japanese menu.  Use option 3, then 1)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=81095\"][{POST_SNAPBACK}][/a][/div]

The mount failed. saying
"
Can't find /hdd1 in /etc/fstab
"

I tried the fdisk and when i go to print the partition table.
It gives me the drive parameters and below that it says
"
          Device Boot          Start            End             Blocks            Id             System
"

Im not sure if that means i have hosed it or not.

What do i do with those files?

[Wareazy]

Tio get to the emergency console unplug the Z and pull the battery. Wait about 5 seconds then reinsert the battery and plug it back in.  Hold down the B and D keys while pressing the On button, hold them until it starts to boot.  This boots it to an emergency console that runs entirely from the 16 Mb flash.  You should be able to 'mount -t ext2 /dev/hda /hdd1' from there.  If mounting fails, take a look at it with fdisk and see if the partition table got hosed.  Hopefully it didn't. 

If you can't fix it by hand, then try putting the files I mentioned (look around this site for links on where to get them, maybe try the Cacko ROM) on an SD card and resetting with those files (pull battery and power as above and, when you restart it, it should come up in a japanese menu.  Use option 3, then 1)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=81095\"][{POST_SNAPBACK}][/a][/div]

The mount failed. saying
"
Can't find /hdd1 in /etc/fstab
"

I tried the fdisk and when i go to print the partition table.
It gives me the drive parameters and below that it says
"
          Device Boot          Start            End             Blocks            Id             System
"

Im not sure if that means i have hosed it or not.

What do i do with those files?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=81105\"][{POST_SNAPBACK}][/a][/div]

Can anyone help out please ?

[wiredog]

Try Cacko 3k  works well.  If you can't get it to install, might be time to call Trisoft or Dynamism (depending on who you bought it from) and get an RMA...

[lardman]

Exactly what command did you use to try to mount the partition and to look at it with fdisk?

The thing about it not existing in fstab is usually only displayed if you don't give the device name.


Simon

[Wareazy]

Exactly what command did you use to try to mount the partition and to look at it with fdisk?

The thing about it not existing in fstab is usually only displayed if you don't give the device name.


Simon
[div align=\"right\"][a href=\"index.php?act=findpost&pid=81261\"][{POST_SNAPBACK}][/a][/div]

The command i used was

'mount -t ext2 /dev/hda /hdd1'

i dont know much about this stuff ... but to me it looks like there are no partitions on the drive. and when i try to create the partitions i cant get them to be the size they are supposed to be, because it lists everything either in cylinders or in sectors.

Any ideas on how i can get them to be the right size?

also ... im following paelons instuctions on how to fix the zaurus. but im doing everything off an sd card, where all his instructions are for cf cards ... would the commands be significantly different?

Im talking about the

# sfdisk -uC /dev/hdc <<EOF
    # 0,203,83
    # ,816,83
    # ,6916,c
    # EOF
   
    # mke2fs -j /dev/hdc1
    # mke2fs -j /dev/hdc2
    # mkfs.vfat -F 32 /dev/hdc3

Another thing to note ... is that when i try these commands ...
i can only do

# sfdisk -uC /dev/hdc <<EOF
    < 0,203,83
    < ,816,83
    < ,6916,c
    < EOF

I dont know if there is a difference between the # and the < but i see it.

HELP PLEASE !

[Wareazy]

Does anyone know, how the drive should be broken up? In terms of cylinders and sectors?

Also, i got rid of the hdd1 error by creating a partition.
But now i get a hdd2 error.
Yes i already tried creating that ... i still get it ... it tells me it has to be an ext3 partition ... how do i create an ext3 partition?

I tried the cacko rom, it has problems with my partitions. I figure all i got to do is get the correct partitions on the drive, then the cacko rom should work.

Please help.

[pelon]

Exactly what command did you use to try to mount the partition and to look at it with fdisk?

The thing about it not existing in fstab is usually only displayed if you don't give the device name.


Simon
[div align=\"right\"][a href=\"index.php?act=findpost&pid=81261\"][{POST_SNAPBACK}][/a][/div]

The command i used was

'mount -t ext2 /dev/hda /hdd1'

i dont know much about this stuff ... but to me it looks like there are no partitions on the drive. and when i try to create the partitions i cant get them to be the size they are supposed to be, because it lists everything either in cylinders or in sectors.

Any ideas on how i can get them to be the right size?

also ... im following paelons instuctions on how to fix the zaurus. but im doing everything off an sd card, where all his instructions are for cf cards ... would the commands be significantly different?

Im talking about the

# sfdisk -uC /dev/hdc <<EOF
    # 0,203,83
    # ,816,83
    # ,6916,c
    # EOF
   
    # mke2fs -j /dev/hdc1
    # mke2fs -j /dev/hdc2
    # mkfs.vfat -F 32 /dev/hdc3

Another thing to note ... is that when i try these commands ...
i can only do

# sfdisk -uC /dev/hdc <<EOF
    < 0,203,83
    < ,816,83
    < ,6916,c
    < EOF

I dont know if there is a difference between the # and the < but i see it.

HELP PLEASE !
[div align=\"right\"][a href=\"index.php?act=findpost&pid=81266\"][{POST_SNAPBACK}][/a][/div]

The "#" is the linux prompt. You do not type this. Linux will automatically add the "<".  I wasn't clear enough for newbies on the help page. I will change it now. But I agree that the Cacko Rom is a superior replacement to the original sharp rom that you are trying to restore.

I've answered your other question on the "Pinned" post: As you follow the instructions to restore, you need to have a working, formatted CF card in the slot.

[Wareazy]

Ok ... after 6 days of head bashing ive done it.

I dont know what the actual issue was or why it was bugging out the way it was.
But I fixed it by creating the partitions that were listed in pelon's guide.
Using fdisk in reverse order ... that is hdd3, hdd2, hdd1.

Other wise i had a bogus hdd3 automatically created after hdd2.

Cacko installed on to the new partitions like it was always there.

So add this to one of the ways to try to get it to work before sending it in to Dynamism.