I saw this advice on how to implement a fix using udev: http://www.nslu2-linux.org/wiki/FAQ/DealWithAutoSpinDownOnSeagateFreeAgent udev Method
Add a rule to the end of /etc/udev/rules.d/local.rules
# Seagate FreeAgent allow_restart fix (i/o errors) SUBSYSTEMS=="scsi",DRIVERS=="sd",ATTRS{vendor}=="Seagate*",ATTRS{model}=="FreeAgent*",RUN+="/bin/sh -c 'echo 1 > /sys/class/scsi_disk/%k/allow_restart'"
I have Fedora 10 installed. Should I add a new file 10-local.rules and put it there? I currently don't have a local.rules file.
$ ls /etc/udev/rules.d/ 40-multipath.rules 51-packagekit-firmware.rules 60-libmtp.rules 60-pcmcia.rules 60-wacom.rules 65-md-incremental.rules 70-persistent-cd.rules 70-persistent-net.rules 85-pcscd_ccid.rules 85-pcscd_egate.rules 90-alsa.rules 90-hal.rules 91-drm-modeset.rules 97-bluetooth-serial.rules 99-fuse.rules
Thank you
Darlene Wallach
On Sun, 2010-03-28 at 15:08 -0700, Darlene Wallach wrote:
I saw this advice on how to implement a fix using udev: http://www.nslu2-linux.org/wiki/FAQ/DealWithAutoSpinDownOnSeagateFreeAgent udev Method
Add a rule to the end of /etc/udev/rules.d/local.rules
# Seagate FreeAgent allow_restart fix (i/o errors) SUBSYSTEMS=="scsi",DRIVERS=="sd",ATTRS{vendor}=="Seagate*",ATTRS{model}=="FreeAgent*",RUN+="/bin/sh -c 'echo 1 > /sys/class/scsi_disk/%k/allow_restart'"
I have Fedora 10 installed. Should I add a new file 10-local.rules and put it there? I currently don't have a local.rules file.
Just try it and see. Remember to restart udev after you make the change.
Note however that F10 is no longer supported.
poc
Patrick,
On Sun, Mar 28, 2010 at 4:45 PM, Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Sun, 2010-03-28 at 15:08 -0700, Darlene Wallach wrote:
I saw this advice on how to implement a fix using udev: http://www.nslu2-linux.org/wiki/FAQ/DealWithAutoSpinDownOnSeagateFreeAgent udev Method
Add a rule to the end of /etc/udev/rules.d/local.rules
# Seagate FreeAgent allow_restart fix (i/o errors) SUBSYSTEMS=="scsi",DRIVERS=="sd",ATTRS{vendor}=="Seagate*",ATTRS{model}=="FreeAgent*",RUN+="/bin/sh -c 'echo 1 > /sys/class/scsi_disk/%k/allow_restart'"
I have Fedora 10 installed. Should I add a new file 10-local.rules and put it there? I currently don't have a local.rules file.
Just try it and see. Remember to restart udev after you make the change.
How do I restart udev? I can always shutdown and reboot, I guess.
Note however that F10 is no longer supported.
I know. When I tried installing Fedora 11, I could not boot as a user, the temporary login did *not* get generated - I tried installing a few times and gave up.
poc
Thank you for taking the time to answer my question.
Darlene Wallach
On 10-03-28 20:44:48, Darlene Wallach wrote: ...
How do I restart udev? I can always shutdown and reboot, I guess.
...
From `man udevadm`, found with `apropos udev`:
... udevadm control command Modify the internal state of the running udev daemon. ... --reload-rules Signal udevd to reload the rules files. The udev daemon detects changes automatically, this option is usually not needed. Reloading rules does not apply any changes to already existing devices. ...
So just change the rule(s).
Tony,
On Sun, Mar 28, 2010 at 6:03 PM, Tony Nelson tonynelson@georgeanelson.com wrote:
On 10-03-28 20:44:48, Darlene Wallach wrote: ...
How do I restart udev? I can always shutdown and reboot, I guess.
...
From `man udevadm`, found with `apropos udev`:
... udevadm control command Modify the internal state of the running udev daemon. ... --reload-rules Signal udevd to reload the rules files. The udev daemon detects changes automatically, this option is usually not needed. Reloading rules does not apply any changes to already existing devices. ...
So just change the rule(s).
Thank you for taking the time to look up the information and answer my question.
Darlene Wallach
On Sun, 2010-03-28 at 21:03 -0400, Tony Nelson wrote:
On 10-03-28 20:44:48, Darlene Wallach wrote: ...
How do I restart udev? I can always shutdown and reboot, I guess.
...
From `man udevadm`, found with `apropos udev`:
... udevadm control command Modify the internal state of the running udev daemon. ... --reload-rules Signal udevd to reload the rules files. The udev daemon detects changes automatically, this option is usually not needed. Reloading rules does not apply any changes to already existing devices. ...
So just change the rule(s).
Unless the device already exists, in which case no changes will be applied.
poc
On Sun, 2010-03-28 at 17:44 -0700, Darlene Wallach wrote:
Note however that F10 is no longer supported.
I know. When I tried installing Fedora 11, I could not boot as a user, the temporary login did *not* get generated - I tried installing a few times and gave up.
Not sure what you mean by "the temporary login". I just used preupgrade and it worked.
poc
Patrick,
On Sun, Mar 28, 2010 at 7:24 PM, Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Sun, 2010-03-28 at 17:44 -0700, Darlene Wallach wrote:
Note however that F10 is no longer supported.
I know. When I tried installing Fedora 11, I could not boot as a user, the temporary login did *not* get generated - I tried installing a few times and gave up.
Not sure what you mean by "the temporary login". I just used preupgrade and it worked.
I prefer to do a clean install. I have not used preupgrade.
When I have done other Fedora installs, a temporary user gets set up for the first login. That failed to happen when I installed Fedora 11, so there was no way for me to login. I know I'm not explaining it very well - it was a while ago that I tried to install Fedora 11.
poc
Darlene Wallach
On Sun, 2010-03-28 at 19:30 -0700, Darlene Wallach wrote:
Patrick,
On Sun, Mar 28, 2010 at 7:24 PM, Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Sun, 2010-03-28 at 17:44 -0700, Darlene Wallach wrote:
Note however that F10 is no longer supported.
I know. When I tried installing Fedora 11, I could not boot as a user, the temporary login did *not* get generated - I tried installing a few times and gave up.
Not sure what you mean by "the temporary login". I just used preupgrade and it worked.
I prefer to do a clean install. I have not used preupgrade.
When I have done other Fedora installs, a temporary user gets set up for the first login. That failed to happen when I installed Fedora 11, so there was no way for me to login. I know I'm not explaining it very well - it was a while ago that I tried to install Fedora 11.
Switch to a console (Ctrl-Alt-Fn for n = 1..6) and log in as root. Then you can create a user account.
poc