firstly, apologies for cross-posting! Please let me know if this is frowned upon and I will stop this behaviour :)
Now, for those who've been following my adventures with Installing Debian Lenny 5.0.7 64-bit on a Sparc machine which already had Solaris 8 on one of the disks, I have additional observations and concerns. The disks in the machine are 72GB. However, after following the section regading Section 6.3.2, “Partitioning and Mount Point Selection”, I observe the following during boot-up:
Checking file systems...fsck 1.41.3 (12-Oct-2008)
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb1
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
/dev/mapper/DebSparcx64--01-home: recovering journal
/dev/mapper/DebSparcx64--01-home: clean, 16/1998848 files, 170528/7987200 blocks
/dev/mapper/DebSparcx64--01-tmp: recovering journal
/dev/mapper/DebSparcx64--01-tmp: clean, 13/97536 files, 22602/389120 blocks
/dev/mapper/DebSparcx64--01-usr: recovering journal
/dev/mapper/DebSparcx64--01-usr: clean, 15539/305216 files, 114625/1220608 blocks
/dev/mapper/DebSparcx64--01-var: recovering journal
/dev/mapper/DebSparcx64--01-var: clean, 1579/183264 files, 59952/732160 blocks
fsck died with exit status 8
failed (code 8).
File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. Please repair the file system manually. failed!
A maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. (warning).
Give root password for maintenance
Setting kernel variables (/etc/sysctl.conf)...done.
Mounting lo[ 5608.111431] VFS: Can't find an ext2 filesystem on dev sdb1.
cal filesystems...mount: wrong f[ 5608.213904] kjournald starting. Commit interval 5 seconds
s type, bad opti[ 5608.309930] EXT3 FS on dm-5, on, bad superblointernal journal
ck on /dev/sdb1,[ 5608.390272] EXT3-fs: mounted filesystem with ordered data mode.
missing[ 5608.497014] kjournald starting. Commit interval 5 seconds
codepage or hel[ 5608.579045] EXT3 FS on dm-4, per program, or internal journal
[ 5608.664245] EXT3-fs: mounted filesystem with ordered data mode.
In some cases useful info is[ 5608.781223] kjournald starting. Commit interval 5 seconds
found in syslog[ 5608.873900] EXT3 FS on dm-1, - try
mesg | tail or [ 5608.954854] EXT3-fs: mounted filesystem with ordered data mode.
[ 5609.082190] kjournald starting. Commit interval 5 seconds
[ 5609.097021] EXT3 FS on dm-2, internal journal
[ 5609.097032] EXT3-fs: mounted filesystem with ordered data mode.
Activating swapfile swap..[ 5609.323560] Adding 4886512k swap on /dev/mapper/DebSparcx64--01-swap_1. Priority:-1 extents:1 across:4886512k
Once the system gets to the login prompt and I login and run 'df -h', I see
/dev/mapper/DebSparcx64--01-root 256M 78M 166M 32% /
tmpfs 2.0G 0 2.0G 0% /lib/init/rw
udev 10M 1.1M 9.0M 11% /dev
tmpfs 2.0G 0 2.0G 0% /dev/shm
/dev/mapper/DebSparcx64--01-home 30G 177M 29G 1% /home
/dev/mapper/DebSparcx64--01-tmp 368M 11M 339M 3% /tmp
/dev/mapper/DebSparcx64--01-usr 4.6G 372M 4.0G 9% /usr
/dev/mapper/DebSparcx64--01-var 2.8G 189M 2.5G 8% /var
The question now is, if you look carefully, I only have ~37GB showing as partitioned. Where is the remaining (72-37 GB) space? This was easy to see in 'format' command in Solaris but doing all sort of cart-wheels in Debian/Linux, I don't know what the heck these dm-* partitions are, which seem to be where this missing space is, and how do I get to it to create a valid partition out of it and mount it and use it?
Thanks so much in advance,