flyboy129
Tue Dec 16, 2014 8:12:27 pm
Hello all, have been running Zorin 6.* 64 bit (12.04 based) for a couple years now without a hitch. Well, all good things must come to an end (or hopefully not), and last night I thought it had happened. Was just browsing on firefox when the program froze. I minimized it and checked Zorin, it was still running at that moment. Tried to close firefox, then the OS froze (cpu indicator on bottom of screen was stuck, menu button wouldn't work, only cursor would move). "No big deal," I thought. Shut off computer, then restarted. Selected Zorin from grub (also have ubuntu 14.04 as a backup just in case. Good thing, btw) and started zorin. Got the initramfs busybox screen. First time I encountered it. Shut down, and tried again. Same thing.
Tried booting into recovery mode with no luck. So, I booted 13.04 and began my quest. I found out about the boot from live cd or gparted and run the commands:
sudo fdisk -l|grep Linux|grep -Ev 'swap'
then, used:
sudo dumpe2fs /dev/sda* | grep superblock
However, no matter which partition I selected to check; 5 (root) or 6 (home), I ended up with:
dumpe2fs 1.** (date,date,2011) as the reply. No superblocks listed as should have been something like this:
Primary superblock at 0, Group descriptors at 1-6
Backup superblock at 32768, Group descriptors at 32769-32774
Backup superblock at 98304, Group descriptors at 98305-98310
Backup superblock at 163840, Group descriptors at 163841-163846
Backup superblock at 229376, Group descriptors at 229377-229382
Backup superblock at 294912, Group descriptors at 294913-294918
Backup superblock at 819200, Group descriptors at 819201-819206
Backup superblock at 884736, Group descriptors at 884737-884742
Backup superblock at 1605632, Group descriptors at 1605633-1605638
Backup superblock at 2654208, Group descriptors at 2654209-2654214
Backup superblock at 4096000, Group descriptors at 4096001-4096006
Backup superblock at 7962624, Group descriptors at 7962625-7962630
Backup superblock at 11239424, Group descriptors at 11239425-11239430
Backup superblock at 20480000, Group descriptors at 20480001-20480006
Backup superblock at 23887872, Group descriptors at 23887873-23887878
the other commands:
sudo fsck -b 32768 /dev/sda*,
mount /dev/sda* /mnt,
sudo cd /mnt,
sudo ls -l
never gave me anything and didn't do any good at this point or so it seemed.
However, after trying the above commands, I tried rebooting to recovery and recovery mode actually booted!
I tried to check file systems and got an error on both root and home partitions (sorry, i didn't write them down, since I could see I had taken a baby step forward and was determined). So, I tried a normal boot. I got an error screen that asked something along the lines of f (fix), i (ignore), and m (manually boot).
First I tried fix, but nothing really happened, so I tried manual boot. It booted into the command prompt, so I ran the sudo commands one more time (with one major difference).
This time, even though the command: 'sudo dumpe2fs /dev/sda* | grep superblock' gave me the same: 'dumpe2fs 1.** (date,date,2011)' as the reply, when I ran the next command using partition '6' (home) in place of all '*':
sudo fsck -b 32768 /dev/sda*, I did get something similar to this:
fsck 1.40.2 (12-Jul-2007)
e2fsck 1.40.2 (12-Jul-2007)
/dev/sda* was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
The next thing that happened gave me hope. My screen filled with numbers passing by in very rapid sequences. While I couldn't really read the whole numbers, I could tell they were getting progressively larger (1*******,2*******,3*******,etc) and I figured the commands were doing their job and checking things. After a few minutes of waiting, I got up and fixed me a midnight snack (I had been at this for nearly 3 hours
), and came back to something like this:
Free blocks count wrong for group #241 (32254, counted=32253).
Fix? yes
Free blocks count wrong for group #362 (32254, counted=32248).
Fix? yes
Free blocks count wrong for group #368 (32254, counted=27774).
Fix? yes
Except it started at a really low number like #001 and I hit y about a couple hundred times (there were lots of free blocks count wrongs to fix, folks).
In the end, I ended up with somethong like:
/dev/sda*: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda*: 59586/30539776 files (0.6% non-contiguous), 3604682/61059048 blocks
I had did this to partition 6 (home), and tried once again to recovery boot. Tried to check files. It gave me an error still!
However, it was only giving me a root error (partition 5), home checked out okay. Progress!!!!!
I once again booted normally till I hit the '(f) fix, (i) ignore, (m) manual' boot screen.
Did all of the commands again with my root partition '(5)' in place of the '*' in 'sda*'.
Waited again, and did all of those steps a second time.
You know what? Something worked! I am typing this using firefox on my Zorin OS!
First thing I did last night was back up all of my important pics, files, and documents to a usb drive (just in case), but now am kind of scared to have to power down should it decide to do something weird. 
I will have an update come through tommorrow (wed) and will probably need to power down before some of those patches will take effect. My question (after all of this huge novel);
Do I need to do anything else to make all correct before I reboot?
Anything I should check?
I really, really, REAAAAALLLLYYYYY, don't want to have to go through all of that again anytime soon.
Thank you all for the time you spent reading this, and for your help.
Tried booting into recovery mode with no luck. So, I booted 13.04 and began my quest. I found out about the boot from live cd or gparted and run the commands:
sudo fdisk -l|grep Linux|grep -Ev 'swap'
then, used:
sudo dumpe2fs /dev/sda* | grep superblock
However, no matter which partition I selected to check; 5 (root) or 6 (home), I ended up with:
dumpe2fs 1.** (date,date,2011) as the reply. No superblocks listed as should have been something like this:
Primary superblock at 0, Group descriptors at 1-6
Backup superblock at 32768, Group descriptors at 32769-32774
Backup superblock at 98304, Group descriptors at 98305-98310
Backup superblock at 163840, Group descriptors at 163841-163846
Backup superblock at 229376, Group descriptors at 229377-229382
Backup superblock at 294912, Group descriptors at 294913-294918
Backup superblock at 819200, Group descriptors at 819201-819206
Backup superblock at 884736, Group descriptors at 884737-884742
Backup superblock at 1605632, Group descriptors at 1605633-1605638
Backup superblock at 2654208, Group descriptors at 2654209-2654214
Backup superblock at 4096000, Group descriptors at 4096001-4096006
Backup superblock at 7962624, Group descriptors at 7962625-7962630
Backup superblock at 11239424, Group descriptors at 11239425-11239430
Backup superblock at 20480000, Group descriptors at 20480001-20480006
Backup superblock at 23887872, Group descriptors at 23887873-23887878
the other commands:
sudo fsck -b 32768 /dev/sda*,
mount /dev/sda* /mnt,
sudo cd /mnt,
sudo ls -l
never gave me anything and didn't do any good at this point or so it seemed.
However, after trying the above commands, I tried rebooting to recovery and recovery mode actually booted!
I tried to check file systems and got an error on both root and home partitions (sorry, i didn't write them down, since I could see I had taken a baby step forward and was determined). So, I tried a normal boot. I got an error screen that asked something along the lines of f (fix), i (ignore), and m (manually boot).
First I tried fix, but nothing really happened, so I tried manual boot. It booted into the command prompt, so I ran the sudo commands one more time (with one major difference).
This time, even though the command: 'sudo dumpe2fs /dev/sda* | grep superblock' gave me the same: 'dumpe2fs 1.** (date,date,2011)' as the reply, when I ran the next command using partition '6' (home) in place of all '*':
sudo fsck -b 32768 /dev/sda*, I did get something similar to this:
fsck 1.40.2 (12-Jul-2007)
e2fsck 1.40.2 (12-Jul-2007)
/dev/sda* was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
The next thing that happened gave me hope. My screen filled with numbers passing by in very rapid sequences. While I couldn't really read the whole numbers, I could tell they were getting progressively larger (1*******,2*******,3*******,etc) and I figured the commands were doing their job and checking things. After a few minutes of waiting, I got up and fixed me a midnight snack (I had been at this for nearly 3 hours
), and came back to something like this:Free blocks count wrong for group #241 (32254, counted=32253).
Fix? yes
Free blocks count wrong for group #362 (32254, counted=32248).
Fix? yes
Free blocks count wrong for group #368 (32254, counted=27774).
Fix? yes
Except it started at a really low number like #001 and I hit y about a couple hundred times (there were lots of free blocks count wrongs to fix, folks).
In the end, I ended up with somethong like:
/dev/sda*: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda*: 59586/30539776 files (0.6% non-contiguous), 3604682/61059048 blocks
I had did this to partition 6 (home), and tried once again to recovery boot. Tried to check files. It gave me an error still!
However, it was only giving me a root error (partition 5), home checked out okay. Progress!!!!!
I once again booted normally till I hit the '(f) fix, (i) ignore, (m) manual' boot screen.
Did all of the commands again with my root partition '(5)' in place of the '*' in 'sda*'.
Waited again, and did all of those steps a second time.
You know what? Something worked! I am typing this using firefox on my Zorin OS!
First thing I did last night was back up all of my important pics, files, and documents to a usb drive (just in case), but now am kind of scared to have to power down should it decide to do something weird. I will have an update come through tommorrow (wed) and will probably need to power down before some of those patches will take effect. My question (after all of this huge novel); Do I need to do anything else to make all correct before I reboot?
Anything I should check?
I really, really, REAAAAALLLLYYYYY, don't want to have to go through all of that again anytime soon.
Thank you all for the time you spent reading this, and for your help.
