--- Begin Message ---
Package: installation-reports
For Debian-GNU/Linux-squeeze-di-RC1-i386 .
I do not know which piece of software/package is responsible for
picking the GNU/Linux Pata_hpt37X driver,
for the Highpoint hpt370 raid controller chip. See the link below;
https://ata.wiki.kernel.org/index.php/Pata_hpt37x 'HighPoint 370
series PCI ATA Controllers'.
# lsmod shows Module hpt366 size 8535 used by 6. is installed, not
Pata_hpt37x
Boot method: DVD graphical installer setting up for booting,
using an array called /dev/md0 built from two hard drive disks,
configured for raid1 mirroring mode.
Image version: URL to dvd image downloaded,
Official snapshot i386 dvd binary1 20110108-16:28.
Only the first DVD 1 of the set is required.
Began installing Date: 08 December 2010.
Machine: Motherboard: A bit KT7, Raid, 1 Ghz.
Processor: AMD AThlon K7, 850 Mhz, Socket 'A'
Memory: SDRAM 2 x 512Mb = 1Gb.
Chipset: Via KT 133 ATX, USB 1.0 compliant, UDMA 100, Socket 'A',
FSB 200Mhz, AGP 4X.
Updated bios: Award Modular Bios v6.00 PG.
07/11/2002-8363-6A6A-6A6LMA19C-A9 The Latest level.
CMOS Set Up Utility: Advanced BIOS features:
First boot device: CDROM,
Second boot device: ATA100RAID,
Third boot device: ATA100RAID, (why not just try the same disk again)
Boot other device: disabled.
Delay for IDE Initial (Secs) 8.
Intergrated Peripherals:
ATA100RAID IDE Controller: Enabled.
Two additional IDE channels provide the capability of adding high
performance device(s) to system.
IDE HDD Block Mode: Enabled.
for automatic detection of the optimal number of block read/writes
per sector the drive can support.
****
DASD chip: On-motherboard HPT370 raid controller 2001
www.highpoint-tech.com (hardware raid)
Is not used by me for 'hardware raid '. The intention is to use the
HPT370 for Debian GNU/Linux MDADM Software raid1 mode (mirroring)
using Debian-GNU/Linux-Squeeze-di-RC1-i386 .
****
Onboard Hipoint HPT370 UDMA/ATA100 RAID controller BIOS v01.11.0402
HPT370 BIOS Setting Utility screen button F1 toggles the view ARRAY
STATUS shows no array or devices. Good! I am not using any raid
function for this boot, just using it as an additional, fast, IDE
controller.
Screen button F1 toggles the view CHANNEL STATUS which shows the devices:
DASD: Quantity two: IBM-DTLA-307030 drives, primary master and
secondary master,
Mode UDMA5 size 30Gb each, as HDD0 and HDD1 both attached to the
HPT370 controller. Good!
HPT370 Bios Setting Utility option 7. Set Boot Disk: I have set no
disk as Boot Disk here, I will check later.
I believe the 'Linux Software Raid Array' is the place to specify
/dev/md2 my /boot partition as bootable in partition manager,
which I have set.
IDE Primary master: none.
IDE Primary slave: Pioneer DVD-ROM ATAP.
IDE Secondary master: LITE-ON LTR-16102B DVD rewriter.
IDE Secondary slave: none.
Partitions: df -Tl
df: invalid option --'T'
BusyBox v1.17.1 (Debian 1:1.17.1-4) multi call binary.
usage: df [-Pkmh] [FILESYSTEM]...
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 505.4M 92.0k 505.3m 0% /dev
/dev/md1 26.6G 473.6m 24.8g 2% /target
/dev/md2 92.0M 17.5M 69.7M 20% /target/boot
/dev/md1 26.6G 473.6M 24.8G 2%
/dev/.static/dev
tmpfs 505.4M 92.0K 505.3M 0% /target/dev
Base System Installation Checklist:
[O] = OK. [E] = Error
Initial boot: [O]
Detect network card: [O]
Configure network: [N/A]
Detect CD: [O]
Load installer modules:[O]
Detect hard drives: [O]
Partition hard drives: [O]
Install base system: [O]
Configure Package Manager: Scanning DVD set disk, Binary-1
only ? (yes)
Clock/timezone setup:[O]
User/password setup: [O]
Install tasks: [O]
Install boot loader: [O]
Overall install: [E] Won't auto boot into new installed system.
Comments/Problems:
Debian-squeeze-di-RC1-i386 maybe installing the wrong driver hpt366 ?
for Highpoint hpt370 raid controller.
I do not know which piece of software is responsible to select the
GNU/Linux Pata_hpt37x driver ?
https://ata.wiki.kernel.org/index.php/Pata_hpt37x 'HighPoint 370
series PCI ATA Controllers'.
The same symptoms since installing Beta1, Beta2 and now
Debian-squeeze-di-RC1-i386 Release Candidate 1.
(jump to my summary “Finally...” at the end of this entry below and
return here.)
I have yet to acheive taking off the machine, my saved debug logs for
bug reporting.
I am unsuccesfully trying to mount and will then save to a usb
thumbdrive in abscence of a floppy drive.
Be aware, these are hand typed excerpts reports only :-
I use the 'Graphical Installer' from a down loaded iso image Binary1,
cut and verified to a single DVD.
After a succesfull install, but unsucessful re booting symptom, I
restart the install again.
Before changing anything in the second install, I reach again;
The first 'Partition Disks' sub menu screen, I
[Go Back] to di-mm 'Debian Installer-Main Menu', I select
'Execute a shell' and start my analysis:-
# lsmod shows Module hpt366 size 8535 used by 6. is installed, not
Pata_hpt37x
# lsmod (These are excerpts. Not all modules have been typed up
and shown here.)
hpt366, ide_generic, ata_generic, ide_gd_mod, pata_via,
libata, ehci_hcd, scsi_mod, nls_base, ise_core, raid1,
dm_mod, pata_vie, ext3, pata_via, ide_generic
*** There is no sign of module Pata_hpt37x, for the ( hp370, hpt370,
hpt 370, hpt-370 ) ***
Is this as it should be ? Or is this the cause of ONE of my fault
symptoms ? I do not know.
Which piece of software is responsible for picking the GNU/Linux
driver hpt366 ?
# lspci -knn
00:13.0 Mass storage controller: HighPoint Technologies, Inc,
HPT366/368/370/370A/372/372N (rev03) 66Mhz Device 0001 [1103:0004]
00:07.4 Bridge: Via Technologies, Inc,
VT82c686 [Apollo Super ACPI] (rev30)
Flags: medium devsel, IRQ 9. 66Mhz Device [1103:0001]
# free mem Total 1,035,092, used 119,916,
free 915,176 shared 0, buffers 456, swap 0.
# lspci -v
00:01.0 PCI Bridge Via Technologies
00:07.1 IDE Interface Via Technologies VT82C586A/B/VT82C68/VT823X
Kernel driver in use: pata_via
# cat /tmp/mdadm.conf ( They are my ...'s )
ARRAY /dev/md/2 metadata 1.2 UUID=5656... name=(none) :2
ARRAY /dev/md/0 metadata 1.2 UUID=11f0... name=(none) :0
ARRAY /dev/md/1 metadata 1.2 UUID=456B... name=(none) :1
Look at the UUID's ends below, they are different.
# ls /target/boot/grub/mdraid.mod
# ls /target/boot/grub/device.map
cat (hd0) /dev/disk/by-id/ata-IBM-DTLA-307030_...6
cat (hd1) /dev/disk/by-id/ata-IBM-DTLA-307030_...5
# ls /grubenv
/grub.cfg (Only part of.)
###BEGIN /etc/grub.d/05_debian_theme###
insmod raid
insmod mdraid
insmod part_msdos ?
insmod part_msdos ?
ext2 ?
set root ='(md/1)'
search --nofloppy --fs -uuid --set 37060... 35d
linux /boot/vmlinux -2.6.32-5-686
root=UUID=37060e...35d ro quiet
---
An observation only,I noticed in bug#593013(Not my situation).
The Installer hardware-summary listing has an extra line
(not mine) # lspci -knn: kernel modules: hpt 366
This is not in my lspci -knn , but that was in 2009
linux 2.6.26-2-686 Debian: 5.0.5. stable i386,
Installer build 20090123 Lenny6
Kernel driver in use: HPT366_IDE interrupt: pin A routed to IRQ 11.
Be aware, this paragraph is somebody else's situation, not my situation.
---
Back to my Debian-squeeze-di-RC1-i386 Release Candidate 1.
cat /proc/ide/ide3/hdg/model IBM-DTAL-307030
cat /proc/ide/ide2/hdg/model IBM-DTAL-307030
cat /proc/disk stats
(briefy has): hde ,1,2,3,5 etc...
hdg, sr0, sr1, 2 md2, 0 md0, 1 md1.
---
I first initially noticed the symptom when installing:-
Debian GNU/Linux squeeze-di-beta1_Squeeze_
-Official Beta i386 DVD Binary-1 20101027-01:46
Thats di-Beta-1, whose abreviated log output is as follows.
Output of lspci -nn
00:00.0 Host Bridge [0600] Via Technologies ... (rev 02)
00:01.0 PCI Bridge [0604] " " ... AGP
07.0 ISA bridge... " " Appollo Super South ... (rev 22)
07.1 IDE ... PIPC Bus Master IDE ... (rev 10)
07.2 USB Controller [0c03]: Via Technologies
VT82xxxxx UHCI USB1.1 Controller ... (rev 10)
07.3 " " " " " " USB1.1
Controller ... (rev 10)
07.4 Bridge " " VT82c686 [Appollo
Super ACPI] ... (rev 30)
11.0 Ethernet controller ...
00:13.0 Mass storage controller [0180]: HighPoint Technologies, Inc.
HPT ... /370/ ... [1103:00041] (rev 03)
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc
3D Rage Pro AGP 1X/2X [1002:47421] (rev 5c)
---
/var/log/syslog excerpt 2010 :-
Dec 8 11:39:18 kernel: [ 486.432151] md: md2 stopped.
Dec 8 11:39:18 kernel: [ 486... ] bind<hdg1>
Dec 8 11:39:18 kernel: [ 486... ] bind<hde1>
Dec 8 11:39:18 kernel: [ 486... ] raid1 personality registered for level 1
Dec 8 11:39:18 kernel: [ 486... ] raid1: raid set md2 active with 2
out of 2 mirrors
Dec 8 11:39:18 kernel: [ 486... ] md2: detected capacity change
from 0 to 99602432
Dec 8 11:39:18 md-devices: mdadm: /dev/md/2 has been started with 2 drives.
Dec 8 11:39:18 kernel: [ 486... ] md2:
Dec 8 11:39:18 kernel: unknown partition table
(I now know this last line is a normal working situation.)
...
Dec 8 11:39:18 kernel: [ 486.432151] md: md0 stopped.
Dec 8 11:39:18 kernel: [ 486... ] bind<hdg2>
Dec 8 11:39:18 kernel: [ 486... ] bind<hde2>
Dec 8 11:39:18 kernel: [ 486... ] raid1 personality registered for level 1
Dec 8 11:39:18 kernel: [ 486... ] raid1: raid set md0 active with 2
out of 2 mirrors
Dec 8 11:39:18 kernel: [ 486... ] md0: detected capacity change
from 0 to 99602432
Dec 8 11:39:18 md-devices: mdadm: /dev/md/0 has been started with 2 drives.
Dec 8 11:39:18 kernel: [ 486... ] md0:
Dec 8 11:39:18 kernel: unknown partition table
...
Dec 8 11:39:18 kernel: [ 486.432151] md: md1 stopped.
Dec 8 11:39:18 kernel: [ 486... ] bind<hdg5>
Dec 8 11:39:18 kernel: [ 486... ] bind<hde5>
Dec 8 11:39:18 kernel: [ 486... ] raid1 personality registered for level 1
Dec 8 11:39:18 kernel: [ 486... ] raid1: raid set md1 active with 2
out of 2 mirrors
Dec 8 11:39:18 kernel: [ 486... ] md1: detected capacity change
from 0 to 99602432
Dec 8 11:39:18 md-devices: mdadm: /dev/md/1 has been started with 2 drives.
Dec 8 11:39:18 kernel: [ 487... ] md1:
Dec 8 11:39:18 kernel: unknown partition table
...
Dec 8 11:39:19 kernel: [ 487... ] device-mapper: uevent version 1.0.3
Dec 8 11:39:19 kernel: [ 487... ] device-mapper: ioctl:
4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
Dec 8 11:39:19 kernel: partman: No physical volumes found
Dec 8 11:39:19 kernel: partman: Reading all physical volumes. This
may take a while...
Dec 8 11:39:19 kernel: partman-lvm: No volume groups found
Dec 8 11:50:17 kernel: [ 1145... ] Adding 1560556k swap on /dev/md0.
Priority:-1 across:1560556k
...
Dec 8 11:50:56 kernel: [ 1184... ] kjournald starting. Commit
interval 5 seconds
Dec 8 11:50:56 kernel: [ 1184... ] EXT3 FS on md1, internal journal
Dec 8 11:50:56 kernel: [ 1184... ] EXT3-fs: mounted file system with
ordered data mode.
...
Dec 8 11:50:56 kernel: [ 1184... ] kjournald starting. Commit
interval 5 seconds
Dec 8 11:50:56 kernel: [ 1184... ] EXT3 FS on md2, internal journal
Dec 8 11:50:56 kernel: [ 1184... ] EXT3-fs: mounted file system with
ordered data mode.
...
Dec 8 11:51:59 debootstrap: dpkg: regarding
.../base-files_5.9_i386.deb containing
base-files, pre-dependancy problem:
Dec 8 11:51:59 debootstrap: base-files pre-depends om awk
Dec 8 11:51:59 debootstrap: awk is not installed.
Dec 8 11:51:59 debootstrap: dpkg: warning: ignoring pre-dependancy problem!
Dec 8 11:51:59 debootstrap: Unpacking base-files (from
.../base-files_5.9_i386.deb) ...
...
Dec 8 11:52:01 debootstrap: Selecting previously deselected package
base-passwd.
Dec 8 11:52:01 debootstrap: Unpacking base-passwd (from
.../base-passwd_3.5.22_i386.deb) ...
Dec 8 11:52:01 debootstrap: dpkg: base-passwd: dependancy problems.
but configuring anyway as you requested:
Dec 8 11:52:01 debootstrap: base-passwd depends on libc6 (>= 2.1); however:
Dec 8 11:52:01 debootstrap: Package libc6 is not installed.
Dec 8 11:52:01 debootstrap: Setting up base-passwd (3.5.22) ...
...
Dec 8 12:49:59 os-prober: No volume groups found
Dec 8 12:49:59 os-prober:
Dec 8 12:49:59 os-prober: debug:
running /user/lib/os-probes/50mounted-tests
on /dev/hde1
/hde2
/hde3
Dec 8 12:49:59 50mounted-tests: debug: /dev/hde3 type not recognised; skipping
(Note:This should be my /boot raid /md2 )
Dec 8 12:49:59 os-prober: debug: os detected by
/usr/lib/os-probes/50mounted-tests
Dec 8 12:49:59 os-prober: debug: running
/user/lib/os-probes/50mounted-tests on /dev/hdg5
Dec 8 12:49:59 os-prober: debug: running
/user/lib/os-probes/50mounted-tests on /dev/hdg1
Dec 8 12:49:59 os-prober: debug: running
/user/lib/os-probes/50mounted-tests on /dev/hdg2
Dec 8 12:49:59 os-prober: debug: running
/user/lib/os-probes/50mounted-tests on /dev/hdg3
Dec 8 12:49:59 50mounted-tests: debug: /dev/hdg3 type not recognised; skipping
Dec 8 12:49:59 os-prober: debug: os detected by
/usr/lib/os-probes/50mounted-tests
Dec 8 12:49:59 os-prober: debug: running
/user/lib/os-probes/50mounted-tests on /dev/hdg5
Dec 8 12:55:21 grub-installer: info: Installing grub on '/dev/hde'
(Note: This should be my raid set md master boot record)
Dec 8 12:55:21 grub-installer: info: grub-install supports --no-floppy
Dec 8 12:55:21 grub-installer: info: Running chroot /target
grub-install --no-floppy --force "/dev/hde"
Dec 8 12:55:24 grub-installer: Installation finished. No error reported.
Dec 8 12:55:24 grub-installer: info: grub-install ran succesfully
...
Finally, This report is just for my perceived driver issue.
Since di-RC1, I believe there is a resolved bug#606035 whose patch/fix
has more recently
been applied to grub-pc grub2/1.99-20110106-1 but I do not believe
made it in time to be within RC1.
I believe this bug#606035 'grub-install /dev/mdo fails (raid-1)' fix
is very relevant to my 'Unable to boot from raid1' symptom situation.
Hopefully the 'Programme Temporary Fix' will be availabe in di-RC2, if
there is to be a di-RC2.
My reporting above therefore reflect the symptoms of bug#606035 as
well, but not to be addresed here in this installation report by me.
This report is just for my perceived driver issue.
I do not believe the bug#606035 PTF (Programme Temporary Fix) will
choose the correct driver for me.
Which may be driver GNU/Linux Pata_hpt37x as mentioned at the
linkbelow, instead of driver hp366 installed.
https://ata.wiki.kernel.org/index.php/Pata_hpt37x 'HighPoint 370
series PCI ATA Controllers'.
If we are still waiting for Pata_hpt37x maybe, which driver should
the software be choosing to install ?
I think my bug report MAY be valid. If not, I appologise in advance if
I am wasting people's time.
Currently, I do not have the needed experience to take this further
AND achieve the Debian imminent release timescales.
Thank you for any help forthcoming to get my raid-1 booting and thanks
to all for all the Great software. Regards, McTech.
--- End Message ---