Menu
▾
▴
devil-linux-develop
|
From: Diego T. <dt...@co...> - 2003-10-27 23:37:32
|
i've found several problems when using the install-on-usb script.
installing lilo as a bootloader is commented. Therefore, i suppose that its deprecated.
If not, there is an error:
Last chance, do you really want to continue ? (y/n)
mke2fs 1.33 (21-Apr-2003)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
32256 inodes, 129008 blocks
6450 blocks (5.00%) reserved for the super user
First data block=1
16 block groups
8192 blocks per group, 8192 fragments per group
2016 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 33 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
tune2fs 1.33 (21-Apr-2003)
Setting maximal mount count to -1
copying files...
cp: cannot stat `/boot/boot.b': No such file or directory
syncing and unmounting (this could take a while)
and thats true, because /boot is on my partition, not in the tarball, neither on the lfs.
when using grub i get also a strange error:
Setting maximal mount count to -1
copying files...
Probing devices to guess BIOS drives. This may take a long time.
GRUB version 0.93 (640K lower / 3072K upper memory)
[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the possible
completions of a device/filename.]
grub> quit
GRUB version 0.93 (640K lower / 3072K upper memory)
[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the possible
completions of a device/filename.]
grub> root ,0)
Error 11: Unrecognized device string
grub> setup
Error 11: Unrecognized device string
grub> quit
syncing and unmounting (this could take a while)
--
-- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799
-- Use of a keyboard or mouse may be linked to serious injuries or disorders.
Diego Torres - dt...@co... - Madrid / España
|
|
From: Bruce S. <bw...@ar...> - 2003-10-28 00:13:15
|
> i've found several problems when using the install-on-usb script. > > installing lilo as a bootloader is commented. Therefore, i suppose that its deprecated. Yes, lilo is no longer used. > grub> root ,0) What exactly did you enter when it ask for partition name? It appears like you may have entered something like: "/dev/sda" instead of "/dev/sda1" - BS |
|
From: Diego T. <dt...@co...> - 2003-10-28 00:30:32
|
On Mon, Oct 27, 2003 at 07:11:22PM -0500, Bruce Smith wrote:
> What exactly did you enter when it ask for partition name?
> It appears like you may have entered something like:
> "/dev/sda" instead of "/dev/sda1"
i entered /dev/sda1
i've inserted the following:
$grub_shell --batch --device-map=$device_map <<-EOF
quit
EOF
install_drive=$(grep "$1\$" $device_map|cut -f1)
root_drive="${install_drive%%)},0)"
+echo install_drive: $install_drive
+echo root_drive: $root_drive
+echo dolar1: $1
+echo dolar2: $2
+echo device_map: $device_map
$grub_shell --batch --device-map=$device_map <<-EOF
root $root_drive
setup $force_lba $install_drive
quit
EOF
And this is the output:
copying files...
grep: grub-tmp-map: File not found
install_drive:
root_drive: ,0)
dolar1: /dev/sda
dolar2: 0
device_map: grub-tmp-map
And thats true, when is the file grub-tmp-map created?
--
-- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799
-- Use of a keyboard or mouse may be linked to serious injuries or disorders.
Diego Torres - dt...@co... - Madrid / España
|
|
From: Bruce S. <bw...@ar...> - 2003-10-28 00:37:07
|
> > What exactly did you enter when it ask for partition name? > > It appears like you may have entered something like: > > "/dev/sda" instead of "/dev/sda1" > > i entered /dev/sda1 Where are you running the script from (what directory)? I think it requires you run "./install-on-usb" from the "dist" directory, where you unpacked the tarball, or output directory of "make dist". If you're running it from anywhere else, it'll probably die. - BS |
|
From: Diego T. <dt...@co...> - 2003-10-28 00:46:09
|
On Mon, Oct 27, 2003 at 07:35:10PM -0500, Bruce Smith wrote: > > > It appears like you may have entered something like: > > > "/dev/sda" instead of "/dev/sda1" > > > > i entered /dev/sda1 > > Where are you running the script from (what directory)? i'm running it from the dist directory (and yes, i'm executing ./install-on-usb). -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Diego T. <dt...@co...> - 2003-10-28 00:46:57
|
On Mon, Oct 27, 2003 at 07:35:10PM -0500, Bruce Smith wrote: > > If you're running it from anywhere else, it'll probably die. when and by whom is the file grub-tmp-map created? -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Diego T. <dt...@co...> - 2003-10-28 01:47:27
|
On Mon, Oct 27, 2003 at 07:35:10PM -0500, Bruce Smith wrote: > > If you're running it from anywhere else, it'll probably die. problem found. i'm using devfsd, so: # cat grub-tmp-map (fd0) /dev/floppy/0 (hd0) /dev/ide/host0/bus0/target0/lun0/disc (hd1) /dev/ide/host0/bus1/target0/lun0/disc (hd2) /dev/ide/host2/bus0/target0/lun0/disc (hd3) /dev/ide/host2/bus1/target0/lun0/disc (hd4) /dev/scsi/host0/bus0/target0/lun0/disc and because of this, none of the commands entered to grub work. :/ help! :) -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
|
From: Bruce S. <bw...@ar...> - 2003-10-28 02:16:47
|
> problem found. i'm using devfsd, so: > # cat grub-tmp-map > (fd0) /dev/floppy/0 > (hd0) /dev/ide/host0/bus0/target0/lun0/disc > (hd1) /dev/ide/host0/bus1/target0/lun0/disc > (hd2) /dev/ide/host2/bus0/target0/lun0/disc > (hd3) /dev/ide/host2/bus1/target0/lun0/disc > (hd4) /dev/scsi/host0/bus0/target0/lun0/disc > > and because of this, none of the commands entered to grub work. :/ help! :) Ah, OK. What's it do when you enter "/dev/scsi/host0/bus0/target0/lun0/disc" when it asks for the device file? - BS |
|
From: Heiko Z. <he...@zu...> - 2003-10-28 02:21:37
|
Diego Torres wrote:
>On Mon, Oct 27, 2003 at 07:35:10PM -0500, Bruce Smith wrote:
>
>
>>If you're running it from anywhere else, it'll probably die.
>>
>>
>
>problem found. i'm using devfsd, so:
># cat grub-tmp-map
>(fd0) /dev/floppy/0
>(hd0) /dev/ide/host0/bus0/target0/lun0/disc
>(hd1) /dev/ide/host0/bus1/target0/lun0/disc
>(hd2) /dev/ide/host2/bus0/target0/lun0/disc
>(hd3) /dev/ide/host2/bus1/target0/lun0/disc
>(hd4) /dev/scsi/host0/bus0/target0/lun0/disc
>
>and because of this, none of the commands entered to grub work. :/ help! :)
>
>
I guess we need some intelligence in the script.
This line is most likely the problem:
GRUBPART=$(expr ${PARTITION##/dev/[hs]d[a-z]} - 1)
cya
Heiko
|
|
From: Bruce S. <bw...@ar...> - 2003-10-28 02:49:41
|
> >problem found. i'm using devfsd, so:
> ># cat grub-tmp-map
> >(fd0) /dev/floppy/0
> >(hd0) /dev/ide/host0/bus0/target0/lun0/disc
> >(hd1) /dev/ide/host0/bus1/target0/lun0/disc
> >(hd2) /dev/ide/host2/bus0/target0/lun0/disc
> >(hd3) /dev/ide/host2/bus1/target0/lun0/disc
> >(hd4) /dev/scsi/host0/bus0/target0/lun0/disc
> >
> >and because of this, none of the commands entered to grub work. :/ help! :)
> >
> I guess we need some intelligence in the script.
> This line is most likely the problem:
>
> GRUBPART=$(expr ${PARTITION##/dev/[hs]d[a-z]} - 1)
Yeah, that'll do it. I'll take a look tomorrow.
What distribution are you running? Does it come standard with devfs?
- BS
|
|
From: Diego T. <dt...@co...> - 2003-10-28 07:52:40
|
On Mon, Oct 27, 2003 at 09:35:04PM -0500, Bruce Smith wrote:
> > >and because of this, none of the commands entered to grub work. :/ help! :)
> > >
> > I guess we need some intelligence in the script.
> > This line is most likely the problem:
> >
> > GRUBPART=$(expr ${PARTITION##/dev/[hs]d[a-z]} - 1)
>
> Yeah, that'll do it. I'll take a look tomorrow.
Not sure. Because on my system, (as i'm running devfsd), i have /dev/sda and /dev/sda1 as links
to /dev/host0.../disc and blahblahblah/part1.
So the problem is beyond that point, because grub doesn't recognize root /dev/host0.../disc as a valid option.
>
> What distribution are you running? Does it come standard with devfs?
Debian unstable.
--
-- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799
-- Use of a keyboard or mouse may be linked to serious injuries or disorders.
Diego Torres - dt...@co... - Madrid / España
|
|
From: Heiko Z. <he...@zu...> - 2003-10-28 00:29:20
|
Diego Torres wrote: >i've found several problems when using the install-on-usb script. > >installing lilo as a bootloader is commented. Therefore, i suppose that its deprecated. > Kind of. We left it in there, so people can use/modify it if they want to. >If not, there is an error: > >Last chance, do you really want to continue ? (y/n) >mke2fs 1.33 (21-Apr-2003) >Filesystem label= >OS type: Linux >Block size=1024 (log=0) >Fragment size=1024 (log=0) >32256 inodes, 129008 blocks >6450 blocks (5.00%) reserved for the super user >First data block=1 >16 block groups >8192 blocks per group, 8192 fragments per group >2016 inodes per group >Superblock backups stored on blocks: > 8193, 24577, 40961, 57345, 73729 > >Writing inode tables: done >Writing superblocks and filesystem accounting information: done > >This filesystem will be automatically checked every 33 mounts or >180 days, whichever comes first. Use tune2fs -c or -i to override. >tune2fs 1.33 (21-Apr-2003) >Setting maximal mount count to -1 >copying files... >cp: cannot stat `/boot/boot.b': No such file or directory >syncing and unmounting (this could take a while) > > >and thats true, because /boot is on my partition, not in the tarball, neither on the lfs. > It actually requires that you have lilo installed. We could get rid of those messages by including the necessary files. But then again, grub is the one which should be used. ;-) >when using grub i get also a strange error: > >Setting maximal mount count to -1 >copying files... >Probing devices to guess BIOS drives. This may take a long time. > > >GRUB version 0.93 (640K lower / 3072K upper memory) > >[ Minimal BASH-like line editing is supported. For the first word, TAB >lists possible command completions. Anywhere else TAB lists the possible >completions of a device/filename.] >grub> quit > >GRUB version 0.93 (640K lower / 3072K upper memory) > >[ Minimal BASH-like line editing is supported. For the first word, TAB >lists possible command completions. Anywhere else TAB lists the possible >completions of a device/filename.] >grub> root ,0) > >Error 11: Unrecognized device string >grub> setup > >Error 11: Unrecognized device string >grub> quit >syncing and unmounting (this could take a while) > > > I'm not familiar with grub. Heiko |
|
From: Diego T. <dt...@co...> - 2003-10-28 00:40:24
|
> >Error 11: Unrecognized device string > >grub> setup > > > >Error 11: Unrecognized device string > >grub> quit > >syncing and unmounting (this could take a while) > > > I'm not familiar with grub. same here. because of that i tried to use lilo, with no success :( -- -- gnupg keyfingerprint -- 48AF 5BF9 8F54 2966 64CC 2327 7CD0 DD91 B09D 5799 -- Use of a keyboard or mouse may be linked to serious injuries or disorders. Diego Torres - dt...@co... - Madrid / España |
