On Fri, Nov 07, 2014 at 12:29:31PM +0100, Achim Spreen wrote: > Hello. > > I have a laptop without cdrom or floppy and it isn't > usb-bootable. After an unsuccessfull installation mininal of debian > wheezy 7.6 i got only a initramfs prompt, busybox and little programs > in /sbin and /bin. I can't write on the disk, all changes get lost after > reboot. Can i and when how write to the disk ? > > Here some output: > > #Grub menu: > > GNU GRUB > ... > search --fs-uuid > echo > ... > linux /boot/vmlinuz-3.2.0-4-686-pae ro > ... > > #boot: > > ... > [ 0.927417] Simple Boot Flag at 0x6e set to 0x1 > ... > [ 0.965249] ERST: Table is not found ! > [ 0.965312] GHES: HEST is not enabled ! > ... > [ 2.129223] sd 0:0:0:0: [sda] Write Protect is off > [ 2.129471] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, > doesn't support DPO or FUA > ... > [ 2.484098] sda: sda1 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 > sda2 > ... > Begin: Loading essential drivers ... done > Begin: Running /scripts/init-premount ... done > ... > modprobe: module unknown not found in modules.dep > mount: can't read '/etc/fstab': No such a file or directory > Begin: Running /scripts/local-bottom ... done > done > Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev > failed: No such a file or directory > done > Target filesystem doesn't have requested /sbin/init. > No init found. Try passing init= bootarg. > [ 4.899187] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver > ... > > > BusyBox v1.20.2 > (Debian 1:1.20.0-7) built-in shell (ash) > Enter 'help' ... > > /bin/sh: > can't access tty: job control turned off > (initramfs) _ OK, so initramfs hasn't been able to find your root filesystem. I thought that generally resulted in the kernel panicking, but apparently not. I notice that you haven't told the kernel where your root filesystem is, though, so either autodetection hasn't worked or there is no autodetection. I would suggest adding "root=<device>" to the end of the "linux /boot/vmlinuz-3.2.0-4-686-pae ro" line, where "<device>" is any valid way of telling linux where the device is (so you could say /dev/sda1, LABEL=rootfs, UUID=1234-567... etc etc). If that works and you get into your system, re-run "sudo update-grub" to fix the grub configuration. > > Bye > > > -- > To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject > of "unsubscribe". Trouble? Contact listmaster@lists.debian.org > Archive: [🔎] aaad2d0fdf31192f09b774865a1fd7a7@andaluciajunta.es">https://lists.debian.org/[🔎] aaad2d0fdf31192f09b774865a1fd7a7@andaluciajunta.es >
Attachment:
signature.asc
Description: Digital signature