antiX-17 install hangs up on fstab

Forum Forums Official Releases antiX-17 “Heather Heyer” antiX-17 install hangs up on fstab

This topic contains 17 replies, has 4 voices, and was last updated by iugamarian Jan 21-4:26 am.

Viewing 15 posts - 1 through 15 (of 18 total)
  • Author
    Posts
  • #6981
    Member
    Avatar
    seaken64

    Hello everyone. I’ve been enjoying learning about antiX and have read many forum posts. It’s been entertaining and enlightening. I hope I can learn enough to contribute one day.

    I’m not a linux newbie but I do struggle sometimes understanding the underpinnings of these Linux variations. I have more familiarity with DOS and Windows but I like Linux alot and it has proven to be the best option for keeping some old computers in use. Hopefully I can help some others who may also have access to some old computers that are no longer supported. But for now this has been only a hobby for me and I am only slowly learning how to be a Linux administrator. (It’s slow because I have a day job that keeps me very busy and I only get a few days a month to experiment).

    Recently I have been experimenting with antiX-17 to see if it will be a suitable system for some of my Pentium 4 class systems. It is working quite good on a Pentium 4 with 1GB RAM running at 2.4Ghz. I had previously been using Xubuntu 16.04 but I was looking for a distro that is a little lighter on memory and has a nice community. It looks like antiX could become my main distro in the future. I had also been experimenting with Debian and Slackware but I really like the IceWM and even Fluxbox.These are perfect for old systems with limited memory and the antiX team has done a great job of setting it all up for a fairly easy OOB experience. As a moderately skilled admin this is important to me. I’m not afraid of code and scripts but I’m not a programmer nor do I have a background in computer science. Just a business man who learns to use his tools.

    So today I ran into a problem I did not expect. I wonder if anyone here has any tips for me as to how to handle this problem and whether there might be a way forward.

    antiX-17 was working so well on my P-4 that I decided I would try to install this current version on my main P-3 system. This P-3 system (1 Ghz w/ 512 RAM) is currently running antiX-16 just fine and I had no trouble with the install of version 16.1. But when I tried to install antiX-17 I could barely get the live distro to load and the install crashes, even with the cli-installer. The system stalls on a “make-fstab” line and follows after several minutes with several “input/output errors”.

    When I finally got to the command line I was able to log in as root. But when I tried to launch the cli-installer it gives me a message that it is replacing, (or making a new?) /etc/fstab. And it just dies there. The only way I can get out is to use CTRL-ALT-DEL to reboot. I have tried every option on the Grub launcher with the same results. I had the most success with the “Failsafe” mode to get to the live installation but the mouse wouldn’t move and I ended up using CTRL-ALT-F1 to go to the command line and reboot.

    This computer has two IDE drives and each drive has several partions for several different distros of Linux. Up until now I have not had a problem installing several Linux variants and antiX-16 has no problems. I also had no problem with MX-14 and Debian 8.

    I’m not good enough at understanding how the installers work and whether I can make a change in the settings to get past this error. I suspect it may have something to do with some changes to the kernel since version 16 or maybe the eudev system replacing the udev system. But I know very little about this kind of stuff and only guess from some things I have read while searching online.

    Maybe this is not enough information to go on? Do I need to capture some screen shots? or gather a log? How do I do this if I can’t even get the live system up and running?

    Anyway, I will stay with antiX-16 for now. But if there is a way to get past these fstab errors and install antiX-17 that would be my preferrence. Any ideas?

    Thanks,
    Sean

    #6988
    Forum Admin
    rokytnji
    rokytnji

    include

    cat /etc/fstab

    and

    sudo parted -l

    in your next post. I have borked fstab on my own also before. I learned to make backups like so.

    sudo cp /etc/fstab /etc/fstab.backup

    But, re-reading your post

    How do I do this if I can’t even get the live system up and running?

    Looks like I don’t know how to respond right. I got by installing full iso AntiX 17 on my IBM T23 Pentium 3 thinkpad with a cpu with no sse2 support with the default kernel shipped. I had no need of a cli install. First I have heard of making a hand made fstab file during the install process. But I have not done a cli install since version 8.5. I also quit multi-booting things like Semplice, Puppy, Slackel, Salix, Vector, Zenwalk, among others because it confused me and I spent too much time on my gear troubleshooting. Vs using my computers.

    I used to be a grub4dos expert.

    So my take on your situation with crashes and stuff. Might be a hardware issue on older gear. Worn out so to speak. I have had the sense to sell off things like my IBM 390 or Net Vista desktop boxes. I keep a old Panasonic CF-48. A old IBM T23. A couple of single core Atom netbooks. Just to post on how I install AntiX on old gear. Then they get put away mostly.

    Because I run daily on big beefy gear like this every day.

    harry@biker:~
    $ inxi -Fxz
    System:    Host: biker Kernel: 4.9.77-antix.1-686-smp-pae i686 bits: 32 gcc: 4.9.2
               Desktop: IceWM 1.3.8 Distro: antiX-15-V_386-full Killah P 30 June 2015
    Machine:   Device: laptop System: LENOVO product: 2347DS2 v: ThinkPad T430 serial: N/A
               Mobo: LENOVO model: 2347DS2 serial: N/A
               UEFI [Legacy]: LENOVO v: G1ET41WW (1.16 ) date: 05/25/2012
    Battery    BAT0: charge: 20.4 Wh 98.8% condition: 20.6/56.2 Wh (37%)
               model: SANYO 45N1001 status: N/A
    CPU:       Dual core Intel Core i5-3320M (-MT-MCP-) arch: Ivy Bridge rev.9 cache: 3072 KB
               flags: (lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 10376
               clock speeds: max: 3300 MHz 1: 1518 MHz 2: 2232 MHz 3: 2634 MHz 4: 3037 MHz
    Graphics:  Card: Intel 3rd Gen Core processor Graphics Controller bus-ID: 00:02.0
               Display Server: X.Org 1.16.4 drivers: intel (unloaded: modesetting,fbdev,vesa)
               Resolution: 1600x900@60.01hz
               OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile x86/MMX/SSE2
               version: 3.3 Mesa 10.3.2 Direct Render: Yes
    Audio:     Card Intel 7 Series/C216 Family High Def. Audio Controller
               driver: snd_hda_intel bus-ID: 00:1b.0
               Sound: Advanced Linux Sound Architecture v: k4.9.77-antix.1-686-smp-pae
    Network:   Card-1: Intel 82579LM Gigabit Network Connection
               driver: e1000e v: 3.2.6-k port: 5080 bus-ID: 00:19.0
               IF: eth2 state: down mac: <filter>
               Card-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi bus-ID: 03:00.0
               IF: wlan0 state: up mac: <filter>
    Drives:    HDD Total Size: 320.1GB (24.9% used)
               ID-1: /dev/sda model: HGST_HTS545032A7 size: 320.1GB
    Partition: ID-1: / size: 7.6G used: 5.1G (71%) fs: ext4 dev: /dev/sda1
               ID-2: /home size: 68G used: 3.1G (5%) fs: ext4 dev: /dev/sda2
               ID-3: swap-1 size: 4.19GB used: 0.00GB (0%) fs: swap dev: /dev/sda3
    Sensors:   System Temperatures: cpu: 48.0C mobo: N/A
               Fan Speeds (in rpm): cpu: 3618
    Info:      Processes: 186 Uptime: 4:10 Memory: 404.3/15936.6MB
               Init: SysVinit runlevel: 5 Gcc sys: 4.9.2 Client: Shell (bash 4.3.301) inxi: 2.3.54 
    harry@biker:~
    

    So me being kinda kicked back and enjoying how far I got on one my motorcycle builds today. Sipping Dos Equis beer. Being off topic.
    Don’t really know how to answer

    antiX-17 was working so well on my P-4 that I decided I would try to install this current version on my main P-3 system. This P-3 system (1 Ghz w/ 512 RAM) is currently running antiX-16 just fine and I had no trouble with the install of version 16.1. But when I tried to install antiX-17 I could barely get the live distro to load and the install crashes, even with the cli-installer. The system stalls on a “make-fstab” line and follows after several minutes with several “input/output errors”.

    When I finally got to the command line I was able to log in as root. But when I tried to launch the cli-installer it gives me a message that it is replacing, (or making a new?) /etc/fstab. And it just dies there. The only way I can get out is to use CTRL-ALT-DEL to reboot. I have tried every option on the Grub launcher with the same results. I had the most success with the “Failsafe” mode to get to the live installation but the mouse wouldn’t move and I ended up using CTRL-ALT-F1 to go to the command line and reboot.

    Because one minute. Everything goes whacko. But AntiX 16 running currently runs fine. Just wondering. Why not copy AntiX 16 /etc/fstab. Read it off usb on one of your other computers to make the /etc/fstab for the cli install?

    Howdy and Welcome from the forum scooter tramp. Hope you find a better poster/answer than me.

    Edit. Did you md5sum check your iso before installing?

    Sometimes I drive a crooked road to get my mind straight.
    Not all who Wander are Lost.
    Linux Registered User # 475019
    How to Search for AntiX solutions to your problems

    #6993
    Member
    Avatar
    seaken64

    Thanks rokytnji,

    You’ve given me some things to think about. I wonder what difference the fstab file makes during an install. I guess I don’t really understand what that file does. And I watched the output from antiX-16 live media and it does not display the “make-fstab” line. I’m assuming this is a script being used in the antiX-17 live media but why it differs from antix-16 I don’t know.

    I was able to get the live install to finish once using “failsafe” I will try that again and then maybe I can get those files recorded and post them here in my next message.

    I was thinking that maybe it has something to do with generating UUID numbers for the partitions in this new kernel. But this is something that I do not completely understand. I just got a handle on the “sda”, “hd0,1”, etc. And now it has all changed to UUID.

    I could try copying the fstab from my version 16 install. But what will I do with it? How do I merge that into the live media? Again, my lack of understanding here may prevent me from success. But I am willing to try to figure it out if I can get the proper guidance from folks like yourself. But this is not a critical system. It’s just an experimental box. I just like to see if I can keep this box working with a modern OS. antiX has been great for that so far.

    Oh, and I must confess I did not do the MD5sum check. I will try that.

    Thanks again for your ideas. My beer was Guiness tonight, followed by a scotch. About time to shut it down here. I’ll pick this up next weekend since I’ll be working the week starting tomorrow.

    Sean

    #6994
    Member
    linuxdaddy
    linuxdaddy

    Hello Seaken64,

    Can you use the antix-16 live disk on it to post lspci and dmesg in a text file. It might me that a
    module for one of the drives might not be in antix-17 that was in antix-16, You can type
    “lspci -kk ” to see which modules are being used, and check the cables on the drives too.
    if you want to try
    To copy from the live cd to the hdd you have to run the file manager from the root teminal.
    1. Boot live cd
    2. open root terminal
    3. run rox/spacefm from root terminal
    4. make sure hdd is mounted
    4. copy fstab from live fstab to hdd fstab or a fstab saved from a usb stick
    one note is from a live cd is the hdd has to be mounted as root to write to it.
    Hope this helps, my beer tonight was a mickey’s 🙂

    Normal == 🙂
    depends on the surrounding crowd ?!

    #7004
    Forum Admin
    rokytnji
    rokytnji

    If you need uuid numbers for anything.

    sudo blkid

    Will help on that

    Sometimes I drive a crooked road to get my mind straight.
    Not all who Wander are Lost.
    Linux Registered User # 475019
    How to Search for AntiX solutions to your problems

    #7029
    Member
    Avatar
    seaken64

    linuxdaddy,

    thanks for the tips. I wasn’t able to get the data from the live cd but I am running the installed antix-16 now and I grabbed the output you asked about. I’ve read it all but I guess I don’t know what to look for.

    #7030
    Member
    Avatar
    seaken64

    Oops. Let’s try that again. Maybe the error is because of no file extension?

    #7033
    Member
    Avatar
    seaken64

    rokytnji,

    here’s the stuff you asked about, attached as text files. The UUID’s also show up in the cat fstab. Also did the inxi.

    #7037
    Member
    Avatar
    seaken64

    Hope this helps, my beer tonight was a mickey’s />

    Is that a mickeys big mouth? I haven’t seen those since I left Seattle over 30 years ago! My local brew out here in NY is usually a Saranac.

    • This reply was modified 6 months, 4 weeks ago by anticapitalista.
    #7038
    Member
    Avatar
    seaken64

    Oops. Looks like I enlarged your emoticon! I clearly don’t know what I am doing! Or it could be the scotch!

    #7039
    Member
    Avatar
    seaken64

    Okay, I tried to duplicate the troubles I had with the antiX-17 installer but something different happened. I knew I was able to get the live distro to work with the “failsafe” choice so I put the DVD in the drive and rebooted, then chose “failsafe”. The install of the live image started up and it came to the same “make-fstab” line and paused. I was expecting the same input/output errors and I was going to write up the errors and post it here.

    But this time it came back with a message saying it put 15 hard disk entries and 1 removable entry into /etc/fstab. Then it continued and eventually completed the startup.

    I soon realized that I had left the USB key drive in place from my last failed boot trying to use PLOP. And it seems that this install was now using the image off the USB instead of the DVD. Weird. I had used the DVD to boot with and that is where I got all the errors, even though I did get through with the “failsafe” choice. But when I tried to use the cli-installer it failed. I then tried to use the USB image along with PLOP to boot from the USB. It failed to boot at all, Just a blank screen with a blinking cursor.

    But when I went back the antix-17 bootable DVD I did not take out the USB key. I used the DVD to boot and chose “failsafe”. And from there it appears that the install routine chose the USB to continue the install. And everything finished just fine. So maybe the problem was the DVD somehow not allowing the fstab to be created. Not sure. But anyway, this USB install seems to be the solution. I thought it was not going to be possible since this machine does not boot from USB. But apparently the install routine knew what to do.

    So now I have antix-17 installed on this Pentium-III. (I used the gui install) But all is not good. More on that in another thread.

    Thanks for all the ideas.

    Sean

    #7040
    Forum Admin
    rokytnji
    rokytnji

    cat /etc/fstab from antix 16 I think?

    $ cat /etc/fstab
    # /etc/fstab: static file system information
    #
    # Created by make-fstab on Tue Feb 27 14:29:24 EST 2018
    
    # <file system>                            <mount point>                               <type>     <options>                       <dump/pass>
    
    #-> /dev/sdb9  label=rootantiX
    UUID=7392d1ab-81d2-4642-806f-66f7595dbe6a  /                                           ext4       defaults                        1 1
    #-> /dev/sda5
    UUID=952aae38-e093-4686-8f42-9b37d64110b3  swap                                        swap       defaults                        0 0
    #-> /dev/sda1
    UUID=7009-BF98                             /media/7009-BF98                            vfat       noauto,uid=1000,gid=users,dmask=002,fmask=113,users  0 0
    #-> /dev/sda2
    UUID=2763c7f1-a7ff-4ade-b71d-63d8f812cc79  /media/2763c7f1-a7ff-4ade-b71d-63d8f812cc79 ext4       noauto,exec,users               0 0
    #-> /dev/sda3
    UUID=e88b0771-f63a-4a4a-ab3b-ce4ff72f2f36  /media/e88b0771-f63a-4a4a-ab3b-ce4ff72f2f36 ext4       noauto,exec,users               0 0
    #-> /dev/sda6
    UUID=ba78f134-fffc-4caa-bf91-77798495b5ad  /media/ba78f134-fffc-4caa-bf91-77798495b5ad ext4       noauto,exec,users               0 0
    #-> /dev/sda7
    UUID=7b901914-a97a-4bf0-a17b-e6a6193fc69a  /media/7b901914-a97a-4bf0-a17b-e6a6193fc69a ext4       noauto,exec,users               0 0
    #-> /dev/sda8
    UUID=e3345ac6-aab6-4fe6-a077-476ea367b73d  /media/e3345ac6-aab6-4fe6-a077-476ea367b73d ext4       noauto,exec,users               0 0
    #-> /dev/sda9
    UUID=4f99d4bf-ddd5-4b6e-b48b-c50713577884  /media/4f99d4bf-ddd5-4b6e-b48b-c50713577884 ext4       noauto,exec,users               0 0
    #-> /dev/sdb5
    UUID=ce1989f2-549f-477f-bb2f-d758750dff10  /media/ce1989f2-549f-477f-bb2f-d758750dff10 ext4       noauto,exec,users               0 0
    #-> /dev/sdb6
    UUID=e51b6e12-4f34-4eb7-ad84-1e0aa9f4e6f8  /media/e51b6e12-4f34-4eb7-ad84-1e0aa9f4e6f8 ext4       noauto,exec,users               0 0
    #-> /dev/sdb7  label=rootantiX-16
    UUID=4f2bf969-e310-4051-a93a-cac05003a9c7  /media/rootantiX-16                         ext4       noauto,exec,users               0 0
    #-> /dev/sdb8
    UUID=da25ce3b-23b9-4afc-aa1a-8e58e9dce416  /media/da25ce3b-23b9-4afc-aa1a-8e58e9dce416 ext4       noauto,exec,users               0 0
    #-> /dev/sdb10  label=FAT32DATA
    UUID=9996-8DBA                             /media/FAT32DATA                            vfat       noauto,uid=1000,gid=users,dmask=002,fmask=113,users  0 0
    /dev/cdrom                                 /media/cdrom                                iso9660    noauto,exec,users,ro            0 0
    /dev/fd0                                   /media/fd0                                  auto       noauto,exec,users,rw            0 0
    /dev/sr0                                   /media/sr0                                  auto       noauto,exec,users,ro            0 0
    

    parted -l

    $ sudo parted -l
    [sudo] password for sean: 
    Model: ATA Maxtor 6L100P0 (scsi)
    Disk /dev/sda: 100GB
    Sector size (logical/physical): 512B/512B
    Partition Table: msdos
    Disk Flags: 
    
    Number  Start   End     Size    Type      File system     Flags
     1      32.3kB  21.0GB  21.0GB  primary   fat32           boot, lba
     2      21.0GB  31.5GB  10.5GB  primary   ext4
     3      31.5GB  41.9GB  10.5GB  primary   ext4
     4      41.9GB  100GB   58.1GB  extended
     5      41.9GB  43.0GB  1077MB  logical   linux-swap(v1)
     6      43.0GB  56.9GB  13.9GB  logical   ext4
     7      56.9GB  70.9GB  13.9GB  logical   ext4
     8      70.9GB  85.1GB  14.2GB  logical   ext4
     9      85.1GB  100GB   14.9GB  logical   ext4
    
    Model: ATA WDC WD1600JB-00R (scsi)
    Disk /dev/sdb: 160GB
    Sector size (logical/physical): 512B/512B
    Partition Table: msdos
    Disk Flags: 
    
    Number  Start   End     Size    Type      File system  Flags
     1      2096kB  95.1GB  95.1GB  extended               boot
     5      2097kB  15.7GB  15.7GB  logical   ext4
     6      15.7GB  31.3GB  15.6GB  logical   ext4
     7      31.3GB  47.5GB  16.2GB  logical   ext4
     8      47.5GB  63.7GB  16.2GB  logical   ext4
     9      63.7GB  79.4GB  15.7GB  logical   ext4
    10      79.4GB  95.1GB  15.6GB  logical   fat32
    
    Model: Lexar USB Flash Drive (scsi)
    Disk /dev/sde: 8005MB
    Sector size (logical/physical): 512B/512B
    Partition Table: msdos
    Disk Flags: 
    
    Number  Start   End     Size    Type     File system  Flags
     1      1049kB  8005MB  8004MB  primary  fat32        boot, lba
    
    

    inxi from 17 which I thought would not install.

    $ inxi -Flx
    System:    Host: antix17 Kernel: 4.10.5-antix.1-486-smp i686 bits: 32 gcc: 6.3.0
               Desktop: IceWM 1.4.2 Distro: antiX-17_386-full Heather Heyer 24 October 2017
    Machine:   Device: desktop System: Compaq product: Deskpro serial: N/A
               Mobo: Compaq model: 0684h serial: N/A
               BIOS: Compaq v: 686P2 v2.04 date: 08/25/2000
    CPU:       Single core Pentium III (Coppermine) (-UP-) 
               arch: P6 III rev.6 cache: 256 KB
               flags: (pae sse) bmips: 1993 speed: 996 MHz (max)
    Graphics:  Card: NVIDIA NV11 [GeForce2 MX200] bus-ID: 01:00.0
               Display Server: X.Org 1.19.2 driver: vesa Resolution: 1024x768@0.00hz
               OpenGL: renderer: Gallium 0.4 on llvmpipe (LLVM 3.9, 128 bits)
               version: 3.3 Mesa 13.0.6 Direct Render: Yes
    Audio:     Card Intel 82801BA/BAM AC'97 Audio Controller
               driver: snd_intel8x0 ports: 2000 2400 bus-ID: 00:1f.5
               Sound: Advanced Linux Sound Architecture v: k4.10.5-antix.1-486-smp
    Network:   Card: Intel 82801BA/BAM/CA/CAM Ethernet Controller
               driver: e100 v: 3.5.24-k2-NAPI port: 1000 bus-ID: 02:08.0
               IF: eth0 state: up speed: 100 Mbps duplex: full mac: 00:02:a5:04:34:81
    Drives:    HDD Total Size: 268.1GB (2.0% used)
               ID-1: /dev/sda model: Maxtor_6L100P0 size: 100.0GB
               ID-2: /dev/sdb model: WDC_WD1600JB size: 160.0GB
               ID-3: USB /dev/sde model: USB_Flash_Drive size: 8.0GB
    Partition: ID-1: / size: 15G used: 3.3G (24%) fs: ext4 dev: /dev/sdb9 label: rootantiX
               ID-2: swap-1 size: 1.08GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
               label: N/A
    Sensors:   None detected - is lm-sensors installed and configured?
    Info:      Processes: 143 Uptime: 1:10 Memory: 110.6/496.3MB
               Init: SysVinit runlevel: 5 Gcc sys: 6.3.0
               Client: Shell (bash 4.4.121) inxi: 2.3.40 
    
    

    Bedtime for Rok

    • This reply was modified 1 year, 5 months ago by rokytnji.

    Sometimes I drive a crooked road to get my mind straight.
    Not all who Wander are Lost.
    Linux Registered User # 475019
    How to Search for AntiX solutions to your problems

    #7042
    Member
    Avatar
    seaken64

    I didn’t think I would get to this until the weekend but I ended up working on this tonight. And even though I got the live antiX-17 installed using the USB I still am at a loss as to why the antix-16 CD-ROM works on this rig but the DVD does not work with antiX-17. And what does the “make-fstab” do and why does it crash? Maybe I’ll never know.Maybe someone on you will see something in those text files that makes sense to you. I read them all and it doesn’t help me understand what is happening with the errors I got. I also was stunned to see the USB key drive being used to launch the live demo after having booted from the DVD. But it was a pleasant surprise I guess since it helped me get it installed.

    See my next post about some issues I have had after the install – having to do with browsers.

    Thanks,
    Sean

    #7158
    Member
    linuxdaddy
    linuxdaddy

    No big mouth it was 12oz cans. But our store here in Moriarty,NM sells mickey big mouth in 6-pack.
    Any way I was looking for a failed driver in dmesg and didn’t see any. You could try turning off
    plug and play OS in the bios. Also the P-3 cpus support pae so you can also try the 686-pae kernel.
    The reason usb boot worked is that GRUB can see the usb stick.

    Normal == 🙂
    depends on the surrounding crowd ?!

    #7159
    Member
    linuxdaddy
    linuxdaddy

    You could also try adding “acpi=off” to the kernel boot line in grub.

    Normal == 🙂
    depends on the surrounding crowd ?!

Viewing 15 posts - 1 through 15 (of 18 total)

You must be logged in to reply to this topic.