conf and it should be owned root (you can't create anything there non-root anyway).
EXTERNAL HARD DRIVE READ ONLY UPDATE
But it seems like there would be more information or an update about it by now?īased on this bug report, you may be able to work around the problem for your Maxtor drive (it is referred to specifically in post #34 of that report) by adding a file to /etc/modprobe.d containing: options usb-storage quirks=0d49:7010:uw Is this the drive? Is this the Raspberry Pi 2's Raspbian OS? I have seen postings at the link below that it might be a bug.
EXTERNAL HARD DRIVE READ ONLY MAC
As odd is it seems, if I connect it to the Mac and use Disk Utility I can format and write to the drive as Mac format of FAT32 and on the Dell server/CentOS without a problem. EXT4-fs (sda1): Remounting filesystem **read-only** EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal blk_update_request: critical target error, dev sda, sector 243533848 EXT4-fs (sda1): mounted filesystem with ordered data mode. blk_update_request: critical target error, dev sda, sector 0 Sometimes after it is mounting it is "rw" but only for a short period of time, like a minute. I can cd to this drive and try to write to it, but it gives an error that it is read-only. dev/sda1 /mnt ext4 **ro**,relatime,data=ordered 0 0 mount -t ext4 /dev/sda1 df -hįilesystem Size Used Avail Use% Mounted on Let's mount it, see what the deal is now. I guess that looks OK, I don't know if the number of Superblock backups matters or not? Writing superblocks and filesystem accounting information: done
So I will proceed with doing a mkfs, maybe that will fix it? Just wishing thinking. I don't know what else to do at this point. When I connect the drive to a Dell server/CentOS and do this, I don't get errors about closing the file. If I do the above to a USB thumb drive, I don't get any of the bolded errors above. Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite) **Disk /dev/sda doesn't contain a valid partition fdisk /dev/sdaĭevice contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabelīuilding a new DOS disklabel with disk identifier 0x8b811c4f.Ĭhanges will remain in memory only, until you decide to write them.Īfter that, of course, the previous content won't be recoverable. I/O size (minimum/optimal): 512 bytes / 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes Now let's see what fdisk has to say about the drive: fdisk -lĭisk /dev/mmcblk0: 7948 MB, 7948206080 bytesĤ heads, 16 sectors/track, 242560 cylinders, total 15523840 sectors sd 1:0:0:0: Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 1:0:0:0: Attached scsi generic sg0 type 0 scsi 1:0:0:0: Direct-Access Maxtor OneTouch 0200 PQ: 0 ANSI: 0 CCS input: Maxtor OneTouch as /devices/platform/soc/b/usb1/1-1/1-1.2/input/input1 ums-onetouch 1-1.2:1.0: USB Mass Storage device detected usb 1-1.2: New USB device strings: Mfr=1, Product=3, SerialNumber=2 usb 1-1.2: New USB device found, idVendor=0d49, idProduct=7000 I powered it up and so far the dmesg output looks good: usb 1-1.2: new high-speed USB device number 5 using dwc_otg I have connected the drive to Dell server running CentOS 6 and don't have any problem with it there, but I do on the Raspberry Pi 2. My goal is to format the drive to use it as ext4, but I'm having troubles along the way with error messages. Linux raspberrypi 4.0.6-v7+ #799 SMP PREEMPT Fri Jun 26 15:50: armv7l GNU/Linux It has the latest updates, upgrades and firmware. I have an old Maxtor USB 250GB external drive I'm trying to use on the Raspberry Pi 2 running Raspbian.
0 kommentar(er)
