Graham S. Jarvis wrote:
> Hello all,
>
> I ran a test yesterday (on a net4801):
> 1. I took the 0.3.0 iso and wrote it to a CD
> 2. I flashed a CF which previously had 0.2.8 on it with 0.3.0 from the CD
> 3. I replaced the CF in my net4801 with the newly flashed one
> 4. I booted.
>
> During the boot I saw this:
>
> [snip]
> SCSI device sda: 501760 512-byte hdwr sectors (257 MB)
> sda: Write Protect is off
> sda: assuming drive cache: write through
> SCSI device sda: 501760 512-byte hdwr sectors (257 MB)
> sda: Write Protect is off
> sda: assuming drive cache: write through
> sda:<7>usb-storage: queuecommand called
> sda1
> Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
> Checking /dev/hda1
> Unexpected filesystem inconsistency on /dev/hda1 - run e2fsck manually.
> Checking /dev/sda1
> /dev/sda1 is clean
> /dev/sda1 is clean
> [snip]
>
> What I'd like to know is:
> a. Why is there a "Unexpected filesystem inconsistency on /dev/hda1"
> b. Why sda1 is detected and checked twice?
>
> Thanks,
>
> -Graham S: Jarvis-
>
Graham,
That was a bug in the 0.3.0 release. I wasn't properly evaluating the
status code of e2fsck, and e2fsck needed to be upgraded to support
filesystems with labels.
sda1 is detected because that is what astkd= is set as. I don't know
why it would be checking it twice. That is odd.
"astup testing" will get you the new init script and e2fsck binary to
fix that problem.
--
Kristian Kielhofner
_______________________________________________
Astlinux-users mailing list
[email protected]
http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to [EMAIL
PROTECTED]
