Re: strange booting behavior

2015-05-27 Thread Petter Adsen
On Wed, 27 May 2015 15:50:12 + gofloss gofloss wrote: > ok, i have more data. i am still going crazy trying to get it to > boot. > > first, what does "cryptopts=source=" in the error message? what > does "-r" mean? > > Check cryptopts=source= bootarg:cat/proc/command line or > missing

Re: strange booting behavior

2015-05-27 Thread gofloss gofloss
ok, i have more data. i am still going crazy trying to get it to boot. first, what does "cryptopts=source=" in the error message? what does "-r" mean? Check cryptopts=source= bootarg:cat/proc/command line or missing modules, device:cat/proc/modules ls/dev -r ALERT! /dev/disk/by-uuid/[the

mount says an existing file system does not exist (was Re: strange booting behavior)

2015-05-25 Thread gofloss gofloss
hi arno, thank you for your explanation. i don't understand why i cannot mount the root partition. when it does not boot, it comes up with initrd busybox shell. i do cryptsetup luksOpen /dev/disk/by-uuid/[uuid] toshiba-root. this works. blkid shows that /dev/mapper/toshiba-root is there and i

RE: strange booting behavior

2015-05-20 Thread Arno Schuring
Hi, > On 5/19/15, Arno Schuring wrote: > > > > Note that you can add break=premount to the kernel cmdline > > to force an initramfs shell, then use sh -x /scripts/$phase/$script > > to manually step through the initramfs procedure. > > > > You can use "grep maybe_break /usr/share/initramfs-tools

Re: strange booting behavior

2015-05-19 Thread gofloss gofloss
On 5/19/15, Arno Schuring wrote: >> kernel loads and starts doing things for 7 seconds. > [..] > > Note that you can add break=premount to the kernel cmdline > to force an initramfs shell, then use sh -x /scripts/$phase/$script > to manually step through the initramfs procedure. > > You can use "g

RE: strange booting behavior

2015-05-19 Thread Arno Schuring
Hi, > i am still trying to get something to boot and will be grateful for > any suggestions, including other places to ask. [..] > > grub comes up, i select the default debian version. the > kernel loads and starts doing things for 7 seconds. [..] Note that you can add break=premount to the ker

Re: strange booting behavior

2015-05-19 Thread gofloss gofloss
i am still trying to get something to boot and will be grateful for any suggestions, including other places to ask. i don't understand why i am getting this boot error on the internal toshiba. it says it does not exist but it does exist? what does "-r" refer to? is it wrong to copy over one's i

Re: strange booting behavior

2015-05-17 Thread Petter Adsen
On Sun, 17 May 2015 16:56:20 + gofloss gofloss wrote: > On 5/17/15, Petter Adsen wrote: > > On Sun, 17 May 2015 05:42:40 + > > gofloss gofloss wrote: > >> the thumb drive is quick to describe. it's in the bios boot > >> sequence, but even though i put grub on it, it doesn't boot. > >>

Re: strange booting behavior

2015-05-17 Thread gofloss gofloss
On 5/17/15, Petter Adsen wrote: > You could also check if there are any updates available for your BIOS. the only update is a windows signing update. i am thinking that the best thing to do is to get the internal toshiba hard drive to work. it is, after all, starting to boot. -- To UNSUBSCRI

Re: strange booting behavior

2015-05-17 Thread gofloss gofloss
On 5/17/15, Petter Adsen wrote: > On Sun, 17 May 2015 05:42:40 + > gofloss gofloss wrote: >> the thumb drive is quick to describe. it's in the bios boot >> sequence, but even though i put grub on it, it doesn't boot. >> it just defaults to the next item on the sequence. so >> perhaps my com

Re: strange booting behavior

2015-05-17 Thread Petter Adsen
On Sun, 17 May 2015 05:42:40 + gofloss gofloss wrote: > the thumb drive is quick to describe. it's in the bios boot > sequence, but even though i put grub on it, it doesn't boot. > it just defaults to the next item on the sequence. so > perhaps my computer is not capable of booting thumb