New installation hangs - Monkeyman - 08-13-2015
Trying to install 2.4 on a new SSD. I'm getting through the actual installation but when it automatically reboots, it hangs up. I get the screen with the feather and the progress bar. The progress bar makes it all the way to the end then.....nothing. I've tried a few times with the same result. The last time, I took a shower and shaved while waiting and nothing had changed. If you hit ANY key (not the "ANY" key), it reboots into nothingness (black screen). I've d/l'ed it twice. First time was a torrent and burned it at whatever speed it automatically burns. The second time was the regular d/l burned at the slowest speed allowed (4x, I think).
Any thoughts? I'd like to install this on my new SSD although it won't really hurt my feelings to wait a couple weeks and try installing 2.6.
Re: New installation hangs - torreydale - 08-13-2015
Is this something you've tried? I would imagine you could do these steps from within the Live CD before you click on the Install Linux Lite icon.
https://www.freecinema2022.gq/manual/install.html#enabletrim
Also do an MD5Sum check on your *.iso file, if you haven't already.
Re: New installation hangs - Wirezfree - 08-13-2015
Hi torreydale
I wrote this on TRIM
https://www.freecinema2022.gq/forums/hard-drives-and-ssd's/(solved)-trim-on-ssd/msg6653/#msg6653
I now have the weekly cron job, I understand doing it via fstab forces a trim every time you delete
Re: New installation hangs - rokytnji - 08-13-2015
just showing how to look for things when they go wrong on booting up.
live cd should be able to access your non booting install ssd drive. look in /var/log/boot.log like i show below.
Code: harry@harry-Latitude-XT2:~$ cd /var/log
harry@harry-Latitude-XT2:/var/log$ ls
alternatives.log dmesg.3.gz mail.log
alternatives.log.1 dmesg.4.gz mail.warn
alternatives.log.2.gz dpkg.log messages
alternatives.log.3.gz dpkg.log.1 pm-powersave.log
alternatives.log.4.gz dpkg.log.2.gz pm-powersave.log.1
alternatives.log.5.gz dpkg.log.3.gz pm-powersave.log.2.gz
alternatives.log.6.gz dpkg.log.4.gz pm-powersave.log.3.gz
alternatives.log.7.gz dpkg.log.5.gz pm-powersave.log.4.gz
alternatives.log.8.gz dpkg.log.6.gz samba
apt dpkg.log.7.gz speech-dispatcher
auth.log dpkg.log.8.gz syslog
auth.log.1 faillog syslog.1
auth.log.2.gz fontconfig.log syslog.2.gz
boot fsck udev
boot.log gpu-manager.log unattended-upgrades
bootstrap.log hp upstart
ConsoleKit installer user.log
cups kern.log wicd
daemon.log lastlog wtmp
debug lightdm wtmp.1
dmesg llupdates.log Xorg.0.log
dmesg.0 lpr.log Xorg.0.log.old
dmesg.1.gz mail.err Xorg.1.log
dmesg.2.gz mail.info Xorg.1.log.old
harry@harry-Latitude-XT2:/var/log$ cat boot.log
* Starting Mount filesystems on boot [ OK ]
* Stopping Track if upstart is running in a container [ OK ]
* Starting Signal sysvinit that the rootfs is mounted [ OK ]
* Starting Clean /tmp directory [ OK ]
* Stopping Clean /tmp directory [ OK ]
* Stopping Read required files in advance (for other mountpoints) [ OK ]
* Starting Initialize or finalize resolvconf [ OK ]
* Starting set console keymap [ OK ]
* Starting Signal sysvinit that virtual filesystems are mounted [ OK ]
* Starting Signal sysvinit that virtual filesystems are mounted [ OK ]
* Starting Bridge udev events into upstart [ OK ]
* Stopping set console keymap [ OK ]
* Starting device node and kernel event manager [ OK ]
* Starting Signal sysvinit that local filesystems are mounted [ OK ]
* Starting D-Bus system message bus [ OK ]
* Starting Signal sysvinit that remote filesystems are mounted [ OK ]
* Starting load modules from /etc/modules [ OK ]
* Starting cold plug devices [ OK ]
* Starting log initial device creation [ OK ]
* Stopping Mount filesystems on boot [ OK ]
* Stopping load modules from /etc/modules [ OK ]
* Starting flush early job output to logs [ OK ]
* Starting SystemD login management service [ OK ]
* Stopping flush early job output to logs [ OK ]
* Starting bluetooth daemon [ OK ]
* Starting system logging daemon [ OK ]
* Starting mDNS/DNS-SD daemon [ OK ]
* Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated [ OK ]
* Stopping Reload cups, upon starting avahi-daemon to make sure remote queues are populated [ OK ]
* Starting Uncomplicated firewall [ OK ]
* Starting configure network device security [ OK ]
* Starting configure network device [ OK ]
* Starting configure network device security [ OK ]
* Starting CUPS printing spooler/server [ OK ]
* Starting Samba Auto-reload Integration [ OK ]
* Starting Mount network filesystems [ OK ]
* Starting SMB/CIFS File Server [ OK ]
* Starting Failsafe Boot Delay [ OK ]
* Starting cups-browsed - Bonjour remote printer browsing daemon [ OK ]
* Starting SMB/CIFS File and Active Directory Server [ OK ]
* Stopping Mount network filesystems [ OK ]
* Stopping Failsafe Boot Delay [ OK ]
* Starting System V initialisation compatibility [ OK ]
* Starting modem connection manager [ OK ]
* Starting configure network device security [ OK ]
* Starting SMB/CIFS File and Active Directory Server [fail]
* Starting network connection manager [ OK ]
* Stopping Samba Auto-reload Integration [ OK ]
* Starting configure network device [ OK ]
* Starting configure network device security [ OK ]
* Starting configure network device [ OK ]
* Starting Bridge file events into upstart [ OK ]
Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
* Starting Bridge socket events into upstart [ OK ]
Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
* Starting AppArmor profiles [ OK ]
* VirtualBox Additions disabled, not in a Virtual Machine
* Setting sensors limits [ OK ]
* Setting up X socket directories... [ OK ]
* Stopping System V initialisation compatibility [ OK ]
* Not starting glances: disabled by /etc/default/glances.
* Starting System V runlevel compatibility [ OK ]
* Starting CPU interrupts balancing daemon [ OK ]
* Starting regular background program processing daemon [ OK ]
* Starting save kernel messages [ OK ]
* Starting configure network device security [ OK ]
* Stopping save kernel messages [ OK ]
* Starting ACPI daemon [ OK ]
* Starting disk temperature monitoring daemon hddtemp: [ OK ]
* Stopping Restore Sound Card State [ OK ]
* speech-dispatcher disabled; edit /etc/default/speech-dispatcher
* Starting configure virtual network devices [ OK ]
* VirtualBox Additions disabled, not in a Virtual Machine
* Starting Network connection manager wicd [ OK ]
saned disabled; edit /etc/default/saned
* Restoring resolver state... [ OK ]
* Stopping System V runlevel compatibility [ OK ]
harry@harry-Latitude-XT2:/var/log$
Re: New installation hangs - Monkeyman - 08-14-2015
(08-13-2015, 09:34 PM)Wirezfree link Wrote: Hi torreydale
I wrote this on TRIM
https://www.freecinema2022.gq/forums/hard-drives-and-ssd's/(solved)-trim-on-ssd/msg6653/#msg6653
I now have the weekly cron job, I understand doing it via fstab forces a trim every time you delete
When I try that, I get this:
fstrim: /: FITRIM ioctl faiiled: Inappropriate ioctl for device
EDIT: Tried again and it showed TRIM is enabled. Thanks.
Re: New installation hangs - Monkeyman - 08-14-2015
Got it to install but when I try to install the updates, here's what happens. They d/l fine but when they're done unpacking, etc, I get an error message that says the updates failed. When I open a terminal, it shows "linux@linux" instead of my user/computer name.
When I try what rokytnji said, I get things like: "could not create certificate. Openssl output was: unable to load 'random state' ", "error generating key", "unable to locate any package files". All of the "OK" or "fail" items show "OK".
EDIT: Tried to d/l updates again and got another error message that says, "couldn't fetch the package cache information lists".
Re: New installation hangs - Monkeyman - 08-14-2015
Success! After a zillion reboots, everything finally worked. No idea what happened differently but thanks to everyone who helped. I switched back to the "old" SSD as there's a TON of tweaking I still need to do (adding progs/apps, adjusting the toolbar, updating FF bookmarks/passwords, etc). I have to work the next 3 days so I'm about out of time. Looks like a good chore for next week.
Thanks again to all!
Re: New installation hangs - Wirezfree - 08-14-2015
(08-14-2015, 05:07 AM)Monkeyman link Wrote: [quote author=Wirezfree link=topic=2169.msg16383#msg16383 date=1439501645]
Hi torreydale
I wrote this on TRIM
https://www.freecinema2022.gq/forums/hard-drives-and-ssd's/(solved)-trim-on-ssd/msg6653/#msg6653
I now have the weekly cron job, I understand doing it via fstab forces a trim every time you delete
When I try that, I get this:
fstrim: /: FITRIM ioctl faiiled: Inappropriate ioctl for device
EDIT: Tried again and it showed TRIM is enabled. Thanks.
[/quote]
Glad it worked...
I had a lot of issues with early SSD's
I moved to Samsung 840/850 Pro's in 2.5" & mSata size in 2014... NO issue's & great performance
Samsung 840
Code: dave@asus-mini-1:~$ sudo hdparm -t /dev/sda
/dev/sda:
Timing buffered disk reads: 1504 MB in 3.00 seconds = 501.18 MB/sec
WD "Black" 2.5" (supposedly the fastest 2.5")
Code: dave@asus-mini-1:~$ sudo hdparm -t /dev/sdb
/dev/sdb:
Timing buffered disk reads: 334 MB in 3.02 seconds = 110.67 MB/sec
|