Welcome, Guest. Please login or register.

Author Topic: NetBSD partition corruption  (Read 1088 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline the_leanderTopic starter

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 3448
    • Show only replies by the_leander
    • http://www.extropia.co.uk/theleander/
NetBSD partition corruption
« on: September 10, 2003, 04:26:28 AM »
Hi there,

Thumper, my BSD mp3 jukebox recently came up with the following error, I was wondering if anyone here knew how to get it repaired...

swapctl: adding /dev/wd0b as swap device at priority 0

Automatic boot in progress: Starting file system checks.

/dev/rwd0a: file system is clean; not checking

/dev/rwd0e: file system is clean; not checking

/dev/rwd1a: INCORRECT BLOCK COUNT I=512209 (84 should be 7696)

CORRECTED

/dev/rwd1a: INCORRECT BLOCK COUNT I=512223 (148 should be 9120)

CORRECTED

19668911 DUP I=3825156

/dev/rwd1a: UNEXPECTED INCONSISTENCY; RUN fsck_ffs

MANUALLY.

panic: amap_wipeout: corrupt amap

Stopped in fsck_ffs at cpu_Debugger+0x4:   leave

db>


At this point I'm totally stuck, so any help would be greatly apreciated, atm I'm playing around with the idea of creating a morphix live cd and correcting the problem from outside the setup itself as I just can't get the netbsd setup on their to play ball.
Blessed Be,
Alan Fisher - the_leander

[SIGPIC]http://www.extropia.co.uk/theleander/[/SIGPIC]
 

Offline csirac_

  • Full Member
  • ***
  • Join Date: Feb 2002
  • Posts: 154
    • Show only replies by csirac_
Re: NetBSD partition corruption
« Reply #1 on: September 10, 2003, 07:02:50 AM »
I'm totally unfamiliar with BSD, but if that was a linux box the first thing I'd do is boot off a CD and run fsck from there.

- Paul
 

Offline the_leanderTopic starter

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 3448
    • Show only replies by the_leander
    • http://www.extropia.co.uk/theleander/
Re: NetBSD partition corruption
« Reply #2 on: September 14, 2003, 02:46:14 AM »
Heh, the guy who set it up rigged it so it could only boot into BSD...

However, I managed to get it to boot into single user mode, and restart the system cleanly. After the restart FSCK managed to fix the problems with the drive... all 20 of them. I lost two mp3's and I'm pretty sure at least one of the dirs was a bit mauled by it all but all in all not too bad.

Next time, I will use a journaling file system rather than the one its got now - ffs.

Nice to be able to listen to my music again after so long!

Blessed Be,
Alan Fisher - the_leander

[SIGPIC]http://www.extropia.co.uk/theleander/[/SIGPIC]