Re: help need for powerpc issue
Jo
> >
> > Bean wrote:
> >>
> >> Hi,
> >>
> >> Have you make any progress on this problem ? I've created a forked
> >> project BURG which is based on grub2, you can try if that works for
> >> you.
> >>
> > Yes I make 2 step beyond (better then the song isn't it ;<).
> > The first I mentioned in a patch proposal
> > (<http://lists.gnu.org/archive/html/grub-devel/2009-11/msg00053.html>) which
> > get me rid of annoying "cursor-on cursor-on word unknown".
>
> Hi,
>
> Yep, the cursor-on problem affects sparc64-ieee1275 as well and it's
> quite annoying, I've disabled it in BURG.
>
Btw any comment on my proposal?
> >
> > The second is about the immediate fallback to 'rescue mode' at thestart up:
> > I just need to add normal module to my grub-mkelfimage ;<)
> >
> > That said, I read well your announce of your BURG proj and I already grab
> > the branch but I did yet test it, sorry ;<(
> > And tbh I don't know yet how much time will I still have access to the
> > system (the company start a process of restructuration which impact my job
> > but when, it's not yet clear. I hope to be able to advise you soon)
> >
Ok here am I back unfortunately with sad news: it failed to boot :
DEFAULT CATCH!, exception-handler=fff00300
at %SRR0: 0000000000c3c25c %SRR1: 800000000000b002
Call History
------------
@ - c3c1f0
close-package - c58060
(poplocals) - c3a758
(init-program) - c7e298
boot - c7ec7c
evaluate - c4a638
invalid pointer - d5f95d
invalid pointer - f
invalid pointer - f
catch - c38fe8
bt-task-boot-on-this - d0fd90
(poplocals) - c3a758
catch - c38fe8
execute-device-method - c58bcc
(poplocals) - c3a758
(select-boot-seq) - c59ba4
Client's Fix Pt Regs:
00 00100000000001f4 ffffffffffffffff 00000000deadbeef
fffffffffffffffc
04 0000000000000000 0000000000000000 0000000000000000
0000000000000001
08 0000000000001000 0000030002001000 0000000000000003
0000000000007000
0c 0000000022800000 0000000000c17100 0000000000c18000
000000000009c4b0
10 0000000000d94fa8 0000000000d94c39 0000000000c57d80
0000000000c58060
14 0000000000000000 ffffffffffffffff 0000000000000000
0000000000000000
18 0000000000c13000 0000000000c38000 0000000000c14d40
0000000000c16ec0
1c 0000000000c20000 0000000000c3fdf0 0000000000c11ea0
0000000000c10fa8
Special Regs:
%IV: 00000300 %CR: 84800000 %XER: 20000008 %DSISR:
08000000
%SRR0: 0000000000c3c25c %SRR1: 800000000000b002
%LR: 0000000000c3c1f0 %CTR: 0000000000000000
%DAR: ffffffffffffffff
Virtual PID = 0
ofdbg
Just build as usual:
1/ autogen.sh
2/ mkdir -p build; cd build
3/
TARGET_CFLAGS="-O0" CFLAGS="-O0" /MySrcTree/burg1781/configure
CC=gcc-4.4 TARGET_CC=gcc-4.4 --build=powerpc-linux-gnu --prefix=/opt/
grub2/burg1781 --includedir="\${prefix}/include" --mandir="\${prefix}/
share/man" --infodir="\${prefix}/share/info" --sysconfdir=/etc --
localstatedir=/var --libexecdir="\${prefix}/lib/grub2" --srcdir=/
MySrcTree/burg1781 --disable-werror --enable-grub-emu --enable-grub-
fstest --enable-grub-mkfont
4/ make
Did I missed something: even thought '--enable-grub-emu' option, make
didn't build grub-emu?
> >>> From your debug output, it seems that it's able to read from disk,
> >
> > Yes 2 evidences:
> > 1/ it read well and so display the (grub.cfg) menu
> > 2/ it boot well the initrd/vmlinux into the 'fat' formated grub file
> > system
> > ;<)
> >
> >> I
> >> wonder why it doesn't show any device in ls, perhaps it's fs related,
> >> you can use lsmod to show if the file system module is loaded.
> >>
> > Well, last test I did yesterday was with an image containing normal, ext2,
> > fat, part_msdos modules.
> > And lsmod showed me well ext2 but that doesn't help yet.
> >
> > So if I have some more time to investigate further, I will so try to add
> > some more grub_printf() in disk.c to discover what is it reading and
> > compare with grub-emu results.
>
> It could be some hidden bug in ext2, can grub-fstest read files from
> that partition ?
>
# grub-fstest /boot/initrd.img-2.6.30-2-powerpc64 ls
(loop0) (host)
Should I test something else?
That said I also notice that for sparc, it is named 'sparc64' so I
guess it's build as a 64bit application?
On the other hand I read from my OFS device-tree (DT) (also accessible
with linux /proc/device-tree) that for / the #address-cells as well as
#size-cells are set to 2; as far as I understand the first would mean
that it uses 64bit width address space and the second that forth unit
cells is also of 64bit width, is it correct?
But what's about the interface between OFS and OS (here grub2) is it a
32bit or a 64bit interface. I am worry that if grub request something
(address or data) the answer is of 64bit width of which grub only read
the half part?
> >
> > That said, am I right to say that grub discover disk with
> > grub_ofdisk_iterate() i.e. grub_devalias_iterate()?
> > That would explain why it only discover 1 disk
> > (/vdevice/v-scsi@30000016/disk@8100000000000000) and not the second one
> > (/vdevice/v-scsi@30000015/disk@8100000000000000: 15 in place of 16) like
> > does linux, though.
>
> That's right, it find disk device by iterating the device alias, and
> compare the device type.
>
Well I tried to boot directly from ofs prompt and I can define new
aliases (check with devalias of course) but either they are just
volatile or they are cleaned up by ofs menu, anyway they didn't
persist after a reboot: I still have to learn a lot about this OFS
implementation ;<)
Thanks in advance for further help,
J.
Bean
> Hello,
>
>> >
>> > Bean wrote:
>> >>
>> >> Hi,
>> >>
>> >> Have you make any progress on this problem ? I've created a forked
>> >> project BURG which is based on grub2, you can try if that works for
>> >> you.
>> >>
>> > Yes I make 2 step beyond (better then the song isn't it ;<).
>> > The first I mentioned in a patch proposal
>> > (<http://lists.gnu.org/archive/html/grub-devel/2009-11/msg00053.html>) which
>> > get me rid of annoying "cursor-on cursor-on word unknown".
>>
>> Hi,
>>
>> Yep, the cursor-on problem affects sparc64-ieee1275 as well and it's
>> quite annoying, I've disabled it in BURG.
>>
> Btw any comment on my proposal?
My method is similar, although instead of adding a new variable, it
set a flags GRUB_IEEE1275_FLAG_SET_CURSOR using
grub_ieee1275_set_flag. The flags are mostly used to enable some
feature in specific ieee1275 platform, I think the cursor-on problem
belongs to them.
in r1872. If that doesn't work, please go back to r1870, it should be
more stable.
with r1871, qemu is a standalone target, it needs to be compile
separately. Although you can use grub-fstest, it's quite convenient to
debug fs related issue.
>
>> >>> From your debug output, it seems that it's able to read from disk,
>> >
>> > Yes 2 evidences:
>> > 1/ it read well and so display the (grub.cfg) menu
>> > 2/ it boot well the initrd/vmlinux into the 'fat' formated grub file
>> > system
>> > ;<)
>> >
>> >> I
>> >> wonder why it doesn't show any device in ls, perhaps it's fs related,
>> >> you can use lsmod to show if the file system module is loaded.
>> >>
>> > Well, last test I did yesterday was with an image containing normal, ext2,
>> > fat, part_msdos modules.
>> > And lsmod showed me well ext2 but that doesn't help yet.
>> >
>> > So if I have some more time to investigate further, I will so try to add
>> > some more grub_printf() in disk.c to discover what is it reading and
>> > compare with grub-emu results.
>>
>> It could be some hidden bug in ext2, can grub-fstest read files from
>> that partition ?
>>
> # grub-fstest /boot/initrd.img-2.6.30-2-powerpc64 ls
> (loop0) (host)
>
> Should I test something else?
grub-fstest /dev/sda ls -l
Shows partitions, for example (loop0,1), (loop0,2), etc.
grub-fstest /dev/sda ls "(loop0,1)/boot/"
List files
grub-fstest /dev/sda cat "(loop0,1)/boot/grub/grub.cfg"
Display file content.
>
> That said I also notice that for sparc, it is named 'sparc64' so I
> guess it's build as a 64bit application?
>
> On the other hand I read from my OFS device-tree (DT) (also accessible
> with linux /proc/device-tree) that for / the #address-cells as well as
> #size-cells are set to 2; as far as I understand the first would mean
> that it uses 64bit width address space and the second that forth unit
> cells is also of 64bit width, is it correct?
>
> But what's about the interface between OFS and OS (here grub2) is it a
> 32bit or a 64bit interface. I am worry that if grub request something
> (address or data) the answer is of 64bit width of which grub only read
> the half part?
>
Although, ppc32 is compatible with ppc64, it should work as well.
>
>> >
>> > That said, am I right to say that grub discover disk with
>> > grub_ofdisk_iterate() i.e. grub_devalias_iterate()?
>> > That would explain why it only discover 1 disk
>> > (/vdevice/v-scsi@30000016/disk@8100000000000000) and not the second one
>> > (/vdevice/v-scsi@30000015/disk@8100000000000000: 15 in place of 16) like
>> > does linux, though.
>>
>> That's right, it find disk device by iterating the device alias, and
>> compare the device type.
>>
> Well I tried to boot directly from ofs prompt and I can define new
> aliases (check with devalias of course) but either they are just
> volatile or they are cleaned up by ofs menu, anyway they didn't
> persist after a reboot: I still have to learn a lot about this OFS
> implementation ;<)
--
Bean
Project: https://launchpad.net/burg
Document: https://help.ubuntu.com/community/Burg
Mailing list: http://groups.google.com/group/burg-devel
Bean
>>> > That said, am I right to say that grub discover disk with
>>> > grub_ofdisk_iterate() i.e. grub_devalias_iterate()?
>>> > That would explain why it only discover 1 disk
>>> > (/vdevice/v-scsi@30000016/disk@8100000000000000) and not the second one
>>> > (/vdevice/v-scsi@30000015/disk@8100000000000000: 15 in place of 16) like
>>> > does linux, though.
>>>
>>> That's right, it find disk device by iterating the device alias, and
>>> compare the device type.
>>>
>> Well I tried to boot directly from ofs prompt and I can define new
>> aliases (check with devalias of course) but either they are just
>> volatile or they are cleaned up by ofs menu, anyway they didn't
>> persist after a reboot: I still have to learn a lot about this OFS
>> implementation ;<)
>
> Oh, your disk is not in the device alias ?
BTW, OFS command nvalias should define a persistent alias.
Jo
On Dec 1, 4:59 pm, Bean <bean12...@gmail.com> wrote:
> >>> > That said, am I right to say that grub discover disk with
> >>> > grub_ofdisk_iterate() i.e. grub_devalias_iterate()?
> >>> > That would explain why it only discover 1 disk
> >>> > (/vdevice/v-scsi@30000016/disk@8100000000000000) and not the second one
> >>> > (/vdevice/v-scsi@30000015/disk@8100000000000000: 15 in place of 16) like
> >>> > does linux, though.
>
> >>> That's right, it find disk device by iterating the device alias, and
> >>> compare the device type.
>
> >> Well I tried to boot directly from ofs prompt and I can define new
> >> aliases (check with devalias of course) but either they are just
> >> volatile or they are cleaned up by ofs menu, anyway they didn't
> >> persist after a reboot: I still have to learn a lot about this OFS
> >> implementation ;<)
>
> > Oh, your disk is not in the device alias ?
>
> Hi,
>
> BTW, OFS command nvalias should define a persistent alias.
>
That makes the drill:
0> nvalias disk1 /vdevice/v-scsi@30000015/disk@8100000000000000 ok
0> nvalias disk2 /vdevice/v-scsi@30000016/disk@8100000000000000 ok
reboot to check:
0 > nvalias
ibm,sp /vdevice/IBM,sp@4000
disk2 /vdevice/v-scsi@30000016/disk@8100000000000000
disk1 /vdevice/v-scsi@30000015/disk@8100000000000000
network /vdevice/l-lan@30000002
net /vdevice/l-lan@30000002
network1 /vdevice/l-lan@30000003
scsi /vdevice/v-scsi@30000015
nvram /vdevice/nvram@4002
rtc /vdevice/rtc@4001
screen /vdevice/vty@30000000
ok
Now boot grub and go to the grub-shell (for my part I just [Escape]
and [ctrl]-c)
sh:grub> ls
(disk2) (disk2,7) (disk2,6) (disk2,5) (disk2,3) (disk2,1) (disk1)
(disk1,2) (disk1,1)
Now try to reboot with such menu entry:
menuentry "Debian GNU/Linux, with Linux 2.6.30-2-powerpc64" {
insmod ext2
set root=(hd1,3)
search --no-floppy --fs-uuid --set 16ef0754-c845-46e9-a948-
b9669ee68329
linux /vmlinux-2.6.30-2-powerpc64
root=UUID=3c51c43e-63a7-4ff1-9b1c-cf98addcb7ed ro sysrq=1
insmod=sym53c8xx insmod=ipr qu
iet
initrd /initrd.img-2.6.30-2-powerpc64
}
it boot fine (and to be absolutely sure I rename vmlinux and initrd
into grub fs with .sav extension so that the original default menu
entry
menuentry "Grub2 tst Debian GNU/Linux, with Linux 2.6.30-2-
powerpc64" {
linux /vmlinux-2.6.30-2-powerpc64
root=UUID=3c51c43e-63a7-4ff1-9b1c-cf98addcb7ed ro sysrq=1
insmod=sym53c8xx insmod=ipr
initrd /initrd.img-2.6.30-2-powerpc64
}
would failed and now I can remove it ;<)
Still have to check why following menu entry:
menuentry "openSUSE 11.1 (ppc) (on /dev/mapper/system-root)" {
insmod lvm
insmod ext2
set root=(system-root)
search --no-floppy --fs-uuid --set 40ed7be1-44a9-493c-866e-
ea835eb94524
linux /boot/vmlinux-2.6.27.7-9-ppc64 root=/dev/mapper/system-
root
initrd /boot/initrd-2.6.27.7-9-ppc64
}
still failed.... (may be lvm.mod wasn't the last release or try to
simply add it in grub boot img?)
Thanks a lot for your kind support,
J.
PS: this success was realized with latest deb src tree 1.97+20091115
to which I added small stuff (cursor patch proposed on grub ml, and
compile with -O0).
Any way I will try your next (or previous?) burg and will advise you
asap.
Bean
You can run insmod lvm in grub console, and use ls to see if there is
new device, grub-fstest can also use to debug lvm/raid. For example,
if lvm has three disks:
grub-fstest -c 3 /dev/sda1 /dev/sdb1 /dev/sdc1 ls
Jo
On Dec 1, 7:02 pm, Bean <bean12...@gmail.com> wrote:
well here is more test results:
I first figure out that some stuff where compiled with -O2 option I so
apply following hack:
=== modified file 'configure.ac'
--- configure.ac 2009-12-01 08:42:58 +0000
+++ configure.ac 2009-12-02 07:29:44 +0000
@@ -121,7 +121,7 @@
pc) machine_CFLAGS="-DGRUB_MACHINE_PCBIOS=1" ;;
emu) machine_CFLAGS="-DGRUB_MACHINE_EMU=1" ;;
esac
-CFLAGS="$CFLAGS $machine_CFLAGS -O2"
+CFLAGS="$CFLAGS $machine_CFLAGS"
AC_SUBST(host_cpu)
AC_SUBST(host_os)
=== <> ===
and burg r 1780 & 1782 boot again but fall back to [grub rescue] mode
without any chance to do anythink :<(
Welcome to GRUB!
Unknown command `menuentry'
Try `help' for usage
error: invalid object file
error: invalid object file
error: invalid object file
Unknown command `}'
Try `help' for usage
Unknown command `menuentry'
Try `help' for usage
error: invalid object file
error: invalid object file
Unknown command `'
Try `help' for usage
Unknown command `
'
Try `help' for usage
Unknown command `'
Try `help' for usage
Unknown command `4'
Try `help' for usage
Unknown command `V'
Try `help' for usage
Unknown command `Z'
Try `help' for usage
Unknown command ``'
Try `help' for usage
Unknown command `x'
Try `help' for usage
Unknown command `?'
Try `help' for usage
Unknown command `?
Try `help' for usage
Unknown command `?
Try `help' for usage
Entering rescue mode...
grub rescue> lsmod
error: invalid object file
That said, I noticed a big diff if grub image size 170Kb for burg
against 200Kb for grub-20091115?
But I also noticed those warning when I run autogen.sh:
# ./autogen.sh
configure.ac:40: installing `./config.guess'
configure.ac:174: required file `./config.rpath' not found
configure.ac:40: installing `./config.sub'
configure.ac:45: installing `./install-sh'
configure.ac:45: installing `./missing'
automake: no `Makefile.am' found for any configure output
WARNING: C file isn't a module: pubkey.c
WARNING: C file isn't a module: primegen.c
WARNING: C file isn't a module: ecc.c
WARNING: C file isn't a module: dsa.c
WARNING: C file isn't a module: hash-common.c
WARNING: C file isn't a module: md.c
WARNING: C file isn't a module: hmac-tests.c
WARNING: C file isn't a module: rsa.c
WARNING: C file isn't a module: elgamal.c
WARNING: C file isn't a module: cipher.c
WARNING: C file isn't a module: ac.c
Otoh, I have some recent issue to rebuild lastest debian src tree
20091130:
gcc-4.4 -Icommands -I/MySrcTree/grub2-1.97+20091130/commands -I. -I./
include -I/MySrcTree/grub2-1.97+2009113
0/gnulib -I/MySrcTree/grub2-1.97+20091130/include -Wall -W -
DGRUB_LIBDIR=\"/usr/lib/`echo grub/powerpc-emu | sed 's,x,x,
'`\" -DLOCALEDIR=\"\" -O0 -DGRUB_MACHINE_EMU=1 -DGRUB_UTIL=1 -MD -c -
o grub_emu-commands_halt.o /MySrcTree/grub2-1.97+20091130/commands/
halt.c
/MySrcTree/grub2-1.97+20091130/commands/halt.c:29:27: error: grub/cpu/
halt.h: No such file or directory
/MySrcTree/grub2-1.97+20091130/commands/halt.c: In function
'grub_cmd_halt':
/MySrcTree/grub2-1.97+20091130/commands/halt.c:37: warning: implicit
declaration of function 'grub_halt'
make[1]: *** [grub_emu-commands_halt.o] Error 1
make[1]: Leaving directory `/MySrcTree/grub2-1.97+20091130/build/grub-
emu'
make: *** [build/grub-emu] Error 2
So I am not yet able to compare (but your burg tree seems to have
fixed this issue so I will try to back port to grub experimental
tree,...)
Ok back to working grub (20091115), lvm module (either loaded at run-
time or included in the image) seems to have issue.
Well the disk with lvm structure is sda:
# cfdisk /dev/sda (i.e. ofs alias disk1)
GNU cfdisk 1.2.3
AIX VDASD
Disk: /dev/sda Disk type: msdos Size: 10737418239B,
10737MB
Heads: 255 Sectors per track: 63 Cylinders: 1305
Number Flags Part Type Filesystem
Label Size
------------------------------------------------------------------------------
1 Bootable Primary
fat16 24.6MB
2 Primary [Linux
LVM] 10709MB
And grub-fstest find well stuff:
# grub-fstest /dev/sda ls -l
Device system-swap: Unknown filesystem
Device system-root: Filesystem type ext2, Last modification time
2009-12-02 09:07:45 Wednesday, UUID 40ed7be1-44a9-493c-866e-
ea835eb94524
Device system-home: Filesystem type ext2, Last modification time
2009-12-02 09:07:45 Wednesday, UUID b6ab41ec-cd1d-4a6f-
aac9-043f511df9c6
Device loop0: Partition table
Partition loop0,2: Unknown filesystem
Partition loop0,1: Filesystem type fat, Label 'root', UUID 4ad5-
c9f7
Device host: Filesystem type hostfs
But:
sh:grub> insmod lvm
sh:grub> lsmod
Name Ref Count Dependencies
lvm 1
minicmd 1
sh 1 normal
part_msdos 1
fat 1
ext2 1 fshelp
fshelp 2
normal 4 boot
boot 5
sh:grub> search --no-floppy --fs-uuid --set 40ed7be1-44a9-493c-866e-
ea835eb9452
4
error: no such device: 40ed7be1-44a9-493c-866e-ea835eb94524
I run the same with debug=disk (too much useless ouput) and it scan
well (disk1,1) the boot fat slice as well as (disk1,2) the target vg
(well of format lvm2).
Well so you agree to let lvm issue aside for the moment and try to
find the root cause of burg boot failure?
Thanks,
J.
Jo
Sorry 2 kbd keys too close for fat finger ;<)
J.
Jo
> Well so you agree to let lvm issue aside for the moment and try to
> find the root cause of burg boot failure?
>
and even though I also encountered menu issue:
Try `help' for usage
Try `help' for usage
Unknown command `menuentry'
Try `help' for usage
I can continue manually and boot linux (with always same lvm issue,
obviously)
e.g.
rescue> lsmod
Name Ref Count Dependencies
minicmd 1
linux 2 boot,elf
elf 3 gzio
gzio 4
search 1 extcmd
extcmd 2
part_msdos 1
fat 1
ext2 3 fshelp
fshelp 4
lvm 1
normal 2 boot
boot 6
Hth,
j.
Bean
> [snip]
> well here is more test results:
>
> I first figure out that some stuff where compiled with -O2 option I so
> apply following hack:
> === modified file 'configure.ac'
> --- configure.ac 2009-12-01 08:42:58 +0000
> +++ configure.ac 2009-12-02 07:29:44 +0000
> @@ -121,7 +121,7 @@
> pc) machine_CFLAGS="-DGRUB_MACHINE_PCBIOS=1" ;;
> emu) machine_CFLAGS="-DGRUB_MACHINE_EMU=1" ;;
> esac
> -CFLAGS="$CFLAGS $machine_CFLAGS -O2"
> +CFLAGS="$CFLAGS $machine_CFLAGS"
>
> AC_SUBST(host_cpu)
> AC_SUBST(host_os)
>
> === <> ===
>
The -O2 is used to enable dead code elimination for gcc. The
GRUB_AS_LIST macro uses a trick that would call grub_assert_fail if
the input data structure is invalid, but if it's ok, it shouldn't
generate any runtime code. If dead code elimination is not enabled,
the grub_assert_fail is still present still in object file and you get
unresolved symbol error. Although if you don't see the error, it's
probably because dead code elimination is enabled by default.
grub. You can either replaces all mod files from burg, or embed the
modules you need in the image, here is a list of modules you probably
wants:
minicmd sh normal nmenu reboot halt part_msdos ext2 fat ls linux
> That said, I noticed a big diff if grub image size 170Kb for burg
> against 200Kb for grub-20091115?
use of new object format.
> But I also noticed those warning when I run autogen.sh:
> # ./autogen.sh
> configure.ac:40: installing `./config.guess'
> configure.ac:174: required file `./config.rpath' not found
> configure.ac:40: installing `./config.sub'
> configure.ac:45: installing `./install-sh'
> configure.ac:45: installing `./missing'
> automake: no `Makefile.am' found for any configure output
> WARNING: C file isn't a module: pubkey.c
> WARNING: C file isn't a module: primegen.c
> WARNING: C file isn't a module: ecc.c
> WARNING: C file isn't a module: dsa.c
> WARNING: C file isn't a module: hash-common.c
> WARNING: C file isn't a module: md.c
> WARNING: C file isn't a module: hmac-tests.c
> WARNING: C file isn't a module: rsa.c
> WARNING: C file isn't a module: elgamal.c
> WARNING: C file isn't a module: cipher.c
> WARNING: C file isn't a module: ac.c
>
to create the lvm volume along with the software version so that I can
try to recreate that environment here ?
Jo
On Dec 2, 3:11 pm, Bean <bean12...@gmail.com> wrote:
well a simple 'strings grubofs' (my grub image) shows me a lot of
grub_ symbol but any _ass, most probably the last hypothesis is right.
(I will try to find more details)
> You can either replaces all mod files from burg, or embed the
> modules you need in the image, here is a list of modules you probably
> wants:
>
> minicmd sh normal nmenu reboot halt part_msdos ext2 fat ls linux
>
just add 'search' module.
As all working fine, I replaced grub's modules by burg's one and use a
smallest image (only normal ext2 fat part_msdos modules) and all is
working fine ;<)
(excepted lvm)
> > That said, I noticed a big diff if grub image size 170Kb for burg
> > against 200Kb for grub-20091115?
>
> Yep, one of the advantage of burg is its small image size, due to the
> use of new object format.
>
>
>
> > But I also noticed those warning when I run autogen.sh:
> > # ./autogen.sh
> > configure.ac:40: installing `./config.guess'
> > configure.ac:174: required file `./config.rpath' not found
> > configure.ac:40: installing `./config.sub'
> > configure.ac:45: installing `./install-sh'
> > configure.ac:45: installing `./missing'
> > automake: no `Makefile.am' found for any configure output
> > WARNING: C file isn't a module: pubkey.c
> > WARNING: C file isn't a module: primegen.c
> > WARNING: C file isn't a module: ecc.c
> > WARNING: C file isn't a module: dsa.c
> > WARNING: C file isn't a module: hash-common.c
> > WARNING: C file isn't a module: md.c
> > WARNING: C file isn't a module: hmac-tests.c
> > WARNING: C file isn't a module: rsa.c
> > WARNING: C file isn't a module: elgamal.c
> > WARNING: C file isn't a module: cipher.c
> > WARNING: C file isn't a module: ac.c
>
> Actually I have fixed some of the warning already, but it's harmless anyway.
>
OpenSuse 10.3 installation DVD during Mars 2008 (at the same time of
my first debian install on powerpc <http://lists.debian.org/debian-
powerpc/2008/03/msg00038.html>). OpenSuse was updated to 11.1 in the
mean time. But I will check if I find back DVD.
That said, now that Grub and Burg let me boot my Debian, I can get rid
of this OpenSuse install and rebuild another debian (e.g. debootstrap)
on a freshly rebuild lvm struct on the second disk (actualy sda) to
see if that help but I will wait your feedback before definitely
deleting everything.
Thanka agin for your support,
J.
Jo
well a simple 'strings grubofs' (my grub image) shows me a lot of
grub_ symbol but any _ass, most probably the last hypothesis is right.
(I will try to find more details)
>
>
> modules you need in the image, here is a list of modules you probably
> wants:
>
> minicmd sh normal nmenu reboot halt part_msdos ext2 fat ls linux
>
just add 'search' module.
As all working fine, I replaced grub's modules by burg's one and use a
smallest image (only normal ext2 fat part_msdos modules) and all is
working fine ;<)
(excepted lvm)
> > against 200Kb for grub-20091115?
>
> Yep, one of the advantage of burg is its small image size, due to the
> use of new object format.
>
>
>
> > But I also noticed those warning when I run autogen.sh:
> > # ./autogen.sh
> > configure.ac:40: installing `./config.guess'
> > configure.ac:174: required file `./config.rpath' not found
> > configure.ac:40: installing `./config.sub'
> > configure.ac:45: installing `./install-sh'
> > configure.ac:45: installing `./missing'
> > automake: no `Makefile.am' found for any configure output
> > WARNING: C file isn't a module: pubkey.c
> > WARNING: C file isn't a module: primegen.c
> > WARNING: C file isn't a module: ecc.c
> > WARNING: C file isn't a module: dsa.c
> > WARNING: C file isn't a module: hash-common.c
> > WARNING: C file isn't a module: md.c
> > WARNING: C file isn't a module: hmac-tests.c
> > WARNING: C file isn't a module: rsa.c
> > WARNING: C file isn't a module: elgamal.c
> > WARNING: C file isn't a module: cipher.c
> > WARNING: C file isn't a module: ac.c
>
> Actually I have fixed some of the warning already, but it's harmless anyway.
>
>
>
OpenSuse 10.3 installation DVD during Mars 2008 (at the same time of
my first debian install on powerpc <http://lists.debian.org/debian-
powerpc/2008/03/msg00038.html>). OpenSuse was updated to 11.1 in the
mean time. But I will check if I find back DVD.
That said, now that Grub and Burg let me boot my Debian, I can get rid
of this OpenSuse install and rebuild another debian (e.g. debootstrap)
on a freshly rebuild lvm struct on the second disk (actualy sda) to
see if that help but I will wait your feedback before definitely
deleting everything.
Thanka agin for your support,
J.
>
Jo
> > Thanks, this looks like a lvm bug. Could you list the commands you use
> > to create the lvm volume along with the software version so that I can
> > try to recreate that environment here ?
>
> mmm, not sure I will still be able to find info: it was build by an
> OpenSuse 10.3 installation DVD during Mars 2008 (at the same time of
> my first debian install on powerpc <http://lists.debian.org/debian-
> powerpc/2008/03/msg00038.html>). OpenSuse was updated to 11.1 in the
> mean time. But I will check if I find back DVD.
>
> That said, now that Grub and Burg let me boot my Debian, I can get rid
> of this OpenSuse install and rebuild another debian (e.g. debootstrap)
> on a freshly rebuild lvm struct on the second disk (actualy sda) to
> see if that help but I will wait your feedback before definitely
> deleting everything.
>
installed packages lvm was lvm2-2.02.25-28.ppc.rpm with kernel-
ppc64-2.6.22.5-31.pp.rpm (not sure the installed sw was the one used
for the installation but that's the best I can find)?
Hth,
J.
Bean
I just create a lvm partition in my ppc machine which installs debian
lenny, and it seems all right. BTW, what's the result of "ls -l"
inside grub console, does it list partitions properly ?
Jo
> Hi,
>
> I just create a lvm partition in my ppc machine which installs debian
> lenny, and it seems all right. BTW, what's the result of "ls -l"
> inside grub console, does it list partitions properly ?
>
structures; here is the info:
As lvm module doesn't part of my grub image:
grub> insmod lvm
grub> lsmod
Name Ref Count Dependencies
lvm 1
minicmd 1
afs 0 fshelp
afs_be 0 fshelp
befs 0 fshelp
befs_be 0 fshelp
cpio 0
hfs 0
hfsplus 0 fshelp
iso9660 0 fshelp
jfs 0
minix 0
ntfs 0 fshelp
reiserfs 0 fshelp
sfs 0 fshelp
tar 0
udf 0 fshelp
ufs1 0
ufs2 0
xfs 0 fshelp
ls 1 lib,extcmd
extcmd 2
nmenu 1 lib,boot
boot 2
sh 1 lib
fat 1
ext2 1 fshelp
normal 2 lib
lib 9
kernel 1
grub> ls -l
Device system-swap: Unknown filesystem
Device system-root: Unknown filesystem
Device system-home: Unknown filesystem
Device p5tst001vg-Sources: Unknown filesystem
Device p5tst001vg-UsrSrc: Unknown filesystem
Device p5tst001vg-home: Unknown filesystem
Device p5tst001vg-tmp: Unknown filesystem
Device p5tst001vg-var: Unknown filesystem
Device disk2: Partition table
Partition disk2,7: Unknown filesystem
Partition disk2,6: Filesystem type ext2, Last modification
time 2009-12-03 14:29:59 Thursda
y, UUID 3c51c43e-63a7-4ff1-9b1c-cf98addcb7ed
Partition disk2,5: Unknown filesystem
Partition disk2,3: Filesystem type ext2, Last modification
time 2009-12-03 14:30:03 Thursda
y, UUID 16ef0754-c845-46e9-a948-b9669ee68329
Partition disk2,1: Filesystem type fat, Label grub2, UUID
4adc-336e
Device disk1: Partition table
Partition disk1,2: Unknown filesystem
Partition disk1,1: Filesystem type fat, Label 'root', UUID
4ad5-c9f7
some explamation:
disk1 (as I defined by previous nvalias) contains the opensuse
installation and contains well 2 slices:
1/ the small fat fs containing yaboot loader
2/ a biger slice containing the 'system' volume group which itself
contains well 3 logical volumes swap, root, home
disk2 contains my debian installation which is still of more classical
silces implementation:
1/ a small fat fs containing now burg image and modules
2/ a a biger slice of about 2Gb for the root (/) fs
3/ the last slice with the rest of the disk containing a vg
'p5tst001vg' for the lv tmp, var, home, 2 more stuff for my usage.
And iirc the disk1 where well formated with opensuse tools and disk2
with debian tools (iirc the first release of 5.0 netinst cd).
That said, this is a small system with all 4 disk bay occupied by disk
usefull for other purpose; more over there isn't external enclosure
available to build a new installation. Any way on disk2 there is still
a very small free space (about 7Mb) where I can create a new vg and a
lv with more recent debian tools (latest unstable updated last
Monday):
(p5_sid)root@p5tst001:~# vgcreate burgvg /dev/sdb2
No physical volume label read from /dev/sdb2
Physical volume "/dev/sdb2" successfully created
Volume group "burgvg" successfully created
(p5_sid)root@p5tst001:~# lvcreate -n tstlv -L 2M burgvg
Rounding up size to full physical extent 4.00 MiB
Logical volume "tstlv" created
(p5_sid)root@p5tst001:~# mke2fs -t ext3 -m 0 /dev/mapper/burgvg-tstlv
mke2fs 1.41.9 (22-Aug-2009)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
1024 inodes, 4096 blocks
0 blocks (0.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=4194304
1 block group
8192 blocks per group, 8192 fragments per group
1024 inodes per group
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 29 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
(p5_sid)root@p5tst001:~# mkdir /mnt/bt
(p5_sid)root@p5tst001:~# mount /dev/mapper/burgvg-tstlv /mnt/bt
(p5_sid)root@p5tst001:~# bdf
Filesystem 1K-blocks Used Available Use% Mounted on
[snip]
/dev/mapper/p5tst001vg-home
507748 26966 480782 6% /home
/dev/mapper/p5tst001vg-UsrSrc
2064208 825664 1238544 40% /usr/src
/dev/mapper/p5tst001vg-Sources
2567984 1758764 809220 69% /Sources
/dev/mapper/burgvg-tstlv
3963 1058 2905 27% /mnt/bt
At the reboot, grub see well the new lv but still failed to see the
underlying fs ;<(
grub> ls -l
Device system-swap: Unknown filesystem
Device system-root: Unknown filesystem
Device system-home: Unknown filesystem
Device burgvg-tstlv: Unknown filesystem
Device p5tst001vg-Sources: Unknown filesystem
Device p5tst001vg-UsrSrc: Unknown filesystem
Device p5tst001vg-home: Unknown filesystem
Device p5tst001vg-tmp: Unknown filesystem
Device p5tst001vg-var: Unknown filesystem
Device disk2: Partition table
Partition disk2,7: Unknown filesystem
Partition disk2,6: Filesystem type ext2, Last modification
time 2009-12-04 08:43:51 Friday,
UUID 3c51c43e-63a7-4ff1-9b1c-cf98addcb7ed
Partition disk2,5: Unknown filesystem
Partition disk2,3: Filesystem type ext2, Last modification
time 2009-12-04 08:43:50 Friday,
UUID 16ef0754-c845-46e9-a948-b9669ee68329
Partition disk2,2: Unknown filesystem
Partition disk2,1: Filesystem type fat, Label grub2, UUID
4adc-336e
Device disk1: Partition table
Partition disk1,2: Unknown filesystem
Partition disk1,1: Filesystem type fat, Label 'root', UUID
4ad5-c9f7
But for you it works so I will go back to the log of my build to see
if I can read some relevant warning?
Tx a lot,
J.
[snip]
Bean
Oh, I only create one partition inside lvm, perhaps I can try multiple
partition as well.
Bean
> Oh, I only create one partition inside lvm, perhaps I can try multiple
> partition as well.
I've tried multiple volume and multiple partition, but still can't
reproduce your result, all seems ok.
However, I only have one disk, you can try removing alias disk1 and
let burg sees disk2 only, see if this makes any difference in
detecting lvm.
BTW, I recommend using stable release such as debian lenny. Last time
I try squeeze, there seems to be some strange issue and rarpd doesn't
work ! I think the powerpc port is not widely tested as i386 so there
could be hidden issue in testing/unstable release.
rubisher
> On Fri, Dec 4, 2009 at 10:12 PM, Bean <bean...@gmail.com> wrote:
>> Oh, I only create one partition inside lvm, perhaps I can try multiple
>> partition as well.
>
> Hi,
>
> I've tried multiple volume and multiple partition, but still can't
> reproduce your result, all seems ok.
>
> However, I only have one disk, you can try removing alias disk1 and
> let burg sees disk2 only, see if this makes any difference in
> detecting lvm.
>
> BTW, I recommend using stable release such as debian lenny. Last time
> I try squeeze, there seems to be some strange issue and rarpd doesn't
> work ! I think the powerpc port is not widely tested as i386 so there
> could be hidden issue in testing/unstable release.
>
Tx again,
J.
Bean
>> However, I only have one disk, you can try removing alias disk1 and
>> let burg sees disk2 only, see if this makes any difference in
>> detecting lvm.
>>
> Ok I can do that but I don't know how? (may be simply 'nvalias disk1'?)
It should be nvunalias disk1.
>> BTW, I recommend using stable release such as debian lenny. Last time
>> I try squeeze, there seems to be some strange issue and rarpd doesn't
>> work ! I think the powerpc port is not widely tested as i386 so there
>> could be hidden issue in testing/unstable release.
>>
> Agree, do you still have to sent me gcc-4.4 and binutils release installed
> right know on your lenny?
suspect the problem could be related to gcc-4.4, perhaps I can install
debian unstable on a testing partition and if it works.
Jo
On Dec 6, 7:48 am, Bean <bean12...@gmail.com> wrote:
> >> However, I only have one disk, you can try removing alias disk1 and
> >> let burg sees disk2 only, see if this makes any difference in
> >> detecting lvm.
>
> > Ok I can do that but I don't know how? (may be simply 'nvalias disk1'?)
>
> Hi,
>
> It should be nvunalias disk1.
>
0 > devalias
ibm,sp /vdevice/IBM,sp@4000
disk2 /vdevice/v-scsi@30000016/disk@8100000000000000
net /vdevice/l-lan@30000002
network1 /vdevice/l-lan@30000003
scsi /vdevice/v-scsi@30000015
nvram /vdevice/nvram@4002
rtc /vdevice/rtc@4001
screen /vdevice/vty@30000000
ok
grub> ls -l
Device p5tst001vg-Sources: Unknown filesystem
Device p5tst001vg-UsrSrc: Unknown filesystem
Device p5tst001vg-home: Unknown filesystem
Device p5tst001vg-tmp: Unknown filesystem
Device p5tst001vg-var: Unknown filesystem
Device disk2: Partition table
Partition disk2,7: Unknown filesystem
Partition disk2,6: Filesystem type ext2, Last modification
Partition disk2,5: Unknown filesystem
Partition disk2,3: Filesystem type ext2, Last modification
Partition disk2,2: Unknown filesystem
Partition disk2,1: Filesystem type fat, Label grub2, UUID
4adc-336e
> >> I try squeeze, there seems to be some strange issue and rarpd doesn't
> >> work ! I think the powerpc port is not widely tested as i386 so there
> >> could be hidden issue in testing/unstable release.
>
> > Agree, do you still have to sent me gcc-4.4 and binutils release installed
> > right know on your lenny?
>
> Debian lenny uses gcc-4.3, which works OOTB (no need to modify -O2). I
> suspect the problem could be related to gcc-4.4, perhaps I can install
> debian unstable on a testing partition and if it works.
>
optimization.
In general the build with gcc-4.3 work better then gcc-4.4 (I don't
encounter any more any failure to boot burg itself ;<) )
Never the less even after the down-grade from gcc-4.3 (unstable
4.3.4-6 to lenny 4.3.2-1.1) and binutils (unstable 2.20-4 to stable
2.18.1~cvs20080103) it doesn't help more:
GNU BURG version bzr.1782
[ Minimal BASH-like line editing is supported. For the first word,
TAB
lists possible command completions. Anywhere else TAB lists
possible
device/file completions. ESC at any time exits. ]
grub> lsmod
Name Ref Count Dependencies
lvm 1
elf 2 gzio
gzio 3
ls 1 lib,extcmd
ext2 1 fshelp
part_msdos 1
halt 1
reboot 1
nmenu 1 lib,boot
boot 3
normal 2 lib
sh 1 lib
lib 6
minicmd 1
search 1 extcmd
extcmd 3
grub> ls -l
Device p5tst001vg-Sources: Unknown filesystem
Device p5tst001vg-UsrSrc: Unknown filesystem
Device p5tst001vg-home: Unknown filesystem
Device p5tst001vg-tmp: Unknown filesystem
Device p5tst001vg-var: Unknown filesystem
Device disk2: Partition table
Partition disk2,7: Unknown filesystem
Partition disk2,6: Filesystem type ext2, Last modification
Partition disk2,5: Unknown filesystem
Partition disk2,3: Filesystem type ext2, Last modification
Partition disk2,2: Unknown filesystem
Partition disk2,1: Filesystem type fat, Label grub2, UUID
4adc-336e
booting the latest burg image)
I am a bit stuck right now :<(
Thanks any way,
J.
Bean
Well, this is quite tricky, perhaps you need to compare debug output
to find possible issue.
You can first create a image to include only the necessary modules, for example:
ls ext2 lvm reboot
and move the modules directory temporary so that it can't find *.lst
and *.mod files (avoid autoload).
In burg:
set debug=disk,fs
set pager=1
ls -l (burgvg-tstlv)
In linux:
grub-fstest -d disk,fs /dev/sda ls -l "(burgvg-tstlv)"
And compare the results.
Bean
Oh BTW, with r1784, gcc-4.4 should work OOTB.
Jo
On Dec 7, 9:11 pm, Bean <bean12...@gmail.com> wrote:
> Hi,
>
> Oh BTW, with r1784, gcc-4.4 should work OOTB.
>
debian release 4.4.2-3):
GNU BURG version bzr1784
[ Minimal BASH-like line editing is supported. For the first word,
TAB
lists possible command completions. Anywhere else TAB lists
possible
device/file completions. ESC at any time exits. ]
grub> ls
home) (p5tst001vg-tmp) (p5tst00
1vg-var) (disk2) (disk2,7) (disk2,6) (disk2,5) (disk2,3) (disk2,2)
(disk2,1)
But doesn't yet fix my vg issue, so here is what I got with only fs
debug (disk only add that it's reading disk, thought)
grub> set debug=fs
grub> ls -l (burgvg-tstlv)
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting affs...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: affs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting afs...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: afs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting afs_be...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: afs_be detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting befs...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: befs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting befs_be...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: befs_be detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting cpiofs...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: cpiofs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting hfs...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: hfs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting hfsplus...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: hfsplus detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting iso9660...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: iso9660 detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting jfs...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: jfs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting minix...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: minix detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting ntfs...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: ntfs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting
reiserfs...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: reiserfs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting sfs...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: sfs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting tarfs...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: tarfs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting udf...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: udf detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting ufs1...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: ufs1 detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting ufs2...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: ufs2 detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting xfs...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: xfs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting fat...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: fat detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting ext2...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: ext2 detection
failed.
Device burgvg-tstlv: /Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58:
Detecting affs...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: affs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting afs...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: afs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting afs_be...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: afs_be detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting befs...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: befs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting befs_be...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: befs_be detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting cpiofs...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: cpiofs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting hfs...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: hfs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting hfsplus...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: hfsplus detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting iso9660...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: iso9660 detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting jfs...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: jfs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting minix...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: minix detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting ntfs...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: ntfs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting
reiserfs...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: reiserfs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting sfs...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: sfs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting tarfs...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: tarfs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting udf...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: udf detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting ufs1...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: ufs1 detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting ufs2...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: ufs2 detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting xfs...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: xfs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting fat...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: fat detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:58: Detecting ext2...
/Sources/jso/Deb.grub2/burg-bzr1784/kern/fs.c:64: ext2 detection
failed.
Unknown filesystem
BTW, may be can you show me from your install what should I better
have as results?
Tx again,
J.
Jo
>
> Oh BTW, with r1784, gcc-4.4 should work OOTB.
>
debian release 4.4.2-3):
GNU BURG version bzr1784
TAB
lists possible command completions. Anywhere else TAB lists
possible
device/file completions. ESC at any time exits. ]
Bean
> BTW, may be can you show me from your install what should I better
> have as results?
It's not much output:
../kern/fs.c:58: Detecting ext2...
Device burgvg-tstlv: ../kern/fs.c:58L Detecting ext2...
Filesystem type ext2, Last modification time ..., UUID ...
The detection begins at line 58 in kern/fs.c:
grub_dprintf ("fs", "Detecting %s...\n", p->name);
(p->dir) (device, "/", dummy_func);
if (grub_errno == GRUB_ERR_NONE)
return p;
grub_error_push ();
grub_dprintf ("fs", "%s detection failed.\n", p->name);
grub_error_pop ();
First, you can clear grub_errno before running p->dir, this would
avoid error occur previously to affect the result:
grub_dprintf ("fs", "Detecting %s...\n", p->name);
grub_errno = 0;
(p->dir) (device, "/", dummy_func);
if (grub_errno == GRUB_ERR_NONE)
return p;
grub_error_push ();
grub_dprintf ("fs", "%s detection failed.\n", p->name);
grub_error_pop ();
The detecting code is in function grub_ext2_dir in fs/ext2.c, you can
add enough grub_printf to see when does it goes wrong, grub_ext2_dir
uses the following subroutine:
grub_ext2_mount detect ext2 fs, a likely place for error
grub_fshelp_find_file is called next, this is a helper function, which
call back to grub_ext2_iterate_dir.
grub_ext2_iterate_dir
Jo
On Dec 8, 3:56 pm, Bean <bean12...@gmail.com> wrote:
looks like some info seems to be clobbered somewhere, thought:
/Sources/jso/Deb.grub2/burg-bzr1784/fs/ext2.c:561: Ext data-
>sblock.magic = 0x00000000
/Sources/jso/Deb.grub2/burg-bzr1784/fs/ext2.c:562: grub_le_to_cpu16
(data->sblock.magic) = 0x000000
00
/Sources/jso/Deb.grub2/burg-bzr1784/fs/ext2.c:565: data->sblock:
0x1c1d0b0
/Sources/jso/Deb.grub2/burg-bzr1784/fs/ext2.c:566: size: 336
/Sources/jso/Deb.grub2/burg-bzr1784/fs/ext2.c:572:
000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000
while with grub-fstest I got for the same fs on same lv:
/Sources/jso/Deb.grub2/burg-bzr1784/fs/ext2.c:561: Ext data-
>sblock.magic = 0x000053ef
/Sources/jso/Deb.grub2/burg-bzr1784/fs/ext2.c:566: size: 336
/Sources/jso/Deb.grub2/burg-bzr1784/fs/ext2.c:572:
000400000010000000000000590b0000f503000001000000
0000000000000000002000000020000000040000abcb184b
c6cb184b01001d0053ef0100010000007dcb184b004eed00
0000000001000000000000000b000000800000003c000000
02000000010000003a687767567b48b9baaa661835b760a5
000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000
00000000000000000000000000000f000000000000000000
0000000000000000080000000000000000000000d78e5171
fd40210b7189f7aa3548a0eb010100000000000000000000
7dcb184ba2000000a3000000a4000000a5000000a6000000
a7000000a8000000a9000000aa000000ab000000ac000000
ad000000ae000000af010000000000000000000000001000
Don't know if related but it becomes even worse when some additional
modules are loaded:
# 1st ls -l (burgvg-tstlv)
/Sources/jso/Deb.grub2/burg-bzr1784/fs/ext2.c:561: Ext data-
>sblock.magic = 0x0000883b
/Sources/jso/Deb.grub2/burg-bzr1784/fs/ext2.c:566: size: 336
/Sources/jso/Deb.grub2/burg-bzr1784/fs/ext2.c:572:
4166006f006e0074002e000f00646d006f0064000000ffff
ffff0000ffffffff464f4e54202020204d4f44200000ea48
883b883b0000ea48883b370e2f20000041660073005f0066
0069000f00216c0065002e006d006f00640000000000ffff
46535f46494c45204d4f44200000ea48883b883b0000ea48
883b490e7e0600004166007300680065006c000f00b47000
2e006d006f00640000000000ffffffff465348454c502020
4d4f44200000ea48883b883b0000ea48883b4d0e9b0b0000
41660073005f00750075000f002b690064002e006d006f00
640000000000ffff46535f55554944204d4f44200000ea48
883b883b0000ea48883b530e8d0600004167006500740074
0065000f0049780074002e006d006f00640000000000ffff
47455454455854204d4f44200000ea48883b883b0000ea48
883b570e950e000041670066007800720067000f007d6e00
# 2d ls -l (burgvg-tstlv)
/Sources/jso/Deb.grub2/burg-bzr1784/fs/ext2.c:561: Ext data-
>sblock.magic = 0x0000380038
/Sources/jso/Deb.grub2/burg-bzr1784/fs/ext2.c:566: size: 336
/Sources/jso/Deb.grub2/burg-bzr1784/fs/ext2.c:572:
5400d97e500bf8005520421e5529c42e7d4a03787d605b78
5300f0427d494b78901f0010913f00144e80042138000001
2f830000419e000838000000812100002f80000191390000
7f21cb78409e008ca01f000c5409442e5400c23e7d200378
7fbd0214813e0578801e05747c390b787fa5eb7838c00008
7ea7ab78552a421e5528c00e552b021e7d085378556bc23e
540a463e7d085b785529463e540bc00e7d2943787d4b5b78
540a421e2b0900007d4b5b785400c42e388000007fc3f378
2f8900007d6003784199fe98409e000c7f80e840419dfe8c
7fc3f378480000013d20000080690000397f015048000000
7c2b0b789421fff03c8000007c0802a63884000038840014
90010014480000017c7f1b783c6000003863000048000001
3d2000003961001093e9000048000000386000004bffffbc
9421fff03c8000007c0802a63c6000003884000038630000
I will so now check how the 'device' structure passed to grub_fs_probe
is filled up.
Cheers,
J.
PS: any chance that making structure 'static' could help a bit (to
avoid issue with gcc optimization?)
Bean
I think this is related to disk read, the first line to read from disk is
grub_disk_read (disk, 1 * 2, 0, sizeof (struct grub_ext2_sblock),
&data->sblock);
from grub_ext2_mount, add some marker around this line, and enable
disk debug. The call should end up in grub_ofdisk_read function of
disk/ieee1275/ofdisk.c.
For grub-fstest, the read should endup in grub_loopback_read in
disk/loopback.c, there is no grub_dprint line here, add one similar to
grub_ofdisk_read.
Now compare the results, see if they read from the same sectors.
Bean
I finally track down a bug in ieee1275 which I believe to be the
cause, please try r1787.
Jo
On Dec 11, 7:27 pm, Bean <bean12...@gmail.com> wrote:
> Hi,
>
> I finally track down a bug in ieee1275 which I believe to be the
> cause, please try r1787.
>
> --
> Bean
>
GNU BURG version 1.97-b
[ Minimal BASH-like line editing is supported. For the first word,
TAB
lists possible command completions. Anywhere else TAB lists
possible
device/file completions. ESC at any time exits. ]
grub>
Device burgvg-tstlv: Unknown filesystem
Device p5tst001vg-Sources: Unknown filesystem
Device p5tst001vg-UsrSrc: Unknown filesystem
Device p5tst001vg-home: Unknown filesystem
Device p5tst001vg-tmp: Unknown filesystem
Device p5tst001vg-var: Unknown filesystem
Device disk2: Partition table
Partition disk2,7: Unknown filesystem
time 2009-12-14 08:47:38 Monday,
Partition disk2,5: Unknown filesystem
time 2009-12-14 08:47:38 Monday,
Partition disk2,2: Unknown filesystem
Partition disk2,1: Filesystem type fat, Label grub2, UUID
4adc-336e
grub> set debug=fs,disk ls -l ls -l (burgvg-
tstlv)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:260: Opening `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting fat...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:404: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:404: Reading
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/disk/ieee1275/ofdisk.c:239:
Reading handle 0x18fb600: sector 0x
b980, size 0x8, buf 0x1c16bf0.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:64: fat detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting ext2...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:404: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:64: ext2 detection
failed.
Device burgvg-tstlv: /Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:
260: Opening `burgvg-tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting fat...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:404: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:64: fat detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting ext2...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:404: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:64: ext2 detection
failed.
Unknown filesystem/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:348:
Closing `burgvg-tstlv'.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:348: Closing `burgvg-
tstlv'.
I also try another lv but not more success ;<(
grub> ls -l (p5tst001vg-var)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:260: Opening
`p5tst001vg-var'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting fat...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:404: Reading
`p5tst001vg-var'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:404: Reading
`disk2,7'...
/Sources/jso/Deb.grub2/burg-bzr1788/disk/ieee1275/ofdisk.c:239:
Reading handle 0x18fb680: sector 0x
a4f9a0, size 0x8, buf 0x1c1bcd0.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:64: fat detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting ext2...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:404: Reading
`p5tst001vg-var'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:404: Reading
`p5tst001vg-var'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:404: Reading
`p5tst001vg-var'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:404: Reading
`disk2,7'...
/Sources/jso/Deb.grub2/burg-bzr1788/disk/ieee1275/ofdisk.c:239:
Reading handle 0x18fb680: sector 0x
a4fba8, size 0x8, buf 0x1c21f40.
Device p5tst001vg-var: /Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:
260: Opening `p5tst001vg-var
'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting fat...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:404: Reading
`p5tst001vg-var'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:64: fat detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting ext2...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:404: Reading
`p5tst001vg-var'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:404: Reading
`p5tst001vg-var'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:404: Reading
`p5tst001vg-var'...
Filesystem type ext2/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:
404: Reading `p5tst001vg-var'..
.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:404: Reading
`p5tst001vg-var'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:404: Reading
`p5tst001vg-var'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:404: Reading
`p5tst001vg-var'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:404: Reading
`p5tst001vg-var'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:404: Reading
`p5tst001vg-var'...
, Last modification time 2009-12-14 08:47:38 Monday/Sources/jso/
Deb.grub2/burg-bzr1788/kern/disk.c:
404: Reading `p5tst001vg-var'...
=== > Here above I was even curious of this msg ("Last modification
time") but that's today and I am absolutely sure to haven't mount any
more since at least 4 days ago.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:404: Reading
`p5tst001vg-var'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:404: Reading
`p5tst001vg-var'...
, UUID 16ef0754-c845-46e9-a948-b9669ee68329/Sources/jso/Deb.grub2/burg-
bzr1788/kern/disk.c:348: Clo
sing `p5tst001vg-var'.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:348: Closing
`p5tst001vg-var'.
grub>
And when I re-launch this same cmdl, I don't it any more
(and I tried compilation OOTB (gcc -Os) and previous tips (gcc -O0)
but nothing help yet.)
I will so continue to insert grub_print() according to your previous
advises ;<)
Tx again,
J.
PS: I do not yet reinstall modules and still work with a grub kernel
with the following built-in matter: search minicmd sh normal nmenu
reboot halt
part_msdos ext2 fat ls linux lvm
Bean
If I guess right, the problem is caused by ofdisk and not lvm. Perhaps
you can try formating your small partition as ext3 and see if burg can
access files in it.
Jo
On Dec 14, 1:32 pm, Bean <bean12...@gmail.com> wrote:
> > Hello,
>
> > On Dec 11, 7:27 pm, Bean <bean12...@gmail.com> wrote:
> >> Hi,
>
> >> I finally track down a bug in ieee1275 which I believe to be the
> >> cause, please try r1787.
>
But here is some more test:
I first add following _dprint();
=== modified file 'fs/ext2.c'
--- fs/ext2.c 2009-11-22 17:01:12 +0000
+++ fs/ext2.c 2009-12-14 11:27:56 +0000
@@ -542,14 +542,25 @@
grub_ext2_mount (grub_disk_t disk)
{
struct grub_ext2_data *data;
+ /* Add tracing */
+ grub_err_t grub_disk_read_err = 0;
+ unsigned int i, j;
+ char *dmyp, dmyt[81];
+
data = grub_malloc (sizeof (struct grub_ext2_data));
if (!data)
return 0;
+ grub_dprintf ("fs", "%s(..., size %d, ...) just b4 grub_disk_read
()...\n", __FUNCTION__,
+ sizeof (struct grub_ext2_sblock));
+
/* Read the superblock. */
- grub_disk_read (disk, 1 * 2, 0, sizeof (struct grub_ext2_sblock),
+ grub_disk_read_err = grub_disk_read (disk, 1 * 2, 0, sizeof (struct
grub_ext2_sblock),
&data->sblock);
+ grub_dprintf ("fs", "%s() just aftr grub_disk_read() with err=
%d ...\n", __FUNCTION__,
+ grub_disk_read_err);
+
if (grub_errno)
goto fail;
=== modified file 'kern/disk.c'
--- kern/disk.c 2009-11-08 19:22:23 +0000
+++ kern/disk.c 2009-12-14 11:29:36 +0000
@@ -401,6 +401,8 @@
char *tmp_buf;
unsigned real_offset;
+ grub_dprintf ("disk", "Enter %s(..., sector 0x%lx, offset 0x%x,
size %d, ...)\n",
+ __FUNCTION__, (unsigned long) sector, offset, size);
grub_dprintf ("disk", "Reading `%s'...\n", disk->name);
/* First of all, check if the region is within the disk. */
@@ -413,6 +415,8 @@
return grub_errno;
}
+ grub_dprintf ("disk", "%s()...aftr success grub_disk_adjust_range()
\n", __FUNCTION__);
+
real_offset = offset;
/* Allocate a temporary buffer. */
What grub shows me:
grub> set debug=fs,disk ls -l (burgvg-tstlv)
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting fat...
grub_disk_read(..., sector 0x0, offset 0
x0, size 0, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adju
st_range()
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x180, offset
0x0, size 0, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adju
st_range()
Reading handle 0x18fb600: sector 0x
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting ext2...
(..., size 336, ...) just b4 grub
_disk_read()...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x2, offset 0
x0, size 0, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adju
st_range()
/Sources/jso/Deb.grub2/burg-bzr1788/fs/ext2.c:562: grub_ext2_mount()
just aftr grub_disk_read() wit
h err= 0 ...
failed.
Device burgvg-tstlv: /Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:
260: Opening `burgvg-tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting fat...
grub_disk_read(..., sector 0x0, offset 0
x0, size 0, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adju
st_range()
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting ext2...
(..., size 336, ...) just b4 grub
_disk_read()...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x2, offset 0
x0, size 0, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adju
st_range()
/Sources/jso/Deb.grub2/burg-bzr1788/fs/ext2.c:562: grub_ext2_mount()
just aftr grub_disk_read() wit
h err= 0 ...
failed.
Unknown filesystem/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:348:
Closing `burgvg-tstlv'.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:348: Closing `burgvg-
tstlv'.
A bit surprising readings of size ZERO?
But even a sample of what grub-fstst shows:
# /opt/grub2/burg1788/bin/grub-fstest -d disk,fs /dev/sdb ls -l
"(burgvg-tstlv)"
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
/Sources/jso/Deb.grub2/burg-bzr1788/fs/ext2.c:562: grub_ext2_mount()
just aftr grub_disk_read() with err= 0 ...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x4, offset 0x0, size 0, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x28, offset 0x0, size 128, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x128, offset 0x0, size 0, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x128, offset 0x0, size 8, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x4, offset 0x0, size 0, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x28, offset 0x0, size 128, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
Filesystem type ext2/Sources/jso/Deb.grub2/burg-bzr1788/fs/ext2.c:556:
grub_ext2_mount(..., size 336, ...) just b4 grub_disk_read().
..
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x2, offset 0x0, size 0, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
/Sources/jso/Deb.grub2/burg-bzr1788/fs/ext2.c:562: grub_ext2_mount()
just aftr grub_disk_read() with err= 0 ...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x4, offset 0x0, size 0, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x28, offset 0x0, size 128, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
/Sources/jso/Deb.grub2/burg-bzr1788/fs/ext2.c:556: grub_ext2_mount
(..., size 336, ...) just b4 grub_disk_read()...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x2, offset 0x0, size 0, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
/Sources/jso/Deb.grub2/burg-bzr1788/fs/ext2.c:562: grub_ext2_mount()
just aftr grub_disk_read() with err= 0 ...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x4, offset 0x0, size 0, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x28, offset 0x0, size 128, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
, Last modification time 2009-12-04 08:43:50 Friday/Sources/jso/
Deb.grub2/burg-bzr1788/fs/ext2.c:556: grub_ext2_mount(..., size 336,
...) just b4 grub_disk_read()...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x2, offset 0x0, size 0, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
/Sources/jso/Deb.grub2/burg-bzr1788/fs/ext2.c:562: grub_ext2_mount()
just aftr grub_disk_read() with err= 0 ...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x4, offset 0x0, size 0, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x28, offset 0x0, size 128, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading `burgvg-
tstlv'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
, UUID 3a687767-567b-48b9-baaa-661835b760a5/Sources/jso/Deb.grub2/burg-
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:348: Closing `burgvg-
tstlv'.
off-line (about 250K here would certainly not appreciated by
reader ;<))
Cheers,
J.
Bean
I have a theory, could you dump the partition layout, including
details about start sector and length ?
Bean
Oh BTW, could you try this binary:
http://grub4dos.sourceforge.net/grub.elf
It includes module minicmd sh normal nmenu reboot halt part_msdos ext2
fat ls linux lvm search.
Jo
On Dec 14, 8:41 pm, Bean <bean12...@gmail.com> wrote:
> Hi,
>
> Oh BTW, could you try this binary:
>
> http://grub4dos.sourceforge.net/grub.elf
>
> It includes module minicmd sh normal nmenu reboot halt part_msdos ext2
> fat ls linux lvm search.
>
DEFAULT CATCH!, exception-handler=fff00300
at %SRR0: 0000000000c3c25c %SRR1: 800000000000b002
Call History
------------
@ - c3c1f0
close-package - c58060
(poplocals) - c3a758
(init-program) - c7e298
boot - c7ec7c
evaluate - c4a638
invalid pointer - d61c95
invalid pointer - f
invalid pointer - f
catch - c38fe8
bt-task-boot-on-this - d12068
(poplocals) - c3a758
catch - c38fe8
execute-device-method - c58bcc
(poplocals) - c3a758
(select-boot-seq) - c59ba4
Client's Fix Pt Regs:
00 00100000000001f4 ffffffffffffffff 00000000deadbeef
fffffffffffffffc
04 0000000000000000 0000000000000000 0000000000000000
0000000000000001
08 0000000000001000 0000030002001000 0000000000000003
0000000000007000
0c 0000000022800000 0000000000c17100 0000000000c18000
000000000009c4b0
10 0000000000d97258 0000000000d96f71 0000000000c57d80
0000000000c58060
14 0000000000000000 ffffffffffffffff 0000000000000000
0000000000000000
18 0000000000c13000 0000000000c38000 0000000000c14d40
0000000000c16ec0
1c 0000000000c20000 0000000000c3fdf0 0000000000c11ea0
0000000000c10fa8
Special Regs:
%IV: 00000300 %CR: 84800000 %XER: 20000008 %DSISR:
08000000
%SRR0: 0000000000c3c25c %SRR1: 800000000000b002
%LR: 0000000000c3c1f0 %CTR: 0000000000000000
%DAR: ffffffffffffffff
Virtual PID = 0
ofdbg
That said here is also the dump of disks:
(sdb being the Debian install and the 2d slice contains the small
burgvg with an ext fs into tstlv)
The readable cfdisk:
AIX VDASD
12885MB
Heads: 64 Sectors per track: 32 Cylinders: 12288
Number Flags Part Type Filesystem
Label Size
------------------------------------------------------------------------------
1 Bootable Primary
2 Primary
[Linux] 7.34MB
3 Primary
ext3 262MB
4
Extended 12591MB
5 Logical linux-swap
(v1) 3145MB
6 Logical
ext3 2097MB
7 Logical [Linux
LVM] 7349MB
the fdisk
Disk /dev/sdb: 64 heads, 32 sectors, 12288 cylinders
Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
1 80 1 0 0 63 31 22 32 47072 06
2 00 0 0 23 63 31 29 47104 14336 83
3 00 0 0 30 63 31 279 61440 512000 83
4 00 0 0 280 63 31 12287 573440 24592384 05
5 00 1 0 280 63 31 3278 573472 6141920 82
Warning: Partition 5 does not end on cylinder
boundary.
6 00 1 0 3279 63 31 5278 6715424 4095968 83
Warning: Partition 6 does not end on cylinder
boundary.
7 00 1 0 5279 63 31 12287 10811424 14354400 8e
Warning: Partition 7 does not end on cylinder
boundary.
or
# sfdisk -d /dev/sdb
# partition table of /dev/sdb
unit: sectors
/dev/sdb1 : start= 32, size= 47072, Id= 6, bootable
/dev/sdb2 : start= 47104, size= 14336, Id=83
/dev/sdb3 : start= 61440, size= 512000, Id=83
/dev/sdb4 : start= 573440, size= 24592384, Id= 5
/dev/sdb5 : start= 573472, size= 6141920, Id=82
/dev/sdb6 : start= 6715424, size= 4095968, Id=83
/dev/sdb7 : start= 10811424, size= 14354400, Id=8e
The same for the disk sda containing the OpenSuse installation:
GNU cfdisk 1.2.3
AIX VDASD
Disk: /dev/sda Disk type: msdos Size: 10737418239B,
10737MB
Heads: 255 Sectors per track: 63 Cylinders: 1305
Number Flags Part Type Filesystem
Label Size
------------------------------------------------------------------------------
1 Bootable Primary
fat16 24.6MB
2 Primary [Linux
LVM] 10709MB
Command (m for help):
x
Expert command (m for help):
p
Disk /dev/sda: 255 heads, 63 sectors, 1305 cylinders
Nr AF Hd Sec Cyl Hd Sec Cyl Start Size ID
1 80 1 0 0 254 62 2 63 48132 06
2 00 0 0 3 254 62 1304 48195 20916630 8e
# sfdisk -d /dev/sda
# partition table of /dev/sda
unit: sectors
/dev/sda1 : start= 63, size= 48132, Id= 6, bootable
/dev/sda2 : start= 48195, size= 20916630, Id=8e
/dev/sda3 : start= 0, size= 0, Id= 0
/dev/sda4 : start= 0, size= 0, Id= 0
Tx,
J.
Bean
Quite strange, what about this one:
http://grub4dos.sourceforge.net/grub1.elf
Bean
And BTW, could you upload your grub.elf ?
Jo
On Dec 15, 9:21 am, Bean <bean12...@gmail.com> wrote:
>
> > On Dec 14, 8:41 pm, Bean <bean12...@gmail.com> wrote:
> >> Hi,
>
> >> Oh BTW, could you try this binary:
>
> >>http://grub4dos.sourceforge.net/grub.elf
>
> >> It includes module minicmd sh normal nmenu reboot halt part_msdos ext2
> >> fat ls linux lvm search.
>
Yes it boot but fallback to 'grub rescue>' because of 'error: no such
partition'
J.
Jo
>
> > On Dec 14, 8:41 pm, Bean <bean12...@gmail.com> wrote:
> >> Hi,
>
> >> Oh BTW, could you try this binary:
>
> >>http://grub4dos.sourceforge.net/grub.elf
>
> >> It includes module minicmd sh normal nmenu reboot halt part_msdos ext2
> >> fat ls linux lvm search.
>
partition'
>
>
J.
Bean
>
>
> On Dec 15, 9:21 am, Bean <bean12...@gmail.com> wrote:
>> On Tue, Dec 15, 2009 at 3:50 PM, Jo <rubis...@scarlet.be> wrote:
>>
>> > On Dec 14, 8:41 pm, Bean <bean12...@gmail.com> wrote:
>> >> Hi,
>>
>> >> Oh BTW, could you try this binary:
>>
>> >>http://grub4dos.sourceforge.net/grub.elf
>>
>> >> It includes module minicmd sh normal nmenu reboot halt part_msdos ext2
>> >> fat ls linux lvm search.
>>
> [snip]
>>
>> Hi,
>>
>> Quite strange, what about this one:
>>
>> http://grub4dos.sourceforge.net/grub1.elf
>>
> Yes it boot but fallback to 'grub rescue>' because of 'error: no such
> partition'
Yep, that's normal as grub1.elf only contains the kernel.
Could you retry grub.elf ? It works in my ppc machine. BTW, you should
rename the module directory as grub.elf is compiled using a lower
version of gcc, it may has issue using modules from disk.
Jo
> > > # sfdisk -d /dev/sdb
> > > # partition table of /dev/sdb
> > > unit: sectors
>
> > > /dev/sdb1 : start= 32, size= 47072, Id= 6, bootable
> > > /dev/sdb2 : start= 47104, size= 14336, Id=83
> > > /dev/sdb3 : start= 61440, size= 512000, Id=83
> > > /dev/sdb4 : start= 573440, size= 24592384, Id= 5
> > > /dev/sdb5 : start= 573472, size= 6141920, Id=82
> > > /dev/sdb6 : start= 6715424, size= 4095968, Id=83
> > > /dev/sdb7 : start= 10811424, size= 14354400, Id=8e
>
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading
`disk2'...
()...aftr success grub_disk_adjust_range()
flag 0x80, type 0x6, start 32, len 47072
/Sources/jso/Deb.grub2/burg-bzr1788/partmap/msdos.c:161: partition 1:
flag 0x0, type 0x8e, start 47104, len 14336
/Sources/jso/Deb.grub2/burg-bzr1788/partmap/msdos.c:161: partition 2:
flag 0x0, type 0x83, start 61440, len 512000
/Sources/jso/Deb.grub2/burg-bzr1788/partmap/msdos.c:161: partition 3:
flag 0x0, type 0x5, start 573440, len 24592384
(I just change code to print a %llu format in place of %llx)
even thought I never read anything about partion 4, 5 & 6?
I launch a simple 'ls -l' and here is what I got only for what I
suppose being related to 2d disk slaice (burgvg-tstlv):
Partition disk2,2: /Sources/jso/Deb.grub2/burg-bzr1788/kern/
disk.c:260: Opening `disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/disk/ieee1275/ofdisk.c:173:
Opening `disk2:0'.
/Sources/jso/Deb.grub2/burg-bzr1788/disk/ieee1275/ofdisk.c:183: Opened
`disk2:0' as handle 0x1bd0b80.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x0, offset 0x0, size 0, ...)
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
flag 0x80, type 0x6, start 0x32, len 0x47072
/Sources/jso/Deb.grub2/burg-bzr1788/partmap/msdos.c:161: partition 1:
flag 0x0, type 0x8e, start 0x47104, len 0x14336
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting affs...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x0, offset 0x0, size 0, ...)
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
/Sources/jso/Deb.grub2/burg-bzr1788/disk/ieee1275/ofdisk.c:239:
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:64: affs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting afs...
grub_disk_read(..., sector 0x2, offset 0x0, size 0, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting afs_be...
grub_disk_read(..., sector 0x2, offset 0x0, size 0, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting befs...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x1, offset 0x0, size 0, ...)
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting befs_be...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x1, offset 0x0, size 0, ...)
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting cpiofs...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x0, offset 0x0, size 0, ...)
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting hfs...
grub_disk_read(..., sector 0x2, offset 0x0, size 0, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting hfsplus...
grub_disk_read(..., sector 0x2, offset 0x0, size 0, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting iso9660...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x40, offset 0x0, size 0, ...)
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
/Sources/jso/Deb.grub2/burg-bzr1788/disk/ieee1275/ofdisk.c:239:
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:64: iso9660 detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting jfs...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x40, offset 0x0, size 0, ...)
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting minix...
grub_disk_read(..., sector 0x2, offset 0x0, size 0, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting ntfs...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x0, offset 0x0, size 0, ...)
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting
reiserfs...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x80, offset 0x0, size 0, ...)
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
/Sources/jso/Deb.grub2/burg-bzr1788/disk/ieee1275/ofdisk.c:239:
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:64: reiserfs detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting sfs...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x0, offset 0x0, size 0, ...)
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting tarfs...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x0, offset 0x0, size 0, ...)
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting udf...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x40, offset 0x0, size 0, ...)
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting ufs1...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x80, offset 0x0, size 0, ...)
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
/Sources/jso/Deb.grub2/burg-bzr1788/disk/ieee1275/ofdisk.c:239:
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x0, offset 0x0, size 0, ...)
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
/Sources/jso/Deb.grub2/burg-bzr1788/disk/ieee1275/ofdisk.c:239:
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:64: ufs1 detection
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting ufs2...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x80, offset 0x0, size 0, ...)
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting xfs...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x0, offset 0x0, size 0, ...)
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
`disk2,2'...
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
()...aftr success grub_disk_adjust_range()
failed.
/Sources/jso/Deb.grub2/burg-bzr1788/kern/fs.c:58: Detecting ext2...
/Sources/jso/Deb.grub2/burg-bzr1788/fs/ext2.c:556: grub_ext2_mount
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:405: Enter
grub_disk_read(..., sector 0x2, offset 0x0, size 0, ...)
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:406: Reading
/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:418: grub_disk_read
/Sources/jso/Deb.grub2/burg-bzr1788/fs/ext2.c:562: grub_ext2_mount()
just aftr grub_disk_read() with err= 0 ...
failed.
Unknown filesystem/Sources/jso/Deb.grub2/burg-bzr1788/kern/disk.c:348:
/Sources/jso/Deb.grub2/burg-bzr1788/disk/ieee1275/ofdisk.c:226:
Closing handle 0x1bd0b80.
That said: this cmdl "ls -l" is supposed to cover all partitions? but
again I read well reading 'disk2,1', disk2,2', 'disk2,3', 'disk2',4'
but never 'disk2,5', 'disk2,6' nor 'disk2,7'?
Don't know if that could help?
Tx,
J.
Jo
On Dec 15, 10:11 am, Bean <bean12...@gmail.com> wrote:
> On Tue, Dec 15, 2009 at 4:21 PM, Bean <bean12...@gmail.com> wrote:
Tx,
J.
Jo
Tx,
J.
Bean
Good point, it seems that it can't access extended partition. BTW, is
it working in grub-fstest ?
Bean
>> And BTW, could you upload your grub.elf ?
>>
> I have a stupid question: how should I do that?
Oh never mind, it's probably not related to gcc anyway.
Jo
On Dec 15, 10:25 am, Bean <bean12...@gmail.com> wrote:
>
> > On Dec 15, 9:21 am, Bean <bean12...@gmail.com> wrote:
> >> On Tue, Dec 15, 2009 at 3:50 PM, Jo <rubis...@scarlet.be> wrote:
>
> >> > On Dec 14, 8:41 pm, Bean <bean12...@gmail.com> wrote:
> >> >> Hi,
>
> >> >> Oh BTW, could you try this binary:
>
> >> >>http://grub4dos.sourceforge.net/grub.elf
>
> >> >> It includes module minicmd sh normal nmenu reboot halt part_msdos ext2
> >> >> fat ls linux lvm search.
>
> > [snip]
>
> >> Hi,
>
> >> Quite strange, what about this one:
>
> >>http://grub4dos.sourceforge.net/grub1.elf
>
> > Yes it boot but fallback to 'grub rescue>' because of 'error: no such
> > partition'
>
> Hi,
>
> Yep, that's normal as grub1.elf only contains the kernel.
>
> Could you retry grub.elf ? It works in my ppc machine. BTW, you should
> rename the module directory as grub.elf is compiled using a lower
> version of gcc, it may has issue using modules from disk.
>
Never the less this time it boot and here is the output of 'ls -l
(burgvg-tstlv)
set debug=fs,disk
grub> ls -l (burgvg-tstlv)
../wrk/unx/burg/kern/disk.c:260: Opening `burgvg-tstlv'...
../wrk/unx/burg/kern/fs.c:58: Detecting fat...
../wrk/unx/burg/kern/disk.c:404: Reading `burgvg-tstlv'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,2'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:239: Reading handle 0x18fb600:
sector 0xb980, size 0x8, buf 0x1c06530.
../wrk/unx/burg/kern/fs.c:64: fat detection failed.
../wrk/unx/burg/kern/fs.c:58: Detecting ext2...
../wrk/unx/burg/kern/disk.c:404: Reading `burgvg-tstlv'...
../wrk/unx/burg/kern/fs.c:64: ext2 detection failed.
Device burgvg-tstlv: ../wrk/unx/burg/kern/disk.c:260: Opening `burgvg-
tstlv'...
../wrk/unx/burg/kern/fs.c:58: Detecting fat...
../wrk/unx/burg/kern/disk.c:404: Reading `burgvg-tstlv'...
../wrk/unx/burg/kern/fs.c:64: fat detection failed.
../wrk/unx/burg/kern/fs.c:58: Detecting ext2...
../wrk/unx/burg/kern/disk.c:404: Reading `burgvg-tstlv'...
../wrk/unx/burg/kern/fs.c:64: ext2 detection failed.
Unknown filesystem../wrk/unx/burg/kern/disk.c:348: Closing `burgvg-
tstlv'.
../wrk/unx/burg/kern/disk.c:348: Closing `burgvg-tstlv'.
grub>
Does it help?
Tx,
J.
Jo
> That said: this cmdl "ls -l" is supposed to cover all partitions? but
> again I read well reading 'disk2,1', disk2,2', 'disk2,3', 'disk2',4'
> but never 'disk2,5', 'disk2,6' nor 'disk2,7'?
>
Please forget this remark, it seems that I erase too much of my log.
Sorry,
J.
Bean
From you partition layout, it seems sdb1 + sdb2 is only 31m, perhaps
you can dd them to a file and upload it somewhere:
sudo dd if=/dev/sdb of=disk_dump bs=512 count=61440
gzip disk_dump
Jo
> > That said: this cmdl "ls -l" is supposed to cover all partitions? but
> > again I read well reading 'disk2,1', disk2,2', 'disk2,3', 'disk2',4'
> > but never 'disk2,5', 'disk2,6' nor 'disk2,7'?
>
> > Don't know if that could help?
>
> Hi,
>
> Good point, it seems that it can't access extended partition. BTW, is
> it working in grub-fstest ?
>
(p5_sid)root@p5tst001:/opt/grub2/burg1788/bin# /opt/grub2/burg1788/bin/
grub-fstest /dev/sdb ls -l
Device burgvg-tstlv: Filesystem type ext2, Last modification time
2009-12-14 14:15:09 Monday, UUID 23db244e-be2e-4022-86a7-01bd8ceacebe
Device p5tst001vg-Sources: Filesystem type ext2, Last modification
time 2009-12-15 11:04:37 Tuesday, UUID
161e55f6-7498-45dd-91fe-35ebbb09bac3
Device p5tst001vg-UsrSrc: Filesystem type ext2, Last modification time
2009-12-15 11:04:37 Tuesday, UUID 3257bc77-e2cb-4359-b283-6bc2d9a37fa3
Device p5tst001vg-home: Filesystem type ext2, Last modification time
2009-12-15 11:04:37 Tuesday, UUID 3b2aa16a-a834-4b54-a102-d0e694b13c94
Device p5tst001vg-tmp: Filesystem type ext2, Last modification time
2009-12-15 11:04:37 Tuesday, UUID 88894569-318c-4be8-91b8-fd8d821e8873
Device p5tst001vg-var: Filesystem type ext2, Last modification time
2009-12-15 11:04:36 Tuesday, UUID c2553cae-c81f-40dd-97fb-aeffcfd9ccb9
Device loop0: Partition table
Partition loop0,7: Unknown filesystem
Partition loop0,6: Filesystem type ext2, Last modification time
2009-12-15 11:04:35 Tuesday, UUID 3c51c43e-63a7-4ff1-9b1c-cf98addcb7ed
Partition loop0,5: Unknown filesystem
Partition loop0,3: Filesystem type ext2, Last modification time
2009-12-15 11:04:36 Tuesday, UUID 16ef0754-c845-46e9-a948-b9669ee68329
Partition loop0,2: Unknown filesystem
Partition loop0,1: Filesystem type fat, Label grub2, UUID 4adc-336e
Device host: Filesystem type hostfs
grub> ls -l
Device burgvg-tstlv: Unknown filesystem
Device p5tst001vg-Sources: Unknown filesystem
Device p5tst001vg-UsrSrc: Unknown filesystem
Device p5tst001vg-home: Unknown filesystem
Device p5tst001vg-tmp: Unknown filesystem
Device p5tst001vg-var: Unknown filesystem
Device disk2: Partition table
Partition disk2,7: Unknown filesystem
Partition disk2,6: Filesystem type ext2, Last modification
Partition disk2,5: Unknown filesystem
Partition disk2,3: Filesystem type ext2, Last modification
Partition disk2,2: Unknown filesystem
Partition disk2,1: Filesystem type fat, Label grub2, UUID
4adc-336e
disk2,2 burgvg-tstlv
disk2,3 my linux boot fs
disk2,5 the linux swap area
disk2,6 the linux root fs
disk2,7 the vg for some other lv and their fs
Excuse for mistakes,
J.
Jo
On Dec 15, 12:17 pm, Bean <bean12...@gmail.com> wrote:
> > [snip]
>
> >> That said: this cmdl "ls -l" is supposed to cover all partitions? but
> >> again I read well reading 'disk2,1', disk2,2', 'disk2,3', 'disk2',4'
> >> but never 'disk2,5', 'disk2,6' nor 'disk2,7'?
>
> > [snip]
> > Please forget this remark, it seems that I erase too much of my log.
>
> Hi,
>
> From you partition layout, it seems sdb1 + sdb2 is only 31m, perhaps
> you can dd them to a file and upload it somewhere:
>
> sudo dd if=/dev/sdb of=disk_dump bs=512 count=61440
> gzip disk_dump
>
J.
Bean
Perhaps you can upload it to the files section of burg-devel.
Jo
On Dec 15, 2:12 pm, Bean <bean12...@gmail.com> wrote:
>
> > On Dec 15, 12:17 pm, Bean <bean12...@gmail.com> wrote:
> >> On Tue, Dec 15, 2009 at 7:11 PM, Jo <rubis...@scarlet.be> wrote:
> >> > [snip]
>
> >> >> That said: this cmdl "ls -l" is supposed to cover all partitions? but
> >> >> again I read well reading 'disk2,1', disk2,2', 'disk2,3', 'disk2',4'
> >> >> but never 'disk2,5', 'disk2,6' nor 'disk2,7'?
>
> >> > [snip]
> >> > Please forget this remark, it seems that I erase too much of my log.
>
> >> Hi,
>
> >> From you partition layout, it seems sdb1 + sdb2 is only 31m, perhaps
> >> you can dd them to a file and upload it somewhere:
>
> >> sudo dd if=/dev/sdb of=disk_dump bs=512 count=61440
> >> gzip disk_dump
>
> > Ok file is ready but where should I put it available for you?
>
> Hi,
>
> Perhaps you can upload it to the files section of burg-devel.
>
<http://groups.google.com/group/burg-devel/files>
I just have to "split" because > 10MB but you should cat DiskDump.gza*
> DiskDump.gz
(md5sum check should be:
(p5_sid)root@p5tst001:/var/tmp# md5sum DiskDump.gz
0482677172d2bcf737ac12ecad03ccfc DiskDump.gz
)
Tx,
J.
PS: Let me know if I have to do something to delete those stuff.
Bean
> Well I didn't pay attention but google group also allow it:
> <http://groups.google.com/group/burg-devel/files>
> I just have to "split" because > 10MB but you should cat DiskDump.gza*
>> DiskDump.gz
> (md5sum check should be:
> (p5_sid)root@p5tst001:/var/tmp# md5sum DiskDump.gz
> 0482677172d2bcf737ac12ecad03ccfc DiskDump.gz
> )
>
> Tx,
> J.
>
> PS: Let me know if I have to do something to delete those stuff.
>
Thanks, I've downloaded the file now, you can delete them.
Bean
Fix some bug for sparc64-ieee1275, please see if it helps for powerpc as well.
Bean
> Hi,
>
> Fix some bug for sparc64-ieee1275, please see if it helps for powerpc as well.
BTW, if it doesn't work, please try this image:
http://grub4dos.sourceforge.net/grub2.elf
Make sure to remove *.mod and *.lst from boot partition so that it
won't be auto loaded.
It should enter rescue shell, enter the following command:
ls (burgvg-tstlv)
Here is my output:
lvm: 384 8 9e3b7f03
lvm: 424 8 7f9e8f73
lvm: 680 8 d0fd2b50
2009-12-14 14:15:09 Monday, UUID 23db244e-be2e-4022-86a7-01bd8ceacebe
Jo
Sorry to disappoint you again but my local build of r1789 doesn't yet
help (even thought it's still booting).
On Dec 15, 8:20 pm, Bean <bean12...@gmail.com> wrote:
> > Hi,
>
> > Fix some bug for sparc64-ieee1275, please see if it helps for powerpc as well.
>
> Hi,
>
> BTW, if it doesn't work, please try this image:
>
> http://grub4dos.sourceforge.net/grub2.elf
>
> Make sure to remove *.mod and *.lst from boot partition so that it
> won't be auto loaded.
>
> It should enter rescue shell, enter the following command:
>
> ls (burgvg-tstlv)
>
> Here is my output:
> lvm: 384 8 9e3b7f03
> lvm: 424 8 7f9e8f73
> lvm: 680 8 d0fd2b50
> Device burgvg-tstlv: Filesystem type ext2, Last modification time
> 2009-12-14 14:15:09 Monday, UUID 23db244e-be2e-4022-86a7-01bd8ceacebe
>
grub rescue> ls (burgvg-tstlv)
lvm: 384 8 74c26092
Device burgvg-tstlv: Unknown filesystem
Tx anyway,
J.
PS: UUID is the same for me ;<)
# /opt/grub2/burg1789/bin/grub-fstest /dev/sdb ls -l "(burgvg-
tstlv)"
Bean
It seems ofdisk has reads the wrong content, as the checksum doesn't match.
Please try this:
http://grub4dos.sourceforge.net/grub3.elf
I've hacked hello.c to dump sector information, for example:
hello 0xb980
Dumps 8 sector starts with 0xb980, which is the sector lvm access for
offset 384. You can use dd to extract it. Compare its content with
real content extract with dd.
Bean
Jo
> Hi,
>
> It seems ofdisk has reads the wrong content, as the checksum doesn't match.
>
> Please try this:
>
> http://grub4dos.sourceforge.net/grub3.elf
>
> I've hacked hello.c to dump sector information, for example:
>
> hello 0xb980
>
> Dumps 8 sector starts with 0xb980, which is the sector lvm access for
> offset 384. You can use dd to extract it. Compare its content with
> real content extract with dd.
>
but here is already some more data from grub3.elf:
grub rescue> hello 0xb980
Reading 1bd0b80 0 24313856
00000000 fa b8 00 10 8e d0 bc 00 b0 b8 00 00 8e d8 8e c0
|................|
00000010 fb be 00 7c bf 00 06 b9 00 02 f3 a4 ea 21 06 00
|...|.........!..|
00000020 00 be be 07 38 04 75 0b 83 c6 10 81 fe fe 07 75 |....
8.u........u|
00000030 f3 eb 16 b4 02 b0 01 bb 00 7c b2 80 8a 74 01 8b
|.........|...t..|
00000040 4c 02 cd 13 ea 00 7c 00 00 eb fe 00 00 00 00 00 |
L.....|.........|
00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
*
000001a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
000001b0 00 00 00 00 00 00 00 00 00 08 da 2f 00 00 80 01
|.........../....|
000001c0 01 00 06 3f 20 16 20 00 00 00 e0 b7 00 00 00 00
|...? . .........|
000001d0 01 17 8e 3f 20 1d 00 b8 00 00 00 38 00 00 00 00
|...? ......8....|
000001e0 01 1e 83 3f 60 17 00 f0 00 00 00 d0 07 00 00 00 |...?
`...........|
000001f0 41 18 05 3f e0 ff 00 c0 08 00 00 40 77 01 55 aa |
A..?.......@w.U.|
00000200 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
*
00000ff0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
but for dd I am a bit confused: I thought first that sector size was
of 512 bytes but 0xb980(47488)*512=1730000(24313856) which is not
1bd0b80.
So may b can you just send me the dd parameters so that I can even use
hexedit to compare?
Sorry for inconvenience,
J.
Jo
On Dec 16, 11:41 am, Bean <bean12...@gmail.com> wrote:
> Hi,
>
> BTW, just found another bug, please try:
>
> http://grub4dos.sourceforge.net/grub4.elf
>
grub rescue> ls -l (burgvg-tstlv)
Device burgvg-tstlv: Filesystem cannot be accessed
error: Read error on block: 47490
and more with set debug=fs,disk
grub rescue> ls -l (burgvg-tstlv)
../wrk/unx/burg/kern/disk.c:404: Reading `burgvg-tstlv'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:239: Reading handle 0x18fb600:
sector 0xb980, size 0x8, buf
sector 0xb980, size 0x8, buf
../wrk/unx/burg/kern/disk.c:472: disk2,2 read failed
../wrk/unx/burg/disk/ieee1275/ofdisk.c:239: Reading handle 0x18fb600:
sector 0xb980, size 0x8, buf
0x1c0f680.
../wrk/unx/burg/kern/disk.c:472: disk2,2 read failed
../wrk/unx/burg/kern/disk.c:472: burgvg-tstlv read failed
Device burgvg-tstlv: ../wrk/unx/burg/kern/disk.c:260: Opening `burgvg-
tstlv'...
Many tx,
J.
Bean
Jo
On Dec 16, 4:19 pm, Bean <bean12...@gmail.com> wrote:
Welcome to GRUB!
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
4096 4096
error: unknown filesystem
Entering rescue mode...
J.
Bean
What does "ls (burgvg-tstlv)" shows ?
Bean
Jo
grub rescue> ls -l (burgvg-tstlv)
4096 0
4096 0
4096 0
512 0
Device burgvg-tstlv: Filesystem cannot be accessed
error: Read error on block: 47490
appology,
J.
On Dec 16, 4:56 pm, Bean <bean12...@gmail.com> wrote:
Jo
On Dec 16, 5:05 pm, Bean <bean12...@gmail.com> wrote:
> On Wed, Dec 16, 2009 at 11:56 PM, Bean <bean12...@gmail.com> wrote:
> > On Wed, Dec 16, 2009 at 11:29 PM, Jo <rubis...@scarlet.be> wrote:
>
> >> On Dec 16, 4:19 pm, Bean <bean12...@gmail.com> wrote:
> >>> On Wed, Dec 16, 2009 at 9:31 PM, Jo <rubis...@scarlet.be> wrote:
[snip]
>
> > Hi,
>
> > What does "ls (burgvg-tstlv)" shows ?
>
> Hi,
>
> Try this one:
>
> http://grub4dos.sourceforge.net/grub6.elf
>
Sorry not yet:
grub rescue> ls -l (burgvg-tstlv)
4096 0
4096 0
4096 0
512 0
Device burgvg-tstlv: Filesystem cannot be accessed
error: Read error on block: 47490
> --
Jo
On Dec 16, 5:05 pm, Bean <bean12...@gmail.com> wrote:
> On Wed, Dec 16, 2009 at 11:56 PM, Bean <bean12...@gmail.com> wrote:
> > On Wed, Dec 16, 2009 at 11:29 PM, Jo <rubis...@scarlet.be> wrote:
>
> >> On Dec 16, 4:19 pm, Bean <bean12...@gmail.com> wrote:
> >>> On Wed, Dec 16, 2009 at 9:31 PM, Jo <rubis...@scarlet.be> wrote:
[snip]
>
> > Hi,
>
> > What does "ls (burgvg-tstlv)" shows ?
>
> Hi,
>
> Try this one:
>
> http://grub4dos.sourceforge.net/grub6.elf
>
Sorry not yet:
grub rescue> ls -l (burgvg-tstlv)
4096 0
4096 0
4096 0
512 0
Device burgvg-tstlv: Filesystem cannot be accessed
error: Read error on block: 47490
> --
Jo
On Dec 16, 5:05 pm, Bean <bean12...@gmail.com> wrote:
> On Wed, Dec 16, 2009 at 11:56 PM, Bean <bean12...@gmail.com> wrote:
> > On Wed, Dec 16, 2009 at 11:29 PM, Jo <rubis...@scarlet.be> wrote:
>
> >> On Dec 16, 4:19 pm, Bean <bean12...@gmail.com> wrote:
> >>> On Wed, Dec 16, 2009 at 9:31 PM, Jo <rubis...@scarlet.be> wrote:
[snip]
>
> > Hi,
>
> > What does "ls (burgvg-tstlv)" shows ?
>
> Hi,
>
> Try this one:
>
> http://grub4dos.sourceforge.net/grub6.elf
>
Sorry not yet:
grub rescue> ls -l (burgvg-tstlv)
4096 0
4096 0
4096 0
512 0
Device burgvg-tstlv: Filesystem cannot be accessed
error: Read error on block: 47490
> --
Bean
>
>
> On Dec 16, 5:05 pm, Bean <bean12...@gmail.com> wrote:
>> On Wed, Dec 16, 2009 at 11:56 PM, Bean <bean12...@gmail.com> wrote:
>> > On Wed, Dec 16, 2009 at 11:29 PM, Jo <rubis...@scarlet.be> wrote:
>>
>> >> On Dec 16, 4:19 pm, Bean <bean12...@gmail.com> wrote:
>> >>> On Wed, Dec 16, 2009 at 9:31 PM, Jo <rubis...@scarlet.be> wrote:
> [snip]
>>
>> > Hi,
>>
>> > What does "ls (burgvg-tstlv)" shows ?
>>
>> Hi,
>>
>> Try this one:
>>
>> http://grub4dos.sourceforge.net/grub6.elf
>>
> Sorry not yet:
> grub rescue> ls -l (burgvg-tstlv)
> 4096 0
> 4096 0
> 4096 0
> 512 0
> Device burgvg-tstlv: Filesystem cannot be accessed
> error: Read error on block: 47490
Hi,
Please try this:
http://grub4dos.sourceforge.net/grub7.elf
Jo
On Dec 17, 9:38 am, Bean <bean12...@gmail.com> wrote:
> On Thu, Dec 17, 2009 at 4:21 PM, Jo <rubis...@scarlet.be> wrote:
>
> > On Dec 16, 5:05 pm, Bean <bean12...@gmail.com> wrote:
> >> On Wed, Dec 16, 2009 at 11:56 PM, Bean <bean12...@gmail.com> wrote:
> >> > On Wed, Dec 16, 2009 at 11:29 PM, Jo <rubis...@scarlet.be> wrote:
>
> >> >> On Dec 16, 4:19 pm, Bean <bean12...@gmail.com> wrote:
> >> >>> On Wed, Dec 16, 2009 at 9:31 PM, Jo <rubis...@scarlet.be> wrote:
> > [snip]
>
> >> > Hi,
>
> >> > What does "ls (burgvg-tstlv)" shows ?
>
> >> Hi,
>
> >> Try this one:
>
> >>http://grub4dos.sourceforge.net/grub6.elf
>
> > Sorry not yet:
> > grub rescue> ls -l (burgvg-tstlv)
> > 4096 0
> > 4096 0
> > 4096 0
> > 512 0
> > Device burgvg-tstlv: Filesystem cannot be accessed
> > error: Read error on block: 47490
>
> Hi,
>
> Please try this:
>
> http://grub4dos.sourceforge.net/grub7.elf
>
Obvioulsy...but unfortunately not yet help:
grub rescue> ls -l (burgvg-tstlv)
4096 0
4096 0
4096 0
4096 0
4096 0
4096 0
512 0
Device burgvg-tstlv: Filesystem cannot be accessed
error: Read error on block: 47490
Tx again,
J.
Jo
On Dec 17, 9:38 am, Bean <bean12...@gmail.com> wrote:
> On Thu, Dec 17, 2009 at 4:21 PM, Jo <rubis...@scarlet.be> wrote:
>
> > On Dec 16, 5:05 pm, Bean <bean12...@gmail.com> wrote:
> >> On Wed, Dec 16, 2009 at 11:56 PM, Bean <bean12...@gmail.com> wrote:
> >> > On Wed, Dec 16, 2009 at 11:29 PM, Jo <rubis...@scarlet.be> wrote:
>
> >> >> On Dec 16, 4:19 pm, Bean <bean12...@gmail.com> wrote:
> >> >>> On Wed, Dec 16, 2009 at 9:31 PM, Jo <rubis...@scarlet.be> wrote:
> > [snip]
>
> >> > Hi,
>
> >> > What does "ls (burgvg-tstlv)" shows ?
>
> >> Hi,
>
> >> Try this one:
>
> >>http://grub4dos.sourceforge.net/grub6.elf
>
> > Sorry not yet:
> > grub rescue> ls -l (burgvg-tstlv)
> > 4096 0
> > 4096 0
> > 4096 0
> > 512 0
> > Device burgvg-tstlv: Filesystem cannot be accessed
> > error: Read error on block: 47490
>
> Hi,
>
> Please try this:
>
> http://grub4dos.sourceforge.net/grub7.elf
>
Obvioulsy...but unfortunately not yet help:
grub rescue> ls -l (burgvg-tstlv)
4096 0
4096 0
4096 0
4096 0
4096 0
4096 0
512 0
Device burgvg-tstlv: Filesystem cannot be accessed
error: Read error on block: 47490
Tx again,
J.
Bean
Hi,
Please try:
http://grub4dos.sourceforge.net/grub8.elf
If it still does work, run this command:
hello 0xb980
Jo
On Dec 17, 2:57 pm, Bean <bean12...@gmail.com> wrote:
Sorry but not yet:
grub rescue> ls -l (burgvg-tstlv)
4096 0
4096 0
4096 0
512 0
Device burgvg-tstlv: Filesystem cannot be accessed
error: Read 18fb600 error on block: 47490
and:
grub rescue> hello 0xb980
Reading 1bd3500 24313856 0
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
*
000003f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
00000400 00 04 00 00 00 10 00 00 00 00 00 00 58 0b 00 00
|............X...|
00000410 f4 03 00 00 01 00 00 00 00 00 00 00 00 00 00 00
|................|
00000420 00 20 00 00 00 20 00 00 00 04 00 00 ec 47 26 4b
|. ... .......G&K|
00000430 6d 48 26 4b 01 00 17 00 53 ef 01 00 01 00 00 00 |
mH&K....S.......|
00000440 bf 47 26 4b 00 4e ed 00 00 00 00 00 01 00 00 00
|.G&K.N..........|
00000450 00 00 00 00 0b 00 00 00 80 00 00 00 3c 00 00 00
|............<...|
00000460 02 00 00 00 01 00 00 00 23 db 24 4e be 2e 40 22 |........#.
$N..@"|
00000470 86 a7 01 bd 8c ea ce be 00 00 00 00 00 00 00 00
|................|
00000480 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
*
000004b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
000004c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0f 00
|................|
000004d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
000004e0 08 00 00 00 00 00 00 00 00 00 00 00 2d 73 7d f1
|............-s}.|
000004f0 a6 41 ba 7b 03 4c 05 9d c8 65 54 31 01 01 00 00 |.A.
{.L...eT1....|
00000500 00 00 00 00 00 00 00 00 bf 47 26 4b a2 00 00 00
|.........G&K....|
00000510 a3 00 00 00 a4 00 00 00 a5 00 00 00 a6 00 00 00
|................|
00000520 a7 00 00 00 a8 00 00 00 a9 00 00 00 aa 00 00 00
|................|
00000530 ab 00 00 00 ac 00 00 00 ad 00 00 00 ae 00 00 00
|................|
00000540 af 01 00 00 00 00 00 00 00 00 00 00 00 00 10 00
|................|
00000550 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
00000560 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
00000570 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
*
000007f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
00000800 12 00 00 00 13 00 00 00 14 00 00 00 58 0b f4 03
|............X...|
00000810 02 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
00000820 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
*
00000ff0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
|................|
but in location 43[89] there is 53 ef (iirc the ext2 siganture you are
looking for?)
Many many tx for help,
J.
Jo
On Dec 17, 2:57 pm, Bean <bean12...@gmail.com> wrote:
Sorry but not yet:
grub rescue> ls -l (burgvg-tstlv)
4096 0
4096 0
4096 0
512 0
Device burgvg-tstlv: Filesystem cannot be accessed
> --
Jo
On Dec 17, 2:57 pm, Bean <bean12...@gmail.com> wrote:
Sorry but not yet:
grub rescue> ls -l (burgvg-tstlv)
4096 0
4096 0
4096 0
512 0
Device burgvg-tstlv: Filesystem cannot be accessed
> --
Bean
Hi,
It's really odd. The hello output is correct, it reads sector 0xb980
properly. However, ofdisk can't read from the same sector, perhaps the
disk handle is corrupted somewhere.
Bean
Jo
On Dec 17, 4:30 pm, Bean <bean12...@gmail.com> wrote:
> On Thu, Dec 17, 2009 at 11:11 PM, Jo <rubis...@scarlet.be> wrote:
>
[snip]
>
> Hi,
>
> It's really odd. The hello output is correct, it reads sector 0xb980
> properly. However, ofdisk can't read from the same sector, perhaps the
> disk handle is corrupted somewhere.
>
My 2 pence thought:
this issue is only for fs under lvm, fs directly build under disk
slices e.g.:
- under burg/grub fat fs (sdb1), grub kernel itself is well read
as well as its modules (without noticable issue)
- it can also well read initrd image from the linux ext2/3 boot fs
(sdb3)
doesn't shows this issue?
Tx again,
J.
Jo
On Dec 17, 4:59 pm, Bean <bean12...@gmail.com> wrote:
> Hi,
>
> Try:
>
> http://grub4dos.sourceforge.net/grub9.elf
>
Here is all what it verbosely shows:
mWelcome to GRUB!
^[[37m^[[40m../wrk/unx/burg/disk/ieee1275/ofdisk.c:82: disk name =
ibm,sp
../wrk/unx/burg/disk/ieee1275/ofdisk.c:82: disk name = disk2
../wrk/unx/burg/kern/disk.c:260: Opening `disk2'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:175: Opening `disk2:0'.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:185: Opened `disk2:0' as handle
0x1bd0b80
.
../wrk/unx/burg/kern/disk.c:404: Reading `disk2'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0x0
, size 0x8, buf 0x1
c17ec0.
../wrk/unx/burg/kern/disk.c:404: Reading `disk2'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2'...
../wrk/unx/burg/kern/disk.c:348: Closing `disk2'.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:228: Closing handle 0x1bd0b80.
../wrk/unx/burg/kern/disk.c:260: Opening `disk2'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:175: Opening `disk2:0'.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:185: Opened `disk2:0' as handle
0x18fad80
.
../wrk/unx/burg/kern/disk.c:404: Reading `disk2'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x18fad80:
sector 0x8
c000, size 0x8, buf
0x1c15e20.
../wrk/unx/burg/kern/disk.c:404: Reading `disk2'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x18fad80:
sector 0x6
67800, size 0x8, bu
f 0x1c13e00.
../wrk/unx/burg/kern/disk.c:404: Reading `disk2'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x18fad80:
sector 0xa
4f800, size 0x8, bu
f 0x1c11de0.
../wrk/unx/burg/kern/disk.c:348: Closing `disk2'.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:228: Closing handle 0x18fad80.
../wrk/unx/burg/kern/disk.c:260: Opening `disk2,7'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:175: Opening `disk2:0'.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:185: Opened `disk2:0' as handle
0x1bd0b80
.
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,7'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,7'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,7'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,7'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,7'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f820, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,7'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,7'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f828, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f830, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f838, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f840, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f848, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f850, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f858, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f860, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f868, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f870, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f878, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f880, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f888, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f890, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f898, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f8a0, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f8a8, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f8b0, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f8b8, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f8c0, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f8c8, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f8d0, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f8d8, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f8e0, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f8e8, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f8f0, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f8f8, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f900, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f908, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f910, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f918, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f920, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f928, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f930, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f938, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f940, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f948, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f950, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f958, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f960, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f968, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f970, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f978, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f980, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f988, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f990, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xa
4f998, size 0x8, bu
f 0x1c0fd90.
../wrk/unx/burg/kern/disk.c:260: Opening `disk2,7'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:175: Opening `disk2:0'.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:185: Opened `disk2:0' as handle
0x18fb680
.
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,7'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,7'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,7'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,7'...
../wrk/unx/burg/kern/disk.c:348: Closing `disk2,7'.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:228: Closing handle 0x1bd0b80.
../wrk/unx/burg/kern/disk.c:260: Opening `disk2,6'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:175: Opening `disk2:0'.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:185: Opened `disk2:0' as handle
0x1bd0b80
.
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,6'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,6'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,6'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,6'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0x6
67820, size 0x8, bu
f 0x37fde0.
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,6'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,6'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,6'...
../wrk/unx/burg/kern/disk.c:348: Closing `disk2,6'.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:228: Closing handle 0x1bd0b80.
../wrk/unx/burg/kern/disk.c:260: Opening `disk2,5'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:175: Opening `disk2:0'.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:185: Opened `disk2:0' as handle
0x1bd0b80
.
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,5'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,5'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,5'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0x8
c020, size 0x8, buf
0x37fde0.
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,5'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,5'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,5'...
../wrk/unx/burg/kern/disk.c:348: Closing `disk2,5'.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:228: Closing handle 0x1bd0b80.
../wrk/unx/burg/kern/disk.c:260: Opening `disk2,3'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:175: Opening `disk2:0'.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:185: Opened `disk2:0' as handle
0x1bd0b80
.
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,3'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,3'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xf
000, size 0x8, buf
0x37fde0.
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,3'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,3'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,3'...
../wrk/unx/burg/kern/disk.c:348: Closing `disk2,3'.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:228: Closing handle 0x1bd0b80.
../wrk/unx/burg/kern/disk.c:260: Opening `disk2,2'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:175: Opening `disk2:0'.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:185: Opened `disk2:0' as handle
0x1bd0b80
.
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,2'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,2'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
800, size 0x8, buf
0x37fde0.
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,2'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,2'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
808, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
810, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
818, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
820, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
828, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
830, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
838, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
840, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
848, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
850, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
858, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
860, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
868, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
870, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
878, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
880, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
888, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
890, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
898, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
8a0, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
8a8, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
8b0, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
8b8, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
8c0, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
8c8, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
8d0, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
8d8, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
8e0, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
8e8, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
8f0, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
8f8, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
900, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
908, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
910, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
918, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
920, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
928, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
930, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
938, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
940, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
948, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
950, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
958, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
960, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
968, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
970, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0xb
978, size 0x8, buf
0x31fdb0.
../wrk/unx/burg/kern/disk.c:260: Opening `disk2,2'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:175: Opening `disk2:0'.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:185: Opened `disk2:0' as handle
0x18fb600
.
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,2'...
../wrk/unx/burg/kern/disk.c:348: Closing `disk2,2'.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:228: Closing handle 0x1bd0b80.
../wrk/unx/burg/kern/disk.c:260: Opening `disk2,1'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:175: Opening `disk2:0'.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:185: Opened `disk2:0' as handle
0x1bd0b80
.
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,1'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,1'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x1bd0b80:
sector 0x2
0, size 0x8, buf 0x
37fde0.
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,1'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,1'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,1'...
../wrk/unx/burg/kern/disk.c:348: Closing `disk2,1'.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:228: Closing handle 0x1bd0b80.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:82: disk name = network
../wrk/unx/burg/disk/ieee1275/ofdisk.c:82: disk name = net
../wrk/unx/burg/disk/ieee1275/ofdisk.c:82: disk name = network1
../wrk/unx/burg/disk/ieee1275/ofdisk.c:82: disk name = scsi
../wrk/unx/burg/disk/ieee1275/ofdisk.c:82: disk name = nvram
../wrk/unx/burg/disk/ieee1275/ofdisk.c:82: disk name = rtc
../wrk/unx/burg/disk/ieee1275/ofdisk.c:82: disk name = screen
../wrk/unx/burg/kern/disk.c:260: Opening `disk2,1'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:175: Opening `disk2:0'.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:185: Opened `disk2:0' as handle
0x1bd0b80
.
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,1'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,1'...
../wrk/unx/burg/kern/disk.c:348: Closing `disk2,1'.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:228: Closing handle 0x1bd0b80.
error: unknown filesystem
Entering rescue mode...
grub rescue> ls -l (burgvg-tstlv)
../wrk/unx/burg/kern/disk.c:260: Opening `burgvg-tstlv'...
../wrk/unx/burg/kern/disk.c:404: Reading `burgvg-tstlv'...
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,2'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x18fb600:
sector 0xb980, size 0x8, buf
0x1c0e3d0.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x18fb600:
sector 0xb980, size 0x8, buf
0x1c0e3d0.
../wrk/unx/burg/kern/disk.c:472: disk2,2 read failed
../wrk/unx/burg/kern/disk.c:404: Reading `disk2,2'...
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x18fb600:
sector 0xb980, size 0x8, buf
0x1c11c50.
../wrk/unx/burg/disk/ieee1275/ofdisk.c:241: Reading handle 0x18fb600:
sector 0xb982, size 0x1, buf
0x1c11c50.
../wrk/unx/burg/kern/disk.c:472: disk2,2 read failed
../wrk/unx/burg/kern/disk.c:472: burgvg-tstlv read failed
Device burgvg-tstlv: ../wrk/unx/burg/kern/disk.c:260: Opening `burgvg-
tstlv'...
../wrk/unx/burg/kern/disk.c:335: Opening `burgvg-tstlv' failed.
../wrk/unx/burg/kern/disk.c:348: Closing `burgvg-tstlv'.
Filesystem cannot be accessed
../wrk/unx/burg/kern/disk.c:348: Closing `burgvg-tstlv'.
error: Read error on block: 47490
More thought: could it be that because of additional lvm layer the
disk was seek for reading lvm structure but not repositioned at to the
starting position to read the underlying fs info?
(Last test for today, sorry?)
Tx again,
J.
Bean
rubisher
grub rescue> ls -l (burgvg-tstlv)
Device burgvg-tstlv: Filesystem type ext2, Last modification time 2009-12-14 14:15:09 Monday, UUID
23db244e-be2e-4022-86a7-01bd8ceacebe
Obviously, I was curious for the other disk (namely disk1) so I reinstall the related nvalias and it works fine too:
grub rescue> ls -l
Device burgvg-tstlv: Filesystem type ext2, Last modification time 2009-12-14 14:15:09 Monday, UUID
23db244e-be2e-4022-86a7-01bd8ceacebe
Device p5tst001vg-Sources: Filesystem type ext2, Last modification time 2009-12-19 13:08:24 Saturda
y, UUID 161e55f6-7498-45dd-91fe-35ebbb09bac3
Device p5tst001vg-UsrSrc: Filesystem type ext2, Last modification time 2009-12-19 13:08:25 Saturday
, UUID 3257bc77-e2cb-4359-b283-6bc2d9a37fa3
Device p5tst001vg-home: Filesystem type ext2, Last modification time 2009-12-19 13:08:25 Saturday,
UUID 3b2aa16a-a834-4b54-a102-d0e694b13c94
Device p5tst001vg-tmp: Filesystem type ext2, Last modification time 2009-12-19 13:08:25 Saturday, U
UID 88894569-318c-4be8-91b8-fd8d821e8873
Device p5tst001vg-var: Filesystem type ext2, Last modification time 2009-12-19 13:08:25 Saturday, U
UID c2553cae-c81f-40dd-97fb-aeffcfd9ccb9
Device system-swap: Unknown filesystem
Device system-root: Filesystem type ext2, Last modification time 2009-12-18 06:56:41 Friday, UUID 4
0ed7be1-44a9-493c-866e-ea835eb94524
Device system-home: Filesystem type ext2, Last modification time 2009-12-18 06:56:41 Friday, UUID b
6ab41ec-cd1d-4a6f-aac9-043f511df9c6
Device disk1: Partition table
Partition disk1,2: Unknown filesystem
Partition disk1,1: Unknown filesystem
Device disk2: Partition table
Partition disk2,7: Unknown filesystem
Partition disk2,6: Filesystem type ext2, Last modification time 2009-12-19 13:08:25 Saturda
y, UUID 3c51c43e-63a7-4ff1-9b1c-cf98addcb7ed
Partition disk2,5: Unknown filesystem
Partition disk2,3: Filesystem type ext2, Last modification time 2009-12-19 13:08:25 Saturda
y, UUID 16ef0754-c845-46e9-a948-b9669ee68329
Partition disk2,2: Unknown filesystem
Partition disk2,1: Unknown filesystem
I curious to read your patch now :<)
Thanks a lot for your support,
J.
Bean
Hi,
There is a post on grub-devel yesterday about sparc's openboot doesn't
support opening same disk twice. Although I can't reproduce it with my
Sun Ultra, I realize that this could be the source of your problem as
lvm needs to keep the underlying disk handle open, so there will be
multiple open request. The latest r1795 contains the fix.
Thanks a lot for your patient testing, :)
Jo
It's may the ultimate test I can do on this system but I just tested
r1797 then r1795 build OOTB but all of them failed to even find lvm?
(Nothing change in my enviroment since last test of r1787 this Dec 14
and I do not add any modules in grub fs)
grub> ls
(disk1) (disk1,2) (disk1,1) (disk2) (disk2,7) (disk2,6) (disk2,5)
(disk2,3) (disk2,2) (disk2,1)
grub> lsmod
Name Ref Count Dependencies
linux 1 elf,boot
elf 2 gzio
gzio 3
ls 1 lib,extcmd
fat 1
ext2 1 fshelp
fshelp 2
part_msdos 1
halt 1
reboot 1
nmenu 1 lib,boot
boot 3
normal 2 lib
sh 1 lib
lib 6
minicmd 1
search 1 extcmd
extcmd 3
lvm 1
kernel 1
grub> ls -l
Device disk1: Partition table
Partition disk1,2: Unknown filesystem
Partition disk1,1: Filesystem type fat, Label 'root', UUID
4ad5-c9f7
Device disk2: Partition table
Partition disk2,7: Unknown filesystem
Partition disk2,6: Filesystem type ext2, Last modification
time 2009-12-22 14:34:28 Tuesday
, UUID 3c51c43e-63a7-4ff1-9b1c-cf98addcb7ed
Partition disk2,5: Unknown filesystem
Partition disk2,3: Filesystem type ext2, Last modification
time 2009-12-22 14:34:28 Tuesday
, UUID 16ef0754-c845-46e9-a948-b9669ee68329
Partition disk2,2: Unknown filesystem
Partition disk2,1: Filesystem type fat, Label grub2, UUID
4adc-336e
Unfortunately, I do not have more time to investigate for the moment
(may be next year, sorry, I couldn't yet be more accurate)
Thanks again for your kind help,
J.
Bean
Jo
First of all best wishes (mainly good health).
On Jan 3, 3:58 pm, Bean <bean12...@gmail.com> wrote:
And thanks, it works:
grub> ls -l
Device burgvg-tstlv: Filesystem type ext2, Last modification time
2009-12-14 14:15:09 Monday, UUID
23db244e-be2e-4022-86a7-01bd8ceacebe
Device p5tst001vg-Sources: Filesystem type ext2, Last modification
time 2010-01-04 07:51:30 Monday,
UUID 161e55f6-7498-45dd-91fe-35ebbb09bac3
Device p5tst001vg-UsrSrc: Filesystem type ext2, Last modification time
2010-01-04 07:51:30 Monday,
UUID 3257bc77-e2cb-4359-b283-6bc2d9a37fa3
Device p5tst001vg-home: Filesystem type ext2, Last modification time
2010-01-04 07:51:30 Monday, UU
ID 3b2aa16a-a834-4b54-a102-d0e694b13c94
Device p5tst001vg-tmp: Filesystem type ext2, Last modification time
2010-01-04 07:51:30 Monday, UUI
D 88894569-318c-4be8-91b8-fd8d821e8873
Device p5tst001vg-var: Filesystem type ext2, Last modification time
2010-01-04 07:51:30 Monday, UUI
D c2553cae-c81f-40dd-97fb-aeffcfd9ccb9
Device system-swap: Unknown filesystem
Device system-root: Filesystem type ext2, Last modification time
2009-12-22 12:36:23 Tuesday, UUID
40ed7be1-44a9-493c-866e-ea835eb94524
Device system-home: Filesystem type ext2, Last modification time
2009-12-22 12:36:16 Tuesday, UUID
b6ab41ec-cd1d-4a6f-aac9-043f511df9c6
Device disk1: Partition table
Partition disk1,2: Unknown filesystem
Partition disk1,1: Unknown filesystem
Device disk2: Partition table
Partition disk2,7: Unknown filesystem
Partition disk2,6: Filesystem type ext2, Last modification
time 2010-01-04 07:51:30 Monday,
UUID 3c51c43e-63a7-4ff1-9b1c-cf98addcb7ed
Partition disk2,5: Unknown filesystem
Partition disk2,3: Filesystem type ext2, Last modification
time 2010-01-04 07:51:30 Monday,
UUID 16ef0754-c845-46e9-a948-b9669ee68329
Partition disk2,2: Unknown filesystem
Partition disk2,1: Unknown filesystem
Tia for additional advise,
J.
Bean
Hi,
Welcome back ! The binary is compiled using latest r1797. BTW, the API
interface have underwent some changed, so you should replace all mod
files.
--
Bean
Jo
On Jan 4, 9:33 am, Bean <bean12...@gmail.com> wrote:
> On Mon, Jan 4, 2010 at 4:15 PM, Jo <rubis...@scarlet.be> wrote:
> > Hello,
[snip]
>
> Hi,
>
> Welcome back ! The binary is compiled using latest r1797. BTW, the API
> interface have underwent some changed, so you should replace all mod
> files.
>
Well there isn't any modules at all in the grub fs.
As there is some new release of debian gcc-4.4, I install it and
rebuild burg r1797 and rebuild the image with:
# cd /opt/grub2/burg1797/lib/grub/powerpc-ieee1275/
the place where I install burg
# ../../../bin/grub-mkelfimage -nv --directory=. --output=/boot/grub/
grub2ofs.t lvm search minicmd sh normal nmenu reboot halt part_msdos
ext2 fat ls linux
Same wrong behaviour???
Reading again previous mails, I figure out that you mentioned modules
in different order and so I try following cmdl:
# ../../../bin/grub-mkelfimage -nv --directory=. --output=/boot/grub/
grub2ofs.t2 minicmd sh normal nmenu reboot halt part_msdos ext2 fat ls
linux lvm search
And this image works fine as your build.
Weird isn't it?
Thanks again for all,
J.
> --
> Bean
Bean
> Well there isn't any modules at all in the grub fs.
> As there is some new release of debian gcc-4.4, I install it and
> rebuild burg r1797 and rebuild the image with:
> # cd /opt/grub2/burg1797/lib/grub/powerpc-ieee1275/
> the place where I install burg
> # ../../../bin/grub-mkelfimage -nv --directory=. --output=/boot/grub/
> grub2ofs.t lvm search minicmd sh normal nmenu reboot halt part_msdos
> ext2 fat ls linux
>
> Same wrong behaviour???
> Reading again previous mails, I figure out that you mentioned modules
> in different order and so I try following cmdl:
Hi,
part_msdos must be loaded before lvm, as lvm scans disks at its
startup function, if part_msdos is not loaded, devices such as
(disk1,2) is not available.
--
Bean
rubisher
of modules list to build this image, though?
Thanks again,
J.
Bean
> Ok but as far as I was building some kind of static kernel image I am a bit
> troubled by this request to respect some order of modules list to build this
> image, though?
Hi,
The general rule for module order is:
Disk access module should be first, for example:
biosdisk
Partition map follows, for example:
part_msdos, part_gpt, ..
Then lvm and raid, the correct order is:
raid raid5rec raid6rec mdraid lvm
This supports lvm on raid
The order of other modules doesn't matter.
--
Bean
Jo
On Jan 6, 7:44 am, Bean <bean12...@gmail.com> wrote:
Thanks fro this clear msg.
Well some delay because I have now some issue with cursor (latest test
was burg bzr 1805) and couldn't any more use arrow keys to select
different menu entry?
But by accident [Ctrl]+e just jump to the alternate Opensuse which now
boot just fine ;<)
Thanks again for your great job,
J.
> --
> Bean