bug-parted
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Assertion (dev->lenght >0) at linuc.c:697 in function init_file failed.


From: Jan Docekal
Subject: Assertion (dev->lenght >0) at linuc.c:697 in function init_file failed. GNU parted 1.6.3
Date: Fri, 3 Oct 2003 18:22:47 +0200
User-agent: KMail/1.5

Assertion (dev->lenght >0) at linuc.c:697 in function init_file failed.  GNU 
parted 1.6.3

Hi,

I got this error while formating a new disk. Unfortunately I am not able to 
give you the exact steps to reproduce the problem, since i did not remeber 
exactly what i did, but i hope that thisis the correct sequence

# parted
select /dev/hda
mkpart primary ext_3 0 -0
quit
# mkfs -t ext_3 /dev/hda1
# e2label /dev/hda3 /repository
# mkdir /repository
# emacs /etc/fstab (adding: LABEL=/Repositry /repsotiry ext3 dafaults 1 2 )
# mount /repository (this went OK)

during reboot, however the disk did not mount and i transfered into disk 
rescue mode, this is the situation I think the error (assert) was proveoked)

# parted
select /dev/hda1 (this caused the assert)


After som experiments/investigations i noticed that the drive (not the 
partition) did not have the lopp label while the disk created during install 
had the msdos label after setting the label to msdos in parted with "mklabel 
msdos" it was possible to create a partition that was able to be mounted 
automatically during reboot following the steps above. Perhaps this is 
another problem in parted (i.e. creating partitions that does not mount 
during the boot process) or it might be a problem elsewhere.

I'm using red hat 9 (i386) soltek mainbord and a AMD 2500+ processor with 512 
MB ram.

Best regards & good luck,

Jan.

P.S. This was the first time i used parted, so I would allready now want to 
appologices if I used wrong terminology or have written something missleading 
(I tried to be as thorough as possible). In any case you are welcome to ask 
for clarifications (unfortunately i will not be able to try to recreate the 
problem, since the disk is allready in production, unless you send me a new 
disk ofcource :-)






reply via email to

[Prev in Thread] Current Thread [Next in Thread]