UFS2 Partition mounten fehlgeschlagen?

RDSe · 27 März 2010

Hi Leute,

ich habe schon wieder ein Problem beim mounten einer Festplatte von mir... diesmal befürchte ich, dass es was ernstes ist. Vorneweg ich bin immer noch ein ziemlicher Anfänger in der BSD-World. Also ich habe heute versucht eine Festplatte von mir zu mounten... und das hat nicht ganz funktioniert.

Es ist eine Samsung HD501LJ (500GB). Auf der Festplatte habe ich zwei Partitionen:
1. NTFS 80GB mit TrueCrypt verschlüsselt
2. UFS2 mit rund 385 GB

Zugreifen wollte ich auf die UFS Partition und das lief nicht. Ich weiß schon mal, dass die Festplatte ansich in Ordnung ist... da ich auf die NTFS Partition (unter Windows) ohne Probleme zugreifen kann.

Nutzen tue ich DesktopBSD 1.6 (FreeBSD 6.3)...

Das Problem ist, dass ich meine UFS Partition nicht mehr mounten kann. Die Partition mounten versuche ich über das eine praktische DesktopBSD-Tool "Mount Control". Eine Fehlermeldung kommt vorerst nicht und gemountet wird es ebenfalls nicht. Stattdessen kommt beim Mount-Versuch ein merkwürdiges (relativ lautes) klicken... dieses wiederholt sich alle 2-3 Minuten. Erst nach ca. 10-15 Minuten bekomme ich dann die Meldung, dass das mounten fehlgeschlagen ist.

Was könnte man da machen?

______________

Falls es einem hilft ->
fdisk

