Hello there. I've got a problem. Recently my personal server issued a
kernel panic. Then there's a dump and so on. But there's no dump
information after reboot. I do not know what was really the panic cause but
assume that savecore failed because of RAID.
Problem - minidump was done (I saw it was) but was not recovered by
savecore after reboot into /var/vrash
Filesystem is UFS
FreeBSD diablo.miekoff.local 10.1-STABLE FreeBSD 10.1-STABLE #0 r277169:
Thu Jan 15 10:22:34 MSK 2015
amd_miek at diablo.miekoff.local:/usr/obj/usr/src/sys/DIABLO64
amd64
rc.conf configuration
dumpdev="AUTO"
dumpdir="/var/crash/"
RAID 1 via graid configuration (JMicron based)
graid list
Geom name: JMicron-6e1c79e
State: OPTIMAL
Metadata: JMicron
Providers:
1. Name: raid/r0
Mediasize: 120024203264 (112G)
Sectorsize: 512
Mode: r6w6e16
Subdisks: ada0 (ACTIVE), ada1 (ACTIVE)
Dirty: No
State: OPTIMAL
Strip: 1024
Components: 2
Transformation: RAID1
RAIDLevel: RAID1
Label: SYSMIRROR
descr: JMicron RAID1 volume
Consumers:
1. Name: ada0
Mediasize: 120034123776 (112G)
Sectorsize: 512
Mode: r1w1e1
ReadErrors: 0
Subdisks: r0(SYSMIRROR):0 at 0
State: ACTIVE (ACTIVE)
2. Name: ada1
Mediasize: 120034123776 (112G)
Sectorsize: 512
Mode: r1w1e1
ReadErrors: 0
Subdisks: r0(SYSMIRROR):1 at 0
State: ACTIVE (ACTIVE)
/etc/fstab
# Device Mountpoint FStype Options
Dump Pass#
/dev/ufs/rootfs / ufs rw,noatime
1 1
/dev/raid/r0p3 none swap sw
0 0
/dev/ufs/varfs /var ufs rw,noatime
2 2
/dev/ufs/tmpfs /tmp ufs rw,noatime
2 2
/dev/ufs/usrfs /usr ufs rw,noatime
2 2
/dev/ufs/configfs /config ufs rw,noatime
2 2
tmpfs /usr/tmpfs tmpfs rw
0 0
proc /proc procfs rw
0 0
fdesc /dev/fd fdescfs rw
0 0
In kernel configuration DEBUG -g is disabled.
--
amd_miek
Think different.
Just superior.
On Mon, Mar 16, 2015 at 9:40 AM, Michael BlackHeart <amdmiek at gmail.com> wrote:> Hello there. I've got a problem. Recently my personal server issued a > kernel panic. Then there's a dump and so on. But there's no dump > information after reboot. I do not know what was really the panic cause but > assume that savecore failed because of RAID. > > Problem - minidump was done (I saw it was) but was not recovered by > savecore after reboot into /var/vrash >(...)> /dev/ufs/varfs /var ufs rw,noatime > 2 2 >Last I checked, savecore had to happen very early --- before filesystems other than / are mounted. -- brandon s allbery kf8nh sine nomine associates allbery.b at gmail.com ballbery at sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
Hello, have you tried to run savecore manually, like savecore -vvf /var/crash /dev/raid/r0p3 Also check that your dump device is working (dumpon -l) On Mon, Mar 16, 2015 at 4:40 PM, Michael BlackHeart <amdmiek at gmail.com> wrote:> Hello there. I've got a problem. Recently my personal server issued a > kernel panic. Then there's a dump and so on. But there's no dump > information after reboot. I do not know what was really the panic cause but > assume that savecore failed because of RAID. > > Problem - minidump was done (I saw it was) but was not recovered by > savecore after reboot into /var/vrash > > Filesystem is UFS > > FreeBSD diablo.miekoff.local 10.1-STABLE FreeBSD 10.1-STABLE #0 r277169: > Thu Jan 15 10:22:34 MSK 2015 > amd_miek at diablo.miekoff.local:/usr/obj/usr/src/sys/DIABLO64 > amd64 > > rc.conf configuration > > dumpdev="AUTO" > dumpdir="/var/crash/" > > > > RAID 1 via graid configuration (JMicron based) > > graid list > Geom name: JMicron-6e1c79e > State: OPTIMAL > Metadata: JMicron > Providers: > 1. Name: raid/r0 > Mediasize: 120024203264 (112G) > Sectorsize: 512 > Mode: r6w6e16 > Subdisks: ada0 (ACTIVE), ada1 (ACTIVE) > Dirty: No > State: OPTIMAL > Strip: 1024 > Components: 2 > Transformation: RAID1 > RAIDLevel: RAID1 > Label: SYSMIRROR > descr: JMicron RAID1 volume > Consumers: > 1. Name: ada0 > Mediasize: 120034123776 (112G) > Sectorsize: 512 > Mode: r1w1e1 > ReadErrors: 0 > Subdisks: r0(SYSMIRROR):0 at 0 > State: ACTIVE (ACTIVE) > 2. Name: ada1 > Mediasize: 120034123776 (112G) > Sectorsize: 512 > Mode: r1w1e1 > ReadErrors: 0 > Subdisks: r0(SYSMIRROR):1 at 0 > State: ACTIVE (ACTIVE) > > /etc/fstab > > # Device Mountpoint FStype Options > Dump Pass# > /dev/ufs/rootfs / ufs rw,noatime > 1 1 > /dev/raid/r0p3 none swap sw > 0 0 > /dev/ufs/varfs /var ufs rw,noatime > 2 2 > /dev/ufs/tmpfs /tmp ufs rw,noatime > 2 2 > /dev/ufs/usrfs /usr ufs rw,noatime > 2 2 > /dev/ufs/configfs /config ufs rw,noatime > 2 2 > tmpfs /usr/tmpfs tmpfs rw > 0 0 > proc /proc procfs rw > 0 0 > fdesc /dev/fd fdescfs rw > 0 0 > > In kernel configuration DEBUG -g is disabled. > > -- > amd_miek > Think different. > Just superior. > _______________________________________________ > freebsd-stable at freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"