Bug 48462

Summary: anaconda crash when one of disk had bad sectors in superblock
Product: [Retired] Red Hat Linux Reporter: Need Real Name <m.hejna>
Component: anacondaAssignee: Brent Fox <bfox>
Status: CLOSED WONTFIX QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-07-21 20:45:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Need Real Name 2001-07-10 18:36:08 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.2-2 i586)

Description of problem:
After selectin what disk I want format (not checking for bad blocks).
Anaconda crash. I think it was due to hdd1 (not formated or mounted --
<unused>) had bad blocks in superblock.

How reproducible:
Always

Steps to Reproduce:
1. Have hdd1 with bad blocks in superblock (ext2 filesystem)
2. Run anaconda
3. Make install on hda2 with choosing hdd1 not for use <unused> in
   selecting mount points. After selecting format hda2 (don`t check
   for bad blocks) anaconda crash.
   I also tried making hdd1 FAT16 entry in fdisk
   and anacaonda still crash
	

Actual Results:  anaconda crash (list included)

Expected Results:  anaconda should continue installation process

Additional info:

My disks:

Disk /dev/hda: 255 heads, 63 sectors, 790 cylinders
Units = cylinders of 16065 * 512 bytes
 
   Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *         1       128   1028128+   6  FAT16
/dev/hda2           129       638   4096575   83 
Linux                      
/dev/hda3           639       671    265072+  82  Linux swap
/dev/hda4           672       790    955867+   5  Extended
/dev/hda5           672       790    955836    6  FAT16

Disk /dev/hdd: 255 heads, 63 sectors, 4865 cylinders
Units = cylinders of 16065 * 512 bytes
 
   Device Boot    Start       End    Blocks   Id  System
/dev/hdd1             1      2415  19398456    83  Linux
/dev/hdd2          2416      4830  19398487+  83  Linux
/dev/hdd3          4831      4865    281137+  83  Linux


note: I tried it with hdd1 as FAT16 (not on disk, but in fdisk entry)
and anaconda still craches.

I first run anaconda just fine (hdd1 was good). After 30 minutes
using my fresh Redhat Linux 7.1 hdd1 crash (bad block in superblock).
I`ve run e2fsck several time and also mke2fs.
Then I reinstall Linux again (Linux crash when hdd1 fail and I don`t
want these errors on hda1 when I can simply avoid them for 30 minutes
of my time).
anaconda then crash as I have reported.
Then I tried install second time. anaconda crash (on the same place
-- chosing format hda2 without check for bad blocks).
Then I run anaconda for third time and in fdisk change hdd1 entry
to 6 (FAT16). anaconda still crash. Then I remove hdd from computer
and anaconda ends fine.

anaconda output (when crash):

Traceback (innermost last):
  File "/usr/bin/anaconda", line 520, in ?
    intf.run(todo, test = test)
  File "/var/tmp/anaconda-7.1//usr/lib/anaconda/gui.py", line 391, in run
    self.icw.run ()
  File "/var/tmp/anaconda-7.1//usr/lib/anaconda/gui.py", line 879, in run
    mainloop ()
  File "/usr/lib/python1.5/site-packages/gtk.py", line 2554, in mainloop
    _gtk.gtk_main()
  File "/usr/lib/python1.5/site-packages/gtk.py", line 125, in __call__
    ret = apply(self.func, a)
  File "/var/tmp/anaconda-7.1//usr/lib/anaconda/gui.py", line 481, in
nextClicked
    next = self.currentScreen.getNext ()
  File "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/format_gui.py", line 21,
in getNext
    rc = self.todo.fstab.checkFormatting(self.todo.intf.messageWindow)
  File "/var/tmp/anaconda-7.1//usr/lib/anaconda/fstab.py", line 57, in
checkFormatting
    if preexisting and isValidExt2(drive):
  File "/var/tmp/anaconda-7.1//usr/lib/anaconda/fstab.py", line 38, in
isValidExt2
    buf = os.read(fd, 2048)
OSError: [Errno 5] Chyba vstupu/v}stupu

Local variables in innermost frame:
file: /tmp/hdd1
device: hdd1
fd: 17

ToDo object:
(itodo
ToDo
p1
(dp2
S'resState'
p3
S''
sS'progressWindow'
p4
NsS'setupFilesystems'
p5
I1
sS'monitorVsync'
p6
S''
sS'videoCardStateNode'
p7
S''
sS'serial'
p8
I0
sS'ddruidReadOnly'
p9
I0
sS'bootdisk'
p10
I0
sS'videoRamState'
p11
S''
sS'monitorOriginalName'
p12
S''
sS'language'
p13
(itodo
Language
(dp14
S'langInfoByName'
p15
(dp16
S'Arabic (Yemen)'
p17
(S'ar_YE'
S'iso06'
S'LatArCyrHeb-16'
tsS'Spanish (Argentina)'
p18
(S'es_AR'
S'iso01'
S'lat0-sun16'
tsS'Italian (Italy)'
p19
(S'it_IT@euro'
S'iso15'
S'lat0-sun16'
tsS'Arabic (Lebanon)'
p20
(S'ar_LB'
S'iso06'
S'LatArCyrHeb-16'
tsS'Spanish (Guatemala)'
p21
(S'es_GT'
S'iso01'
S'lat0-sun16'
tsS'Malay (Malaysia)'
p22
(S'ms_MY'
S'iso01'
S'lat0-sun16'
tsS'Arabic (Libyan Arab Jamahiriya)'
p23
(S'ar_LY'
S'iso06'
S'LatArCyrHeb-16'
tsS'Arabic (Oman)'
p24
(S'ar_OM'
S'iso06'
S'LatArCyrHeb-16'
tsS'Arabic (Iraq)'
p25
(S'ar_IQ'
S'iso06'
S'LatArCyrHeb-16'
tsS'Arabic (Kuwait)'
p26
(S'ar_KW'
S'iso06'
S'LatArCyrHeb-16'
tsS'English (South Africa)'
p27
(S'en_ZA'
S'iso01'
S'lat0-sun16'
tsS'French (Switzerland)'
p28
(S'fr_CH'
S'iso01'
S'lat0-sun16'
tsS'Arabic (Bahrein)'
p29
(S'ar_BH'
S'iso06'
S'LatArCyrHeb-16'
tsS'Croatian'
p30
(S'hr_HR'
S'iso02'
S'lat2-sun16'
tsS'French (France)'
p31
(S'fr_FR@euro'
S'iso15'
S'lat0-sun16'
tsS'Greenlandic (Greenland)'
p32
(S'kl_GL'
S'iso01'
S'lat0-sun16'
tsS'Korean (Republic of Korea)'
p33
(S'ko_KR.euckr'
S'iso01'
S'lat0-16'
tsS'Ukrainian'
p34
(S'uk_UA'
S'koi8-u'
S'cyr-sun16'
tsS'Spanish (Mexico)'
p35
(S'es_MX'
S'iso01'
S'lat0-sun16'
tsS'Greek'
p36
(S'el_GR'
S'iso07'
S'gr.f16'
tsS'Spanish (El Salvador)'
p37
(S'es_SV'
S'iso01'
S'lat0-sun16'
tsS'Spanish (Peru)'
p38
(S'es_PE'
S'iso01'
S'lat0-sun16'
tsS'Spanish (Honduras)'
p39
(S'es_HN'
S'iso01'
S'lat0-sun16'
tsS'Spanish (Costa Rica)'
p40
(S'es_CR'
S'iso01'
S'lat0-sun16'
tsS'English (Denmark)'
p41
(S'en_DK'
S'iso01'
S'lat0-sun16'
tsS'Dutch (Netherlands)'
p42
(S'nl_NL@euro'
S'iso15'
S'lat0-sun16'
tsS'Serbian (Yugoslavia)'

Comment 1 Brent Fox 2001-07-11 01:45:15 UTC
I think one of two things is happening.  
1) Maybe you have a bad hard drive.  If there's something physically wrong with
the drive, there's not much we can do.
2) Maybe there's something wrong with the disk handling code in anaconda.  The
existing disk handling code is being re-worked, so if this is causing the
problem you are seeing, you shouldn't see this in the future.  

I would recommend trying the install one more time, except use fdisk instead of
Disk Druid to make your partitions.  After you make the partitions, try
rebooting and then see if anaconda can see your drive.

Comment 2 Brent Fox 2001-07-20 22:05:42 UTC
Closing due to inactivity. Please reopen if you have more information.

Comment 3 Need Real Name 2001-07-21 20:34:08 UTC
reply to last mail:
I can`t reproduse bug. I`ve already returned that bad disk. But:
I used fdisk (I like it). But I didn`t reboot computer after using fdisk in
anaconda.
But I ran anaconda two times.
First time I didn`t use fdisk (all disk was partitioned right).
Second time I changed type of hdd1 (which has bad sectors in superblock)
to FAT16 (type 6). I hoped that this force anaconda to NOT look on this drive.

The problem as I see it is that anaconda look on drives (I mean partitions)
which
I don`t want. I was installing on hda2, I did`t want anaconda look on hdd1/2/3.
These three drives was marked as <unused> but anaconda looks on these drives
(mainly on hdd1) (I think -- because it crash).
Or anaconda should be more robust when finds bad drive. It didn`t crash due to
disk malfunction (as locked bus), but there was some "exception execution" in
code.
I was still able to save report to fd0 and restart computer by clicking on some
button.



Comment 4 Need Real Name 2001-07-21 20:45:03 UTC
I am sorry I didn`t reply to your second question:
anaconda saw all disks right every time. (hda and hdd were already partitioned
right).

I was also able to select mount points (hda2 as /, hda5 as swap, all others as
<unused>), after that (and after selecting that only hda2 should be formated)
anaconda crashed (as I already sad I think it was due to bad sectors in hdd1
-- which (disk hdd1) had nothing to do with install process! I`ve used
this disk only as backup and even if it was ext2 I wanted to be <unused>.


Comment 5 Michael Fulbright 2001-07-27 20:20:15 UTC
I recommend you disconnect any hardware which is not performing nominally when
attempting to install.  We simply cannot support installing on hardware which is
not working.