https://bugzilla.novell.com/show_bug.cgi?id=381671
User sheeryjay@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=381671#c49
--- Comment #49 from Jaromir Sir 2008-05-15 18:41:47 MST ---
Tejun, I did try as requested.
Indeed my SATA drive was accessible from command shell without any modprobe
etc. commands, only simple mount was required and I saw contents of LiveCD
disk.
When I tried to run the commands you requested I had to use my iRiver T60
instead of USB stick (but works as mass storage). I had it connected and
started all the time since boot up and was unable to connect to it (/dev/sda1
seems to be first partition of my SATA disk and other files in /dev didnt seem
to be of usb stick relevancy .. only some called usb storage something (might
have some - or similar characters in them) and they wouldnt mount).
I had to repeat steps several times (countdown to 120s till reboot is quite
short, it would be really useful if the countdown could be stopped somehow) and
i think that on 4th reboot I tried to type df on console (I was going to try
mount my disk partition and use it to store requested info), then maybe just
mount command without arguments (not sure though) and it (very surprisingly)
resumed loading liveCD (while it has on tty0 screen already written that "drive
not ready" and maybe also "Couldn´t find CD image configuration file" (not
sure if it managed to get to this point as I was on tty1 at that time)).
So after successful start of KDE, I simply mounted usb stick and copied
requested information, they will follow in next 3 messages (isn't there a way
to insert them in only 1 post?).
I also tried to repeat the steps involved (df and successful loading of KDE)
but to no avail, so I am kinda puzzled what actually happened and if df had any
relevance to what happened. I'll try what happens with beta3 once I download it
today/tomorrow. If you need anything else, just say, I'd be glad to help.
--
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.