issues with dumpdev in /etc/defaults/rc.conf
-
What about a cron @reboot root dumpon /dev/ada0s3b or something like that? I mean that should fix it right? Swap on a different /dev/da0 and dump set to save locally. Should work right? It shows when I reboot now YEAH~!~!
Shell Output - swapinfo Device 512-blocks Used Avail Capacity /dev/da0p1.eli 250066944 0 250066944 0% Shell Output - dumpon -l ada0s3b
-
even with me running dumpon and setting it and it showing dumpon -l it does not show rc.dumpon will it still work?
-
Right presumably because you have moved SWAP to that other format where fails the test. But if the raw command shows it it should work fine.
-
@stephenw10
Ok I will be right back I am going to trigger it to test itsysctl debug.kdb.panic=1
-
I am just worried it wont see it because of this program
#!/bin/sh # # rc.dumpon # # part of pfSense (https://www.pfsense.org) # Copyright (c) 2004-2013 BSD Perimeter # Copyright (c) 2013-2016 Electric Sheep Fencing # Copyright (c) 2014-2023 Rubicon Communications, LLC (Netgate) # All rights reserved. # # Based on src/etc/rc.d/dumpon from FreeBSD # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. dumpon_try() { if /sbin/dumpon "${1}" ; then # Make a symlink in devfs for savecore echo "Using ${1} for dump device." ln -fs "${1}" /dev/dumpdev return 0 fi echo "Unable to specify $1 as a dump device." return 1 } # Enable dumpdev so that savecore can see it. Enable it # early so a crash early in the boot process can be caught. # while read dev mp type more ; do [ "${type}" = "swap" ] || continue [ -c "${dev}" ] || continue dumpon_try "${dev}" && works=true done </etc/fstab if [ "${works}" != "true" ]; then # fstab entries did not work, try swap labels for dev in /dev/label/swap*; do if [ ! -e "${dev}" ]; then continue; fi dumpon_try "${dev}" && works=true done if [ "${works}" != "true" ]; then echo "No suitable dump device was found." 1>&2 exit fi fi
will savecore see it...
-
It does not populate I wonder what else is needed
-
ln -fs /dev/ada0s3b /dev/dumpdev
I think this linker file is still needed for it to work I need to generate it manually because the program does it only based on fstab
-
still no report /var/crash weird I even manual created the link for devdump
-
#!/bin/sh # # rc.dumpon # # part of pfSense (https://www.pfsense.org) # Copyright (c) 2004-2013 BSD Perimeter # Copyright (c) 2013-2016 Electric Sheep Fencing # Copyright (c) 2014-2023 Rubicon Communications, LLC (Netgate) # All rights reserved. # # Based on src/etc/rc.d/dumpon from FreeBSD # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License. ln -fs /dev/ada0s3b /dev/dumpdev echo "OK ADAPTED ADA0S3B ONLINE" return 0
This might fix it
-
@JonathanLee said in issues with dumpdev in /etc/defaults/rc.conf:
sysctl debug.kdb.panic=1
Custom solution
- add the cron
- copy the rc.dumpon to rc.dumpon.old
add the new info
and it works