Re: getting data from degraded RAID 1 boot disk
On Tue, Jan 31, 2017 at 05:23:10PM -0500, Jiri B wrote: > I have a disk which used to be boot disk of a degraded RAID 1 (softraid). > The second disk is totally gone. > > I don't want to use this disk as RAID 1 disk anymore, just to get data > from it. > > I'm asking because when I plugged the disk, bioctl said 'not enough disks'. > > Do we really have to necessary require two disks when attaching already > existing > degraded RAID 1 with only one disk available? Can you describe in more detail what you did to "plug the disk"? It sounds like you ran 'bioctl' in a way that tries to create a new RAID1 volume. Why? If the disk is present during system boot, is it not auto-assembled as a degraded RAID1 volume? I would expect a degraded softraid RAID1 disk to show up which you can copy data from.
getting data from degraded RAID 1 boot disk
I have a disk which used to be boot disk of a degraded RAID 1 (softraid). The second disk is totally gone. I don't want to use this disk as RAID 1 disk anymore, just to get data from it. I'm asking because when I plugged the disk, bioctl said 'not enough disks'. Do we really have to necessary require two disks when attaching already existing degraded RAID 1 with only one disk available? (I find it generally pretty sad we can't define RAID 1 with only disk. I could imagine constructing RAID 1 with one disk as useful feature, eg. migration from non-mirrored boot disk to RAID 1 boot disks which attaching just new additional disk. At least we used to do this on RHEL.) My current workaround is running a VM under qemu and accessing this disk as raw device. Surprisingly this works fine in comparision with previous attaching with bioctl. kern.version=OpenBSD 6.0-current (GENERIC.MP) #117: Sat Jan 7 09:10:45 MST 2017 j.
Re: init: can't open /dev/console: Device not configured.
On Tue, Jan 31, 2017 at 02:11:37PM +0100, Christophe Jarry wrote: > Dear OpenBSD developers an users, > > I have installed OpenBSD 6.0 on my 14 years-old hp pavilion ze5418EA > (i386). I used an USB key on which I dd'ed install60.fs. > > The installation process went smoothly, I used the default answer to > almost every question. > I made a custom partition table with one partition of 28 GB for > OpenBSD, 26 GB for another OS and 2 GB or so of swap. > I answered "no" to "Change default console to com1?" Try booting bsd.rd from boot loader, then mount your root filesystem at /mnt and inspect /mnt/etc/boot.conf. For desktop you generally don't need this file at all. j.
Re: OpenBSD removed from minifree project
On 31/01/17 21:58, Foo74 wrote: I was recently looking to purchase a minifree (https://minifree.org/) laptop to support the LibreBoot project. OpenBSD was listed as an option. Unfortunately, Leah, the leader of the project said she had to remove OpenBSD because it was too difficult to get it installed on their laptops with LibreBoot. Does anyone know if they will be bringing it back or what the difficulties might be with LibreBoot and OpenBSD? https://libreboot.org/faq/#bsd https://libreboot.org/docs/bsd/openbsd.html https://notabug.org/vimuser/libreboot-website/commit/6d8ac69e0c252c4e0bdf019aee978d8a13de0e10 http://zammit.org/libreboot-screwup.html G
Re: OpenBSD removed from minifree project
> Does anyone know if they will be bringing it back or what the difficulties > might be > with LibreBoot and OpenBSD? Ask on their list! Isn't that obvious?
OpenBSD removed from minifree project
I was recently looking to purchase a minifree (https://minifree.org/) laptop to support the LibreBoot project. OpenBSD was listed as an option. Unfortunately, Leah, the leader of the project said she had to remove OpenBSD because it was too difficult to get it installed on their laptops with LibreBoot. Does anyone know if they will be bringing it back or what the difficulties might be with LibreBoot and OpenBSD?
Xfce shutdown and reboot not available on first login
Hi, Since I've switched from SLiM to XDM as login manager I'm not able to shutdown or reboot from Xfce on the first login (buttons are greyed out). When I logout and login again, the options are available. Any suggestions how to fix this? Kind regards, Martijn Rijkeboer $ sysctl kern.version kern.version=OpenBSD 6.0-current (GENERIC.MP) #158: Mon Jan 30 19:30:12 MST 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP $ cat /etc/rc.conf.local xdm_flags= pkg_scripts=messagebus $ cat .xsession /usr/local/bin/startxfce4 --with-ck-launch $ pkg_info |egrep 'console|polkit|^xfce-' consolekit2-1.0.2p1 framework for defining and tracking users, sessions & seats polkit-0.113p3 framework for granting privileged operations to users xfce-4.12p6 Xfce desktop meta-package (base installation)
init: can't open /dev/console: Device not configured.
Dear OpenBSD developers an users, I have installed OpenBSD 6.0 on my 14 years-old hp pavilion ze5418EA (i386). I used an USB key on which I dd'ed install60.fs. The installation process went smoothly, I used the default answer to almost every question. I made a custom partition table with one partition of 28 GB for OpenBSD, 26 GB for another OS and 2 GB or so of swap. I answered "no" to "Change default console to com1?" After the installation of the default sets from HTTP server ftp.fr.openbsd.org, under pub/OpenBSD/6.0/i386, I rebooted with "reboot". After this, the boot process took place and ended up with: root on wd0a (ef0e3f6a9c48d192.a) swap on wd0b dump on wd0b init: can't open /dev/console: Device not configured. How may I fix this? Note: I have not been able to write the output of dmesg somewhere. Christophe
Re: sendsyslog: dropped 4 messages, error 55
p...@thinkage.ca (Peter Fraser), 2017.01.30 (Mon) 18:17 (CET): > My /var/log/messages is filling up with messages like the following: > > Jan 30 10:28:06 gateway sendsyslog: dropped 4 messages, error 55 > Jan 30 10:28:06 gateway sendsyslog: dropped 2 messages, error 55 > Jan 30 10:28:06 gateway sendsyslog: dropped 2 messages, error 55 > Jan 30 10:28:06 gateway sendsyslog: dropped 1 message, error 55 > Jan 30 10:28:06 gateway sendsyslog: dropped 2 messages, error 55 > Jan 30 10:28:06 gateway last message repeated 2 times > Jan 30 10:28:06 gateway sendsyslog: dropped 4 messages, error 55 > Jan 30 10:28:06 gateway sendsyslog: dropped 2 messages, error 55 > Jan 30 10:28:06 gateway last message repeated 2 times > Jan 30 10:28:06 gateway sendsyslog: dropped 1 message, error 55 > Jan 30 10:28:06 gateway sendsyslog: dropped 1 message, error 55 > > The messages occur in bursts with several hundred messages per burst, > and here may be several seconds or hours between the bursts. > > I am quite willing to believe that I have done something stupid, but I have no > idea what. > Any hints to find out what is generating these messages. src/lib/libc/gen/syslog_r.c, 188: * If the sendsyslog() fails, it means that syslogd * is not running or the kernel ran out of buffers. sendsyslog(2) RETURN VALUES Upon successful completion, the value 0 is returned; otherwise the value -1 is returned and the global variable errno is set to indicate the error. errno(2) 55 ENOBUFS No buffer space available. An operation on a socket or pipe was not performed because the system lacked sufficient buffer space or because a queue was full. But I can't tell you why your kernel is running out of buffers. You did not give much information... Marcus > !DSPAM:588f7557249121949212877!
