BUG REPORT.
HARD: M/b ASRock M266A
HDDs (2 units): (hd0) 3 partitions Quantum + (hd1) 2 partitions Samsung
(hd0,0) - grub partition with PLOP bootmanager.
BOOT FLASHS (3 units, different) with grub
Plug USBFlash DRIVE and run SETUP BIOS.
AMI BIOS boot devices: (hd0), (hd1), flash
Test booting: (hd0) - OK, flash - doesn't work.
Well. Boot fom (hd0,0), go to grub consol, enter command
find
(hd0,0)
(hd0,1)
(hd0,2)
(hd1,0)
(hd1,1)
(fd0)
It's OK:
(hd0) 3 partitions Quantum + (hd1) 2 partitions Samsung+(fd0) flash
NEXT STEP - PLOP booting.
Command:
kernel (hd0,0)/PLOP/plpbt.bin
boot
SYSTEM REBOOT and BOOT from Flash.
- It's OK?
- NO!
-Why?
-Well, let's test list of devices.
go to grub consol, enter command
find
(hd0,0)
(hd0,1)
(hd0,2)
(hd1,0)
(hd1,1)
(hd1,2)
(fd0)
-Ups!? Let's control partitions.
ls (hd0,0) \ - it is flash (ОК)
ls (hd0,1) \ - error (is it fantom of Quantum?)
ls (hd0,2) \ - error (is it fantom of Quantum?)
ls (hd1,0) \ - it is Quantum (OK)
ls (hd1,1) \ - it is Quantum (OK)
ls (hd1,2)\ - it is Quantum (OK)
WHERE IS SAMSUNG?
This experiment has been repeat with 3 flash drive and 2 different PC.
Second PC: m/b ASUS P5KPL-CM with 3 hard disks.
BUG: After PLOP booting one of harddrives IS LOST?
???
Resolved?
map (hd1) (hd2)
map (hd2) (hd1)
map --hook
map --unhook
find
(hd0,0)
(hd0,1)
(hd0,2)
(hd1,0)
(hd1,1)
(hd1,2)
(hd2,0)
(hd2,1)
May be grub's bug?
What about "fantom"?