[SOLVED] vsftpd read only

How can I set read only access rights for user when he logs in through FTP? I'm using vsftpd.
Last edited by kdemon (2008-12-26 20:21:12)

Add "write_enable=NO" to /etc/vsftpd.conf (I think it's the default setting actually, so if you just leave the line "write_enable=YES" commented, it should have the same effect).
You can also set read-only permissions with chmod (directories need to be executable though).
See "man vsftpd.conf" for more information.
*edit*
I've just checked and it is the default setting, so as long as you don't add the line "write_enable=YES" to vsftpd.conf, users won't have write permissions
Last edited by Xyne (2008-12-26 20:05:32)

Similar Messages

Read only column in tabular form

There is a not null column ( say SEQ) in a tabular form that is getting an auto value from other process. 2 more columns need user input on each row.I need to make this column(SEQ) as read only.
If I make this column (SEQ) as standard report column then when I submit the newly added row , I always get ORA-20001 error- can not insert NULL into SEQ.. even though I can see there is a value there. Switch ithe column back to text field, the insert went just fine .
How do you solve this read only column issue ?
Thanks a bunch for your help.
Tai

thank you for your reply.
Nope, SEQ is not the first column. Primary Key is and I leave the pK alone.
When I press ADDROW button , tabular form is like the following: ( table alreay has 2 rows), I auto populate SEQ column and I like to make this SEQ column display only.
-- represents checkbox
PK      SEQ      col1           col2
--     1     890          test1
--     2     675          test2
--     3

Cant edit birthday calendar (read-only)

Hello,
im pretty new to iCal, just started today.
i recognised it imports / offers a calendar for each location you have on your mac os X.
in prefs i found the additional birthday calendar option.
after enabling it, i was wondering why i cant edit it.
"you cannot change events or toDo in a read-only calendar"
i hoped the type birthday calendar offers my the option to use all inserts i did for all coming years.
any ideas howto solve that read-only status ?
best regards
fidel

Hi fidel,
iCal's birthday calendar takes it's data from birthdays you put into Address Book. It is not editable from within iCal.
Best wishes
John M

Render button ok but fields displayed as read-only(solved)

Dear JHeadstart,
I'm trying to solve the next situation.
I'm Using a form with 'Same Page?' checked.
I'm rendering an add-button: when a row is not found I display the add button and when a row is found, the add button is not displayed.
This works well with the EL expression: #{bindings.<viewobject>InputDate.inputValue eq null} in the 'Insert allowed EL expression'. For if now row is found this field is null.
But when I press the add button I only get readonly fields where I'm hoping for inputfields to fill so I can insert a new row in the table.
In the jspx file I find, the EL expression I used, back for every field in the form.
The form is based on a VO based on 2 entity objects. One is always updateble (here I want to have the inputfields) and one is read-only.
I've also tried the EL: #{!((bindings.<viewobject>Iterator.currentRowIndexInRange!=-1 and bindings.<viewobject>Iterator.findMode!='true'))} which is used to render the value="#{nls['NO_ROWS_FOUND']}" in de jspx file.
but with the same results.
So what can I do to make those fields insertable?
Help will be appreciated!
regards,
Marcel.
After some more googling I found:
http://download-east.oracle.com/docs/html/B25947_01/bcvoeo009.htm#BABJEEFA
Section 7.9.3 got me on track.
In my create() the InputDate field was filled (sic).
When I used another field in the EL, it worked.
Message was edited by:
user571204

Finally I think I have found the problem.
In the View where I am printing the ADOBEFORM, it is needed this code under the method WDDOMODIFYVIEW.
method WDDOMODIFYVIEW .
DATA: LV_INTERACTIVE_FORM   TYPE REF TO CL_WD_INTERACTIVE_FORM,
             LV_METHOD_HANDLER     TYPE REF TO IF_WD_IACTIVE_FORM_METHOD_HNDL.
LV_INTERACTIVE_FORM ?= VIEW->GET_ELEMENT( 'INT_FORM' ). "   adobeform object in view
IF LV_INTERACTIVE_FORM IS NOT INITIAL.
      LV_METHOD_HANDLER ?= LV_INTERACTIVE_FORM->_METHOD_HANDLER.
      LV_METHOD_HANDLER->SET_LEGACY_EDITING_ENABLED( ABAP_TRUE ).
      LV_METHOD_HANDLER->SET_HIDE_NAVIGATION_PANEL( ABAP_TRUE ).
      LV_METHOD_HANDLER->SET_DISABLE_PRINT_BUTTON( ABAP_TRUE ).
      WD_THIS->M_METHOD_HANDLER ?= LV_INTERACTIVE_FORM->_METHOD_HANDLER.
      WD_THIS->M_METHOD_HANDLER->SET_HIDE_TOOLBARS( ABAP_TRUE ).
    ENDIF.
endmethod.
Regards,
Carles

Filesystem read only[Solved]

hello
i install arch but when i want to install a software i can't.
there is an error "file system read only"
what should i do?
Last edited by MHALAH152 (2013-05-12 06:31:48)

MHALAH152 wrote:
65kid wrote:just use "defaults", nothing else. Don't add any other options unless you actually know what they are doing.
I do that.but now i have new problem
my system can't find internet and i can't install any software
Then please mark this thread as [Solved] by editing your first post and prepending it to the title.
Then open a new thread about your networking issue and include information about your network card, drivers, what you have set up in your configs etc...
https://wiki.archlinux.org/index.php/Fo … ow_to_Post

When I converted a file from PDF to WORD.DOC it opened as Read Only and I'm unable to alter any of the text. How can I solve this problem?

When I tried to convert a file from PDF to WORD.DOC it opened as Read Only and I'm unable to alter any of the text. How do I solve this problem? I don't know how to change it from Read Only.

Dear Sara
Thank you very much for sending the converted file. Yes, I am able to edit it - that will be very useful to me and I appreciate your help.
Referring to your previous message when you said you'd converted via Acrobat and not Acrobat.com, I'm converting via Acrobat.com because that's the only option that is shown (how do I convert via Acrobat? - perhaps that would be more successful). I'm using the Export PDF website, and the OCR is enabled to "Recognize text in English UK". However, I've just tried converting a different LPA pdf form, this time for Health & Welfare https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/245571/LPA114_He alth_welfare_LPA.pdf and again I have the same problem as before. I've altered it from "Read only" and thought I'd then be able to enter text, but "Drawing Tools" is shown in the pane and I'm unable to enter anything onto the form - everything appears to be in images. Also, the lettering on the heading of' page 1 has become jumbled, with the word "Public" overlaying the word "Guardian." Any suggestions as to what it is I'm doing wrong would be welcome - I don't like to be beaten!
Regards,
Judith.

Read only after install [SOLVED -- systemd related]

Anyone know why a new (booted ~2-3 times) install would suddenly mount read-only? /etc/fstab is fine, /etc/mtab reports rootfs / as rw, and I am logged in as root, but I get "read-only filesystem", hence there are no logs, etc.
Last edited by goldilocks (2012-10-14 18:01:41)

DSpider wrote:You probably removed "ro" from syslinux.cfg.
Nope. I have a startup service I use on fedora, and since the target I usually use wasn't apparent, I casually systemctl enabled it with WantedBy=local-fs.target, figuring if that was too early it would just fail (it writes to to disk).
Using "mount -o remount,rw /" worked, so I tried a few things like switching fstab to use a UUID instead of a device node, that didn't work. Finally I disabled the service and everything is back to normal.
I did this a couple of times (enabling, rebooting, disabling, rebooting) just to confirm that was the cause. I guess that target runs before the rw remount, maybe this causes systemd to crap out in some way. Shame it can't just fail the service, log it, and continue. Maybe even an oversight verging on "bug", though I am sure they are aware of it already.
I'd mark this "SOLVED" but I don't see a button...
Last edited by goldilocks (2012-10-14 17:49:16)

[Solved] Laptop Suspend puts Hard Drive into Read-Only

My problem is that s2ram brings back X (and the virtual console, if I'm on one), but never the hard drive.
s2ram -f -a 1 suspends just like s2ram -f. -a 2 and 3 just make a high pitched sound.
I tried both http://wiki.archlinux.org/index.php/Suspend_to_RAM and http://wiki.archlinux.org/index.php/Pm-utils methods.
I updated my BIOS drivers but that didn't help
s2disk works perfectly.
This is a COMPAQ Presario CQ60-215DX
Here is my log of the trouble during resume:
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
sd 3:0:0:0: [sda] Starting disk
ata4.00: qc timeout (cmd 0xec)
ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata4.00: revalidation failed (errno=-5)
ata3.00: qc timeout (cmd 0xa1)
ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata3.00: revalidation failed (errno=-5)
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: qc timeout (cmd 0xa1)
ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata3.00: revalidation failed (errno=-5)
ata3: limiting SATA link speed to 1.5 Gbps
ata4.00: qc timeout (cmd 0xec)
ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata4.00: revalidation failed (errno=-5)
ata4: limiting SATA link speed to 1.5 Gbps
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata4: SATA link up <unknown> (SStatus 103 SControl 310)
And my full log:
Linux version 2.6.30-ARCH (root@T-POWA-LX) (gcc version 4.4.1 (GCC) ) #1 SMP PREEMPT Fri Jul 31 07:30:28 CEST 2009
Command line: root=/dev/disk/by-uuid/9ae7dfa5-74b2-41e2-89bc-b344bbf47109 ro
KERNEL supported cpus:
Intel GenuineIntel
AMD AuthenticAMD
Centaur CentaurHauls
libata version 3.00 loaded.
pata_amd 0000:00:06.0: version 0.4.1
pata_amd 0000:00:06.0: setting latency timer to 64
scsi0 : pata_amd
scsi1 : pata_amd
ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x30c0 irq 14
ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x30c8 irq 15
ahci 0000:00:09.0: version 3.0
ACPI: PCI Interrupt Link [LSI0] enabled at IRQ 22
ahci 0000:00:09.0: PCI INT A -> Link[LSI0] -> GSI 22 (level, low) -> IRQ 22
ahci 0000:00:09.0: irq 25 for MSI/MSI-X
ahci 0000:00:09.0: AHCI 0001.0200 32 slots 2 ports 3 Gbps 0x3 impl IDE mode
ahci 0000:00:09.0: flags: 64bit ncq sntf led clo pmp pio slum part
ahci 0000:00:09.0: setting latency timer to 64
scsi2 : ahci
scsi3 : ahci
ata3: SATA max UDMA/133 abar m8192@0xc0004000 port 0xc0004100 irq 25
ata4: SATA max UDMA/133 abar m8192@0xc0004000 port 0xc0004180 irq 25
ata2: port disabled. ignoring.
Clocksource tsc unstable (delta = 4397486409693 ns)
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4.00: ATA-8: TOSHIBA MK2555GSX, FG002C, max UDMA/100
ata4.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata4.00: configured for UDMA/100
ata3.00: ATAPI: Optiarc DVD RW AD-7580S, FH03, max UDMA/100
ata3.00: configured for UDMA/100
scsi 2:0:0:0: CD-ROM Optiarc DVD RW AD-7580S FH03 PQ: 0 ANSI: 5
scsi 3:0:0:0: Direct-Access ATA TOSHIBA MK2555GS FG00 PQ: 0 ANSI: 5
Driver 'sr' needs updating - please use bus_type methods
sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 2:0:0:0: Attached scsi CD-ROM sr0
Driver 'sd' needs updating - please use bus_type methods
sd 3:0:0:0: [sda] 488397168 512-byte hardware sectors: (250 GB/232 GiB)
sd 3:0:0:0: [sda] Write Protect is off
sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2 sda3 < sda5 > sda4
sd 3:0:0:0: [sda] Attached SCSI disk
EXT4-fs: INFO: recovery required on readonly filesystem.
EXT4-fs: write access will be enabled during recovery.
EXT4-fs: barriers enabled
kjournald2 starting: pid 569, dev sda2:8, commit interval 5 seconds
EXT4-fs: delayed allocation enabled
EXT4-fs: file extents enabled
EXT4-fs: mballoc enabled
EXT4-fs: sda2: orphan cleanup on readonly fs
ext4_orphan_cleanup: deleting unreferenced inode 148384
ext4_orphan_cleanup: deleting unreferenced inode 147907
ext4_orphan_cleanup: deleting unreferenced inode 147903
EXT4-fs: sda2: 3 orphan inodes deleted
EXT4-fs: recovery complete.
EXT4-fs: mounted filesystem sda2 with ordered data mode
rtc_cmos 00:06: RTC can wake from S4
rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one year, y3k, 114 bytes nvram, hpet irqs
udev: starting version 141
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
ACPI: AC Adapter [ADP1] (on-line)
forcedeth: Reverse Engineered nForce ethernet driver. Version 0.64.
ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 21
forcedeth 0000:00:0a.0: PCI INT A -> Link[LMAC] -> GSI 21 (level, low) -> IRQ 21
forcedeth 0000:00:0a.0: setting latency timer to 64
sr 2:0:0:0: Attached scsi generic sg0 type 5
sd 3:0:0:0: Attached scsi generic sg1 type 0
usbcore: registered new device driver usb
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
cfg80211: Calling CRDA to update world regulatory domain
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
ACPI: Power Button [PWRF]
input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input3
ACPI: Lid Switch [LID0]
input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input4
ACPI: Sleep Button [SLPB]
input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input5
ACPI: Power Button [PWRB]
processor ACPI_CPU:00: registered as cooling_device0
processor ACPI_CPU:01: registered as cooling_device1
forcedeth 0000:00:0a.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:1f:16:74:cb:72
forcedeth 0000:00:0a.0: highdma csum pwrctl mgmt lnktim msi desc-v3
ACPI: PCI Interrupt Link [LUS2] enabled at IRQ 17
ehci_hcd 0000:00:02.1: PCI INT B -> Link[LUS2] -> GSI 17 (level, low) -> IRQ 17
ehci_hcd 0000:00:02.1: setting latency timer to 64
ehci_hcd 0000:00:02.1: EHCI Host Controller
ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:02.1: debug port 1
ehci_hcd 0000:00:02.1: cache line size of 64 is not supported
ehci_hcd 0000:00:02.1: irq 17, io mem 0xc0007000
ACPI: WMI: Mapper loaded
ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
i2c-adapter i2c-0: nForce2 SMBus adapter at 0x3040
i2c-adapter i2c-1: nForce2 SMBus adapter at 0x3000
ACPI: PCI Interrupt Link [LUS0] enabled at IRQ 17
ohci_hcd 0000:00:02.0: PCI INT A -> Link[LUS0] -> GSI 17 (level, low) -> IRQ 17
ohci_hcd 0000:00:02.0: setting latency timer to 64
ohci_hcd 0000:00:02.0: OHCI Host Controller
ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:02.0: irq 17, io mem 0xc0006000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
ACPI: PCI Interrupt Link [Z011] enabled at IRQ 16
ehci_hcd 0000:00:04.1: PCI INT B -> Link[Z011] -> GSI 16 (level, low) -> IRQ 16
ehci_hcd 0000:00:04.1: setting latency timer to 64
ehci_hcd 0000:00:04.1: EHCI Host Controller
ehci_hcd 0000:00:04.1: new USB bus registered, assigned bus number 3
ehci_hcd 0000:00:04.1: debug port 1
ehci_hcd 0000:00:04.1: cache line size of 64 is not supported
ehci_hcd 0000:00:04.1: irq 16, io mem 0xc0007400
ehci_hcd 0000:00:04.1: USB 2.0 started, EHCI 1.00
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 4 ports detected
ACPI: PCI Interrupt Link [Z010] enabled at IRQ 16
ohci_hcd 0000:00:04.0: PCI INT A -> Link[Z010] -> GSI 16 (level, low) -> IRQ 16
ohci_hcd 0000:00:04.0: setting latency timer to 64
ohci_hcd 0000:00:04.0: OHCI Host Controller
ohci_hcd 0000:00:04.0: new USB bus registered, assigned bus number 4
ohci_hcd 0000:00:04.0: irq 16, io mem 0xc0008000
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 4 ports detected
thermal LNXTHERM:01: registered as thermal_zone0
ACPI: Thermal Zone [TZS0] (68 C)
ACPI: Battery Slot [BAT0] (battery present)
thermal LNXTHERM:02: registered as thermal_zone1
ACPI: Thermal Zone [TZS1] (68 C)
usb 1-1: new high speed USB device using ehci_hcd and address 2
nvidia: module license 'NVIDIA' taints kernel.
Disabling lock debugging due to kernel taint
usb 1-1: configuration #1 chosen from 1 choice
Synaptics Touchpad, model: 1, fw: 7.0, id: 0x1a0b1, caps: 0xd04711/0xa00000
acpi device:13: registered as cooling_device2
input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:10/device:11/input/input6
ACPI: Video Device [VGA] (multi-head: yes rom: no post: no)
usb 3-4: new high speed USB device using ehci_hcd and address 2
input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio2/input/input7
ath5k 0000:07:00.0: PCI INT A -> Link[Z012] -> GSI 23 (level, low) -> IRQ 23
ath5k 0000:07:00.0: setting latency timer to 64
ath5k 0000:07:00.0: registered as 'phy0'
usb 3-4: configuration #1 chosen from 1 choice
ACPI: PCI Interrupt Link [LGPU] enabled at IRQ 20
nvidia 0000:02:00.0: PCI INT A -> Link[LGPU] -> GSI 20 (level, low) -> IRQ 20
nvidia 0000:02:00.0: setting latency timer to 64
NVRM: loading NVIDIA UNIX x86_64 Kernel Module 185.18.31 Tue Jul 28 17:52:27 PDT 2009
EXT4 FS on sda2, internal journal on sda2:8
Adding 3148700k swap on /dev/sda5. Priority:-1 extents:1 across:3148700k
scsi 4:0:0:0: Direct-Access Generic- Multi-Card 1.00 PQ: 0 ANSI: 0 CCS
sd 4:0:0:0: Attached scsi generic sg2 type 0
usb-storage: device scan complete
sd 4:0:0:0: [sdb] Attached SCSI removable disk
scsi 5:0:0:0: Direct-Access USB Driver 0.00 PQ: 0 ANSI: 0 CCS
sd 5:0:0:0: Attached scsi generic sg3 type 0
usb-storage: device scan complete
sd 5:0:0:0: [sdc] 7827456 512-byte hardware sectors: (4.00 GB/3.73 GiB)
sd 5:0:0:0: [sdc] Write Protect is off
sd 5:0:0:0: [sdc] Mode Sense: 23 00 00 00
sd 5:0:0:0: [sdc] Assuming drive cache: write through
sd 5:0:0:0: [sdc] Assuming drive cache: write through
sdc:
sd 5:0:0:0: [sdc] Attached SCSI removable disk
forcedeth 0000:00:0a.0: irq 26 for MSI/MSI-X
eth0: no link during initialization.
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth0: link is not ready
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.00 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
Suspending console(s) (use no_console_suspend to debug)
sd 3:0:0:0: [sda] Synchronizing SCSI cache
sd 3:0:0:0: [sda] Stopping disk
ath5k 0000:07:00.0: PCI INT A disabled
forcedeth 0000:00:0a.0: wake-up capability disabled by ACPI
forcedeth 0000:00:0a.0: PME# disabled
forcedeth 0000:00:0a.0: PCI INT A disabled
HDA Intel 0000:00:07.0: PCI INT A disabled
ata2: port disabled. ignoring.
ehci_hcd 0000:00:04.1: PCI INT B disabled
ehci_hcd 0000:00:04.1: PME# disabled
ohci_hcd 0000:00:04.0: PCI INT A disabled
ohci_hcd 0000:00:04.0: PME# disabled
ehci_hcd 0000:00:02.1: PCI INT B disabled
ehci_hcd 0000:00:02.1: PME# disabled
ohci_hcd 0000:00:02.0: PCI INT A disabled
ohci_hcd 0000:00:02.0: PME# disabled
ACPI: Preparing to enter system sleep state S3
Disabling non-boot CPUs ...
CPU 1 is now offline
SMP alternatives: switching to UP code
CPU0 attaching NULL sched-domain.
CPU1 attaching NULL sched-domain.
CPU0 attaching NULL sched-domain.
CPU1 is down
Extended CMOS year: 2000
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Back to C!
Extended CMOS year: 2000
Enabling non-boot CPUs ...
SMP alternatives: switching to SMP code
Booting processor 1 APIC 0x1 ip 0x6000
Initializing CPU#1
Calibrating delay using timer specific routine.. 4001.76 BogoMIPS (lpj=6666816)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106
CPU1: AMD Athlon Dual-Core QL-62 stepping 01
CPU0 attaching NULL sched-domain.
Switched to high resolution mode on CPU 1
CPU0 attaching sched-domain:
domain 0: span 0-1 level MC
groups: 0 1
CPU1 attaching sched-domain:
domain 0: span 0-1 level MC
groups: 1 0
CPU1 is up
ACPI: Waking up from system sleep state S3
ohci_hcd 0000:00:02.0: restoring config space at offset 0x1 (was 0xb00007, writing 0xb00003)
ehci_hcd 0000:00:02.1: restoring config space at offset 0x1 (was 0xb00006, writing 0xb00002)
ohci_hcd 0000:00:04.0: restoring config space at offset 0x1 (was 0xb00007, writing 0xb00003)
ehci_hcd 0000:00:04.1: restoring config space at offset 0x1 (was 0xb00006, writing 0xb00002)
pata_amd 0000:00:06.0: restoring config space at offset 0x1 (was 0xb00005, writing 0xb80005)
HDA Intel 0000:00:07.0: restoring config space at offset 0xf (was 0x5020100, writing 0x502010a)
HDA Intel 0000:00:07.0: restoring config space at offset 0x4 (was 0x0, writing 0xc0000000)
HDA Intel 0000:00:07.0: restoring config space at offset 0x1 (was 0xb00000, writing 0xb00002)
ahci 0000:00:09.0: restoring config space at offset 0x1 (was 0xb00007, writing 0xb00407)
pcieport-driver 0000:00:14.0: restoring config space at offset 0x7 (was 0x1f1, writing 0x200001f1)
pcieport-driver 0000:00:14.0: restoring config space at offset 0x1 (was 0x100107, writing 0x1005
nvidia 0000:02:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10a)
nvidia 0000:02:00.0: restoring config space at offset 0x9 (was 0x1, writing 0x4001)
nvidia 0000:02:00.0: restoring config space at offset 0x7 (was 0xc, writing 0xc400000c)
nvidia 0000:02:00.0: restoring config space at offset 0x5 (was 0xc, writing 0xd000000c)
ath5k 0000:07:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
nForce2_smbus 0000:00:01.1: PME# disabled
ohci_hcd 0000:00:02.0: PME# disabled
ohci_hcd 0000:00:02.0: PCI INT A -> Link[LUS0] -> GSI 17 (level, low) -> IRQ 17
ohci_hcd 0000:00:02.0: setting latency timer to 64
ohci_hcd 0000:00:02.0: PME# disabled
ehci_hcd 0000:00:02.1: PME# disabled
ehci_hcd 0000:00:02.1: PCI INT B -> Link[LUS2] -> GSI 17 (level, low) -> IRQ 17
ehci_hcd 0000:00:02.1: setting latency timer to 64
ehci_hcd 0000:00:02.1: PME# disabled
usb usb1: root hub lost power or was reset
ehci_hcd 0000:00:02.1: debug port 1
ehci_hcd 0000:00:02.1: cache line size of 64 is not supported
ohci_hcd 0000:00:04.0: PME# disabled
ohci_hcd 0000:00:04.0: PCI INT A -> Link[Z010] -> GSI 16 (level, low) -> IRQ 16
ohci_hcd 0000:00:04.0: setting latency timer to 64
ohci_hcd 0000:00:04.0: PME# disabled
ehci_hcd 0000:00:04.1: PME# disabled
ehci_hcd 0000:00:04.1: PCI INT B -> Link[Z011] -> GSI 16 (level, low) -> IRQ 16
ehci_hcd 0000:00:04.1: setting latency timer to 64
ehci_hcd 0000:00:04.1: PME# disabled
usb usb3: root hub lost power or was reset
ehci_hcd 0000:00:04.1: debug port 1
ehci_hcd 0000:00:04.1: cache line size of 64 is not supported
pata_amd 0000:00:06.0: restoring config space at offset 0x1 (was 0xb00005, writing 0xb80005)
pata_amd 0000:00:06.0: setting latency timer to 64
ata2: port disabled. ignoring.
HDA Intel 0000:00:07.0: PCI INT A -> Link[LAZA] -> GSI 19 (level, low) -> IRQ 19
HDA Intel 0000:00:07.0: setting latency timer to 64
pci 0000:00:08.0: setting latency timer to 64
ahci 0000:00:09.0: setting latency timer to 64
forcedeth 0000:00:0a.0: wake-up capability disabled by ACPI
forcedeth 0000:00:0a.0: PME# disabled
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
forcedeth 0000:00:0a.0: irq 26 for MSI/MSI-X
eth0: no link during initialization.
pci 0000:00:0b.0: setting latency timer to 64
ath5k 0000:07:00.0: PCI INT A -> Link[Z012] -> GSI 23 (level, low) -> IRQ 23
sd 3:0:0:0: [sda] Starting disk
ata4.00: qc timeout (cmd 0xec)
ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata4.00: revalidation failed (errno=-5)
ata3.00: qc timeout (cmd 0xa1)
ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata3.00: revalidation failed (errno=-5)
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: qc timeout (cmd 0xa1)
ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata3.00: revalidation failed (errno=-5)
ata3: limiting SATA link speed to 1.5 Gbps
ata4.00: qc timeout (cmd 0xec)
ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata4.00: revalidation failed (errno=-5)
ata4: limiting SATA link speed to 1.5 Gbps
ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata4: SATA link up <unknown> (SStatus 103 SControl 310)
ata4.00: qc timeout (cmd 0xec)
ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata4.00: revalidation failed (errno=-5)
ata4.00: disabled
ata3.00: qc timeout (cmd 0xa1)
ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata3.00: revalidation failed (errno=-5)
ata3.00: disabled
sd 3:0:0:0: [sda] START_STOP FAILED
sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
sd 3:0:0:0: [sda] Unhandled error code
sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
end_request: I/O error, dev sda, sector 134590273
Buffer I/O error on device sda2, logical block 1094141
lost page write due to I/O error on sda2
sd 3:0:0:0: [sda] Unhandled error code
sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
end_request: I/O error, dev sda, sector 135807281
Buffer I/O error on device sda2, logical block 1246267
lost page write due to I/O error on sda2
sd 3:0:0:0: [sda] Unhandled error code
sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
end_request: I/O error, dev sda, sector 135815833
Buffer I/O error on device sda2, logical block 1247336
lost page write due to I/O error on sda2
JBD2: Detected IO errors while flushing file data on sda2:8
sd 3:0:0:0: [sda] Unhandled error code
sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
end_request: I/O error, dev sda, sector 155463993
Aborting journal on device sda2:8.
sd 3:0:0:0: [sda] Unhandled error code
sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
end_request: I/O error, dev sda, sector 155459417
Buffer I/O error on device sda2, logical block 3702784
lost page write due to I/O error on sda2
JBD2: I/O error detected when updating journal superblock for sda2:8.
PM: Device 3:0:0:0 failed to resume: error 262144
usb 1-1: reset high speed USB device using ehci_hcd and address 2
usb 3-4: reset high speed USB device using ehci_hcd and address 2
Restarting tasks ... <2>ext4_abort called.
EXT4-fs error (device sda2): ext4_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
ext4_da_writepages: jbd2_start: 1024 pages, ino 131086; err -30
Pid: 20, comm: pdflush Tainted: P 2.6.30-ARCH #1
Call Trace:
[<ffffffffa00d738d>] ? ext4_da_writepages+0x47d/0x4b0 [ext4]
[<ffffffff8026c6a4>] ? bit_waitqueue+0x24/0xe0
[<ffffffff802c8332>] ? do_writepages+0x32/0x60
[<ffffffff80321b7a>] ? __writeback_single_inode+0xba/0x490
[<ffffffff802406e6>] ? dequeue_task_fair+0x56/0x1d0
[<ffffffff8020a95c>] ? __switch_to+0xdc/0x3b0
[<ffffffff803223b3>] ? generic_sync_sb_inodes+0x193/0x530
[<ffffffff803229c5>] ? writeback_inodes+0x65/0x120
[<ffffffff802c85a6>] ? wb_kupdate+0xc6/0x160
[<ffffffff802c995b>] ? pdflush+0x16b/0x2a0
[<ffffffff802c84e0>] ? wb_kupdate+0x0/0x160
[<ffffffff802c97f0>] ? pdflush+0x0/0x2a0
[<ffffffff802c97f0>] ? pdflush+0x0/0x2a0
[<ffffffff8026c204>] ? kthread+0x64/0xc0
[<ffffffff8024af20>] ? schedule_tail+0x30/0x80
[<ffffffff8020d4fa>] ? child_rip+0xa/0x20
[<ffffffff8026c1a0>] ? kthread+0x0/0xc0
[<ffffffff8020d4f0>] ? child_rip+0x0/0x20
sd 3:0:0:0: [sda] Unhandled error code
sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
end_request: I/O error, dev sda, sector 126637417
sd 3:0:0:0: [sda] Unhandled error code
sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
end_request: I/O error, dev sda, sector 126637417
sd 3:0:0:0: [sda] Unhandled error code
sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
end_request: I/O error, dev sda, sector 126637417
sd 3:0:0:0: [sda] Unhandled error code
sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
end_request: I/O error, dev sda, sector 126637417
sd 3:0:0:0: [sda] Unhandled error code
sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
end_request: I/O error, dev sda, sector 126637417
done.
sd 3:0:0:0: [sda] Unhandled error code
sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
end_request: I/O error, dev sda, sector 130097993
EXT4-fs error (device sda2): ext4_find_entry: reading directory #139292 offset 0
sd 3:0:0:0: [sda] Unhandled error code
sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
end_request: I/O error, dev sda, sector 126637417
sd 3:0:0:0: [sda] Unhandled error code
sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
end_request: I/O error, dev sda, sector 126004889
EXT4-fs error (device sda2): ext4_find_entry: reading directory #98457 offset 0
sd 3:0:0:0: [sda] Unhandled error code
sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
end_request: I/O error, dev sda, sector 126004889
EXT4-fs error (device sda2): ext4_find_entry: reading directory #98457 offset 0
ANY help would be much appreciated.
Last edited by Cappy (2009-08-10 08:19:09)

Nevermind .. *sigh* ... pci=msi on the kernel fixed it .. going to go cut myself now ...

[kinda solved, hd broken]Salvaged hard drive mounted as read-only

My old netbook died recently (if a guy in a shady computer store in Edinburgh tells you that "this adapter will surely work" -- what ever you do, don't believe him). Got a new netbook, and an external usb hd case for the old hard drive in the hope of salvaging it.
The old hd seems to have survived, as it mounts just fine and all my old partitions show up (home folder, root, swap...). However, I cannot change the permissions of the files using thunar as root, nor can I copy them to my internal hd --probably because the drive is mounted as read-only. The /home partition, which is the one I'm interested in copying things from, is formated in ext4.
I'm guessing I should change something in my fstab, though I'm not sure what exactly. What's weird though is that the drive does not show up when I run sudo fdisk -l, nor does it show in gparted (which is run as root, of course) -- meaning I don't know what rule I should put in my fstab file, as I dont know what mount point to apply it to. I use xfce on my current laptop, but seeing as the problem persists when I try on my partners ubuntu laptop I figure that the DE hasn't got much to do with it.
I guess I could open up the computer, put in the old hard drive and change some configs, install drivers etc. to make my new computer boot properly from it. Does seem like a drag though, so I figured I'd try asking here first. I suspect this is a fairly common problem, but my google-fu does not appear to be strong enough as I've failed to find a solution on my own.
Last edited by caligo (2010-07-19 20:09:01)

karol wrote:'mount: /dev/sdd2: cannot read superblock' is quite different from mounting read-only - I'd call it read ... NOT!
I hope you have some sort of backup.
Yes, "cannot read" is indeed a more disheartening message... When trying to copy the files through thunar, I can see them but not move or open them -- and trying to change the permissions results in an error message about the file system being "read-only".
itsbrad212 wrote:# fsck /dev/sdd2
results in
Attempt to read block from filesystem resulted in short read
The thing might indeed be dead...
I have backups of all the important things -- just wanted to save some recent random files and a bunch of wallpapers, but I think I'll survive the loss. Thanks for the help guys. Might try to format the whole thing, see if its just the data that's corrupted or of the harware is busted as well.

Filesystem read only at boot "SOLVED"

Hi archers
I have a frustrating problem.... for some unknown reason... I rebooted today, and havn't been able
to get back into arch....
it complains that my filesystem is read only etc. heres the error
******************* FILESYSTEM CHECK FAILED *************
* Please repair manually and reboot. Note that the root *
* filesystem is currently mounted read-only. To remount *
* it read-write type: mount -n -o remount,rw / *
* When you exit the mantenance shel the system will *
* reboot automatically.
i've tried what it suggests "mount -n -o remount,rw /
i reboot, and still get the same problem over and over again.
I don't know what could of caused this.... i havn't been messing with anything unusual....
I better output my fstab and partitions:
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0007f78b
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104422 83 Linux
/dev/sda2 14 46 265072+ 82 Linux swap / Solaris
/dev/sda3 47 1003 7687102+ 83 Linux
/dev/sda4 1004 19457 148231755 83 Linux
Fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
/dev/sda1 /boot ext2 defaults 0 1
/dev/sda2 swap swap defaults 0 0
/dev/sda3 / ext4 defaults 0 1
/dev/sda4 /home ext4 defaults 0 1
Pleaasseeee Help
I'm using a live cd to access the internet right now
thanx in advance
any ideas?
thankyou
Last edited by kaddy (2009-10-18 13:38:16)

Few days, or maybe a week ago, when i was trying to get X to work, i always had to use the computer's reset button because the keyboard would be irresponsive. Normally Arch would fix itself and re-reboot, but eventually it broke because of whatever reason. I thought of wiping the partition and reinstalling Arch from scratch as i didn't have many things on it anyway, but guess what, GParted could fix the filesystem.
(By the way, in case you're curious, the reason X wasn't working properly was that i had no keyboard or mouse drivers installed.)
If you have another Linux on your PC, or a Live CD, or even an installation CD, see if it has a disk-partitioning tool that has an option to fix filesystems. If it doesn't, but if the Linux you use is installed on your PC, just install GParted. But if you're using an installation- or Live CD, you can't do that, and in that case i think you'll have to get another Linux; i would say download Puppy Linux and make a Live CD of that; it has GParted and is friendly for newcomers in every other way too. And you can be sure that having a Live CD lying around is always something good. You never know when something like this will happen again.
(Oh, i just realized that you already ARE using a Live CD... Keep installation CDs, and Puppy Linux, in mind though.)
Last edited by TaylanUB (2009-10-18 13:36:48)

[SOLVED]pacman -Sf zim makes arch read-only filesystem

Hi,
Last night I was trying to install zim, it looks like there were a couple packages which weren't properly installed before. I googled the error I received and found somewhere on the forum the tip to use
pacman -Sf package
I ran the command and it installed some sort of new kernel, fstab, something with python, and zim of course. While it was installing the packages I noticed it moved a couple files around and I'm not quite sure what it all did. anyway when I booted arch this morning it didn't quite make it to gdm, so I quickly booted into ubuntu, mounted my arch partition changed the inittab to boot to init 3. I then noticed that it mounted the arch / as read-only, I looked around a bit seems like my /etc/fstab was moved to /etc/fstab.pacorig. Now before I start playing around and maybe break things more than they are, anyone have a tip about how to figure out everything that was changed?
I also noticed that I could login as root without having to use a password which I don't like at all, which is a little scary.
Last edited by whitethorn (2010-06-26 13:50:11)

First things first; using the -f/--force flag with pacman is the absolute last resort, when everything else fails, and when you know exactly what you're doing. Using it just because you found a tip on the forum, and clearly without thinking about the potential consequences, is just asking for trouble - and you've got it.
To fix: your pacman log will tall you what packages were installed, and also has a record of any install-time messages. Comb through that, and work out how to revert the major issues.
[edit] overlap with loafer - he was faster because he used fewer words.

[SOLVED] More rsync problems after restore... Read only filesystem?

Yesterday I backed up all of my data with rsync to a USB thumb drive. Surprisingly it all fit, but my intentions were to wipe my disk and create a new partition scheme for a dualboot while still being able to continue where I left off with arch. So after backing up with the script from the arch wiki titled full system restore with rsync, I followed the rest of that page, and modified the fstab on the backup on the USB and reconfigured grub and restarted my computer and I was able to boot into the USB. Then, I decided that it would be easier to just use the live cd to repartition and pacstrap the base system and generated an fstab. Next, I chrooted from the livecd environment into the newly built base and installed rsync. I then mounted my USB to /mnt in the chrooted environment and used
rsync -aAXv /mnt/ARCH_BACKUP/* / --exclude={/mnt/ARCH_BACKUP/etc/fstab,/mnt/ARCH_BACKUP/boot/grub/}
I just did this since I figured that all of the directories excluded in the script wouldn't really have to be excluded here since they were already empty. Everything seemed to run smoothly except for one file(or maybe directory?) called /etc/resolv.conf.t.jbnW2 which kept giving an error. I figured the file was unique to the USB or something and continued to reinstall grub and then reboot. The weird thing is that everything was back on my system, but it didn't automatically boot into a display manager which it's set up to do. Then when trying to manually start x, that wouldn't work. Then I tried to connect to wifi, it recognized my network but wouldn't connect, so I tried sudo su, which worked but returned an error that the var file system was read only. I then tried to use rsync again thinking maybe that directory would transfer now that I wasn't in the chrooted environment. But instead, it was trying to restore every single file, but every one returned the error "filesystem is read only".
It seems like when I restored all of the files in my entire system were made read only.
Can anyone tell me what may have caused this and how to fix it?
I think it may either be that when I mounted the device in the chrooted environment I didn't specify 'rw' capabilities, or it may be that when I backed up I didn't specify 'rw' capabilities I just opened the file manager and clicked on it and it automagically mounted to /media/.
Last edited by eroge008 (2013-01-25 20:29:22)

Ok, well I fiixed it. I had edited the fstab on the usb to be able to boot into the usb, and, while I edited it again on the hdd each time I restored from the backup, I didn't realize that the top entry /dev/sda1 (which is my root partition) was on a line that was commented out. I guess I accidentally hit the backspace button or something while editing it to be able to boot into the usb.
Also, I think there was a second problem, that my usb controller is starting to fail. Because on the last time that I backed up, if I moved my computer or anything I would get a I/O error. This was caused by the failing usb controller. The computer would remount it as read-only because of the failure. The solution to this was to use
hdparm -r0 /dev/sdxy
Note: The device must be unmounted.
Where x is the device and y is the partition number, for me this was sdb1.
Then mount specifying read-write option.
mount -o rw /dev/sdxy /media/<BACKUP>
I also tried
mount -o remount,rw /dev/sdxy /media/<BACKUP>
as was recommended on all of the sites that I could find, but this command kept returning an error.
Note: For newer users, Arch does not automatically create the media folder as it doesn't provide automatic mounting of external drives. If such is the case, and you haven't installed a desktop environment with a file manager that will automatically do this for you when the device is recognized, you must make the media directory and the directory which you intend to mount to manually.
# mkdir /media
# mkdir /media/<BACKUP>
Where <BACKUP> can be whatever you want it to be.
Last edited by eroge008 (2013-01-25 20:27:52)

[Solved]please help with btrfs read only filesystem

Yesterday I deleted a snapshot using the command
sudo btrfs subvolume delete /snapshot-2014-**-**
in which the snapshot-... is a snapshot I created eariler. But a few hours later I suddenly found that the file system became read-only. I reboot and the message stuck at mounting /dev/sda1 and failed, into an emergency shell, saying something like "no subvolume is find". I tried to mount /dev/sda1 using a rescue usb stick but still failed...
I have been using the same command to create and delete snapshots for several months without problem, but this time... I don't know what was I doing wrong, maybe I mistyped something this time?
So... How could I recovery the filesystem? I've searched for a bit but cannot find any satisfied result.
EDIT: I re-installed the system.
Last edited by Frefreak (2014-09-27 10:39:45)

LoBo3268715 wrote:Just gonna take a stab at what you want to do here but I assume you want to switch to the ATI card correct? using open source drivers? Google around for vgaswitcharoo. It can be a royal PITA but I got it working with my intel integrated card and ATI mobility 5650. Also there is a package in the AUR for this. https://aur.archlinux.org/packages.php?ID=51704
Yes, that's exactly what I'm trying to achieve. Thanks for the advice, I will explore all the possibilities with vga_switcheroo

[SOLVED] Strange Hard Drive Errors - Read Only Filesystem?

Solution: Discard old laptop, buy new laptop
I have an Acer Aspire 5103WLMi. For about 2 months now, Arch has been running smoothly. Until 2 weeks ago.
It all started when I tried to install and configure autofs on Arch x86_64. On the next reboot, all manner of errors were printed to the screen, to the effect that the internal hard drive was only being mounted read-only, rendering the system unusable. I tried to find a solution, but there were no references to read-only anywhere; fstab, grub etc. None that I could find.
I tried reinstalling. However, x86_64 Arch refused to boot properly first time due to the exact same error; and I *know* that I'm configuring everything correctly. I managed (somehow) to coerce i686 Arch to install, and things "work".
Seemingly out of the blue, during normal operation, all running applications will stop, and spit out error after error to the effect of "Cannot Write to Read Only Filesystem!". Sakura won't load (Input/Output error, apparently), and the only way to shut down the laptop is a hard reset (I can't log in as root or use sudo because it wants to write to the filesystem first, which it obviously can't.
Now, I'm going to be giving the insides of this laptop a good cleanout this weekend, and I'm in the process of backing up all of my data, but I was wondering if anyone else has come across a similar form of misbehaviour; or (with a bit of luck) some potential solutions?
This is very peculiar, because there seems to be no reason why the laptop suddenly loses write permissions to the hard drive. Cheers.
Edit: I think I should point out that my /boot partition is Ext2, and / and /home are Ext3
Last edited by aphirst (2013-03-27 14:51:38)

Smartctl gives me the impression it's my Hard Drive:
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1711
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 6194
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 3291
10 Spin_Retry_Count 0x0033 223 100 030 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1218
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 294
193 Load_Cycle_Count 0x0032 088 088 000 Old_age Always - 123904
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 34 (Lifetime Min/Max 15/62)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 17
220 Disk_Shift 0x0002 100 100 000 Old_age Always - 118
222 Loaded_Hours 0x0032 094 094 000 Old_age Always - 2425
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
226 Load-in_Time 0x0026 100 100 000 Old_age Always - 444
240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
Everything being either Old_age or Pre-fail is not encouraging. Additionally, in the output is what I believe to be records of what caused my strange read-only behaviour:
Error 19 occurred at disk power-on lifetime: 3287 hours (136 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
84 51 01 11 18 6a e1 Error: ICRC, ABRT 1 sectors at LBA = 0x016a1811 = 23730193
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 48 c4 17 6a e1 00 04:43:08.023 READ DMA
c8 00 48 14 e3 69 e1 00 04:43:08.022 READ DMA
c8 00 a0 5c e2 69 e1 00 04:43:08.010 READ DMA
c8 00 08 9c e5 69 e1 00 04:43:08.010 READ DMA
c8 00 20 5c e5 69 e1 00 04:43:08.009 READ DMA
Could this truly be referring to my problem, since the 'logs' show that the *exact same* error occurred many times.
Not that this tells me how to fix it...
Well, if anyone knows if there is a solution, I'd love to know. If the only solution is to ditch the Hard Drive, fair enough. Either way: I'm backing up all of my important data ASAP.
Cheers.
Oh, and kclive18, after I noticed that I couldn't get onto my Drive, I reinstalled arch, leaving no trace of /etc/autofs/auto.media.
Additionally, somehow I have now been able to install Arch x86_64, but the problems still occur...

[SOLVED] Root mounted as "Read-only filesystem". mkinitcpio issue?

I am currently in the middle of setting up system encryption with LUKS. I have been making good progress so far, but I do have one remaining issue.
After typing my LUKS password, the Linux kernel starts to complain that root is a read-only filesystem. "Starting NetworkManager... cannot touch file XYZ: Read-only filesystem". When it has finally finished booting, I am dropped into a TTY. I can log in and cat my files, but I cannot write to any files our use any programs that do (like pacman).
I wonder if this is an mkinitcpio issue, but I am not sure. For whatever it's worth, here's my basic setup:
* /dev/sda1: Boot
* /dev/sda2: Swap
* /dev/sda3: Root (LUKS/ext4)
* menu.lst looks like this
* /etc/fstab contains this line:
/dev/mapper/root / ext4 defaults 0 1
* /etc/mkinitcpio.conf contains these lines:
MODULES="ext4"
HOOKS="base udev pata scsi sata encrypt filesystems"
edit: I should note that I did reinstall the kernel after making those edits to mkinitcpio.conf.
Any idea what I'm doing wrong? As always, I really do appreciate the help. Thanks in advance!
Last edited by jalu (2011-04-16 22:14:20)

So it looks like this major problem was caused by a minor mistake. The file /etc/rc.sysinit was not executable. This made it impossible for the kernel to run the script, which in turn made it impossible for the kernel to mount /dev/sda2 (the swap partition) at /dev/mapper/swap. For some unknown reason, this in turn caused /dev/sda2 to be mounted at /, messing everything up.
Anyway, a simple sudo chmod +x /etc/rc.sysinit fixed the problem. Thanks for the help, MadTux!

[SOLVED] vsftpd read only

Similar Messages

Maybe you are looking for