https://bugzilla.novell.com/show_bug.cgi?id=830468 https://bugzilla.novell.com/show_bug.cgi?id=830468#c0 Summary: YaST2 spins up unmounted harddisks for many harddisk-unrelated config tasks Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: andreas_nordal_4@hotmail.com QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 When YaST2 is opened, it shows a lot of icons (bootloader, network, …). I have noticed that the first thing that happens when clicking many of those, is that all harddisks spin up. I have several harddisks that I like to keep spun down: 1. My backup harddisk. 2. My failed raid1 array that I'm perpetually rescuing data from. 3. My family's failed harddisk that I'm perpetually rescuing data from. 4. My backup-backup harddisk that vibrates and squeals like a pig. Problem 1 — inconvenience: After say, adjusting bootloader settings, I have to open a terminal and do `for i in c d e f g; do hdparm -Y /dev/sd$i; done` as root to spin them down again. Problem 2 — unnecessity: Some settings are just totally harddisk-unrelated, e.g. network settings! Arguably all settings are unrelated, because these harddisks are not part of the system. Problem 3 — fragility: Don't rely on my failed harddisks! You won't be able to read the partition table of my family's failed harddisk anyway, and this apparently broke kernel upgrading… Reproducible: Always Steps to Reproduce: 1. Open YaST2 2. Click the network settings Actual Results: Harddisks spin up. It gets noisy. The mere presence of my family's failed harddisk causes things to take extremely long time and/or fail. Expected Results: Unused harddisks should remain spun down. -- 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.