I'm running Debian x64 on a Sparc based V240 Sun Server. The situation is the following:
I had Solaris 8 Installed on this machine on Disk1. I then decided to try installing Debian x64 on the 2nd Disk following instructions I found in the FAQ or the Debian Comprehensive manual on the Debian Website. I was also able to successfully boot into Debian. And just for convenience sake, I exchanged the disk with debian on it with the disk with Solaris on it so Disk1 was now Disk2 and vice-versa. This happened about 3 weeks ago and I actually have really bad memory so I can't tell if I tried booting Solaris and was able to boot into it as well. So far, so good!
During boot-up however, I see these errors:
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
This is obviously on the Disk with Solaris on it and that is NOT an ext3 FS. Should I just ignore these errors?
Thanks in advance,