UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
On an upgrade from 7.10 to 8.04 Ubuntu refused the restart....on a maintenance shell it registered „fsck died with exit status 8...file system check failed, please repair manually“. Apparently its a problem with hda7, home folder. Can somebody please hel me out here?
well you need to run fsck hda7. two ways boot up in recovery mode or if you are booted into a system as root umount /dev/hda7 then fsck -y /dev/hda7 some systems require you to type e2fsck instead of fsck.
Reiserfs journal '/dev/hda7' in blocks [18..8211]: 0 transactions replayed
Checking internal tree..finished
Comparing bitmaps..finished
Checking Semantic tree:
finished
No corruptions found
There are on the filesystem:
Leaves 1381
Internal nodes 10
Directories 1310
Other files 7356
Data block pointers 141685 (2568 of them are zero)
Safe links 0
###########
reiserfsck finished at Sun Mar 8 04:57:40 2009
The system won't recognise /dev/hda7 because on upgrade to 8.04 partition allocations/names change....
Current fdisk -l output, live CD 8.04.2
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3ddf3dde
Device Boot Start End Blocks Id System
/dev/sda2 * 2 9729 78140160 f W95 Ext'd (LBA)
/dev/sda5 2 6375 51199123+ 83 Linux
/dev/sda6 6376 6694 2562336 82 Linux swap / Solaris
/dev/sda7 6695 7331 5116671 83 Linux
Disk /dev/sdb: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x1fdc1fdb
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 12749 102406311 7 HPFS/NTFS
/dev/sdb2 12750 38913 210162330 f W95 Ext'd (LBA)
/dev/sdb5 12750 22311 76806733+ 7 HPFS/NTFS
/dev/sdb6 22312 25499 25607578+ 7 HPFS/NTFS
/dev/sdb7 25500 25742 1951866 82 Linux swap / Solaris
/dev/sdb8 25743 28302 20563168+ 83 Linux
/dev/sdb9 28303 37863 76798701 83 Linux
/dev/sdb10 37864 38913 8434093+ 83 Linux
ubuntu@ubuntu:~$
....but when fdisk -l is exercised on bootup/recovery mode sdb1-10 becomes sda1-10 and sda2...becomes becomes sdb2....
Is this normal?
...but when fdisk -l is exercised on bootup/recovery mode sdb1-10 becomes sda1-10 and sda2...becomes becomes sdb2....
Is this normal?
yes this is normal the ubuntu to system does not use hda or any hdx any more. this was to keep the auto mount of external drives simple. It is just there scripts and for them it is much more simple for there custom kernel to treat everything as a scsi device it forces the system to read the device then load it. either at boot or when plugging in an external device.
O.k.,but why change designation from sda to sdb....it just makes things more difficult!
Try assigning your partitions in fstab by their uuids. Ubuntu now sets up fstab and grub's menu.lst by uuids. To get the uuids for your partitions run:
Code:
sudo blkid
or
Code:
ls -l /dev/disk/by-uuid/
Then change your fstab for /dev/sda7 so it looks like the entry for /dev/hda5. Something like:
Works with UUID's, now booting into Hardy.
That was my "test" installation. I`ve just upgraded my "working" system (also "Hardy")
Problem...
boot menu still shows „Ubuntu 7.10 Kernel 2.6.22.16“
..$ cat /etc/issue
Ubuntu 8.04.2 \n \l
..$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 8.04.2
Release: 8.04
Codename: hardy
HUH?!
Last edited by stoppage; 03-15-2009 at 03:30 PM.
Reason: spelling
Works with UUID's, now booting into Hardy.
That was my "test" installation. I`ve just upgraded my "working" system (also "Hardy")
Problem...
boot menu still shows „Ubuntu 7.10 Kernel 2.6.22.16“
..$ cat /etc/issue
Ubuntu 8.04.2 \n \l
Does the grub menu list the entries for Hardy? I assume it is since the output of cat /etc/issue ans lsb_release -a shows Hardy.
You can just edit the /boot/grub/menu.lst and remove the entries for Ubuntu 7.10. Add any entries for Hardy to menu.lst if you need to.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.