DaemonForums  

Go Back   DaemonForums > NetBSD > NetBSD Installation and Upgrading

NetBSD Installation and Upgrading Have trouble getting NetBSD on your toaster?

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 3 Weeks Ago
commodorejohn commodorejohn is offline
Real Name: John
Stubborn throwback
 
Join Date: Jun 2014
Location: Duluth, MN
Posts: 27
Default sysinst segfaults on Alpha ("file system full") - install help

Trying to get a NetBSD 9.0 install going on an Alpha 3000 300X workstation since Tru64 is being a pain in the butt. The install environment boots and runs, and I can do a bunch of stuff from the shell with no issues, but the installer itself craps out when partitioning the disk. I can partition the same disk with disklabel and create filesystems with newfs totally without issue, so it's not an issue with the drive - unfortunately, this doesn't give it whatever magic blessing sysinst needs to recognize the appropriate mount points automatically, and when I try to use the sysinst partition utility to do anything (even just set the mount points on already partitioned and formatted filesystems,) it kills with the following message:

Code:
/: write failed, file system is full
[1]   Segmentation fault
Someone else described the same issue here for the SGI port sixteen-plus years ago :/ So I'm not exactly thrilled about the chances of a fix coming along, but it's worth asking, I suppose. One thing I did notice was that /dev/mda0 (the in-memory filesystem for the installer) ends up very close to completely full, and part of that is a sysinst.core dump, but I'm not clear on whether sysinst is dumping core because the filesystem is full, or vice versa. It doesn't seem like memory constraints should be an issue, though - the box has 160 MB of RAM, way more than the listed minimum.

I think my better shot here is: can I just avoid the sysinst partitioning utility entirely? I can do everything needed with the disk from the shell, except apparently chant the proper blessing upon the resulting partitions. How does sysinst determine which partitions in the disklabel should map to which mount points in the target install? Where is that magic documented or stored?
__________________
Computers: Amiga 1200, DEC VAXStation 4000/60, DEC MicroPDP-11/73
Synthesizers: Roland JX-10/MT-32/D-10, Oberheim Matrix-6, Yamaha DX7/FB-01, Korg MS-20 Mini, Ensoniq Mirage/SQ-80, Sequential Circuits Prophet-600, Hohner String Performer
Reply With Quote
  #2   (View Single Post)  
Old 3 Weeks Ago
J65nko J65nko is offline
Administrator
 
Join Date: May 2008
Location: Budel - the Netherlands
Posts: 3,588
Default

I cannot give you any assistance on your "sysinst" issue but .....

The mapping of BSD partitions/labels to file systems is done in the file "/etc/fstab".
The following is from my OpenBSD install:
Code:
hp_server$ cat /etc/fstab
e9298df9f130b613.b none swap sw
e9298df9f130b613.a / ffs rw 1 1
e9298df9f130b613.e /home ffs rw,nodev,nosuid 1 2
e9298df9f130b613.d /usr ffs rw,wxallowed,nodev 1 2
By convention partition/label "a" is used for the root file system "/", where the system boots from. Partition/label "b" is used by convention for swap. On NetBSD the "c" label covers the NetBSD slice (MBR partition), while on OpenBSD it covers the whole disk. For NetBSD label "d" covers the whole disk. See http://netbsd.org/docs/guide/en/chap...tall-partition
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump
Reply With Quote
  #3   (View Single Post)  
Old 2 Weeks Ago
Sensucht94's Avatar
Sensucht94 Sensucht94 is offline
Real Name: Paolo Vincenzo Olivo
Shell Scout
 
Join Date: Oct 2017
Location: Rome
Posts: 87
Default

Quote:
Originally Posted by commodorejohn View Post
when I try to use the sysinst partition utility to do anything (even just set the mount points on already partitioned and formatted filesystems,) it kills with the following message:

[code]/: write failed, file system is full
On i386 once I experienced the same problem when the MBR had been overwritten with a BSD label (resulting in a 'dangerously dedicated disk'), since...
Quote:
unfortunately, this doesn't give it whatever magic blessing sysinst needs to recognize the appropriate mount points automatically
Quote:
How does sysinst determine which partitions in the disklabel should map to which mount points in the target install? Where is that magic documented or stored?
sysinst relies on the MBR in order to get the correct BIOS geometry, or other partition table to get the disk layout. What about dropping to shell at boot and running disklabel -w /wd0 before launching sysinst?
__________________
“Mi casa tendrá dos piernas y mis sueños no tendrán fronteras„
Reply With Quote
Reply

Tags
aaarrrrggghhh, installer, netbsd

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Compiling message: "write failed, file system is full"? Nureo OpenBSD Packages and Ports 13 19th July 2016 01:36 AM
directory "USR" is full philo_neo71 OpenBSD Packages and Ports 3 29th November 2014 07:25 PM
Is there any BSD operating system running on the so called "Android Mini PC MK802" ? bsdnotbdsm General Hardware 20 25th July 2013 02:35 AM
Filesystem /var "stuck" at 105% full daneric OpenBSD General 2 18th October 2012 06:18 PM
Fixed "xinit" after _7 _8, "how" here in case anyones' "X" breaks... using "nvidia" jb_daefo Guides 0 5th October 2009 09:31 PM


All times are GMT. The time now is 07:57 AM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick