SliTaz Forum

No init found on mounted partition

(3 posts) (2 voices)

• Started 12 years ago by relic_tinkerer
• Latest reply from relic_tinkerer
• This topic is resolved

Tags:

No tags yet.

1. 

   relic_tinkerer
   

   offline

   Member

   Hi all,
   After shelving the project for a couple of months, I've returned to trying to get Slitaz to work on an old Pentium laptop with 24MB RAM. I couldn't get any of the normal installation options to work (even floppy ended up hanging), so I decided to try a manual install. I used a DamnSmallLinux boot I was able to get working to set up the target and swap partitions (as the second and third partitions on the drive - the first is MS-DOS).

   I followed the Manual Installation instructions to get the Slitaz files onto my target partition and install GRUB 0.97. I went through a few iterations of trying to tweak the kernel to recognize the disk controller hardware, and tried to set up the config files that came to mind to fit my machine. However, I've hit a bit of a wall. The kernel seems to be able to find my hard drive, as indicated in this boot log segment:
   

   scsi0 : pata_mpiix
   ata1: PATA max PIO4 cmd 0x1f0 ctl 0x3f6 irq 14
   scsi1 : pata_legacy
   ata2: PATA max PIO4 cmd 0x170 ctl 0x376 irq 15
   ata1.00: ATA-0: FUJITSU M2714T, 3040, max MWDMA2
   ata1.00: 2125220 sectors, multi 0: LBA
   ata1.00: configured for PIO4
   ata1.00: configured for PIO4
   ata1: EH complete
   scsi 0:0:0:0: Direct-Access     ATA      FUJITSU M2714T   3040 PQ: 0 ANSI: 5
   sd 0:0:0:0: [sda] 2125220 512-byte hardware sectors: (1.08 GB/1.01 GiB)
   sd 0:0:0:0: [sda] Write Protect is off
   sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    sda:<5>sd 0:0:0:0: Attached scsi generic sg0 type 0
    sda1 sda2 sda3
   sd 0:0:0:0: [sda] Attached SCSI disk

   But even after seeming to mount the partition, it fails to find init (and I'm not sure what to think of the "hd: no drives specified" bit, since it seemed to identify it earlier):
   

   hd: no drives specified - use hd=cyl,head,sectors on kernel command line
   input: PS/2 Generic Mouse as /devices/platform/i8042/serio1/input/input2
   kjournald starting.  Commit interval 5 seconds
   EXT3-fs: mounted filesystem with writeback data mode.
   VFS: Mounted root (ext3 filesystem) readonly on device 8:2.
   Freeing unused kernel memory: 356k freed
   Warning: unable to open an initial console.
   Failed to execute /sbin/init.  Attempting defaults...
   Kernel panic - not syncing: No init found.  Try passing init= option to kernel.
   Pid: 1, comm: swapper Not tainted 2.6.30.6-slitaz #16
   Call Trace:
    [<c03d0826>] ? printk+0xf/0x11
    [<c03d078a>] panic+0x39/0xc6
    [<c01012f9>] init_post+0xc8/0xcb
    [<c051e4dc>] kernel_init+0xad/0xb4
    [<c051e42f>] ? kernel_init+0x0/0xb4
    [<c0103313>] kernel_thread_helper+0x7/0x10

   As a sanity check, this is what the relevant menu.lst entry looks like normally:

   title Slitaz 3.0 Custom (Kernel 2.6.30.6-custom)
   root (hd0,1)
   kernel /boot/bzImage root=/dev/sda2 init=/sbin/init vga=normal laptop

   And as another sanity check, I did check that /sbin/init does, in fact, exist on sda2, which is the only ext3 partition on this machine.

   I even tried to specify the cyl,head,sectors field at one point, but that didn't change the outcome. In case there's more that's relevant, I've attached the entire boot log up to the freeze. Any idea what I might be doing wrong here?

   Thanks!

   EDIT: I can't seem to get my text log to upload (denied mime), so if more of it is needed, please let me know, and I'll paste it into a response. Sorry!

   Posted 12 years ago #
2. 

   Bellard
   

   offline

   Key Master

   1- /sbin/init needs libraries in /lib (and some devices in /dev). Are they present ?

   2- You can check that the kernel see you disk partition:
   get http://mirror.slitaz.org/~bellard/busybox-static , remane it in /somewhere/sh and try to boot with
   kernel /boot/bzImage root=/dev/sda2 init=/somewhere/sh

   To get busybox commands, copy /somewhere/sh to /somewhere/busybox and run '/somewhere/busybox <cmd>'

   3- Tiny SliTaz (http://tiny.slitaz.org/) should boot in RAM. It should be useful to mount and test /dev/sda2 with a 'SliTaz' kernel.

   Posted 12 years ago #
3. 

   relic_tinkerer
   

   offline

   Member

   Thank you for the tips; I've finally got it booting!

   It turned out that I had made a mistake in converting the rootfs file's compression. I was doing the manual install with DSL, which does not have LZMA support, so I went to re-compress it into GZ. Well, I made a mistake along the way, and made it even worse in trying to correct it (Windows was involved). Long story short, I lost all of the Unix file type identifiers. So the files were there, but the ones in /dev didn't know they were block devices, etc., and the Busybox links in /sbin didn't know they were links.

   I started over on converting rootfs.gz's compression from LZMA to GZ, and this time things seemed to work.

   Now that the custom kernel is working, I've tweaked it just a little more, and have copied over the custom module set. It now appears to boot quasi-normally. Next step - try to get networking set up.

   Thanks again!

   Posted 12 years ago #

RSS feed for this topic

Reply

You must log in to post.