Christian PERRIER a écrit :
Quoting Jean-Christian de Rivaz (j...@eclis.ch):
Unfortunately there is no /var/log/installer/ directory:
That dir exists on the installed system. As you couuldn't install, it
is indeed not there
ls -al /var/log
drwxr-xr-x 2 root root 0 Nov 5 22:33 .
drwxr-xr-x 8 root root 0 Nov 5 22:23 ..
-rw-r--r-- 1 root root 17172 Nov 5 22:33 hardware-summary
lrwxrwxrwx 1 root root 44 Nov 5 22:33
install-report.template ->
/usr/share/save-logs/install-report.template
lrwxrwxrwx 1 root root 16 Nov 5 22:33 lsb-release
-> /etc/lsb-release
-rw-r--r-- 1 root root 993 Nov 5 22:23 partman
lrwxrwxrwx 1 root root 20 Nov 5 22:33 status ->
/var/lib/dpkg/status
-rw-r--r-- 1 root root 71813 Nov 5 22:33 syslog
/var/log/partman is what Miguel wanted to mention.
Thanks for the clarification, here is the /var/log/partman:
/bin/partman: *******************************************************
/lib/partman/init.d/25md-devices:
*******************************************************
/lib/partman/init.d/30parted:
*******************************************************
parted_server: ======= Starting the server
parted_server: main_loop: iteration 1
parted_server: Opening infifo
/lib/partman/init.d/30parted: IN: OPEN =dev=sda /dev/sda
parted_server: Read command: OPEN
parted_server: command_open()
parted_server: Request to open =dev=sda
parted_server: Opening outfifo
parted_server: OUT: OK
parted_server: OUT: OK
parted_server: Note =dev=sda as unchanged
parted_server: Closing infifo and outfifo
parted_server: main_loop: iteration 2
parted_server: Opening infifo
/lib/partman/init.d/30parted: IN: OPEN =dev=sdb /dev/sdb
parted_server: Read command: OPEN
parted_server: command_open()
parted_server: Request to open =dev=sdb
parted_server: Opening outfifo
parted_server: OUT: OK
parted_server: OUT: OK
I suspect that something like "Closing infifo and outfifo" for /dev/sdb
is missing. On the screen I have at this moment a progress bar "Starting
up the partitioner" fixed at 50% and a statement "Scanning disks..." on
the lower left. If I understand correctly, those /var/log/partman traces
are related to this code from /lib/partman/init.d/30parted that seem to
talk to a parted_server process:
cd $dev
open_dialog OPEN "$(cat $dev/device)"
read_line response
close_dialog
if [ "$response" = failed ]; then
cd /
rm -rf $dev
fi
Maybe parted_server is not responding to /lib/partman/init.d/30parted. A
'ps' give this processes list:
PID USER VSZ STAT COMMAND
1 root 1360 S /bin/busybox init
2 root 0 SW [kthreadd]
3 root 0 SW [ksoftirqd/0]
4 root 0 SW [watchdog/0]
5 root 0 SW [events/0]
6 root 0 SW [cpuset]
7 root 0 SW [khelper]
8 root 0 SW [netns]
9 root 0 SW [async/mgr]
10 root 0 SW [pm]
11 root 0 SW [sync_supers]
12 root 0 SW [bdi-default]
13 root 0 SW [kintegrityd/0]
14 root 0 SW [kblockd/0]
15 root 0 SW [kacpid]
16 root 0 SW [kacpi_notify]
17 root 0 SW [kacpi_hotplug]
18 root 0 SW [kseriod]
19 root 0 SW [kondemand/0]
20 root 0 SW [khungtaskd]
21 root 0 SW [kswapd0]
22 root 0 SWN [ksmd]
23 root 0 SW [aio/0]
24 root 0 SW [crypto/0]
44 root 1356 S < udevd --daemon --resolve-names=never
202 root 0 SW [ksuspend_usbd]
203 root 0 SW [khubd]
204 root 0 SW [ata/0]
205 root 0 SW [ata_aux]
207 root 0 SW [scsi_eh_0]
208 root 0 SW [scsi_eh_1]
209 root 0 SW [scsi_eh_2]
210 root 0 SW [scsi_eh_3]
222 root 0 SW [scsi_eh_4]
223 root 0 SW [usb-storage]
257 root 1360 S /sbin/syslogd -m 0 -O /var/log/syslog -S
259 root 1360 S /sbin/klogd -c 2
321 root 1364 S /bin/sh /sbin/debian-installer
322 root 1872 S -/bin/sh
323 root 1360 S /bin/busybox init
324 root 1360 S /usr/bin/tail -f /var/log/syslog
334 root 3364 S /usr/bin/bterm -f /lib/unifont.bgf -l C.UTF-8
/lib/d
335 root 14248 S debconf -o d-i /usr/bin/main-menu
341 root 1236 S /usr/bin/main-menu
1983 root 0 SW< [loop0]
4463 root 1868 S udhcpc -i eth0 -V d-i -O subnet -O broadcast
-O rout
4744 root 1352 S < udevd --daemon --resolve-names=never
5212 root 1712 S udpkg --configure --force-configure partman-base
5213 root 1868 S /bin/sh
/var/lib/dpkg/info/partman-base.postinst con
5214 root 1872 S /bin/sh /bin/partman
5440 root 0 SW [jfsIO]
5441 root 0 SW [jfsCommit]
5442 root 0 SW [jfsSync]
5456 root 0 SW [xfs_mru_cache]
5457 root 0 SW [xfslogd/0]
5458 root 0 SW [xfsdatad/0]
5459 root 0 SW [xfsconvertd/0]
5493 root 0 SW [kstriped]
5506 root 1872 S /bin/sh /lib/partman/init.d/30parted
5519 root 1352 S < udevd --daemon --resolve-names=never
5564 root 1872 R ps
Should be there a 'parted_server' process ? I have found a
/bin/parted_server executable, but I failed to find from what code it is
compiled from.
I could be very wrong, but I have this theory: parted_server could have
crashed because of this btrfs deflate problem into the kernel, since
this machine actually have a btrfs partition form Meego 1.1:
Nov 5 22:23:36 kernel: [ 338.431776] btrfs: Unknown symbol zlib_deflateEnd
Nov 5 22:23:36 kernel: [ 338.433279] btrfs: Unknown symbol zlib_deflate
Nov 5 22:23:36 kernel: [ 338.434232] btrfs: Unknown symbol
zlib_deflate_workspacesize
Nov 5 22:23:36 kernel: [ 338.435804] btrfs: Unknown symbol
zlib_deflateInit2
What is not right with this theory is that the problem seem to be
related to /dev/sdb that only have a 5MB FAT12 partition and not to
/dev/sda where the btrfs partition reside. Other problem is that I don't
have any message about a process crashing.
I very much appreciate any help to catch this problem.
Jean-Christian de Rivaz
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4cd52ae6.2060...@eclis.ch