******* Working on device /dev/ad4 *******
parameters extracted from in-core disklabel are:
cylinders=310101 heads=16 sectors/track=63 (1008 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=310101 heads=16 sectors/track=63 (1008 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 7 (0x07),(OS/2 HPFS, NTFS, QNX-2 (16 bit) or Advanced UNIX)
start 2048, size 94412800 (46100 Meg), flag 80 (active)
beg: cyl 0/ head 32/ sector 33;
end: cyl 1023/ head 13/ sector 24
The data for partition 2 is:
sysid 131 (0x83),(Linux native)
start 94430070, size 31230360 (15249 Meg), flag 0
beg: cyl 1023/ head 255/ sector 63;
end: cyl 1023/ head 254/ sector 63
The data for partition 3 is:
sysid 5 (0x05),(Extended DOS)
start 125660430, size 155669850 (76010 Meg), flag 0
beg: cyl 1023/ head 0/ sector 1;
end: cyl 1023/ head 254/ sector 63
The data for partition 4 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 281330280, size 31246425 (15257 Meg), flag 0
beg: cyl 1023/ head 255/ sector 63;
end: cyl 1023/ head 254/ sector 63

ls -l /dev/ad*

crw-rw---- 1 root mount 0, 94 26 Mär 23:15 /dev/ad4
crw-rw---- 1 root mount 0, 106 26 Mär 23:15 /dev/ad4s1
crw-rw---- 1 root mount 0, 109 26 Mär 23:15 /dev/ad4s2
crw-rw---- 1 root mount 0, 110 26 Mär 23:15 /dev/ad4s3
crw-rw---- 1 root mount 0, 111 26 Mär 23:15 /dev/ad4s4
crw-rw---- 1 root mount 0, 114 26 Mär 23:15 /dev/ad4s4a
crw-rw---- 1 root mount 0, 115 26 Mär 23:15 /dev/ad4s4b
crw-rw---- 1 root mount 0, 116 26 Mär 23:15 /dev/ad4s4c
crw-rw---- 1 root mount 0, 117 26 Mär 23:15 /dev/ad4s4d
crw-rw---- 1 root mount 0, 118 26 Mär 23:15 /dev/ad4s4e
crw-rw---- 1 root mount 0, 112 26 Mär 23:15 /dev/ad4s5
crw-rw---- 1 root mount 0, 113 26 Mär 23:15 /dev/ad4s6

dmesg

Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 6.3-RC2 #30: Sun Jan 6 01:54:42 UTC 2008
root@tinderbox.3c-consulting.lokal:/usr/obj/usr/src/sys/SMP
acpi_alloc_wakeup_handler: can't alloc wake memory
ACPI APIC Table: <DELL M08 >
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz (2194.52-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x6fa Stepping = 10
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Features2=0xe3bd<SSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM>
AMD Features=0x20100000<NX,LM>
AMD Features2=0x1<LAHF>
Cores per package: 2
real memory = 2145984512 (2046 MB)
avail memory = 2081812480 (1985 MB)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
ioapic0: Changing APIC ID to 2
ioapic0 <Version 2.0> irqs 0-23 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
hptrr: HPT RocketRAID controller driver v1.1 (Jan 6 2008 01:54:15)
acpi0: <DELL M08 > on motherboard
Timecounter "HPET" frequency 14318180 Hz quality 900
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
cpu0: <ACPI CPU> on acpi0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
p4tcc0: <CPU Frequency Thermal Control> on cpu0
cpu1: <ACPI CPU> on acpi0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
p4tcc1: <CPU Frequency Thermal Control> on cpu1
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
nvidia0: <GeForce 8600M GT> port 0xdf00-0xdf7f mem 0xfd000000-0xfdffffff,0xe0000000-0xefffffff,0xfa000000-0xfbffffff irq 16 at device 0.0 on pci1
nvidia0: [GIANT-LOCKED]
uhci0: <UHCI (generic) USB controller> port 0x6f20-0x6f3f irq 20 at device 26.0 on pci0
uhci0: [GIANT-LOCKED]
usb0: <UHCI (generic) USB controller> on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: <UHCI (generic) USB controller> port 0x6f00-0x6f1f irq 21 at device 26.1 on pci0
uhci1: [GIANT-LOCKED]
usb1: <UHCI (generic) USB controller> on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfed1c400-0xfed1c7ff irq 22 at device 26.7 on pci0
ehci0: [GIANT-LOCKED]
usb2: EHCI version 1.0
usb2: companion controllers, 2 ports each: usb0 usb1
usb2: <EHCI (generic) USB 2.0 controller> on ehci0
usb2: USB revision 2.0
uhub2: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub2: 4 ports with 4 removable, self powered
pcm0: <Intel 82801H High Definition Audio Controller> mem 0xfebfc000-0xfebfffff irq 21 at device 27.0 on pci0
pcib2: <ACPI PCI-PCI bridge> at device 28.0 on pci0
pci11: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> at device 28.1 on pci0
pci12: <ACPI PCI bus> on pcib3
pci12: <network> at device 0.0 (no driver attached)
pcib4: <ACPI PCI-PCI bridge> at device 28.3 on pci0
pci13: <ACPI PCI bus> on pcib4
uhci2: <UHCI (generic) USB controller> port 0x6f80-0x6f9f irq 20 at device 29.0 on pci0
uhci2: [GIANT-LOCKED]
usb3: <UHCI (generic) USB controller> on uhci2
usb3: USB revision 1.0
uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
uhci3: <UHCI (generic) USB controller> port 0x6f60-0x6f7f irq 21 at device 29.1 on pci0
uhci3: [GIANT-LOCKED]
usb4: <UHCI (generic) USB controller> on uhci3
usb4: USB revision 1.0
uhub4: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub4: 2 ports with 2 removable, self powered
uhci4: <UHCI (generic) USB controller> port 0x6f40-0x6f5f irq 22 at device 29.2 on pci0
uhci4: [GIANT-LOCKED]
usb5: <UHCI (generic) USB controller> on uhci4
usb5: USB revision 1.0
uhub5: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub5: 2 ports with 2 removable, self powered
ehci1: <EHCI (generic) USB 2.0 controller> mem 0xfed1c000-0xfed1c3ff irq 20 at device 29.7 on pci0
ehci1: [GIANT-LOCKED]
usb6: EHCI version 1.0
usb6: companion controllers, 2 ports each: usb3 usb4 usb5
usb6: <EHCI (generic) USB 2.0 controller> on ehci1
usb6: USB revision 2.0
uhub6: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub6: 6 ports with 6 removable, self powered
ugen0: OmniVision Technologies, Inc. -2640-07.07.20.3 Laptop Integrated Webcam, rev 2.00/1.00, addr 2
pcib5: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci3: <ACPI PCI bus> on pcib5
bfe0: <Broadcom BCM4401-B0 Fast Ethernet> mem 0xf9bfe000-0xf9bfffff irq 17 at device 0.0 on pci3
miibus0: <MII bus> on bfe0
bmtphy0: <BCM4401 10/100baseTX PHY> on miibus0
bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
bfe0: Ethernet address: 00:1c:23:91:b4:9f
fwohci0: <1394 Open Host Controller Interface> mem 0xf9bfd800-0xf9bfdfff irq 19 at device 1.0 on pci3
fwohci0: OHCI version 1.10 (ROM=0)
fwohci0: No. of Isochronous channels is 4.
fwohci0: EUI64 33:4f:c0:00:28:7d:10:70
fwohci0: Phy 1394a available S400, 1 ports.
fwohci0: Link S400, max_rec 2048 bytes.
firewire0: <IEEE1394(FireWire) bus> on fwohci0
fwe0: <Ethernet over FireWire> on firewire0
if_fwe0: Fake Ethernet address: 32:4f:c0:7d:10:70
fwe0: Ethernet address: 32:4f:c0:7d:10:70
fwe0: if_start running deferred for Giant
sbp0: <SBP-2/SCSI over FireWire> on firewire0
fwohci0: Initiate bus reset
fwohci0: BUS reset
fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode
firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
firewire0: bus manager 0 (me)
pci3: <base peripheral> at device 1.1 (no driver attached)
pci3: <base peripheral> at device 1.2 (no driver attached)
pci3: <base peripheral> at device 1.3 (no driver attached)
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ATA controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x6fa0-0x6faf irq 16 at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
atapci1: <Intel ATA controller> port 0x6eb0-0x6eb7,0x6eb8-0x6ebb,0x6ec0-0x6ec7,0x6ec8-0x6ecb,0x6ee0-0x6eef,0xeff0-0xefff irq 17 at device 31.2 on pci0
ata2: <ATA channel 0> on atapci1
ata3: <ATA channel 1> on atapci1
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
acpi_lid0: <Control Method Lid Switch> on acpi0
acpi_button0: <Power Button> on acpi0
acpi_button1: <Sleep Button> on acpi0
acpi_acad0: <AC Adapter> on acpi0
battery0: <ACPI Control Method Battery> on acpi0
acpi_tz0: <Thermal Zone> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64,0x62,0x66 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model GlidePoint, device ID 0
pmtimer0 on isa0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xcd7ff,0xcd800-0xcffff on isa0
ppc0: parallel port not found.
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 8250 or not responding
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
uhub7: Broadcom BCM2045B2, class 9/0, rev 2.00/1.00, addr 2
uhub7: 3 ports with 0 removable, bus powered
ugen1: Broadcom Corp BCM2045, rev 2.00/1.00, addr 3
ukbd0: Broadcom Corp product 0x4502, rev 2.00/1.00, addr 4, iclass 3/1
kbd2 at ukbd0
ums0: Broadcom Corp product 0x4503, rev 2.00/1.00, addr 5, iclass 3/1
ums0: 3 buttons.
ums1: Wacom Co.,Ltd. CTE-450, rev 2.00/1.13, addr 2, iclass 3/1
ums1: 3 buttons and Z dir.
Timecounters tick every 1.000 msec
hptrr: no controller detected.
acd0: DVDR <PBDS DVD+/-RW DS-8W1P/BD1B> at ata0-master UDMA33
acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00
ad4: 152627MB <Hitachi HTS541616J9SA00 SB4OC7KP> at ata2-master UDMA33
pcm0: <HDA Codec: Sigmatel (Unknown)>
pcm0: <HDA Driver Revision: 20071129_0050>
acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00
SMP: AP CPU #1 Launched!
cd0 at ata0 bus 0 target 0 lun 0
cd0: <PBDS DVD+-RW DS-8W1P BD1B> Removable CD-ROM SCSI-0 device
cd0: 33.000MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not present
Trying to mount root from ufs:/dev/ad4s4a
umass0: JMicron USB to ATA/ATAPI Bridge, rev 2.00/1.00, addr 3
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <SAMSUNG HD501LJ 0-12> Fixed Direct Access SCSI-2 device
da0: 40.000MB/s transfers
da0: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C)
WARNING: /media/UFS (385 GB) was not properly dismounted
g_vfs_done():da0s1[READ(offset=6144000, length=16384)]error = 5
WARNING: /media/UFS (385 GB) was not properly dismounted

df

Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/ad4s4a 253678 78810 154574 34% /
devfs 1 1 0 100% /dev
/dev/ad4s4d 507630 141822 325198 30% /var
/dev/ad4s4e 13856570 9649850 3098196 76% /usr
/usr/tmp 13856570 9649850 3098196 76% /tmp
procfs 4 4 0 100% /proc
linprocfs 4 4 0 100% /usr/compat/linux/proc

waki87 · 27 März 2010

WARNING: /media/UFS (385 GB) was not properly dismounted

Ich würde erst einmal ein fsck probieren.

Oh, und die Platte ist bei dir /dev/da0, nicht ad*.

RDSe · 27 März 2010

ah, okay....

#ls -l /dev/da0

crw-rw---- 1 root mount 0, 137 27 Mär 09:01 /dev/da0

_______________

Ich weiß nicht, ob ich den Befehl richtig angewendet habe... habe einfach nur fsck in der Konsole angewendet... aber anscheinend hat es nicht geholfen...

Code:

** /dev/ad4s4a (NO WRITE)
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
2061 files, 39404 used, 87435 free (275 frags, 10895 blocks, 0.2% fragmentation)
** /dev/ad4s4d (NO WRITE)
** Last Mounted on /var
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? no

24523 files, 71154 used, 182661 free (12813 frags, 21231 blocks, 5.0% fragmentation)
** /dev/ad4s4e (NO WRITE)
** Last Mounted on /usr
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
UNREF FILE I=188435  OWNER=didi MODE=100600
SIZE=84897 MTIME=Mar 27 09:03 2010
CLEAR? no

UNREF FILE I=188438  OWNER=didi MODE=100600
SIZE=65 MTIME=Mar 27 09:04 2010
CLEAR? no

UNREF FILE I=188446  OWNER=didi MODE=100600
SIZE=84650 MTIME=Mar 27 09:03 2010
CLEAR? no

UNREF FILE I=188447  OWNER=didi MODE=100600
SIZE=90914 MTIME=Mar 27 09:03 2010
CLEAR? no

UNREF FILE I=188448  OWNER=didi MODE=100600
SIZE=86129 MTIME=Mar 27 09:03 2010
CLEAR? no

UNREF FILE I=188449  OWNER=didi MODE=100600
SIZE=25029 MTIME=Mar 27 09:04 2010
CLEAR? no

UNREF FILE I=188450  OWNER=didi MODE=100600
SIZE=27943 MTIME=Mar 27 09:04 2010
CLEAR? no

UNREF FILE I=188451  OWNER=didi MODE=100600
SIZE=12017 MTIME=Mar 27 09:04 2010
CLEAR? no

UNREF FILE I=188452  OWNER=didi MODE=100600
SIZE=4896 MTIME=Mar 27 09:04 2010
CLEAR? no

UNREF FILE I=188453  OWNER=didi MODE=100600
SIZE=12067 MTIME=Mar 27 09:04 2010
CLEAR? no

** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? no

329012 files, 4824639 used, 2103641 free (102705 frags, 250117 blocks, 1.5% fragmentation)

Anscheinend wurde /dev/da0 gar nicht geprüft... aber

Code:

#fsck /dev/da0
fsck: Could not determine filesystem type

# fsck -y /dev/da0
fsck: Could not determine filesystem type

bringt auch nichts... ich mache bestimmt was falsch?

Kamikaze · 27 März 2010

Erst einmal versuchst du fsck auf das ganze Device anzuwenden. Was gibt es überhaupt für Paritionen auf dem Device?

# ls /dev/da0*

Das Device kann aber auch ohne Partitionstabelle komplett UFS-formatiert sein.

Dann wäre der Befehl fsck /dev/da0 richtig gewesen. Wenn fsck in so einem Fall nicht den Partitionstyp erkennt muss der manuell mit angegeben werden:

# fsck -t ufs /dev/<device>

RDSe · 27 März 2010

Wow, ihr beiden seit sooo geil. Läuft nun und ich kann auf die Partition zugreifen.

Folgende Partitionen:
# ls /dev/da0*

Code:

/dev/da0        /dev/da0s1      /dev/da0s1a     /dev/da0s1c     /dev/da0s2      /dev/da0s5

Ausgeführt habe ich
fsck -t ufs /dev/dev/da0s1

Code:

** /dev/da0s1

CANNOT READ BLK: 12000
CONTINUE? [yn] y

THE FOLLOWING DISK SECTORS COULD NOT BE READ: 12009,
BAD SUMMARY INFORMATION
CONTINUE? [yn] y

** Last Mounted on /media/UFS (385 GB)
** Phase 1 - Check Blocks and Sizes
INCORRECT BLOCK COUNT I=23198738 (119584 should be 384)
CORRECT? [yn] y

** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
LINK COUNT DIR I=2  OWNER=root MODE=40775
SIZE=512 MTIME=Sep 22 16:51 2009  COUNT 20 SHOULD BE 19
ADJUST? [yn] y

ZERO LENGTH DIR I=21361664  OWNER=root MODE=40775
SIZE=0 MTIME=Apr 26 00:25 2009
CLEAR? [yn] y

ZERO LENGTH DIR I=22821895  OWNER=1002 MODE=40775
SIZE=0 MTIME=Apr 26 00:25 2009
CLEAR? [yn] y

ZERO LENGTH DIR I=22845450  OWNER=1002 MODE=40775
SIZE=0 MTIME=Apr 26 00:25 2009
CLEAR? [yn] y

ZERO LENGTH DIR I=22868999  OWNER=1002 MODE=40775
SIZE=0 MTIME=Apr 26 00:25 2009
CLEAR? [yn] y

UNREF FILE  I=23198735  OWNER=1002 MODE=100644
SIZE=66583936 MTIME=Mar 26 21:22 2009
RECONNECT? [yn] y

NO lost+found DIRECTORY
CREATE? [yn] y

UNREF FILE  I=23198736  OWNER=1002 MODE=100644
SIZE=69208708 MTIME=Mar 26 21:45 2009
RECONNECT? [yn] y

UNREF FILE  I=23198737  OWNER=1002 MODE=100644
SIZE=60980350 MTIME=Mar 26 21:08 2009
RECONNECT? [yn] y

UNREF FILE  I=23198738  OWNER=1002 MODE=100644
SIZE=61175732 MTIME=Mar 26 21:20 2009
RECONNECT? [yn] y

ZERO LENGTH DIR I=28121140  OWNER=root MODE=40775
SIZE=0 MTIME=Apr 26 00:25 2009
CLEAR? [yn] y

ZERO LENGTH DIR I=28733445  OWNER=root MODE=40775
SIZE=0 MTIME=Apr 26 00:25 2009
CLEAR? [yn] y

ZERO LENGTH DIR I=29086727  OWNER=root MODE=40775
SIZE=0 MTIME=Apr 26 00:25 2009
CLEAR? [yn] y

ZERO LENGTH DIR I=29204566  OWNER=root MODE=40775
SIZE=0 MTIME=Apr 26 00:25 2009
CLEAR? [yn] y

** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? [yn] y

SUMMARY INFORMATION BAD
SALVAGE? [yn] y

BLK(S) MISSING IN BIT MAPS
SALVAGE? [yn] y

94875 files, 133772875 used, 62109369 free (10649 frags, 7762340 blocks, 0.0% fragmentation)

***** FILE SYSTEM MARKED CLEAN *****

***** FILE SYSTEM WAS MODIFIED *****

Kann mir einer noch sagen, ob ich hier soweit alles richtig gemacht habe... also im Grunde habe ich während des Vorgangs immer nur mit y bestätigt... war es soweit richtig?

waki87 · 27 März 2010

Jap. Jetzt mountest du das Filesystem, zum Beispiel mit:

Code:

mount /dev/da0s1 /mnt

und schaust gegebenenfalls noch nach, was für Dateien im lost+found-Ordner sind.

Elwood · 27 März 2010

Du kannst bei solchen Aktionen auch fsck -y benutzen. Dadurch wird automatisch y bei den SALVAGE-Fragen gesetzt.

RDSe · 27 März 2010

Super, ich danke euch allen.

UFS2 Partition mounten fehlgeschlagen?

RDSe

Member

waki87

Well-Known Member

RDSe

Member

Kamikaze

Warrior of Sunlight

RDSe

Member

waki87

Well-Known Member

Elwood

Naiver Mutmaßlicher

RDSe

Member

Wir schützen deine Privatsphäre