[Bug 228813] New: Automatic system repair from install media can't do anything if / is on XFS
https://bugzilla.novell.com/show_bug.cgi?id=228813 Summary: Automatic system repair from install media can't do anything if / is on XFS Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: admin@eregion.de QAContact: jsrain@novell.com I use XFS as my filesystem of choice, and the automatic system repair on the installation media always fails with "no valid xfs filesystem". This has been going on since at least 10.0. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=228813 jsuchome@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsuchome@novell.com Status|NEW |NEEDINFO Info Provider| |admin@eregion.de ------- Comment #1 from jsuchome@novell.com 2006-12-15 08:02 MST ------- Please provide the log files from your repair session: http://en.opensuse.org/Bugs/YaST -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=228813 ------- Comment #2 from admin@eregion.de 2006-12-15 08:40 MST ------- where would i find such log files? the installation dvd is hardly writable... -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=228813 admin@eregion.de changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|admin@eregion.de |jsuchome@novell.com -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=228813 jsuchome@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|jsuchome@novell.com |admin@eregion.de ------- Comment #3 from jsuchome@novell.com 2006-12-18 00:21 MST ------- 1. The log files are in ramdisk during installation or repair. You have to copy them to USB stick or over the network before you reboot. Read http://en.opensuse.org/Bugs/YaST#I_reported_a_YaST2_bug.2C_and_now_I_am_aske... 2. You can also run the repair module on the installed system, just write '/sbin/yast2 repair' command as root. Is the behaviour same as from installation DVD? If yes, please attach also logfiles from this session. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=228813 admin@eregion.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|admin@eregion.de | ------- Comment #4 from admin@eregion.de 2006-12-18 23:45 MST ------- Created an attachment (id=110231) --> (https://bugzilla.novell.com/attachment.cgi?id=110231&action=view) yast logs as requested I booted into the installation, and went to "Automatic system repair". Right after the "failed, no valid XFS" problem, i switched to a console and ran save_y2logs. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=228813 jsuchome@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |admin@eregion.de ------- Comment #5 from jsuchome@novell.com 2006-12-19 01:58 MST ------- Thanks. Please, could you test it also on installed system (point 2 from comment #3)? I assume it will fail as well, but for installed system I could provide a patch to test (I think I already know where is the problem). -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=228813 ------- Comment #6 from admin@eregion.de 2006-12-19 11:40 MST ------- Created an attachment (id=110390) --> (https://bugzilla.novell.com/attachment.cgi?id=110390&action=view) yast2 logfiles -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=228813 admin@eregion.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|admin@eregion.de | ------- Comment #7 from admin@eregion.de 2006-12-19 11:42 MST ------- Tried it on a installed (booted) system, went through without any trouble, mainly (from what i see) because of course it could not mount and/or fsck the partitions because they of course were already mounted. see 2nd attachment for y2logs. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=228813 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |jsuchome@novell.com |screening@forge.provo.novell| |.com | -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=228813 jsuchome@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Normal Status|NEW |ASSIGNED ------- Comment #8 from jsuchome@novell.com 2006-12-20 01:39 MST ------- Oh, I didn't know that it is your root file system. But I probably know the problem, so I could submit a fix anyway. BTW, this can't be critical bug. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=228813 ------- Comment #9 from admin@eregion.de 2006-12-20 02:05 MST ------- .. Title of this bug: "Bug 228813 - Automatic system repair from install media can't do anything if / is on XFS" anyways, for me it WAS rather critical, see bug #228806. since grub was caught in that reboot loop, i couldnt even get into windows... wasted two days of my precious free time over the weekend where i usually would do juch more interesting things than wrestle a computer into submission... -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=228813 ------- Comment #10 from jsuchome@novell.com 2006-12-20 02:15 MST ------- Well, you're right that the whole problem can be called critical, but actually the critical part is what broke your system (bug #228806) and not that yast2-repair cannot repair it. Yes, there is a silly bug in yast2-repair that prevents correct XFS detection (the yast module checks for "uuid" in xfs_admin output, while it actually prints "UUID" in this version). Sure, this will be fixed in 10.3 Another note: the title is not really correct, the repair surely can do something, there are other tools repair offers, not only repairing corrupted file system. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=228813 jsuchome@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |mmarek@novell.com ------- Comment #11 from jsuchome@novell.com 2006-12-20 03:10 MST ------- Looking inside yast2-repair, I can see that it uses "/usr/sbin/xfs_admin -l -u <partition>" call to check if given partition uses XFS file system. It assumes it has it if the output of this call contains "label" and "uuid" strings. Well, it looks like that this way it works, but I'm not sure if this is a correct check for partition type. Wouldn't it be better to check just return value of xfs_admin command? Michal, what do you think? Will xfs_admin call above always return 0 when called on xfs partition and non-0 otherwise? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=228813 mmarek@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mmarek@novell.com Status|NEEDINFO |ASSIGNED Info Provider|mmarek@novell.com | ------- Comment #12 from mmarek@novell.com 2006-12-20 05:29 MST ------- lol # file -s /dev/sda6 /dev/sda6: ReiserFS V3.6 block size 4096 num blocks 1502064 r5 hash # xfs_admin -l -u /dev/sda6; echo $? xfs_admin: unexpected XFS SB magic number 0x00000000 xfs_admin: read failed: Invalid argument xfs_admin: data size check failed /usr/sbin/xfs_admin: line 28: 16317 Segmentation fault (core dumped) xfs_db -x -p xfs_admin -r -c label -r -c uuid /dev/sda6 139 But yes, checking the exit code should do. You could also just run xfs_db <partition> </dev/null. I'll look at the segfault. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=228813 jsuchome@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #13 from jsuchome@novell.com 2006-12-20 06:16 MST ------- Fixed (by checking exit code instead of stdout) in yast2-repair-2.15.0 and yast2-repair-2.13.10 -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=228813 admin@eregion.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #14 from admin@eregion.de 2007-01-03 16:06 MST ------- could you guys create a rescue cd with that fix, so that people can repair their systems? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=228813 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aj@novell.com Status|NEEDINFO |REOPENED Info Provider|aj@novell.com | ------- Comment #16 from aj@novell.com 2007-01-08 01:12 MST ------- The first 10.3 alpha will have this - the current factory tree should have it as well. We're not creating complete new rescue disks for 10.2. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=228813 jsuchome@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED ------- Comment #17 from jsuchome@novell.com 2007-01-08 01:48 MST ------- It is also done there, no need to reopen. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=228813 admin@eregion.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED ------- Comment #18 from admin@eregion.de 2007-01-08 02:15 MST ------- would that mean, if i have the same grub problem with xfs again, i could try and use the 10.3 alpha (when they're here) or factory install cds and try that? ah well. -- 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, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com