Unable to write anything to HDD
-
- A semi-regular
- Posts: 28
- https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA
- Joined: Sat Apr 20, 2013 6:05 am
Unable to write anything to HDD
After the reset of 06 March, I have been unable to write anything. If I try to run a screen session (IE for irssi) I am presented with the following error message:
mkfifo /var/run/screen/S-Potcat/5059.irssi failed
Anything that requires more than a read fails similarly.
mkfifo /var/run/screen/S-Potcat/5059.irssi failed
Anything that requires more than a read fails similarly.
Re: Unable to write anything to HDD
UPDATE: Some programs (ZNC) can't even read their config files.
Re: Unable to write anything to HDD
Is your partition mounted read-only? What is your dmesg output?
Re: Unable to write anything to HDD
Should I post the entire output of that command? Because there is a lot to it.
Re: Unable to write anything to HDD
Code: Select all
acpiphp: Slot [20] registered
acpiphp: Slot [21] registered
acpiphp: Slot [22] registered
acpiphp: Slot [23] registered
acpiphp: Slot [24] registered
acpiphp: Slot [25] registered
acpiphp: Slot [26] registered
acpiphp: Slot [27] registered
acpiphp: Slot [28] registered
acpiphp: Slot [29] registered
acpiphp: Slot [30] registered
acpiphp: Slot [31] registered
ipmi message handler version 39.2
IPMI System Interface driver.
ipmi_si: Adding default-specified kcs state machine
ipmi_si: Trying default-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
ipmi_si: Interface detection failed
ipmi_si: Adding default-specified smic state machine
ipmi_si: Trying default-specified smic state machine at i/o address 0xca9, slave address 0x0, irq 0
ipmi_si: Interface detection failed
ipmi_si: Adding default-specified bt state machine
ipmi_si: Trying default-specified bt state machine at i/o address 0xe4, slave address 0x0, irq 0
ipmi_si: Interface detection failed
ipmi_si: Unable to find any System Interface(s)
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
ACPI: Power Button [PWRF]
input: Sleep Button as /devices/LNXSYSTM:00/LNXSLPBN:00/input/input1
ACPI: Sleep Button [SLPF]
ACPI: acpi_idle registered with cpuidle
ERST: Table is not found!
GHES: HEST is not enabled!
alloc irq_desc for 28 on node -1
alloc kstat_irqs on node -1
xen-platform-pci 0000:00:03.0: PCI INT A -> GSI 28 (level, low) -> IRQ 28
Grant table initialized
Non-volatile memory driver v1.3
Linux agpgart interface v0.103
crash memory driver: version 1.1
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
brd: module loaded
loop: module loaded
input: Macintosh mouse button emulation as /devices/virtual/input/input2
Fixed MDIO Bus: probed
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
uhci_hcd: USB Universal Host Controller Interface driver
uhci_hcd 0000:00:01.2: PCI INT D -> GSI 23 (level, low) -> IRQ 23
uhci_hcd 0000:00:01.2: setting latency timer to 64
uhci_hcd 0000:00:01.2: UHCI Host Controller
uhci_hcd 0000:00:01.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:01.2: irq 23, io base 0x0000c140
usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: UHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.32-358.2.1.el6.x86_64 uhci_hcd
usb usb1: SerialNumber: 0000:00:01.2
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one day, 114 bytes nvram, hpet irqs
cpuidle: using governor ladder
cpuidle: using governor menu
EFI Variables Facility v0.08 2004-May-17
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
registered taskstats version 1
XENBUS: Device with no driver: device/vbd/768
XENBUS: Device with no driver: device/vbd/5632
XENBUS: Device with no driver: device/vbd/5696
XENBUS: Device with no driver: device/vkbd/0
XENBUS: Device with no driver: device/vif/0
rtc_cmos 00:05: setting system clock to 2015-03-06 16:59:09 UTC (1425661149)
Initalizing network drop monitor service
Freeing unused kernel memory: 1264k freed
Write protecting the kernel read-only data: 10240k
Freeing unused kernel memory: 904k freed
Freeing unused kernel memory: 1676k freed
dracut: dracut-004-303.el6
dracut: rd_NO_LUKS: removing cryptoluks activation
dracut: rd_NO_LVM: removing LVM activation
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.23.6-ioctl (2012-07-25) initialised: dm-devel@redhat.com
udev: starting version 147
dracut: Starting plymouth daemon
dracut: rd_NO_DM: removing DM RAID activation
dracut: rd_NO_MD: removing MD RAID activation
ata_piix 0000:00:01.1: version 2.13
ata_piix 0000:00:01.1: setting latency timer to 64
scsi0 : ata_piix
scsi1 : ata_piix
ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc160 irq 14
ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc168 irq 15
usb 1-2: new full speed USB device number 2 using uhci_hcd
ata2.00: ATAPI: QEMU DVD-ROM, 0.10.2, max UDMA/100
ata2.01: ATAPI: QEMU DVD-ROM, 0.10.2, max UDMA/100
ata2.00: configured for MWDMA2
ata2.01: configured for MWDMA2
scsi 1:0:0:0: CD-ROM QEMU QEMU DVD-ROM 0.10 PQ: 0 ANSI: 5
scsi 1:0:1:0: CD-ROM QEMU QEMU DVD-ROM 0.10 PQ: 0 ANSI: 5
xlblk_init: register_blkdev major: 202
alloc irq_desc for 934 on node 0
alloc kstat_irqs on node 0
vbd vbd-5632: 19 xenbus_dev_probe on device/vbd/5632
vbd vbd-5632: failed to write error node for device/vbd/5632 (19 xenbus_dev_probe on device/vbd/5 632)
vbd vbd-5696: 19 xenbus_dev_probe on device/vbd/5696
vbd vbd-5696: failed to write error node for device/vbd/5696 (19 xenbus_dev_probe on device/vbd/5 696)
blkfront: xvda: barriers disabled
xvda: xvda1 xvda2
input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input4
sr0: scsi3-mmc drive: 4x/4x xa/form2 tray
Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0
sr1: scsi3-mmc drive: 4x/4x xa/form2 tray
sr 1:0:1:0: Attached scsi CD-ROM sr1
Refined TSC clocksource calibration: 2899.998 MHz.
Switching to clocksource tsc
usb 1-2: New USB device found, idVendor=0627, idProduct=0001
usb 1-2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb 1-2: Product: QEMU USB Tablet
usb 1-2: Manufacturer: QEMU 0.10.2
usb 1-2: SerialNumber: 1
usb 1-2: configuration #1 chosen from 1 choice
input: QEMU 0.10.2 QEMU USB Tablet as /devices/pci0000:00/0000:00:01.2/usb1/1-2/1-2:1.0/input/inp ut5
generic-usb 0003:0627:0001.0001: input,hidraw0: USB HID v0.01 Pointer [QEMU 0.10.2 QEMU USB Table t] on usb-0000:00:01.2-2/input0
EXT4-fs (xvda2): mounted filesystem with ordered data mode. Opts:
dracut: Mounted root filesystem /dev/xvda2
SELinux: Disabled at runtime.
SELinux: Unregistering netfilter hooks
type=1404 audit(1425661151.443:2): selinux=0 auid=4294967295 ses=4294967295
dracut:
dracut: Switching root
readahead-collector: starting
udev: starting version 147
sr 1:0:0:0: Attached scsi generic sg0 type 5
sr 1:0:1:0: Attached scsi generic sg1 type 5
piix4_smbus 0000:00:01.3: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xadd r
Initialising Xen virtual ethernet driver.
alloc irq_desc for 933 on node 0
alloc kstat_irqs on node 0
microcode: CPU0 sig=0x206d7, pf=0x1, revision=0x70b
platform microcode: firmware: requesting intel-ucode/06-2d-07
microcode: CPU1 sig=0x206d7, pf=0x1, revision=0x70b
platform microcode: firmware: requesting intel-ucode/06-2d-07
microcode: CPU2 sig=0x206d7, pf=0x1, revision=0x70b
platform microcode: firmware: requesting intel-ucode/06-2d-07
Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
microcode: CPU0 update to revision 0x70d failed
microcode: CPU1 update to revision 0x70d failed
microcode: CPU2 update to revision 0x70d failed
microcode: CPU0 update to revision 0x70d failed
microcode: CPU1 update to revision 0x70d failed
microcode: CPU2 update to revision 0x70d failed
microcode: CPU0 update to revision 0x70d failed
microcode: CPU1 update to revision 0x70d failed
microcode: CPU2 update to revision 0x70d failed
microcode: CPU0 update to revision 0x70d failed
microcode: CPU1 update to revision 0x70d failed
microcode: CPU2 update to revision 0x70d failed
microcode: CPU0 update to revision 0x70d failed
microcode: CPU1 update to revision 0x70d failed
microcode: CPU2 update to revision 0x70d failed
microcode: CPU0 update to revision 0x70d failed
microcode: CPU1 update to revision 0x70d failed
microcode: CPU2 update to revision 0x70d failed
parport_pc 00:0b: reported by Plug and Play ACPI
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
ppdev: user-space parallel port driver
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ip6_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
type=1305 audit(1425679161.424:6664): audit_pid=0 old=344 auid=4294967295 ses=4294967295 res=1
type=1300 audit(1425679161.425:6665): arch=c000003e syscall=59 success=yes exit=0 a0=22b2c60 a1=2 2b52c0 a2=22b1810 a3=18 items=2 ppid=1028 pid=1032 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsui d=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="plymouth" exe="/bin/plymouth" key=(null )
type=1309 audit(1425679161.425:6665): argc=2 a0="/bin/plymouth" a1="--details"
type=1307 audit(1425679161.425:6665): cwd="/"
type=1302 audit(1425679161.425:6665): item=0 name="/bin/plymouth" inode=429 dev=ca:02 mode=010075 5 ouid=0 ogid=0 rdev=00:00
type=1302 audit(1425679161.425:6665): item=1 name=(null) inode=164791 dev=ca:02 mode=0100755 ouid =0 ogid=0 rdev=00:00
type=1300 audit(1425679161.425:6666): arch=c000003e syscall=2 success=yes exit=3 a0=3fdde1b201 a1 =0 a2=1 a3=0 items=1 ppid=1028 pid=1032 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="plymouth" exe="/bin/plymouth" key=(null)
type=1307 audit(1425679161.425:6666): cwd="/"
type=1302 audit(1425679161.425:6666): item=0 name="/etc/ld.so.cache" inode=137159 dev=ca:02 mode= 0100644 ouid=0 ogid=0 rdev=00:00
type=1300 audit(1425679161.425:6667): arch=c000003e syscall=2 success=yes exit=3 a0=7fed18e05927 a1=0 a2=0 a3=646c2d6362696c67 items=1 ppid=1028 pid=1032 auid=4294967295 uid=0 gid=0 euid=0 suid= 0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="plymouth" exe="/bin/plymouth" key =(null)
eth0: no IPv6 routers present
__ratelimit: 1496 callbacks suppressed
type=1305 audit(1425679452.242:6896): auid=4294967295 ses=4294967295 op="remove rule" key=(null) list=4 res=1
type=1305 audit(1425679452.242:6897): audit_enabled=0 old=1 auid=4294967295 ses=4294967295 res=1
readahead-collector: sorting
readahead-collector: finished
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Re: Unable to write anything to HDD
The only thing that really sticks out for me there is that your OS must be a bit old because it doesn't understand all of the Xen devices (but gets some of them).
What is the output to "mount" and "df"?
What is the output to "mount" and "df"?
Re: Unable to write anything to HDD
Mount:
DF:
Code: Select all
/sys on /chroot-starbound/sys type sysfs (rw,noatime)
mount: warning: /etc/mtab is not writable (e.g. read-only filesystem).
It's possible that information reported by mount(8) is not
up to date. For actual information about system mount points
check the /proc/mounts file.
Code: Select all
Filesystem 1K-blocks Used Available Use% Mounted on
/sys 309486892 48764360 245004440 17% /chroot-starbound/sys
Re: Unable to write anything to HDD
It looks like you're running that inside a chroot'd environment that isn't set up quite right. You'll need to back out of the chroot to troubleshoot this further.
Re: Unable to write anything to HDD
I'm not quite sure how to do that. This chroot is all consuming.
Re: Unable to write anything to HDD
I'm not sure why you'd be inside a chroot in the first place. If you didn't set that up, you should talk to the person who did for guidance on this.