Anyway bios and F12 gabroke,been trying command line: a@a-laptop:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 149.1G 0 disk ├─sda1 8:1 0 135.3G 0 part / ├─sda2 8:2 0 1K 0 part ├─sda3 8:3 0 9.8G 0 part /home └─sda5 8:5 0 4G 0 part [SWAP] sr0 11:0 1 1024M 0 rom a@a-laptop:~$ mount|grep ^'/dev' /dev/sda1 on / type ext4 (rw,errors=remount-ro) /dev/sda3 on /home type ext4 (rw,nosuid,nodev) a@a-laptop:~$ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 139506636 16942716 115454292 13% / none 4 0 4 0% /sys/fs/cgroup udev 2053588 4 2053584 1% /dev tmpfs 412640 1340 411300 1% /run none 5120 0 5120 0% /run/lock none 2063196 80 2063116 1% /run/shm none 102400 64 102336 1% /run/user /dev/sda3 9948012 6445028 2974600 69% /home a@a-laptop:~$ df a@a-laptop:~$ wodim --devices wodim: No such file or directory. Cannot open SCSI driver! For possible targets try 'wodim --devices' or 'wodim -scanbus'. For possible transport specifiers try 'wodim dev=help'. For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from the wodim documentation. a@a-laptop:~ ANY IDEAS AT ALL,YOU ALL,BEST a
A., Have you tried F2 and the Boot menu to see if the CDROM is listed ahead of the hard disk? You might also give Removable Drive priority so that a usb stick could also be used for your boot up device. Anyway, make a few tries, I have found it may take four start ups on average to get the live/install process to work. Also check the install disk for scratches, as they do wear out eventually. Good luck. Ted P.
Ted; cdrom listed ahead of hard disk: yes I have tried lives disks ubuntu and mint new from os disks. here a few command line searches perhaps will give you more ideas. a@a-laptop:~$ sudo mount /dev/sda1 mnt [sudo] password for a: a@a-laptop:~$ sudo fdisk -l Disk /dev/sda: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000c9cfd Device Boot Start End Blocks Id System /dev/sda1 * 2048 283731967 141864960 83 Linux /dev/sda2 304214014 312580095 4183041 5 Extended /dev/sda3 283731968 304211967 10240000 83 Linux /dev/sda5 304214016 312580095 4183040 82 Linux swap / Solaris Partition table entries are not in disk order a@a-laptop:~$ sudo mount /dev/sda1 mnt mount: /dev/sda1 already mounted or mnt busy mount: according to mtab, /dev/sda1 is already mounted on /home/a/mnt a@a-laptop:~$ wodim --devices wodim: No such file or directory. Cannot open SCSI driver! For possible targets try 'wodim --devices' or 'wodim -scanbus'. For possible transport specifiers try 'wodim dev=help'. For IDE/ATAPI devices configuration, see the file README.ATAPI.setup from the wodim documentation. a@a-laptop:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 149.1G 0 disk ├─sda1 8:1 0 135.3G 0 part / ├─sda2 8:2 0 1K 0 part ├─sda3 8:3 0 9.8G 0 part /home └─sda5 8:5 0 4G 0 part [SWAP] sr0 11:0 1 1024M 0 rom a@a-laptop:~$ best,a On 06/06/2015 02:32 PM, Ted Pomeroy wrote:
A., Have you tried F2 and the Boot menu to see if the CDROM is listed ahead of the hard disk? You might also give Removable Drive priority so that a usb stick could also be used for your boot up device. Anyway, make a few tries, I have found it may take four start ups on average to get the live/install process to work. Also check the install disk for scratches, as they do wear out eventually. Good luck. Ted P. _______________________________________________ nmglug mailing list nmglug@lists.nmglug.org http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org
a., I think there is more going on than I can figure out for you. But I have one observation - your home partition is very small. My home directory is about 8 GB and this is not a longstanding install, I can add about 500MB a month if I just accumulate downloads and photos, etc, so I expect it to grow to 20-50 GB. And from the description in lsblk it looks like you have an install that still doesn't boot or that boots and is uncooperative or broken, which is where you began. Check your boot-up parameters again and try to run a live session. Debian or Ubuntu current 32-bit versions should all work, or any Linux flavor you like. What was your original install version and method? Have you tried that to test the hardware? Are you willing to try a fresh install? That may be the best answer. You may be preserving some corrupt file that is breaking the system. Good luck , Ted P.
Ted; A fresh install would be fine,the question is how? the original install as either a downloaded iso or a live disc. The home install was the result of using the suggestion from an online. How do suggest proceeding with a fresh install? Best,a On 06/07/2015 02:14 PM, Ted Pomeroy wrote:
a., I think there is more going on than I can figure out for you. But I have one observation - your home partition is very small. My home directory is about 8 GB and this is not a longstanding install, I can add about 500MB a month if I just accumulate downloads and photos, etc, so I expect it to grow to 20-50 GB. And from the description in lsblk it looks like you have an install that still doesn't boot or that boots and is uncooperative or broken, which is where you began. Check your boot-up parameters again and try to run a live session. Debian or Ubuntu current 32-bit versions should all work, or any Linux flavor you like. What was your original install version and method? Have you tried that to test the hardware? Are you willing to try a fresh install? That may be the best answer. You may be preserving some corrupt file that is breaking the system. Good luck , Ted P. _______________________________________________ nmglug mailing list nmglug@lists.nmglug.org http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org
a., do you have a disk and some help to review the F2 settings? Or a usb image? If not, is there another Linux user in your area who can give you a disk or usb image. Since you boot into an accessible commandline, and your disk actually seems to be present in lsblk, try 'sudo reboot -n' when the disk is in the cd drive and use F12 or F2 to select the disk for booting. If that continues to fail, try a usb image or one on an SD card if you have an SD slot. Good luck, Ted P.
participants (2)
-
a -
Ted Pomeroy