https://bugzilla.novell.com/show_bug.cgi?id=349529
User mmrazik@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=349529#c3
--- Comment #3 from Martin Mrazik
Hi, I have had a look for the log files. There are 4 files in the YaST2 folder in /var/log. These are disk_sda perl-BL-standalone-log volume_info y2log If you can tell me how I can get the to you it would be great.
I cannot copy them to memory stick because system is not set up yet (that media is not recognised).
The media should be recognized at this point by kernel. If you plug your stick into your computer you should be able to see something like this in the output of "dmesg" command: USB Mass Storage support registered. usb-storage: waiting for device to settle before scanning scsi 6:0:0:0: Direct-Access USB 2.0 Flash Disk 0.00 PQ: 0 ANSI: 2 sd 6:0:0:0: [sdb] 7897087 512-byte hardware sectors (4043 MB) sd 6:0:0:0: [sdb] Write Protect is off sd 6:0:0:0: [sdb] Mode Sense: 00 00 00 00 sd 6:0:0:0: [sdb] Assuming drive cache: write through sd 6:0:0:0: [sdb] 7897087 512-byte hardware sectors (4043 MB) sd 6:0:0:0: [sdb] Write Protect is off sd 6:0:0:0: [sdb] Mode Sense: 00 00 00 00 sd 6:0:0:0: [sdb] Assuming drive cache: write through sdb: sdb1 sd 6:0:0:0: [sdb] Attached SCSI removable disk sd 6:0:0:0: Attached scsi generic sg2 type 0 usb-storage: device scan complete In this case you should be able to run the following commands: mkdir /mnt/flash mount /dev/sdb1 /mnt/flash Now you should be able to copy your logs to /mnt/flash Another option would be to create a separate partition on your HDD and copy the logs there. You should be able to read them later from your working system.
I cannot copy them to CD because the system is not set up to recognise CD. I cannot copy them to floppy disk because there is no FD in the machine. I cannot copy them across the network because the network is not set up. I cannot email you from that machine because the network is not set up.
let me know what I can do. otherwise you will have to look through the code to find where an Error 22 is generated and look at the conditions that cause that. Bear in mind that at this moment I have done nothing except sun with the defaults in the installation program therefore this a) should not happen and b) it has failed because of something you guys have put together - not something I have messed with post installation.
Maybe someone at your end can try to run the install process with a machine with a single SATA drive in it and see what happens.
I'm also using single SATA drive system and I don't have this problem with my 10.3 installation. Thats the reason why we need your y2logs. Otherwise its almost impossible to find out what is different in your particular case. 2nd e-mail: On Wednesday 02 of January 2008 16:00:25 you wrote:
Martin, I there any progress on this bug. I have sent you a couple of emails about the information you have requested - which I simply cannot seem to forward to you. At the moment I have a machine tied up which will not install Open SUSE. I have not done anything except to allow the machine to run the install program using defaults so it should work. If it doesn't it must be something in the install process that is wrong. I have looked at the GRUB website and the list of error commands and this all seems to point to a problem at your end. I am happy to help you sort out the problem but I cannot do so if I don't get further feedback from you.
See above.
Regards Steve
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.