This is a static archive of the old Zorin Forum.

The information below may be outdated. Visit the new Zorin Forum here ›

If you have registered on the old forum, you will need to create an account on the new forum.

System won't boot up after upgrading to OS12

vaw5

Fri Jun 02, 2017 1:33:20 pm

Computer hardware (custom-built):
Processor: 2x AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ : 2399.95MHz
Memory: 1942MB
Storage: sda1 - 214 GB, of which 98 GB free
sda 5 - 16 GB, of which 13 GB free - (ext4 partition)
Graphics: Gallium 0.4 on NV67
X11 Vendor: The X.Org Foundation
BIOS: Date: 01/10/2008 Vendor: Phoenix Technologies, LTD (http://www.phoenix.com) Version: 6.00 PG
OS - dual boot Windows XP and Zorin

I was a user of Zorin OS9 core, dual-booting with Windows XP. I upgraded to Zorin OS12 core but afterwards my computer would no longer boot up at all. It just gives an error message:
Boot from CD:
error: file '/boot/grub/i386-pc/normal.mod' not found.
Entering rescue mode...
grub rescue>


In general the upgrade worked out as described in the instructions, and everything followed as expected (I am fairly new to Linux though). However there are a couple of things that I noticed about the installation procedure :
- I wasn't asked about resizing or creating any new partitions or anything, although I had done the deletes (of linux-swap partition and so forth) as instructed. Perhaps the install software accepted the partition used for OS 9
- when it said on screen, I think, that the OS update was complete, I may have accidentally brushed the End, Delete or Arrow keys area of the keyboard. It's possible that I mis-hit a key in doing so. Just after that, unless it was coincidence, the window closed and the text-only screen came up with the message:
sdb No caching mode page found (or similar wording)
sdb Assuming drive cache: write through (or similar)
sda Ubuntu carrying out installation ... (or similar)


This message carried on slowly flashing on and off for well over half an hour, so I assumed an error and turned off the power on the machine. I thought I had given it long enough to close of its own accord.

In the past, when using OS9, I may have seen some reference to the GRUB when updating, but did not know what it meant. So perhaps the initial mistake goes back a while.

So far I have tried using Boot-repair-disk https://help.ubuntu.com/community/Boot-Repair, as suggested by Aiiaiiio in another (closed) thread (thanks for your suggestions, Aiiaiiio)
http://zoringroup.com/forum/viewtopic.php?f=5&t=12517
Boot-repair looks promising, but it will not proceed beyond this error message:
Please close all your package managers (Software Center, Update Manager, Synaptic... ) then try again. Yet I am not using the package managers that it implies. I have tried deleting the 'lock' file at /var/lib/dpkg/lock (suggested at Ubuntu) but this makes no difference.

Any ideas welcome.

Swarfendor437

Sat Jun 03, 2017 12:27:33 pm

Hi, Can you please boot into live mode using Zorin 9, start GParted and submit a screenshot?

Thanks.

vaw5

Tue Jun 06, 2017 12:51:09 pm

Hello Swarfendor437,

Thanks for your message.
The screenshot of my partitions is attached below.

Since posting, I have received some further info on my enquiry thread at Ubuntu Forums.org about about possibly using Ubuntu Boot-Repair-Disk (advanced options). Of course, this is mainly designed for Ubuntu, not Zorin.
https://ubuntuforums.org/showthread.php ... 351&page=2

Please see below for references to other material referred to.

Perhaps I could just uninstall Zorin OS12 and reinstall (nothing stored on it).

To give you further information, one of the Summary files produced by Boot-Repair can be viewed here:
http://paste.ubuntu.com/24747143/

Also below are are some results I have obtained from the ‘grub rescue>’ prompt.

For the time being I am continuing to use the computer using Puppy Linux booted from CD, with settings kept on squash file on the hard disk.

Hope this is of use.

Many thanks.


Information obtained from ‘grub rescue>’ prompt:

grub rescue> set
cmdpath = (hd0)
prefix = (hd0,msdos5)/boot/grub
root = hd0,msdos5

grub rescue> ls
(hd0) (hd0,msdos6) (hd0,msdos5) (hd0,msdos1) (fd0)

grub rescue> ls (hd0,1)
(hd0,1): Filesystem is unknown

grub rescue> ls (hd0,6)
(hd0,6): Filesystem is unknown

grub rescue> ls (hd0,5)
(hd0,5): Filesystem is ext2.

grub rescue> ls /
. / .. / lost+found / etc / media / var / bin / boot / dev / home / lib / mnt / opt / proc / oot / run / sbin / snap / srv / sys / tmp / usr / initrd.img vmlinuz

grub rescue> ls(hd0,5)/boot/
./ ../ efi/ grub/ System.map-4.4.0-47-generic abi-4.4.0-47-generic config-4.4.0-47-generic initrd.img-4.4.0-47-generic memtest86+ .bin memtest86+ .elf memtest86+ multiboot.bin vmlinuz-4.4.0-47-generic

grub rescue> ls (hd0,5)/boot/grub/
./ ../ gfxblacklist.txt unicode.pf2

grub rescue> ls (hd0,5)/usr/share/doc/grub-common/examples/
./ ../ grub.cfg




References
https://help.ubuntu.com/community/Resto ... Bootloader
https://help.ubuntu.com/community/Grub2 ... ken_System
https://help.ubuntu.com/community/Boot-Repair
https://sourceforge.net/p/boot-repair/home/Home/
https://help.ubuntu.com/community/Grub2 ... ch_.26_Set
http://www.howtogeek.com/114884/how-to- ... wont-boot/

Swarfendor437

Mon Jun 12, 2017 7:57:20 pm

Sorry for any delay - for some reason your last post needed to be 'approved' when normally only first posts need to be approved then you should have no issues - will raise with zorink.

Right, back on track. Just looking at your screenshot of your partitions would appear to be the biggest issue - not enough room for Zorin to install correctly. Can you boot into Windows at all or is the GRUB error preventing you from doing so? I would boot whatever GNU/Linux live disc you are using and run GParted to delete your linux swap, then the Zorin partition, then your extended partition. Increase your NTFS partition that has XP on it back to its full allocation size and apply. Next to get your XP to boot again, hopefully you have an XP disc to hand - without it it won't be recoverable. Boot with XP CD into 'Repair Mode' when it gets to installation choice.

"Actually, you should probably use your XP CD and boot to the Recovery console. Then use the FIXMBR and FIXBOOT commands in that and you should be ok."

from here:

https://www.experts-exchange.com/questi ... -boot.html

If it doesn't you need to login to your C:\ drive at the DOS Prompt using XP CD and choosing repair and enter:

Code:
fdisk /mbr


Let's get back to a working Windows before progressing - keep us posted! ;) :D

vaw5

Fri Jun 23, 2017 8:28:56 am

Many thanks, Swarfendor437.
It's worked! Windows XP boots fine now! Used Windows CD to carry out repair.
Linux-swap, and ext4 partition deleted. (Extended partition not deleted yet.)
Gparted screen shot attached.

Swarfendor437

Fri Jun 23, 2017 7:23:25 pm

OK. Great News! Please boot into Windows, schedule a chkdsk on next reboot to check hard drive for errors then after reboot from chkdsk check to see if the hard drive needs defragmenting. Then report back here. Thanks

vaw5

Mon Jun 26, 2017 3:53:58 pm

Thanks, Swarfendor437.
I've performed the CheckDisk and Defragmentation. When using CheckDisk I selected the options to repair bad sectors as part of the check. Results are below.

Chkdsk results as recorded in EventViewer:


Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 31 unused index entries from index $SII of file 0x9.
Cleaning up 31 unused index entries from index $SDH of file 0x9.
Cleaning up 31 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.

224577708 KB total disk space.
118905200 KB in 288544 files.
127396 KB in 17885 indexes.
0 KB in bad sectors.
843520 KB in use by the system.
65536 KB occupied by the log file.
104701592 KB available on disk.

4096 bytes in each allocation unit.
56144427 total allocation units on disk.
26175398 allocation units available on disk.

Internal Info:
50 a0 07 00 bc ac 04 00 72 44 06 00 00 00 00 00 P.......rD......
c6 6a 00 00 03 00 00 00 36 06 00 00 00 00 00 00 .j......6.......
da 79 b6 2c 00 00 00 00 b2 58 f9 ff 00 00 00 00 .y.,.....X......
68 58 97 7f 00 00 00 00 7a 94 7c 7c 1b 00 00 00 hX......z.||....
a4 e8 cc 52 03 00 00 00 be 06 e5 8a 20 00 00 00 ...R........ ...
60 02 0e 8f 00 00 00 00 90 38 07 00 20 67 04 00 `........8.. g..
00 00 00 00 00 c0 65 59 1c 00 00 00 dd 45 00 00 ......eY.....E..

Windows has finished checking your disk.
Please wait while your computer restarts.

Defragmentation log:
Volume (C:)
Volume size = 214 GB
Cluster size = 4 KB
Used space = 114 GB
Free space = 99.85 GB
Percent free space = 46 %

Volume fragmentation
Total fragmentation = 0 %
File fragmentation = 0 %
Free space fragmentation = 0 %

File fragmentation
Total files = 288,546
Average file size = 553 KB
Total fragmented files = 22
Total excess fragments = 387
Average fragments per file = 1.00

Pagefile fragmentation
Pagefile size = 2.00 GB
Total fragments = 1

Folder fragmentation
Total folders = 17,884
Fragmented folders = 1
Excess folder fragments = 0

Master File Table (MFT) fragmentation
Total MFT size = 488 MB
MFT record count = 308,943
Percent MFT in use = 61 %
Total MFT fragments = 3

--------------------------------------------------------------------------------
Fragments File Size Files that cannot be defragmented
2 15 KB \Documents and Settings\...
4 31 KB \Documents and Settings\...
6 36 KB \Documents and Settings\...
4 38 KB \Documents and Settings\...
5 40 KB \Documents and Settings\...
3 44 KB \Documents and Settings\...
3 59 KB \Documents and Settings\...
4 130 KB \Documents and Settings\...
3 171 KB \Documents and Settings\...
6 4 MB \Documents and Settings\...
282 26 MB \Documents and Settings\...

Screen shot after defragmenting:
I have defragmented several times, but there is still a bit of blue over on the right-hand side of the display. I don't know if ideally it is supposed to be all white on that side or not.

Swarfendor437

Mon Jun 26, 2017 4:37:59 pm

I shouldn't worry too much about the white space as it is only a graphical representation of what is where. So if your results are 'clean' and fragmentation appears to be less than 10% it looks healthy enough.
Now use Disk Management in XP to claim back the lost space at the end of the Drive, wait for it to complete the operation and restart your computer. Go back into Disk Management and select C:\ drive and use the tool to 'shrink' the volume, letting Windows decide to shrink it and let us know the size of the free space that is created once you have done this. Thanks.

vaw5

Fri Jun 30, 2017 2:24:48 pm

I have been learning about Disk Management and think I see how to claim back the unallocated space, using the command prompt:

>diskpart
>list volume
>select volume 1
>extend
[with no size specified, so that Primary Partition C will extend through all the the 18.17 GB of unallocated space back to the end of the disk]

If I have understood this properly, I am ready to go ahead with this step.

But, as for the next step, I can't see a 'shrink' command in the menus. I have only seen references to it in Microsoft help pages about Windows Vista or later.

So shall I hold on this step - or does the 'shrink' command show up after completing step one?

Thanks!

Swarfendor437

Sat Jul 01, 2017 10:23:17 am

Hi, You could also use GParted in live mode of Zorin to extend your ntfs partition to the end. Once you have extended your partitions to the end reboot into Windows to make sure all is well before shrinking the partition. ;) :D

vaw5

Fri Jul 07, 2017 7:56:57 am

Successfully extended NTFS partition, except for a tiny bit at the end - see screen-shot, it just shows up at the end, a couple of MB. I had selected to have 0 MB space after the partition though.

I selected alignment as ‘cylinder’ and not ‘MiB’, (I did this since it’s Windows XP with MSDos partition table.) Perhaps that is to do with it.

I ran GParted again to try to remove it, but it’s still there. (Logs shown below.) Shall I just ignore it?

Windows XP Diskpart utility didn’t work, by the way. It gave an error message: ‘Diskpart failed to extend the volume. Please make sure the volume is valid for extending.’

GParted was good - they gave a lot of tips about preparation on their ‘help’ page. I spend quite a lot of time on this and sorted out a lot of the disk contents, which was worth it.

Window has booted up fine since.

Just wondering what is referred to in the log - ‘You might resize at 81151377408 bytes or 81152 MB (freeing 168905 MB).’


------------------------------------------------------------------------------------------------
LOG FOR FIRST RUN

GParted 0.16.1

Libparted 3.1
Grow /dev/sda1 from 214.17 GiB to 232.88 GiB 00:00:51 ( SUCCESS )

calibrate /dev/sda1 00:00:00 ( SUCCESS )

path: /dev/sda1
start: 63
end: 449155490
size: 449155428 (214.17 GiB)
check file system on /dev/sda1 for errors and (if possible) fix them 00:00:12 ( SUCCESS )

ntfsresize -P -i -f -v /dev/sda1

ntfsresize v2012.1.15AR.1 (libntfs-3g)
Device name : /dev/sda1
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 229967573504 bytes (229968 MB)
Current device size: 229967579136 bytes (229968 MB)
Checking for bad sectors ...
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 81151 MB (35.3%)
Collecting resizing constraints ...
Estimating smallest shrunken size supported ...
File feature Last used at By inode
$MFT : 137516 MB 0
Multi-Record : 229877 MB 9
$MFTMirr : 125025 MB 1
Compressed : 204842 MB 46703
Sparse : 106121 MB 80269
Ordinary : 204379 MB 9475
You might resize at 81150763008 bytes or 81151 MB (freeing 148817 MB).
Please make a test run using both the -n and -s options before real resizing!
grow partition from 214.17 GiB to 232.88 GiB 00:00:00 ( SUCCESS )

old start: 63
old end: 449155490
old size: 449155428 (214.17 GiB)
new start: 63
new end: 488392064
new size: 488392002 (232.88 GiB)
check file system on /dev/sda1 for errors and (if possible) fix them 00:00:12 ( SUCCESS )

ntfsresize -P -i -f -v /dev/sda1

ntfsresize v2012.1.15AR.1 (libntfs-3g)
Device name : /dev/sda1
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 229967573504 bytes (229968 MB)
Current device size: 250056705024 bytes (250057 MB)
Checking for bad sectors ...
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 81151 MB (35.3%)
Collecting resizing constraints ...
Estimating smallest shrunken size supported ...
File feature Last used at By inode
$MFT : 137516 MB 0
Multi-Record : 229877 MB 9
$MFTMirr : 125025 MB 1
Compressed : 204842 MB 46703
Sparse : 106121 MB 80269
Ordinary : 204379 MB 9475
You might resize at 81150763008 bytes or 81151 MB (freeing 148817 MB).
Please make a test run using both the -n and -s options before real resizing!
grow file system to fill the partition 00:00:27 ( SUCCESS )

run simulation 00:00:13 ( SUCCESS )

ntfsresize -P --force --force /dev/sda1 --no-action

ntfsresize v2012.1.15AR.1 (libntfs-3g)
Device name : /dev/sda1
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 229967573504 bytes (229968 MB)
Current device size: 250056705024 bytes (250057 MB)
New volume size : 250056700416 bytes (250057 MB)
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 81151 MB (35.3%)
Collecting resizing constraints ...
Schedule chkdsk for NTFS consistency check at Windows boot time ...
Resetting $LogFile ... (this might take a while)
Updating $BadClust file ...
Updating $Bitmap file ...
Updating Boot record ...
The read-only test run ended successfully.
real resize 00:00:14 ( SUCCESS )

ntfsresize -P --force --force /dev/sda1

ntfsresize v2012.1.15AR.1 (libntfs-3g)
Device name : /dev/sda1
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 229967573504 bytes (229968 MB)
Current device size: 250056705024 bytes (250057 MB)
New volume size : 250056700416 bytes (250057 MB)
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 81151 MB (35.3%)
Collecting resizing constraints ...
Schedule chkdsk for NTFS consistency check at Windows boot time ...
Resetting $LogFile ... (this might take a while)
Updating $BadClust file ...
Updating $Bitmap file ...
Updating Boot record ...
Syncing device ...
Successfully resized NTFS on device '/dev/sda1'.


========================================

LOG FOR SECOND RUN

GParted 0.16.1

Libparted 3.1
resize/move /dev/sda1 (new and old partition have the same size and position. Hence continuing anyway) 00:00:12 ( SUCCESS )

calibrate /dev/sda1 00:00:00 ( SUCCESS )

path: /dev/sda1
start: 63
end: 488392064
size: 488392002 (232.88 GiB)
check file system on /dev/sda1 for errors and (if possible) fix them 00:00:12 ( SUCCESS )

ntfsresize -P -i -f -v /dev/sda1

ntfsresize v2012.1.15AR.1 (libntfs-3g)
Device name : /dev/sda1
NTFS volume version: 3.1
Cluster size : 4096 bytes
Current volume size: 250056700416 bytes (250057 MB)
Current device size: 250056705024 bytes (250057 MB)
Checking for bad sectors ...
Checking filesystem consistency ...
Accounting clusters ...
Space in use : 81152 MB (32.5%)
Collecting resizing constraints ...
Estimating smallest shrunken size supported ...
File feature Last used at By inode
$MFT : 137516 MB 0
Multi-Record : 229877 MB 9
$MFTMirr : 125025 MB 1
Compressed : 204842 MB 46703
Sparse : 106121 MB 80269
Ordinary : 204379 MB 9475
You might resize at 81151377408 bytes or 81152 MB (freeing 168905 MB).
Please make a test run using both the -n and -s options before real resizing!
resize/move partition 00:00:00 ( SUCCESS )

new and old partition have the same size and position. Hence skipping this operation

----------------------------------------------------------------------------------------------------

Swarfendor437

Fri Jul 07, 2017 11:56:24 am

Will Windows Disk Management not auto-shrink? I must admit that I have only used Disk Management to shrink using Windows recommendations with Windows 7. ;)

vaw5

Fri Jul 07, 2017 9:48:56 pm

I couldn't find any menu link to auto-shrink at all. When I did an internet search, references to it that I saw seemed to refer not to Windows XP but to Windows 7.

PS Seems to be some info via web search about this though:
https://www.google.co.uk/?gfe_rd=cr&ei= ... Windows+XP

Swarfendor437

Mon Jul 10, 2017 12:09:49 pm

Hi, Take a look at this thread re GParted as the possible way forward:

https://superuser.com/questions/379853/ ... -partition

GParted comes as a separate OS/Live Disk but be sure to read all the links in the above thread. ;) :D