Skip to contentSkip to conversation

nit picking UDF

DISCUSSION David Ford 2 participants 2 messages Mar 27, 2003

lore
Share & tools
lore

David Ford

author
#0 lore raw

ACPI: (supports S0 S1 S4 S4bios S5)
You didn't specify the type of your ufs filesystem

mount -t ufs -o ufstype=sun|sunx86|44bsd|old|hp|nextstep|netxstep-cd|openstep ...

Quoted 1 line
Quoted 1 line
Quoted 1 line

WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old

ufs_read_super: bad magic number
UDF-fs DEBUG fs/udf/lowlevel.c:65:udf_get_last_session: CDROMMULTISESSION not supported: rc=-25 UDF-fs DEBUG fs/udf/super.c:1472:udf_fill_super: Multi-session=0
UDF-fs DEBUG fs/udf/super.c:460:udf_vrs: Starting at sector 16 (2048 byte sectors)
UDF-fs DEBUG fs/udf/super.c:1208:udf_check_valid: Failed to read byte 32768. Assuming open disc. Skipping validity check UDF-fs DEBUG fs/udf/misc.c:286:udf_read_tagged: location mismatch block 256, tag 18 != 256
UDF-fs DEBUG fs/udf/super.c:1262:udf_load_partition: No Anchor block found
UDF-fs: No partition found (1)
found reiserfs format "3.6" with standard journal

Is all this blurbage necessary? I don't even have a disc in the 'rom drive because it causes the kernel to lock up hard on bootup if I do. Right at the moment, the 'rom isn't even plugged in.

David

#1 lore raw
Quoted 22 lines

ACPI: (supports S0 S1 S4 S4bios S5)
You didn't specify the type of your ufs filesystem

mount -t ufs -o ufstype=sun|sunx86|44bsd|old|hp|nextstep|netxstep-cd|openstep ...

Quoted 1 line
Quoted 1 line
Quoted 1 line

WARNING<<< Wrong ufstype may corrupt your filesystem, default is

ufstype=old
ufs_read_super: bad magic number
UDF-fs DEBUG fs/udf/lowlevel.c:65:udf_get_last_session:
CDROMMULTISESSION not supported: rc=-25
UDF-fs DEBUG fs/udf/super.c:1472:udf_fill_super: Multi-session=0 UDF-fs DEBUG fs/udf/super.c:460:udf_vrs: Starting at sector 16 (2048 byte sectors)
UDF-fs DEBUG fs/udf/super.c:1208:udf_check_valid: Failed to read byte 32768. Assuming open disc. Skipping validity check
UDF-fs DEBUG fs/udf/misc.c:286:udf_read_tagged: location mismatch block 256, tag 18 != 256
UDF-fs DEBUG fs/udf/super.c:1262:udf_load_partition: No Anchor block found
UDF-fs: No partition found (1)
found reiserfs format "3.6" with standard journal

Quoted 3 lines

Is all this blurbage necessary? I don't even have a disc in the 'rom drive
because it causes the kernel to lock up hard on bootup if I do. Right at
the moment, the 'rom isn't even plugged in.

Is this with 2.5.66?

I also get an oops during boot on 2.5.66 if I have
hdc=ide-scsi
on the kernel boot command line. I have to remove it to boot 2.5.66. I don't mind editing lilo.conf, but the oops shouldn't be what makes me edit it.

~Randy